dbcve.org
HTTP ServerWeb server / proxy · Oracle

CVE-2013-2566

MEDIUM · 5.9 CVSS v3.1 Published 2013-03-15
Fix available
A fix is available. Upgrade to 17.0.11 / 24.1.1 or later.
See remediation →
68/100
Remediation priority · Elevated
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
The RC4 algorithm, as used in the TLS protocol and SSL protocol, has many single-byte biases, which makes it easier for remote attackers to conduct plaintext-recovery attacks via statistical analysis of ciphertext in a large number of sessions that use the same plaintext.

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 RC4 cipher used in TLS/SSL has statistical single-byte biases that allow attackers to recover plaintext by analyzing large numbers of ciphertext samples from sessions using identical plaintext. This is a known cryptographic weakness in the RC4 algorithm.

MitigationDisable RC4 cipher suites in all TLS/SSL configurations and ensure only modern, secure cipher suites (such as AES-based ciphers) are enabled.

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:= 11.1.1.7.0= 11.1.1.9.0= 12.1.3.0.0= 12.2.1.1.0= 12.2.1.2.0
Ubuntu LinuxOperating system
Affected:= 12.04= 12.10= 13.04= 13.10
FirefoxWeb browser
Affected:< 17.0.11< 25.0.1>= 24.1.0, < 24.1.1
Communications Application Session ControllerApplication
Affected:>= 3.0.0, <= 3.9.1
Integrated Lights Out Manager FirmwareOperating system
Affected:>= 3.0.0, <= 3.2.11>= 4.0.0, <= 4.0.4
Sparc Enterprise M3000 FirmwareOperating system
Affected:>= xcp, < xcp_1121
Sparc Enterprise M4000 FirmwareOperating system
Affected:>= xcp, < xcp_1121
Sparc Enterprise M5000 FirmwareOperating system
Affected:>= xcp, < xcp_1121

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

CVSS:3.1/AV:N/AC:H/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 TLS/SSL services accepting RC4 cipher suites
    Scan SSL/TLS endpoints using tools like nmap with ssl-enum-ciphers script or testssl.sh to list enabled cipher suites. Look for cipher strings containing RC4, such as RC4-SHA, RC4-MD5, or EXP-RC4-MD5.
    Affected if RC4-based cipher suites appear in the list of enabled ciphers for any TLS/SSL service
  2. Check Oracle HTTP Server SSL configuration
    Examine the SSL configuration files (typically in $ORACLE_HOME/ohs/conf/ssl.conf or mod_ssl configuration). Search for SSLCipherSuite or SSLProtocol directives that include RC4-related cipher strings.
    Affected if The cipher configuration includes RC4 variants such as RC4-SHA, RC4-MD5, EXP-RC4-MD5, or wildcard patterns matching RC4 ciphers
  3. Verify Mozilla Firefox version
    In Firefox, navigate to Help > About Firefox to display the version number. Alternatively, check the package version on systems where Firefox is installed via package management.
    Affected if The installed version is less than 17.0.11, or between 24.0.0 and 24.1.0 inclusive, or equals 25.0.0 (all versions before 25.0.1 and before 24.1.1 are affected)
  4. Check Ubuntu Linux OpenSSL/libssl version
    Run `openssl version` and `dpkg -l | grep libssl` to identify the installed OpenSSL library version. For Ubuntu 12.04-13.10, the base OpenSSL version shipped with those releases contains RC4 by default.
    Affected if The system runs Ubuntu 12.04, 12.10, 13.04, or 13.10 with default SSL libraries that enable RC4 cipher suites in client and server configurations
  5. Verify Oracle product versions
    For Oracle HTTP Server, run `opmnctl status -verbose` or check the installation inventory. For Oracle Communications Application Session Controller and ILOM, use the product-specific version command or check the management interface for firmware/software version.
    Affected if The installed version matches 11.1.1.7.0, 11.1.1.9.0, 12.1.3.0.0, 12.2.1.1.0, 12.2.1.2.0 (OHS); 3.0.0 through 3.9.1 (ASC); 3.0.0 through 3.2.11 or 4.0.0 through 4.0.4 (ILOM)
  6. Check Fujitsu Sparc Enterprise firmware version
    Access the system controller via ILOM or SC console and execute version commands (such as `showrev` or firmware version display) to identify the xcp firmware revision.
    Affected if The firmware revision is >= xcp and < xcp_1121 on M3000, M4000, or M5000 systems

A system is affected if RC4 cipher suites are enabled in any TLS/SSL configuration OR if the product version exactly matches one of the listed affected versions, regardless of cipher configuration.

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 17.0.11 / 24.1.1 / 25.0.1 or later
Fixed in 17.0.1124.1.125.0.1
Interim mitigation

Disable RC4 cipher suites in all TLS/SSL configurations and ensure only modern, secure cipher suites (such as AES-based ciphers) are enabled.

Fix this in HTTP 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 the upgrade done

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-2013-2566 — 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-2013-2566 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