CVE-2024-21734
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 Marketing (Contacts App) - version 160, allows an attacker with low privileges to trick a user to open malicious page which could lead to a very convincing phishing attack with low impact on confidentiality and integrity 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 Marketing Contacts App version 160 contains an open redirect vulnerability where an authenticated attacker with low privileges can craft malicious URLs that trick users into visiting external phishing pages. The vulnerability allows manipulation of redirect parameters to bypass Same-Origin policy expectations, enabling credential harvesting through convincing phishing attacks with low confidentiality and integrity 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= 160CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 if SAP Marketing is deployedCheck your SAP system landscape for systems running SAP Marketing component. Query SAP transaction SM37 or use SAINT to list installed software components.Affected if SAP Marketing component is not present in the system.
-
Determine SAP Marketing Contacts App versionUse SAP transaction SPAM or SAINT to view installed software components and their versions. Look for component 'SAP_MKT' or 'SAP Marketing' and note the version number.Affected if The installed version is exactly 160.
-
Verify Contacts App is accessibleCheck if the SAP Marketing Contacts App (transaction code often related to Marketing, typically accessed via Fiori Launchpad or transaction code like 'MDG_MKT_CONTACT' or similar Marketing transactions). Confirm the app is active in the system.Affected if The Contacts App is not deployed or accessible in the environment.
-
Inspect redirect parameter handlingReview the Contacts App configuration and any custom ICF (Internet Communication Framework) services related to redirect functionality. Use transaction SICF to check handler classes for redirect logic.Affected if The system shows redirect handlers that accept external URLs without strict domain validation.
-
Check authentication and authorizationReview if low-privileged users (with limited roles) can access the Contacts App and trigger redirect functionality. Use transaction SUIM to check role assignments.Affected if Users with low privilege roles (e.g., read-only or limited Marketing roles) can access the Contacts App redirect features.
A system is affected if it has SAP Marketing Contacts App version 160 deployed with the Contacts App accessible to low-privileged users and no validation on redirect URL parameters.
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 strict validation and whitelisting of redirect URLs in the Contacts App, ensuring all redirect targets are verified against an approved domain list before redirection occurs. Apply canonicalization checks to prevent URL manipulation via encoding or domain spoofing.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21734 — 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-21734 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