Iplanet Web ServerApplication · Oracle

CVE-2020-9315

HIGH · 7.5 CVSS v3.1 Published 2020-05-10
Fix available
A fix is available. Upgrade to after 7.0.27 or later.
See remediation →
84/100
Remediation priority · High
High EPSS 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
** PRODUCT NOT SUPPORTED WHEN ASSIGNED ** Oracle iPlanet Web Server 7.0.x has Incorrect Access Control for admingui/version URIs in the Administration console, as demonstrated by unauthenticated read access to encryption keys. NOTE: a related support policy can be found in the www.oracle.com references attached to this CVE.

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

Oracle iPlanet Web Server 7.0.x contains an incorrect access control vulnerability in the Administration console's admingui/version URIs. This allows unauthenticated remote attackers to access sensitive information including encryption keys without any authentication credentials.

MitigationSince the product is end-of-life and unsupported, restrict network access to the Administration console via firewall/network segmentation, or migrate to a supported Oracle Web Server product.

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
Iplanet Web ServerApplication
Affected:>= 7.0, <= 7.0.27

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 iPlanet Web Server is installed
    Check for the presence of Oracle iPlanet Web Server process or installation directory. Common paths include /opt/sun/webserver or C:\Program Files\Sun\WebServer7. Look for processes named 'webservd' or 'httpd' with SunONE/iPlanet branding.
    Affected if The software is Oracle iPlanet Web Server 7.0.x
  2. Determine the installed version
    Check the version string in the server's banner or documentation. The version is typically displayed in the Administration console or can be found in version files within the installation directory. Look for files like 'version.txt' or check the admin server response headers.
    Affected if The version is between 7.0 and 7.0.27 inclusive
  3. Check if Administration console is network-accessible
    Attempt to access the admingui interface over the network. The typical URL pattern is https://<server>:8889/admingui or http://<server>:8800/admingui. The specific port depends on your admin server configuration.
    Affected if The Administration console port is exposed to untrusted networks without firewall protection
  4. Test the vulnerable version endpoint
    Send an HTTP GET request to the /admingui/version URI without providing any authentication credentials. For example: curl http://target:8889/admingui/version or curl https://target:8889/admingui/version
    Affected if The endpoint returns version information or sensitive data without requiring authentication

You are affected if Oracle iPlanet Web Server version 7.0 through 7.0.27 is installed and the /admingui/version endpoint is accessible without authentication credentials.

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
Upgrade available Upgrade to a release after 7.0.27
Interim mitigation

Since the product is end-of-life and unsupported, restrict network access to the Administration console via firewall/network segmentation, or migrate to a supported Oracle Web Server product.

Fix this in Iplanet Web Server 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 the upgrade done

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-2020-9315 — 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-2020-9315 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