CVE-2024-41737
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 CRM ABAP (Insights Management) allows an authenticated attacker to enumerate HTTP endpoints in the internal network by specially crafting HTTP requests. On successful exploitation this can result in information disclosure. It has no impact on integrity and availability 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 CRM ABAP (Insights Management) contains a vulnerability allowing authenticated attackers to enumerate HTTP endpoints in the internal network through specially crafted HTTP requests, resulting in information disclosure but with no impact on integrity or availability.
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= bbpcrm_700= bbpcrm_701= bbpcrm_702= bbpcrm_712= bbpcrm_713= bbpcrm_714CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 CRM ABAP Insights Management componentUse SAP transaction code SE11 or SE84 to search for objects related to 'BBPCRM' and 'INSIGHTS MANAGEMENT' in your SAP system. Confirm the Insights Management component is installed.Affected if The Insights Management component (BBPCRM) is present in the system
-
Check installed BBPCRM versionUse SAP transaction code SM37 or execute ABAP report to query the BBPCRM component version. Compare your installed version against the affected list: bbpcrm_700, bbpcrm_701, bbpcrm_702, bbpcrm_712, bbpcrm_713, bbpcrm_714.Affected if The installed BBPCRM version matches one of the listed versions exactly (700, 701, 702, 712, 713, or 714)
-
Verify ICF HTTP service nodes for Insights ManagementUse SAP transaction code SICF to inspect the ICF tree for paths related to 'insights' or 'bbpcrm' HTTP services. Check if these service nodes are active and exposed.Affected if ICF HTTP service nodes for Insights Management exist and are currently active in the system
-
Confirm authentication on Insights Management HTTP endpointsReview ICF service configuration (via SICF) for the Insights Management related paths and verify that proper authentication methods (e.g., SAML, form-based, or certificate) are enforced on these endpoints.Affected if The HTTP endpoints lack proper authentication configuration or allow anonymous access despite the CVE requiring authenticated access
A user is affected if the system runs SAP CRM ABAP with Insights Management (BBPCRM) at version 700, 701, 702, 712, 713, or 714 and the ICF HTTP service nodes for Insights Management are active without adequate authentication controls.
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 dataImplement proper authentication and authorization checks on all HTTP endpoints, apply network segmentation to restrict internal endpoint access, and consider rate limiting to prevent enumeration.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41737 — 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-41737 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