# CVE-2024-21039: Missing authorization in Complex Maintenance, Repair, and Overhaul > Unauthenticated attackers can modify or read data in Oracle Complex Maintenance, Repair, and Overhaul via HTTP, requiring user interaction. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 16 Apr 2024 - **Updated:** 27 Mar 2025 - **Also known as:** GHSA-8g9c-f7h3-mxcj ## What is CVE-2024-21039? CVE-2024-21039 is a medium-severity missing authorization vulnerability in Oracle Corporation Complex Maintenance, Repair, and Overhaul, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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). Weakness: CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2024-21039? It affects 1 product. Products: Oracle Complex Maintenance Repair and Overhaul. ## How do I fix CVE-2024-21039? No fix has been published for CVE-2024-21039 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-21039 being exploited? There is no known exploitation of CVE-2024-21039 in the wild and no public exploit code. ## Other vulnerabilities in Oracle Corporation Complex Maintenance, Repair, and Overhaul - [CVE-2026-46915](https://insights.sbomify.com/CVE-2026-46915/): Auth bypass in Oracle Complex Maintenance, Repair and Overhaul (high 8.5) - [CVE-2016-3456](https://insights.sbomify.com/CVE-2016-3456/): Information disclosure in n/a (high 8.2) - [CVE-2026-61138](https://insights.sbomify.com/CVE-2026-61138/): Missing authorization in Oracle Complex Maintenance, Repair and Overhaul (high 7.5) - [CVE-2026-46934](https://insights.sbomify.com/CVE-2026-46934/): Auth bypass in Oracle Complex Maintenance, Repair and Overhaul (high 7.5) - [CVE-2026-46935](https://insights.sbomify.com/CVE-2026-46935/): Auth bypass in Oracle Complex Maintenance, Repair and Overhaul (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-21039 and fix it if it is affected. What it is: CVE-2024-21039 is a medium-severity missing authorization vulnerability in Oracle Corporation Complex Maintenance, Repair, and Overhaul, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-21039 in the wild and no public exploit code. Affected product: Oracle Corporation Complex Maintenance, Repair, and Overhaul. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-21039/ (Markdown: https://insights.sbomify.com/CVE-2024-21039/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-21039 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-21039 - OSV: https://osv.dev/vulnerability/CVE-2024-21039 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-21039/ Summaries are generated and may contain mistakes; the official description above is the record.