dbcve.org
Java Enterprise SystemApplication · Sun

CVE-2006-3127

HIGH · 7.8 CVSS v2.0 Published 2006-06-21
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
Memory leak in Network Security Services (NSS) 3.11, as used in Sun Java Enterprise System 2003Q4 through 2005Q1 and Java System Directory Server 5.2, allows remote attackers to cause a denial of service (memory consumption) by performing a large number of RSA cryptographic operations.

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

Memory leak in Network Security Services (NSS) 3.11 allows remote attackers to cause denial of service via memory consumption by performing a large number of RSA cryptographic operations. The vulnerability affects Sun Java Enterprise System 2003Q4 through 2005Q1 and Java System Directory Server 5.2.

MitigationUpgrade NSS to a patched version (3.11.3 or later) and validate compatibility with dependent applications. For legacy systems where upgrading may be difficult, consider rate-limiting or restricting RSA operations from untrusted sources.

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
Java Enterprise SystemApplication
Affected:= 2003q4= 2004q2= 2005q1
Java System Directory ServerApplication
Affected:= 5.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. Check NSS library version
    Run 'nsstrace -version' or check the NSS library file version. On Unix systems, examine libnsspem.so or nss3.so in the /usr/lib or /opt/nss/lib directory using 'ls -la' and check the file version properties.
    Affected if Version is 3.11.x (any minor release) or earlier
  2. Identify Sun Java Enterprise System version
    Check the installed Sun Java Enterprise System version by examining the product metadata in /var/sadm/pkg/ or using 'productregistry' command if available, or check /etc/release for system version information.
    Affected if Version equals 2003q4, 2004q2, or 2005q1
  3. Identify Sun Java System Directory Server version
    Run 'dsadm --version' or check the Directory Server installation path typically under /opt/SUNWdsee/ and examine the version file, or query the directory server instance for its version number.
    Affected if Version equals 5.2 specifically
  4. Verify RSA operations are network-exposed
    Examine the Directory Server or application configuration for SSL/TLS listener ports (typically 389, 636, 8443) and check whether LDAP or LDAPS services are bound to network interfaces accessible from untrusted sources.
    Affected if RSA-based SSL/TLS or LDAP services are listening on interfaces accessible to remote/untrusted clients
  5. Monitor memory consumption during RSA operations
    Use system monitoring tools (top, ps, vmstat) to observe the memory usage of the NSS-related processes (like ns-slapd for Directory Server) during periods of heavy RSA cryptographic activity.
    Affected if Process memory grows continuously without releasing during repeated SSL/TLS handshakes or RSA operations

The environment is affected if NSS version 3.11.x is in use AND the system is Sun Java Enterprise System 2003Q4/2004Q2/2005Q1 or Sun Java System Directory Server 5.2, with RSA operations exposed to network access.

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

Upgrade NSS to a patched version (3.11.3 or later) and validate compatibility with dependent applications. For legacy systems where upgrading may be difficult, consider rate-limiting or restricting RSA operations from untrusted sources.

Fix this in Java Enterprise System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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