Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21041

MEDIUM · 6.1 CVSS v3.1 Published 2024-04-16

Fix available

A fix is available. Upgrade to after 12.2.13 or later.

See remediation →

68/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

Vulnerability in the Oracle Complex Maintenance, Repair, and Overhaul product of Oracle E-Business Suite (component: 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 Complex Maintenance, Repair, and Overhaul. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Complex Maintenance, Repair, and Overhaul, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Complex Maintenance, Repair, and Overhaul accessible data as well as unauthorized read access to a subset of Oracle Complex Maintenance, Repair, and Overhaul accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Technical summary

dbcve analysis · high confidence

Unauthenticated HTTP vulnerability in the List of Values (LOV) component of Oracle Complex Maintenance, Repair, and Overhaul allows attackers with network access to perform unauthorized read and write operations on a subset of accessible data. The vulnerability requires human interaction and can impact additional products beyond the affected component due to scope change.

MitigationApply Oracle Critical Patch Update (CPU) for CVE-2024-21041. If immediate patching is not feasible, restrict network access to Oracle E-Business Suite HTTP interfaces and implement monitoring for anomalous LOV-related requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Complex Maintenance Repair And OverhaulApplication

Affected:>= 12.2.3, <= 12.2.13

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if Oracle Complex Maintenance Repair And Overhaul is installed

Locate the Oracle E-Business Suite installation directory and check for CMRO (Complex Maintenance, Repair, and Overhaul) module. Query the Oracle applications registry table (FND_APPLICATlONS or similar) for the product name 'Complex Maintenance Repair and Overhaul' or its internal name.

Affected if The product is present in the environment
Determine the installed version of CMRO

Query the Oracle version tables (such as FND_PRODUCT_INSTALLATIONS or the specific CMRO version tables) to retrieve the current version number. Compare against the affected range: 12.2.3 through 12.2.13.

Affected if The version falls within 12.2.3 to 12.2.13 inclusive
Verify HTTP interface exposure

Check the Oracle E-Business Suite HTTP server configuration (typically in Oracle HTTP Server or Apache configuration files) to determine if the /oa_html/ or /webservices/ endpoints are accessible externally. Review load balancer or firewall rules that govern access to the application HTTP ports.

Affected if The HTTP interfaces are reachable from untrusted networks
Confirm LOV component accessibility

Test access to the List of Values (LOV) functionality by attempting to access known LOV-related URLs such as /oa_html/lov.jsp or by monitoring HTTP access logs for requests containing 'lov' in the URI path.

Affected if LOV endpoints respond to HTTP requests without requiring authentication

The environment is affected if Oracle Complex Maintenance Repair And Overhaul version 12.2.3 through 12.2.13 is installed AND the HTTP interface is network-accessible, allowing unauthenticated attackers to reach the LOV component.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.2.13

Interim mitigation

Apply Oracle Critical Patch Update (CPU) for CVE-2024-21041. If immediate patching is not feasible, restrict network access to Oracle E-Business Suite HTTP interfaces and implement monitoring for anomalous LOV-related requests.

Recommended fix High confidence

Oracle E-Business Suite 12.2.14 or latest 12.2.x release

Verify current Oracle E-Business Suite Complex Maintenance, Repair, and Overhaul version is within 12.2.3-12.2.13 range
Upgrade to Oracle E-Business Suite 12.2.14 or later (the first fixed release beyond the vulnerable range)
Alternatively, apply the relevant Oracle Critical Patch Update (CPU) that addresses CVE-2024-21041
After upgrade/patch, verify the LOV component no longer accepts unsanitized input by testing list-of-values fields for XSS vulnerability
Confirm the fix by reviewing Oracle's April 2024 Critical Patch Update documentation

Caveat Standard E-Business Suite upgrade precautions apply - test thoroughly in staging environment including related LOV-dependent workflows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Complex Maintenance Repair And Overhaul Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing10.0 h
Review / QA3.0 h

22.0 hours of engineering $3,720

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,952.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-21041 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21041 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-21041?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsUpgrade to after 12.2.13 or later

Severity 6.1 Medium

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Complex Maintenance Repair And Overhaul

Remediation

Need this fixed?

Fix this in Complex Maintenance Repair And Overhaul 22 hrs · Moderate

Typical engagement from $3,720

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-21041 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References