# CVE-2024-20956: Missing authorization in Agile Product Lifecycle Management for Process > Unauthenticated attackers can read, modify, or delete data and cause partial denial of service in Oracle Agile PLM via HTTP. - **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 17 Feb 2024 - **Updated:** 5 Dec 2024 - **Also known as:** GHSA-xh58-v5pj-37jw ## What is CVE-2024-20956? CVE-2024-20956 is a high-severity missing authorization vulnerability in Oracle Corporation Agile Product Lifecycle Management for Process, published on 17 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Vulnerability in the Oracle Agile Product Lifecycle Management for Process product of Oracle Supply Chain (component: Installation). Supported versions that are affected are Prior to 6.2.4.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Agile Product Lifecycle Management for Process. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Agile Product Lifecycle Management for Process accessible data as well as unauthorized read access to a subset of Oracle Agile Product Lifecycle Management for Process accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Agile Product Lifecycle Management for Process. CVSS 3.1 Base Score 7.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L). ## Which versions are affected by CVE-2024-20956? It affects 1 product. Products: Oracle Agile Product Lifecycle Management for Process. ## How do I fix CVE-2024-20956? No fix has been published for CVE-2024-20956 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-20956 being exploited? There is no known exploitation of CVE-2024-20956 in the wild and no public exploit code. ## Other vulnerabilities in Oracle Corporation Agile Product Lifecycle Management for Process - [CVE-2026-61178](https://insights.sbomify.com/CVE-2026-61178/): Auth bypass in Oracle Agile Product Lifecycle Management for Process (critical 9.8) - [CVE-2026-61183](https://insights.sbomify.com/CVE-2026-61183/): Auth bypass in Oracle Agile Product Lifecycle Management for Process (critical 9.8) - [CVE-2026-21969](https://insights.sbomify.com/CVE-2026-21969/): Auth bypass in Oracle Agile Product Lifecycle Management for Process (critical 9.8) - [CVE-2026-61184](https://insights.sbomify.com/CVE-2026-61184/): Missing authorization in Oracle Agile Product Lifecycle Management for Process (critical 9.1) - [CVE-2026-61179](https://insights.sbomify.com/CVE-2026-61179/): Auth bypass in Oracle Agile Product Lifecycle Management for Process (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-20956 and fix it if it is affected. What it is: CVE-2024-20956 is a high-severity missing authorization vulnerability in Oracle Corporation Agile Product Lifecycle Management for Process, published on 17 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-20956 in the wild and no public exploit code. Affected product: Oracle Corporation Agile Product Lifecycle Management for Process. 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-20956/ (Markdown: https://insights.sbomify.com/CVE-2024-20956/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-20956 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-20956 - OSV: https://osv.dev/vulnerability/CVE-2024-20956 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-20956/ Summaries are generated and may contain mistakes; the official description above is the record.