CVE-2018-2361
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 · uneditedIn SAP Solution Manager 7.20, the role SAP_BPO_CONFIG gives the Business Process Operations (BPO) configuration user more authorization than required for configuring the BPO tools.
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 confidenceThe SAP_BPO_CONFIG role in SAP Solution Manager 7.20 grants excessive authorization privileges to Business Process Operations configuration users beyond what is required for their intended job functions, creating a privilege escalation risk where users may access sensitive system capabilities they should not have.
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= 7.20CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Confirm SAP Solution Manager versionUse transaction SM37 or execute 'SAPCAR -xvf <kernel_archive>' to identify the installed Solution Manager version, or check via SAP MII version informationAffected if Version is exactly 7.20
-
Locate the SAP_BPO_CONFIG roleUse transaction PFCG or run report RSUSR008_009_NEW to list all roles in the system and search for SAP_BPO_CONFIGAffected if The SAP_BPO_CONFIG role exists in the system
-
Examine authorization objects in SAP_BPO_CONFIG roleUse transaction PFCG, enter SAP_BPO_CONFIG as the role, and view the Authorizations tab to list all assigned authorization objects and valuesAffected if Role contains authorization objects beyond standard BPO configuration needs, such as SAP_ALL, SAP_NEW, or sensitive system administration authorizations
-
Compare assigned privileges against least-privilege requirementsReview the authorization objects from step 3 and identify any that grant access to transaction codes SM37, SE37, SA38, or other system administration/technical functions not required for Business Process Operations configurationAffected if The role includes privileged transaction codes or authorization objects not essential for BPO configuration tasks
You are affected if running SAP Solution Manager version 7.20 with the SAP_BPO_CONFIG role containing excessive authorization privileges beyond standard BPO configuration needs
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 dataReview and restrict the SAP_BPO_CONFIG role to enforce least-privilege principles by removing unnecessary authorizations while preserving required BPO configuration capabilities.
- 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-2018-2361 — 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-2018-2361 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