CVE-2024-21280
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 Service Contracts product of Oracle E-Business Suite (component: Authoring). Supported versions that are affected are 12.2.5-12.2.13. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Service Contracts. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Service Contracts accessible data as well as unauthorized access to critical data or complete access to all Oracle Service Contracts accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 confidenceOracle Service Contracts Authoring component contains a vulnerability exploitable via HTTP by low privileged attackers, allowing unauthorized creation, deletion, modification, or access to critical data within the Service Contracts 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.5, <= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Oracle Service Contracts installationQuery the Oracle Applications database for installed modules: SELECT product_version FROM fnd_product_installations WHERE product LIKE '%Service Contracts%'; Or check the Oracle E-Business Suite version banner.Affected if Oracle Service Contracts is not installed - not affected by this CVE.
-
Verify the Service Contracts versionRun: SELECT version FROM fnd_application WHERE application_id = (SELECT application_id FROM fnd_application WHERE application_short_name = 'OKS'); Or check the Oracle E-Business Suite patch level.Affected if Version is greater than or equal to 12.2.5 and less than or equal to 12.2.13 - falls within the affected range.
-
Confirm Authoring component is accessibleCheck if the Service Contracts Authoring responsibility is assigned to any users: SELECT DISTINCT fr.responsibility_name FROM fnd_responsibility fr JOIN fnd_resp_application fra ON fr.responsibility_id = fra.responsibility_id WHERE fr.responsibility_name LIKE '%Authoring%'; Also verify the responsibility is enabled in the system.Affected if The Authoring responsibility is present and enabled - the vulnerable component is accessible.
-
Check HTTP servlet access for Service ContractsReview Oracle HTTP Server configuration or Oracle E-Business Suite profile options (FND_VALIDATION_ENABLED) to confirm web-based access to Service Contracts functions is enabled. Check the Apache/OHS configuration for /okc/ or /servicecontracts/ endpoints.Affected if HTTP access to Service Contracts is enabled - the attack vector is available.
Affected if Oracle Service Contracts version is between 12.2.5 and 12.2.13 inclusive AND the Authoring component is accessible via HTTP to low-privileged users.
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 Oracle Critical Patch Update for the affected versions (12.2.5-12.2.13) and review Authoring component access controls to ensure only necessary privileges are granted.
- Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2024-21280. Contact Oracle Support or check the Oracle Critical Patch Updates advisory for the applicable patch for Oracle E-Business Suite 12.2.
- Alternatively, apply the one-off patch specifically released for CVE-2024-21280 in Oracle Service Contracts Authoring component, if available from Oracle Support.
- After applying the patch, verify that the fix is properly installed by checking the Oracle application version and testing the Authoring component functionality.
- Review user privileges in Oracle Service Contracts to ensure users have only the minimum necessary authorizations (principle of least privilege), as a defense-in-depth measure.
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-21280 — 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-21280 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