Enterprise Manager Grid ControlApplication · Oracle

CVE-2016-0455

MEDIUM · 5.2 CVSS v2.0 Published 2016-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
54/100
Remediation priority · Moderate
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 Enterprise Manager Base Platform component in Oracle Enterprise Manager Grid Control 11.1.0.1, 11.2.0.4, 12.1.0.4, and 12.1.0.5 allows local users to affect confidentiality and availability via unknown vectors related to Agent Next Gen.

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

This is a local privilege vulnerability in Oracle Enterprise Manager Grid Control's Agent Next Gen component. The CVSS 5.2 score with Local attack vector (AV:L) indicates a local user can potentially elevate privileges or access sensitive data through unspecified vectors affecting confidentiality and availability.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for January 2016 that addresses CVE-2016-0455. Verify that the EM Agent Next Gen component is properly configured with least-privilege access controls.

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
Enterprise Manager Grid ControlApplication
Affected:= 11.1.0.1= 11.2.0.4= 12.1.0.4= 12.1.0.5

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
Local
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
None
Availability
Partial

AV:L/AC:L/Au:S/C:C/I:N/A:P

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 Enterprise Manager Grid Control installation
    Check for the presence of Oracle Enterprise Manager Grid Control by looking for its installation directory (commonly under $ORACLE_HOME/em or similar Oracle inventory locations) or check Windows services for 'Oracle Enterprise Manager' related services
    Affected if The product is not installed or no Grid Control components are found, the vulnerability does not apply
  2. Determine installed Grid Control version
    Locate the version file or use Oracle inventory commands (such as 'opatch lsinventory' or checking the 'emctl status' output) to obtain the exact installed version of Oracle Enterprise Manager Grid Control
    Affected if The installed version matches one of the affected versions: 11.1.0.1, 11.2.0.4, 12.1.0.4, or 12.1.0.5
  3. Confirm Agent Next Gen component is present
    Check for the Agent Next Gen component by examining the Grid Control installation for the 'agent11g' or 'agent12c' directory structure, or run 'emctl status agent' to verify the Agent component is configured
    Affected if The Agent Next Gen component is installed and running - this component must be present for the vulnerability to be exploitable
  4. Verify current patch level
    Run 'opatch lsinventory' or check the applied patches list to see if the January 2016 Critical Patch Update (CPU) has been applied
    Affected if The January 2016 CPU has NOT been applied and the version matches an affected release, the system remains vulnerable

You are affected if Oracle Enterprise Manager Grid Control is installed with version 11.1.0.1, 11.2.0.4, 12.1.0.4, or 12.1.0.5, the Agent Next Gen component is present, and the January 2016 Critical Patch Update has not been applied.

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 relevant Oracle Critical Patch Update (CPU) for January 2016 that addresses CVE-2016-0455. Verify that the EM Agent Next Gen component is properly configured with least-privilege access controls.

Fix this in Enterprise Manager Grid Control Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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