CVE-2024-21079
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 · uneditedVulnerability in the Oracle Marketing product of Oracle E-Business Suite (component: Campaign LOV). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Marketing. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Marketing accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
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 confidenceInformation disclosure vulnerability in the Campaign List of Values (LOV) component of Oracle Marketing in Oracle E-Business Suite versions 12.2.3-12.2.13. Unauthenticated attackers with network access via HTTP can exploit this to gain unauthorized access to sensitive data in the Oracle Marketing module.
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>= 12.2.3, <= 12.2.13CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Verify Oracle E-Business Suite versionQuery the Oracle Applications version using SQL: SELECT release_name FROM apps.fnd_product_groups; or check the about page at $OA_HTML/about.html. Compare the version number against the affected range 12.2.3 through 12.2.13.Affected if The installed version falls within 12.2.3 to 12.2.13 inclusive.
-
Confirm Oracle Marketing module is installedQuery the Oracle Applications tables: SELECT application_name, application_id FROM apps.fnd_application_vl WHERE application_name LIKE '%Marketing%'; or check via Oracle Applications Manager (OAM).Affected if The Oracle Marketing application module is present in the E-Business Suite environment.
-
Check if Campaign List of Values (LOV) is accessibleLog into Oracle E-Business Suite and navigate to the Marketing module. Access the Campaign component and verify the List of Values feature is available. Alternatively, check if the URL path /oa_html/ (or equivalent) is accessible for the Marketing module.Affected if The Campaign LOV component is enabled and accessible within the Marketing module.
-
Assess network exposure of HTTP interfacesReview web server configuration and determine if Oracle E-Business Suite HTTP services are exposed to untrusted networks. Check the Oracle HTTP Server (OHS) configuration and firewall rules for external-facing endpoints.Affected if The HTTP interface for Oracle E-Business Suite is accessible from untrusted network segments without authentication restrictions.
A user is affected if their Oracle E-Business Suite version is 12.2.3-12.2.13, the Marketing module is installed, and the HTTP interface is network-accessible to unauthenticated attackers.
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 Oracle's latest Critical Patch Update (CPU) for Oracle E-Business Suite. Review Oracle Support Document for the specific patch targeting this vulnerability and ensure the Marketing module is included in the testing scope after deployment.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21079 — 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-21079 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