dbcve.org
HTTP ServerWeb server / proxy · Oracle

CVE-1999-1068

MEDIUM · 5.0 CVSS v2.0 Published 1997-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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
Oracle Webserver 2.1, when serving PL/SQL stored procedures, allows remote attackers to cause a denial of service via a long HTTP GET request.

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 Webserver 2.1 contains a denial-of-service vulnerability when processing PL/SQL stored procedure requests. A remote attacker can send an excessively long HTTP GET request to crash the webserver or make it unresponsive.

MitigationThis is end-of-life software with no patches available. Migrate to a supported Oracle application server (Oracle WebLogic Server, Oracle Fusion Middleware, or Oracle Cloud Infrastructure) as Oracle Webserver 2.1 is obsolete and unsupported.

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
HTTP ServerWeb server / proxy
Affected:= 2.1

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
Partial

AV:N/AC:L/Au:N/C:N/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. Identify if Oracle HTTP Server is installed
    Check the system for Oracle HTTP Server binaries, services, or documentation. Look for Oracle Webserver installation directories or check running processes for 'ows' or 'oracle http' processes.
    Affected if Oracle HTTP Server version 2.1 is installed on the system
  2. Verify the installed version is 2.1
    Check the version of Oracle HTTP Server by examining the binary, startup scripts, or Oracle inventory. Common locations include ORACLE_HOME directory or check the process version information if available.
    Affected if The installed version is exactly 2.1 (no other version)
  3. Confirm the HTTP service is running and accessible
    Check if the Oracle HTTP Server process is running and listening on network ports (typically port 80 or 8080). Use commands like 'netstat' or 'ps' to identify active HTTP services.
    Affected if The Oracle HTTP Server service is running and accepting network connections

The environment is affected only if Oracle HTTP Server version 2.1 is installed, running, and exposed to network requests that could trigger the denial-of-service condition.

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

This is end-of-life software with no patches available. Migrate to a supported Oracle application server (Oracle WebLogic Server, Oracle Fusion Middleware, or Oracle Cloud Infrastructure) as Oracle Webserver 2.1 is obsolete and unsupported.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA4.0 h
48.0 hours of engineering $8,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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