Process abort via unbounded parser recursion
Published Jun 27, 2022 · Updated Apr 23, 2025
Uncontrolled recursion in Pomsky before 0.4.3 allows attackers to crash a hosting process by supplying deeply nested expressions. The parser recursively descends through nested constructs without a depth limit, exhausting the thread stack and aborting the process. Exposure requires a service to pass untrusted expressions into the parser, and the demonstrated consequence is service interruption through a process crash.
Summary
What happened
Uncontrolled recursion in Pomsky before 0.4.3 allows attackers to crash a hosting process by supplying deeply nested expressions. The parser recursively descends through nested constructs without a depth limit, exhausting the thread stack and aborting the process. Exposure requires a service to pass untrusted expressions into the parser, and the demonstrated consequence is service interruption through a process crash.
The record
- CVE
- CVE-2022-31099
- Published
- Jun 27, 2022
- Updated
- Apr 23, 2025
- Vendor
- Pomsky
- Product
- Pomsky
- Classifications
- CWE-674, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 27, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.4.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo