CVE-2025-43001
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSAPCAR allows an attacker logged in with high privileges to override the permissions of the current and parent directories of the user or process extracting the archive, leading to privilege escalation. On successful exploitation, an attacker could modify the critical files by tampering with signed archives without breaking the signature, but it has a low impact on the confidentiality and availability of the system.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSAPCAR archive extraction utility allows a high-privileged attacker to override permissions of the current and parent directories during extraction, enabling privilege escalation. The vulnerability permits tampering with signed archives without invalidating the signature, allowing modification of critical files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate SAPCAR executable on the systemSearch for 'SAPCAR' executable in common SAP installation paths (e.g., /usr/sap/hostctrl/exe, /sapmnt/<SID>/exe, C:\Program Files\sap\, or C:\usr\sap\) and system PATH directories using 'which SAPCAR' (Unix) or 'where SAPCAR' (Windows).Affected if SAPCAR executable is found on the system at any location.
-
Determine installed SAPCAR versionRun 'SAPCAR -version' or 'SAPCAR -v' from the located executable path and capture the version string in the output.Affected if The displayed version is not yet patched to include the CVE-2025-43001 fix (compare against vendor advisory version when released).
-
Identify recent extraction operationsReview system audit logs, SAP security logs, and extraction history logs for commands containing 'SAPCAR -xvf' or 'SAPCAR -extract' run within the last 90 days.Affected if Extraction operations exist in logs, particularly to directories outside standard SAP installation paths.
-
Check extraction target directory permissionsInspect permissions on directories used for SAPCAR extraction (typically under /sapmnt, /usr/sap, or custom extraction folders) using 'ls -ld <directory>' or file system audit reports.Affected if Extraction target directories are writable by the SAPCAR process user or have permission modifications logged.
A system is affected if SAPCAR is installed and the installed version predates the vendor patch for CVE-2025-43001, regardless of whether extraction operations have occurred.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply SAP security patches for CVE-2025-43001 when available. Restrict high-privilege SAPCAR usage and monitor extraction operations to directories outside expected paths.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-43001 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data