# CVE-2025-30012: Multiple vulnerabilities in SAP Supplier Relationship Management (Live Auction Cockpit)

> Unauthenticated attackers can execute arbitrary OS commands as SAP Administrator via malicious deserialization in the Live Auction Cockpit.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** 13 May 2025
- **Updated:** 24 Jul 2025
- **Also known as:** GHSA-3xfw-592p-fx76

## What is CVE-2025-30012?

CVE-2025-30012 is a critical unsafe deserialization vulnerability in SAP_SE SAP Supplier Relationship Management (Live Auction Cockpit), published on 13 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Live Auction Cockpit in SAP Supplier Relationship Management (SRM) uses a deprecated java applet component, which allows an unauthenticated attacker to send malicious payload request in a specific encoding format. The servlet will then decode this malicious request which will result in deserialization of data in the application leading to execution of arbitrary OS command on target as SAP Administrator. This vulnerability has High impact on confidentiality, integrity, and availability of the application.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-30012?

It affects 1 product.


Products: Sap Supplier Relationship Management.

## How do I fix CVE-2025-30012?

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

## Is CVE-2025-30012 being exploited?

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

## Other vulnerabilities in SAP_SE SAP Supplier Relationship Management (Live Auction Cockpit)

- [CVE-2025-30018](https://insights.sbomify.com/CVE-2025-30018/): Multiple vulnerabilities in SAP Supplier Relationship Management (Live Auction Cockpit) (high 8.6)
- [CVE-2025-42920](https://insights.sbomify.com/CVE-2025-42920/): Cross-Site Scripting (XSS) vulnerability in SAP Supplier Relationship Management (medium 6.1)
- [CVE-2025-30009](https://insights.sbomify.com/CVE-2025-30009/): Multiple vulnerabilities in SAP Supplier Relationship Management (Live Auction Cockpit) (medium 6.1)
- [CVE-2025-30010](https://insights.sbomify.com/CVE-2025-30010/): Multiple vulnerabilities in SAP Supplier Relationship Management (Live Auction Cockpit) (medium 6.1)
- [CVE-2019-0361](https://insights.sbomify.com/CVE-2019-0361/): Cross-site scripting in SAP Supplier Relationship Management (Master Data Management Catalog) (SRM MDM CAT) (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30012 and fix it if it is affected.

What it is: CVE-2025-30012 is a critical unsafe deserialization vulnerability in SAP_SE SAP Supplier Relationship Management (Live Auction Cockpit), published on 13 May 2025. 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-2025-30012 in the wild and no public exploit code.

Affected product: SAP_SE SAP Supplier Relationship Management (Live Auction Cockpit). 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-2025-30012/ (Markdown: https://insights.sbomify.com/CVE-2025-30012/index.md)
```

## Sources

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

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