CVE-2005-3087: The SecureW2 3.0 TLS implementation uses weak random number generators (rand and srand from system time) durin

Routine

MEDIUM 5.0DOWNGRADE

CVE-2005-3087 is a medium-severity flaw (CVSS 5.0) affecting securew2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The SecureW2 3.0 TLS implementation uses weak random number generators (rand and srand from system time) during generation of the pre-master secret (PMS), which makes it easier for attackers to guess the secret and decrypt sensitive data.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	1.0% (top 37%)
CISA exploited list	No
Published	2005-09-27
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: securew2

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-09-27 20:03 UTCPublished CVE record published
2026-06-16 22:16 UTCUpdated Record last modified

securew2 securew2 DOWNGRADE

Affected: 3.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.0

1. Check installed version

apt-cache policy securew2 || rpm -q securew2 || securew2 --version

2. No fixed release: DOWNGRADE to a release before 3.0 (Debian / Ubuntu)

apt-cache madison securew2 sudo apt install securew2=<VERSION_BEFORE_3.0> sudo apt-mark hold securew2

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list securew2 sudo dnf downgrade securew2-<VERSION_BEFORE_3.0> sudo dnf versionlock add securew2

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-3087?

securew2: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-3087 being exploited?

CVE-2005-3087 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-3087 affect?

CVE-2005-3087 affects securew2. Severity is medium (CVSS 5.0). The SecureW2 3.0 TLS implementation uses weak random number generators (rand and srand from system time) during generation of the pre-master secret (PMS), which makes it easier for attackers to guess the secret and decrypt sensitive data.

How urgent is CVE-2005-3087?

Priority 33/100. No elevated risk signals yet.

References

← Back to latest CVEs