dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 12 Dec 2024.
Agile Product Lifecycle ManagementApplication · Oracle

CVE-2024-21287

HIGH · 7.5 CVSS v3.1 Published 2024-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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 PLM Framework product of Oracle Supply Chain (component: Software Development Kit, Process Extension). The supported version that is affected is 9.3.6. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Agile PLM Framework. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Agile PLM Framework accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 · moderate confidence

Unauthenticated HTTP vulnerability in Oracle Agile PLM Framework's Software Development Kit/Process Extension component (version 9.3.6) allows remote attackers to access sensitive data via network requests without any authentication or user interaction.

MitigationRestrict network access to the affected Oracle Agile PLM endpoints and apply the Oracle patch when available; if the Process Extension component is not required, disable it.

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 ManagementApplication
Affected:= 9.3.6

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Verify Oracle Agile PLM version
    Locate the Agile PLM installation directory and check the version.properties or about screen in the application. Common paths include $AGILE_HOME/agileDomain/servers/ or check the admin console for the deployed application version.
    Affected if Installed version is exactly 9.3.6
  2. Confirm SDK/Process Extension component is deployed
    Check if the Software Development Kit or Process Extension module is deployed on the Oracle Agile PLM application server. Review the deployed web applications or EAR/WAR files in the application server (typically WebLogic) for SDK-related modules.
    Affected if SDK component is deployed and accessible as part of the Agile PLM application
  3. Identify exposed SDK endpoints
    Review the application web.xml and any custom servlet mappings for Process Extension or SDK-related endpoints. Common endpoint patterns include paths containing '/px/', '/sdk/', or '/processExtension/' in the URL.
    Affected if SDK/Process Extension HTTP endpoints are exposed and reachable via HTTP
  4. Test unauthenticated access to SDK endpoints
    Using a tool like curl or a browser, attempt to access known SDK processing endpoints without providing authentication credentials. Look for HTTP responses that return data or successful processing rather than 401/403 authentication errors.
    Affected if Requests to SDK endpoints return successful responses without requiring authentication
  5. Check network accessibility of Agile PLM interfaces
    Determine if the Agile PLM HTTP/HTTPS ports are exposed to untrusted networks by reviewing firewall rules, load balancer configurations, and network segmentation policies.
    Affected if Agile PLM HTTP interfaces are accessible from untrusted networks without VPN or firewall restrictions

You are affected if running Oracle Agile PLM version 9.3.6 with the SDK/Process Extension component exposed to network access where unauthenticated requests to SDK endpoints are accepted without access controls.

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

Restrict network access to the affected Oracle Agile PLM endpoints and apply the Oracle patch when available; if the Process Extension component is not required, disable it.

Fix this in Agile Product Lifecycle Management Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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