SAP SQL Anywhere: Stack-based Buffer Overflow
CVE-2022-35299 is a critical-severity stack-based buffer overflow vulnerability in SAP SQL Anywhere from SAP, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected SAP SQL Anywhere versions: 17.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.23% chance of exploitation within 30 days, higher than 70% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of SAP SQL Anywhere you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on launchpad.support.sap.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| SAP | SAP SQL Anywhere | 17.0 | Not stated |
| SAP | SAP IQ | 16.1 | Not stated |
| SAP | SQL Anywhere | 17.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
SAP SQL Anywhere - version 17.0, and SAP IQ - version 16.1, allows an attacker to leverage logical errors in memory management to cause a memory corruption, such as Stack-based buffer overflow.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Stack-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the stack.
How developers prevent this class of flaw
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Implement and perform bounds checking on input.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- launchpad.support.sap.com/#/notes/3232021Permissions Required
- sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.htmlNot Applicable
Other vulnerabilities in SAP SQL Anywhere
- 7.1 High severity
Recent Stack-based Buffer Overflow vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 8.1 High severity
- 7.8 High severity
- 7.5 High severity
Spotted an error? Tell us.