dbcve.org
Agile Product Lifecycle Management For ProcessApplication · Oracle

CVE-2024-21092

HIGH · 8.1 CVSS v3.1 Published 2024-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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: Product Quality Management). The supported version that is affected is 6.2.4.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Agile Product Lifecycle Management for Process. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Agile Product Lifecycle Management for Process accessible data as well as unauthorized access to critical data or complete access to all Oracle Agile Product Lifecycle Management for Process 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 confidence

CVE-2024-21092 is a high-severity vulnerability in Oracle Agile Product Lifecycle Management for Process (Product Quality Management component) version 6.2.4.2. The flaw allows a low-privileged attacker with network access via HTTP to create, delete, or modify critical data, as well as gain unauthorized access to critical or all accessible data within the application. Both confidentiality and integrity are severely impacted while availability remains unaffected.

MitigationApply the Oracle security patch for CVE-2024-21092 when available from Oracle Support. Until a patch is applied, restrict network access to the Product Quality Management interface to trusted users only and monitor for unauthorized data access or modification attempts.

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
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 checks

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

  1. Identify Oracle Agile PLM for Process installation
    Locate the Oracle Agile PLM for Process installation directory or check system inventory for the presence of this product
    Affected if The product is not installed, the vulnerability does not apply
  2. Verify installed version is 6.2.4.2
    Check the installed version of Oracle Agile Product Lifecycle Management for Process through the Oracle Enterprise Manager, about page, or version file within the installation directory
    Affected if The installed version is exactly 6.2.4.2, indicating the specific affected release
  3. Confirm Product Quality Management component is enabled
    Check the Oracle Agile PLM configuration or admin console to determine if the Product Quality Management module is active and accessible
    Affected if The Product Quality Management component is enabled and accessible within the application
  4. Assess network exposure of the PQM interface
    Review network configuration, firewall rules, or access controls to determine if the Product Quality Management interface is reachable over HTTP/HTTPS from untrusted networks
    Affected if The Product Quality Management interface is exposed to network access without proper restriction to trusted users only

A defender is affected if Oracle Agile PLM for Process version 6.2.4.2 is installed with the Product Quality Management component enabled and accessible over the network to untrusted users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle security patch for CVE-2024-21092 when available from Oracle Support. Until a patch is applied, restrict network access to the Product Quality Management interface to trusted users only and monitor for unauthorized data access or modification attempts.

Fix this in Agile Product Lifecycle Management For Process Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21092 — 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-21092 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