CVE-2022-39801
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 · uneditedSAP GRC Access control Emergency Access Management allows an authenticated attacker to access a Firefighter session even after it is closed in Firefighter Logon Pad. This attack can be launched only within the firewall. On successful exploitation the attacker can gain access to admin session and completely compromise the application.
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 confidenceIn SAP GRC Access Control's Emergency Access Management feature, a session validation flaw in the Firefighter Logon Pad allows an authenticated attacker to access a Firefighter session even after it has been explicitly closed. Since Firefighter sessions provide elevated administrative privileges, successful exploitation grants the attacker full admin access to the application.
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= 12CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Identify SAP Access Control installation and versionQuery the SAP system for installed software components related to GRC Access Control. Use transaction code SAPMSSM or check via SAP Solution Manager. Look for component name 'GRC Access Control' and note the version number.Affected if The installed version is SAP Access Control version 12 (or 12.x series).
-
Verify Emergency Access Management is enabledIn the SAP system, navigate to the Firefighter Logon Pad configuration area (typically via GRC transaction codes such as GRACFIREFIGHTER or SPRO settings). Check if the Emergency Access Management feature is active.Affected if Emergency Access Management feature is enabled and configured in the SAP GRC system.
-
Check for active or recently closed Firefighter sessionsQuery the Firefighter session logs or audit tables (such as GRAC* tables in SAP). Use transaction code GRACMONITOR or review session history to identify any Firefighter sessions that were active or closed around the time of potential exploitation.Affected if There are active Firefighter sessions or sessions that were recently closed but may still have valid session tokens.
-
Inspect session validation configurationReview the Firefighter Logon Pad configuration settings in transaction code SPRO under SAP GRC Access Control. Look for session management parameters that control how sessions are terminated and validated after logout.Affected if Session validation is set to allow continued access after explicit session closure, or configuration shows permissive session handling.
-
Review Firefighter audit and access logsExamine Firefighter audit logs (transaction code GRAC_AUDIT_LOG or similar) for any unauthorized access patterns or sessions that persisted beyond their intended closure time.Affected if Audit logs show sessions accessing the system after their recorded closure time or unexpected session continuations.
If SAP Access Control version 12 is running with the Emergency Access Management/Firefighter feature enabled, and there is evidence of sessions persisting after closure or unusual session activity, the environment is likely affected by CVE-2022-39801.
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 the relevant SAP security patch for CVE-2022-39801 and rotate any credentials or sessions that may have been exposed. Additionally, enforce stricter network segmentation even for internal firewall boundaries.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39801 — 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-2022-39801 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