E Business SuiteApplication · Oracle

CVE-2012-0535

MEDIUM · 5.0 CVSS v2.0 Published 2012-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Unspecified vulnerability in the Oracle Application Object Library component in Oracle E-Business Suite 12.0.6 and 12.1.3 allows remote attackers to affect confidentiality via unknown vectors related to Change Password Page.

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

Unspecified vulnerability in Oracle E-Business Suite's Application Object Library Change Password page allows remote attackers to affect confidentiality. The specific attack vector and exploitation mechanism are not detailed in available sources, but the vulnerability impacts the password change functionality in versions 12.0.6 and 12.1.3.

MitigationApply Oracle Critical Patch Updates (CPU) for Oracle E-Business Suite to obtain the security fix. Until the patch is applied, consider restricting network access to the Change Password functionality and monitoring for unauthorized access 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
E Business SuiteApplication
Affected:= 12.0.6= 12.1.3

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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/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. Identify Oracle E-Business Suite version
    Query the database using SQL: SELECT release_name FROM apps.fnd_product_installations WHERE patch_level IS NOT NULL; or access Oracle Application Manager > License Manager to view installed versions.
    Affected if The version returned is exactly 12.0.6 or exactly 12.1.3
  2. Verify Application Object Library is installed
    Check if AOL component is deployed by querying: SELECT application_name FROM fnd_application WHERE application_name = 'FND' OR application_id IN (SELECT application_id FROM fnd_application_tl WHERE product_code = 'FND');
    Affected if FND (Application Object Library) is present in the installation
  3. Confirm Change Password page is accessible
    Access the Change Password function via URL pattern: /OA_HTML/AppsLogin?functionId=CHGPWD or check in Oracle Application Manager under Function > CHGPWD is enabled.
    Affected if The Change Password functionality (function ID CHGPWD) is enabled and accessible to users
  4. Review audit logs for password change activity
    Check Oracle E-Business Suite audit tables: SELECT * FROM fnd_logins WHERE user_id IN (SELECT user_id FROM fnd_user) AND start_time > SYSDATE - 30; or review Oracle HTTP Server access logs for /OA_HTML/*CHGPWD* requests.
    Affected if Unexpected or unauthorized password change attempts are logged from external IP addresses

You are affected if your Oracle E-Business Suite installation is exactly version 12.0.6 or 12.1.3 AND the Change Password functionality is enabled and accessible.

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 Oracle Critical Patch Updates (CPU) for Oracle E-Business Suite to obtain the security fix. Until the patch is applied, consider restricting network access to the Change Password functionality and monitoring for unauthorized access attempts.

Fix this in E Business Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0535 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0535 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