dbcve.org
E Business SuiteApplication · Oracle

CVE-2012-3190

MEDIUM · 6.4 CVSS v2.0 Published 2013-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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 Universal Work Queue component in Oracle E-Business Suite 11.5.10.2, 12.0.6, 12.1.1, 12.1.2, and 12.1.3 allows remote attackers to affect confidentiality and integrity, related to UWQ Server Issues.

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

A vulnerability in the Oracle Universal Work Queue (UWQ) component of Oracle E-Business Suite allows remote attackers to impact confidentiality and integrity. The specific flaw is in UWQ Server Issues and affects versions 11.5.10.2 through 12.1.3, enabling unauthorized data access or modification.

MitigationApply Oracle Critical Patch Updates (CPU) for E-Business Suite that address the UWQ Server Issues vulnerability. Test thoroughly in a non-production environment before production deployment due to Oracle EBS complexity.

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:= 11.5.10.2= 12.0.6= 12.1.1= 12.1.2= 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
Partial
Availability
None

AV:N/AC:L/Au:N/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 checks

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

  1. Identify Oracle E-Business Suite installation
    Look for Oracle EBS application directories such as $APPL_TOP, $ORACLE_HOME, or check for Oracle E-Business Suite services running on the system. Common installation paths include /u01/oracle/EBS/ on Linux or C:\oracle\EBS\ on Windows.
    Affected if Oracle E-Business Suite is not installed on the system, then the CVE does not apply.
  2. Determine the installed Oracle EBS version
    Check the Oracle EBS version by examining the version file or context file. The version is often stored in the Oracle Applications environment file, in the context file under $INST_TOP/apps/appl/admin, or can be queried through Oracle Application Manager.
    Affected if The installed version is one of: 11.5.10.2, 12.0.6, 12.1.1, 12.1.2, or 12.1.3. If the version is outside this range, the system may not be affected.
  3. Verify if Universal Work Queue (UWQ) is configured
    Check if the UWQ component is enabled in Oracle E-Business Suite. This can be verified through Oracle Application Manager under Site Map > Oracle Applications Manager > Oracle Universal Work Queue, or by checking the Oracle EBS configuration for UWQ-related modules.
    Affected if The UWQ Server component is actively configured or running. If UWQ is not enabled or not present, the specific flaw may not be exploitable in that environment.
  4. Check for unauthorized UWQ Server access points
    Review the Oracle EBS web entry points and URLs for UWQ Server Issues functionality. Examine Apache/OHS configuration files in $ORACLE_HOME/Apache/Apache/conf for UWQ-related application modules, and check for exposed UWQ Server endpoints.
    Affected if UWQ Server is accessible via network without proper authentication controls, or the UWQ module is publicly reachable without restricted access policies.

A system is affected if Oracle E-Business Suite is installed with version 11.5.10.2, 12.0.6, 12.1.1, 12.1.2, or 12.1.3, and the Universal Work Queue (UWQ) Server component 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 E-Business Suite that address the UWQ Server Issues vulnerability. Test thoroughly in a non-production environment before production deployment due to Oracle EBS complexity.

Fix this in E Business Suite 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-2012-3190 — 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-2012-3190 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