# CVE-2022-35299: Memory corruption in SAP IQ

> Attackers can exploit memory management errors in SAP SQL Anywhere and SAP IQ to cause stack-based buffer overflows, potentially leading to code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cvhc-gp9g-22mj

## What is CVE-2022-35299?

CVE-2022-35299 is a critical memory corruption vulnerability in SAP IQ, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2022-35299?

It affects 2 products.


Products: Sap Sap Iq, Sap Sql Anywhere.

## How do I fix CVE-2022-35299?

No fix has been published for CVE-2022-35299 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-35299 being exploited?

There is no known exploitation of CVE-2022-35299 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35299 and fix it if it is affected.

What it is: CVE-2022-35299 is a critical memory corruption vulnerability in SAP IQ, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-35299 in the wild and no public exploit code.

Affected product: SAP IQ. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-35299/ (Markdown: https://insights.sbomify.com/CVE-2022-35299/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-35299
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-35299
- OSV: https://osv.dev/vulnerability/CVE-2022-35299

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-35299/
Summaries are generated and may contain mistakes; the official description above is the record.