Industry ApplicationsApplication · Oracle

CVE-2015-4795

HIGH · 7.5 CVSS v2.0 Published 2015-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Utilities Work and Asset Management component in Oracle Industry Applications 1.9.1.1.2 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Add-On Applications.

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

CVE-2015-4795 is an unspecified vulnerability in Oracle Utilities Work and Asset Management v1.9.1.1.2 affecting the Add-On Applications component. The vulnerability is remotely exploitable and allows attackers to impact confidentiality, integrity, and availability, indicating potential for full system compromise. As an 'unspecified' vulnerability in Oracle's CPU advisory, technical specifics are not publicly disclosed.

MitigationApply Oracle Critical Patch Update July 2015 or later which addresses this vulnerability. If patching is not feasible, restrict network access to the affected Oracle Industry Applications systems and review Add-On Applications configurations for suspicious activity.

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
Industry ApplicationsApplication
Affected:= 1.9.1.1.2

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
Partial

AV:N/AC:L/Au:N/C:P/I:P/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. Identify Oracle Utilities Work and Asset Management installation
    Locate and verify the Oracle Utilities Work and Asset Management application in your environment - check installed programs, application inventory, or consult your Oracle software licensing records
    Affected if The application is present and running
  2. Verify the exact product version
    Check the installed version of Oracle Utilities Work and Asset Management - this is typically visible in the application About section, Oracle Enterprise Manager, or via command line tools such as 'opatch lsinventory'
    Affected if The version is 1.9.1.1.2 exactly
  3. Confirm Add-On Applications component status
    Check whether the Add-On Applications module is installed and enabled in your Oracle Utilities Work and Asset Management deployment - review module configuration files or Oracle Application Explorer
    Affected if Add-On Applications component is present and enabled
  4. Assess network accessibility
    Determine if the Oracle application is exposed to network access - verify firewall rules, network ACLs, and whether the application ports (typically Oracle WebLogic/Oracle HTTP Server ports) are reachable from untrusted networks
    Affected if The application is reachable from external or untrusted networks

You are affected if Oracle Utilities Work and Asset Management version 1.9.1.1.2 with Add-On Applications enabled is running in your environment.

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 Update July 2015 or later which addresses this vulnerability. If patching is not feasible, restrict network access to the affected Oracle Industry Applications systems and review Add-On Applications configurations for suspicious activity.

Fix this in Industry Applications Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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