dbcve.org
Application ServerApplication · Oracle

CVE-2007-2120

HIGH · 7.8 CVSS v2.0 Published 2007-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
The Oracle Discoverer servlet in Oracle Application Server 9.0.4.3, 10.1.2.0.2, and 10.1.2.2.0 allows remote attackers to shut down an Oracle TNS Listener via a TNS STOP command in a request that uses the database/TNS alias, aka AS01.

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 · high confidence

The Oracle Discoverer servlet in Oracle Application Server versions 9.0.4.3, 10.1.2.0.2, and 10.1.2.2.0 lacks proper authorization controls, allowing remote unauthenticated attackers to send TNS STOP commands via the servlet using a database/TNS alias. This enables remote shutdown of the Oracle TNS Listener, causing complete denial of service for database-dependent applications.

MitigationApply Oracle security patches for this vulnerability; if patches are unavailable, restrict network access to the Discoverer servlet via firewall rules or remove/disable the servlet if not required, and implement strong authentication for any remaining access.

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
Application ServerApplication
Affected:= 9.0.4.3= 10.1.2.0.2= 10.1.2.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
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/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. Identify Oracle Application Server installation
    Look for Oracle Application Server installations on the system. Check common installation paths such as $ORACLE_HOME/Apache/Apache or search for Oracle binaries and configuration files. On Windows, check Program Files for Oracle folders.
    Affected if Oracle Application Server is installed and the version matches 9.0.4.3, 10.1.2.0.2, or 10.1.2.2
  2. Confirm the installed version
    Check the version of Oracle Application Server by examining the ORACLE_HOME directory or running version查询 commands. Look for a version file or check the Oracle inventory. The version must equal one of: 9.0.4.3, 10.1.2.0.2, or 10.1.2.2
    Affected if The installed version exactly matches 9.0.4.3, 10.1.2.0.2, or 10.1.2.2
  3. Verify if Discoverer servlet is enabled
    Check if the Oracle Discoverer servlet is deployed and enabled. Look for the discoverer servlet configuration in the Oracle Application Server httpd.conf or mod_oc4j configuration. Common paths include $ORACLE_HOME/Apache/Apache/conf/httpd.conf or $ORACLE_HOME/j2ee/home/config/application.xml
    Affected if The Discoverer servlet is loaded and accessible on the application server
  4. Check network exposure of the Discoverer servlet
    Determine if the Discoverer servlet is reachable over the network by checking firewall rules and listening ports. The servlet typically runs on port 7776, 7777, or 7778 for Oracle Application Server. Use netstat or similar tools to identify if these ports are exposed externally.
    Affected if The Discoverer servlet port (typically 7776-7778) is accessible from untrusted networks

The environment is affected if Oracle Application Server versions 9.0.4.3, 10.1.2.0.2, or 10.1.2.2 is installed, the Discoverer servlet is enabled, and the servlet is network-accessible to untrusted users.

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 security patches for this vulnerability; if patches are unavailable, restrict network access to the Discoverer servlet via firewall rules or remove/disable the servlet if not required, and implement strong authentication for any remaining access.

Fix this in Application Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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