Unauthenticated memory corruption via memory management errors
Published Oct 11, 2022 · Updated Aug 3, 2024
Stack-based buffer overflow in SAP SQL Anywhere 17.0 and SAP IQ 16.1 allows remote attackers to corrupt server memory over the network. SAP attributes the flaw to logical errors in memory management but does not disclose the affected function, processed input, or erroneous operation. Exploitation requires no authentication but does require the database server to run with a debugging option enabled; successful attacks can inject code into the server process.
Summary
What happened
Stack-based buffer overflow in SAP SQL Anywhere 17.0 and SAP IQ 16.1 allows remote attackers to corrupt server memory over the network. SAP attributes the flaw to logical errors in memory management but does not disclose the affected function, processed input, or erroneous operation. Exploitation requires no authentication but does require the database server to run with a debugging option enabled; successful attacks can inject code into the server process.
The record
- CVE
- CVE-2022-35299
- Published
- Oct 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- SAP SE
- Product
- SAP SQL Anywhere Server
- Classifications
- CWE-121, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17.0
What conditions does exploitation require?
What is affected?
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