CVE-2023-27500
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 · uneditedAn attacker with non-administrative authorizations can exploit a directory traversal flaw in program SAPRSBRO to over-write system files. In this attack, no data can be read but potentially critical OS files can be over-written making the system unavailable.
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 · high confidenceA directory traversal vulnerability in SAP program RSBRO allows authenticated users with non-administrative privileges to overwrite critical OS files on the server. The attack permits write-only access to system files, enabling denial of service by corrupting or overwriting essential operating system files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 700= 701= 702= 731= 740= 750= 751= 752= 753= 754= 755= 756CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
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.
-
Identify if RSBRO program is deployed in your SAP systemAccess SAP transaction code SE38 or SE80 and search for program RSBRO, or use transaction SAAB to check if RSBRO is registered in the system. Alternatively, query table TRDIR or TADIR for object name RSBRO.Affected if RSBRO program exists in your system and is accessible to authenticated users
-
Verify the SAP NetWeaver AS ABAP versionExecute transaction SM51 or check system information via transaction SYSID. You can also use ABAP report RSVERSION or check system version table SAPVERSIONS. Compare your version against the affected list: 700, 701, 702, 731, 740, 750, 751, 752, 753, 754, 755, 756.Affected if Your installed NetWeaver AS ABAP version matches one of the listed affected versions
-
Check which users have access to RSBRO transaction/programUse transaction SUIM to query for users assigned to RSBRO-related roles. Check profile S_RS_BRO (if it exists) or examine authorization objects S_PROGRAM or S_TRANSPRT for RSBRO usage permissions.Affected if Non-administrative users have authorization to execute RSBRO program
You are affected if RSBRO program is present in your SAP system, your NetWeaver ABAP version is one of the listed affected versions (700-756), and non-administrative users have access to execute the RSBRO program.
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 vendor-supplied SAP security patches for RSBRO program and implement input validation controls to sanitize file path parameters before processing.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27500 — 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-2023-27500 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