CVE-2012-0565
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 · uneditedUnspecified vulnerability in the Oracle Agile component in Oracle Supply Chain Products Suite 5.2.2, 6.0.0, and 6.1.1 allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Install.
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 confidenceUnspecified vulnerability in Oracle Agile PLM affecting the Install functionality in versions 5.2.2, 6.0.0, and 6.1.1. Allows remote authenticated users to impact confidentiality and integrity via unknown vectors, likely involving improper access controls or path traversal in the install/setup processes.
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= 5.2.2= 6.0.0= 6.1.1CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/C:P/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Agile PLM installationCheck for Oracle Agile PLM application components on the system. Look for the Agile application server process, web application files, or Oracle Agile PLM directories in the Oracle middleware home or application directory structure.Affected if Oracle Agile PLM software is present on the system.
-
Determine installed versionLocate and read the version information file or use Oracle's version detection mechanisms. Common locations include the application's about page, version.properties file, or Oracle Enterprise Manager if deployed. Compare the discovered version against the affected versions: 5.2.2, 6.0.0, or 6.1.1.Affected if The installed version is exactly 5.2.2, 6.0.0, or 6.1.1.
-
Verify Install/Setup functionality statusCheck whether the Install, Setup, or configuration web endpoints are enabled and accessible on the Oracle Agile PLM web interface. Look for /install, /setup, or similar configuration paths in the application's URL routing or web.xml configuration.Affected if The Install or Setup functionality is enabled and publicly or broadly accessible.
-
Review access control configurationInspect the access control lists, roles, or permissions configured for the Install/Setup functionality in the Oracle Agile PLM security settings. Verify which user roles can access the installation or configuration features.Affected if Non-administrator or unauthenticated users have access to Install/Setup features.
The environment is affected if Oracle Agile PLM versions 5.2.2, 6.0.0, or 6.1.1 are installed and the Install/Setup functionality is accessible to authenticated users beyond restricted administrators.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Updates for Oracle Agile PLM. Upgrade to a patched version if available. Restrict access to Install/Setup functionality to only necessary administrators.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0565 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-0565 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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