dbcve.org
E Business SuiteApplication · Oracle

CVE-2015-4798

HIGH · 10.0 CVSS v2.0 Published 2015-10-21
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Applications Technology Stack component in Oracle E-Business Suite 11.5.10.2 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to DB Listener, a different vulnerability than CVE-2015-4839.

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

Oracle E-Business Suite 11.5.10.2 contains an unspecified vulnerability in the DB Listener component of the Applications Technology Stack. The vulnerability allows remote unauthenticated attackers to impact confidentiality, integrity, and availability with attack vectors through the DB Listener service.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for July 2015 that addresses CVE-2015-4798. Restrict network access to the DB Listener ports and ensure Oracle E-Business Suite is behind appropriate network segmentation.

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

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
Complete
Integrity
Complete
Availability
Complete

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

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. Confirm Oracle E-Business Suite version
    Access the Oracle Applications Manager (OAM) or run the SQL query 'SELECT release_name FROM apps.fnd_product_groups' to identify the installed E-Business Suite version
    Affected if The version returned is exactly 11.5.10.2
  2. Verify DB Listener component status
    Check if the Oracle Database Listener is running and configured. This can be done by attempting to connect to the listener port (typically 1521) or using the 'lsnrctl status' command if you have access to the database server
    Affected if The DB Listener is active and accepting connections on its configured port
  3. Assess DB Listener network exposure
    Determine if the DB Listener port is accessible from untrusted network segments. Use tools like 'netstat' on the DB server to identify listening ports and verify firewall rules or ACLs restricting access
    Affected if The DB Listener port is exposed to untrusted or public network segments without proper access controls
  4. Check for unauthorized listener configurations
    Review the listener.ora configuration file for any unauthorized or unexpected entries, and verify that only expected services are registered with the listener
    Affected if Unexpected services or unauthorized configurations are found in the listener setup

A system is affected if it runs Oracle E-Business Suite version 11.5.10.2 with the DB Listener component exposed to network access, allowing remote attackers to impact confidentiality, integrity, or availability.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply the relevant Oracle Critical Patch Update (CPU) for July 2015 that addresses CVE-2015-4798. Restrict network access to the DB Listener ports and ensure Oracle E-Business Suite is behind appropriate network segmentation.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.1.x or 12.2.x (contact Oracle Support for upgrade path from 11.5.10.2)

  1. 1. Access Oracle Support and navigate to the Oracle Critical Patch Update - October 2015 (http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html)
  2. 2. Locate the Oracle E-Business Suite 11.5.10.2 patches section for the DB Listener vulnerability (CVE-2015-4798)
  3. 3. Download the specific patch file(s) listed for E-Business Suite 11.5.10.2 from the October 2015 CPU
  4. 4. Review the patch readme and prerequisites documentation provided with the patch
  5. 5. Apply the patch following Oracle's standard patching procedures for E-Business Suite (typically using ADPATCH)
  6. 6. Verify the patch was applied successfully by checking the applied patches in Oracle Applications Manager
  7. 7. Restart affected services/components as required by the patch
Caveat E-Business Suite 11i (11.5.10.2) is in Sustaining Support only; Oracle strongly recommends upgrading to 12.1.x or 12.2.x as patches for 11i are limited

Generated from the published advisory — verify against the referenced sources before acting.

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 the patch applied

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-2015-4798 — 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-2015-4798 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