# CVE-2024-33008: Memory Corruption vulnerability in SAP Replication Server

> An attacker can crash the SAP Replication Server via memory corruption triggered by gateway commands, impacting system availability.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2024
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-qfqw-rh34-r78m

## What is CVE-2024-33008?

CVE-2024-33008 is a medium-severity memory corruption vulnerability in SAP_SE SAP Replication Server, published on 14 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SAP Replication Server allows an attacker to use gateway for executing some commands to RSSD. This could result in crashing the Replication Server due to memory corruption with high impact on Availability of the system.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-33008?


## How do I fix CVE-2024-33008?

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

## Is CVE-2024-33008 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33008 and fix it if it is affected.

What it is: CVE-2024-33008 is a medium-severity memory corruption vulnerability in SAP_SE SAP Replication Server, published on 14 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33008 in the wild and no public exploit code.

Affected product: SAP_SE SAP Replication Server. 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-2024-33008/ (Markdown: https://insights.sbomify.com/CVE-2024-33008/index.md)
```

## Sources

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

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