CVE-2024-28164
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 NetWeaver AS Java (CAF - Guided Procedures) allows an unauthenticated user to access non-sensitive information about the server which would otherwise be restricted causing low impact on confidentiality of 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 · moderate confidenceSAP NetWeaver AS Java CAF (Guided Procedures) contains an information disclosure vulnerability where an unauthenticated user can access non-sensitive server information that should otherwise be restricted, resulting in low confidentiality impact.
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= gp-core_7.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 NetWeaver AS Java installationLocate the SAP NetWeaver Application Server Java installation directory or check running Java processes for SAP NetWeaver componentsAffected if SAP NetWeaver AS Java is not installed on the system
-
Check gp-core component versionUse SAP NWA (NetWeaver Administrator) or check the gp-core component version in the SAP system information. Compare your installed gp-core version against the affected version 7.5Affected if The gp-core component version is 7.5
-
Verify CAF Guided Procedures is enabledCheck the SAP CAF (Composite Application Framework) Guided Procedures configuration in NWA or through the SAP Management Console to determine if this component is activeAffected if CAF Guided Procedures component is enabled and running
-
Test unauthenticated information accessAttempt to access the Guided Procedures endpoint without authentication using a browser or HTTP tool to see if server information is returnedAffected if Non-sensitive server information is accessible to unauthenticated users through the Guided Procedures interface
A user is affected if SAP NetWeaver AS Java with gp-core version 7.5 is installed and the CAF Guided Procedures component is enabled, allowing unauthenticated access to restricted server information.
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.
dbcve · scopedApply the relevant SAP security patch for CVE-2024-28164 and verify that the Guided Procedures component properly restricts access to sensitive server information.
- 1. Access the SAP Support Portal at support.sap.com and search for Security Note related to CVE-2024-28164
- 2. Apply the relevant SAP Security Patch/Security Note for this vulnerability
- 3. Restart the SAP NetWeaver AS Java application server as required by the patch
- 4. Verify the patch has been applied successfully by checking the system information is no longer accessible to unauthenticated users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28164 — 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-2024-28164 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