Service restart via oversized debug integer
Published Jun 26, 2024 · Updated Nov 5, 2024
Buffer overflow in SAS Broker 9.2 build 1495 allows remote authenticated users to trigger a restart through the _debug parameter. The debug handler processes an oversized integer without a safe bounds check, causing integer overflow and an error page that exposes the software version and build number. Low-privilege network access is required; the reported consequences are an unexpected application restart and disclosure of version metadata.
Summary
What happened
Buffer overflow in SAS Broker 9.2 build 1495 allows remote authenticated users to trigger a restart through the _debug parameter. The debug handler processes an oversized integer without a safe bounds check, causing integer overflow and an error page that exposes the software version and build number. Low-privilege network access is required; the reported consequences are an unexpected application restart and disclosure of version metadata.
The record
- CVE
- CVE-2024-37571
- Published
- Jun 26, 2024
- Updated
- Nov 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1190, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2024CVE publishedPublication date reported by the CVE source.
- Nov 5, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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