Traffix Signaling Delivery ControllerApplication · F5
CVE-2015-5738
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 · uneditedThe RSA-CRT implementation in the Cavium Software Development Kit (SDK) 2.x, when used on OCTEON II CN6xxx Hardware on Linux to support TLS with Perfect Forward Secrecy (PFS), makes it easier for remote attackers to obtain private RSA keys by conducting a Lenstra side-channel attack.
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 confidenceA side-channel vulnerability (Lenstra attack) in the RSA-CRT implementation within Cavium SDK 2.x on OCTEON II CN6xxx hardware allows remote attackers to extract private RSA keys used in TLS connections with Perfect Forward Secrecy. The vulnerability exploits timing or cache side-channel leakage in the cryptographic operation.
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
Traffix Signaling Delivery ControllerApplication
>= 3.3.2, <= 3.5.1>= 4.0.0, <= 4.4.0= 2.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify F5 Traffix SDC versionCheck system version via 'show system info' or review /etc/version file; compare against affected ranges: 3.3.2-3.5.1 or 4.0.0-4.4.0Affected if Installed version falls within any listed range
-
Identify Marvell SDK versionCheck installed Cavium SDK version via 'dpkg -l | grep -i cavium' or review SDK release notes; affected version is exactly 2.0Affected if Cavium SDK version is exactly 2.0
-
Verify OCTEON II CN6xxx hardwareCheck hardware platform via 'cat /proc/cpuinfo' or 'lspci' looking for Cavium OCTEON II CN6xxx processorAffected if System uses OCTEON II CN6xxx hardware platform
-
Confirm RSA-CRT key usageReview SSL/TLS configuration and check for RSA key pairs in use; verify keys were generated or imported into the systemAffected if RSA keys are loaded and active on the affected hardware/SDK version
-
Check TLS with PFS enabledReview TLS cipher suites configuration; check if ephemeral Diffie-Hellman (DHE/ECDHE) cipher suites are enabledAffected if TLS Perfect Forward Secrecy (PFS) cipher suites are enabled on affected version
System is affected if it runs F5 Traffix SDC within version 3.3.2-3.5.1 or 4.0.0-4.4.0, or uses Cavium SDK 2.0, on OCTEON II CN6xxx hardware with RSA-CRT keys and TLS PFS enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate or patch the Cavium SDK to a version that addresses the RSA-CRT side-channel vulnerability, and regenerate all RSA key pairs that may have been exposed on affected systems.
Fix this in Traffix Signaling Delivery Controller
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5738 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5738 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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