dbcve.org
Agile Product Lifecycle Management For ProcessApplication · Oracle

CVE-2024-20956

HIGH · 7.3 CVSS v3.1 Published 2024-02-17
Fix available
A fix is available. Upgrade to 6.2.4.2 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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).

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 · moderate confidence

Unauthenticated HTTP vulnerability in the Installation component of Oracle Agile Product Lifecycle Management for Process allows remote attackers to read, modify, or delete certain data and cause partial denial of service. The vulnerability affects versions prior to 6.2.4.2 and is easily exploitable via network access.

MitigationApply Oracle's patch by upgrading to version 6.2.4.2 or later as documented in the Oracle Critical Patch Update. Restrict HTTP access to the Installation component through network segmentation or web server configuration until patched.

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
Agile Product Lifecycle Management For ProcessApplication
Affected:< 6.2.4.2

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 checks

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

  1. Identify the Oracle Agile PLM for Process version
    Access the application administration console or check the installation directory for version information. The version is typically displayed in the product header, about section, or can be retrieved via the Fusion Middleware Control console.
    Affected if The installed version is below 6.2.4.2 (e.g., 6.2.4.0, 6.2.3.x, earlier versions)
  2. Locate the Installation component endpoint
    Identify the HTTP URL path for the Installation component. This is typically accessed via the /Installation/ path relative to the application's base URL.
    Affected if The /Installation/ path is accessible via HTTP/HTTPS on the application server
  3. Verify unauthenticated access to the Installation component
    Attempt an HTTP request to the Installation component endpoint without providing credentials. Use a tool like curl: curl -I http(s)://<hostname>/Installation/
    Affected if The endpoint returns an HTTP 200 response without requiring authentication
  4. Check network exposure of the component
    Review network configuration, load balancer rules, or web server proxies to determine if the Installation component is exposed to untrusted networks. Verify firewall rules allow direct access to the application port.
    Affected if The Installation component is reachable from network segments outside the trusted administration zone
  5. Confirm the component is enabled and running
    Check the Oracle WebLogic or other application server console to verify the Installation module is deployed and in Running state.
    Affected if The Installation application is deployed and running on the server

You are affected if your Oracle Agile PLM for Process version is below 6.2.4.2 AND the Installation component is accessible via HTTP without authentication from your network.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.2.4.2 or later
Fixed in 6.2.4.2
Interim mitigation

Apply Oracle's patch by upgrading to version 6.2.4.2 or later as documented in the Oracle Critical Patch Update. Restrict HTTP access to the Installation component through network segmentation or web server configuration until patched.

Recommended fix High confidence

6.2.4.2

  1. Review Oracle Agile Product Lifecycle Management for Process upgrade documentation for version 6.2.4.2
  2. Ensure system meets prerequisites for version 6.2.4.2
  3. Create a complete backup of the current database and configuration files
  4. Stop all Oracle Agile PLM for Process services
  5. Install version 6.2.4.2 following Oracle's installation guide
  6. Verify all services start correctly after upgrade
  7. Validate that the Installation component is properly configured
  8. Test that the HTTP vulnerability is no longer present
Caveat Oracle recommends reviewing the upgrade guide for any configuration or integration changes between your current version and 6.2.4.2

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

Fix this in Agile Product Lifecycle Management For Process Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20956 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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