dbcve.org
CyasslApplication · Yassl

CVE-2014-2899

MEDIUM · 5.0 CVSS v2.0 Published 2014-04-22
Fix available
A fix is available. Upgrade to after 2.9.0 or later.
See remediation →
59/100
Remediation priority · Elevated
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
wolfSSL CyaSSL before 2.9.4 allows remote attackers to cause a denial of service (NULL pointer dereference) via (1) a request for the peer certificate when a certificate parsing failure occurs or (2) a client_key_exchange message when the ephemeral key is not found.

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

wolfSSL CyaSSL before 2.9.4 contains a NULL pointer dereference vulnerability that can be triggered remotely during TLS handshakes. When certificate parsing fails during a peer certificate request, or when an ephemeral key cannot be found during client_key_exchange processing, the library attempts to dereference a NULL pointer, causing a denial of service condition.

MitigationUpgrade wolfSSL CyaSSL to version 2.9.4 or later. Additionally, ensure proper certificate validation and key exchange handling is in place before upgrading to prevent triggering the vulnerable code paths.

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
CyasslApplication
Affected:<= 2.9.0= 0.2.0= 0.3.0= 0.4.0= 0.5.0= 0.5.5= 0.6.0= 0.6.2= 0.6.3= 0.8.0= 0.9.0= 0.9.6

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
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 if wolfSSL or CyaSSL is installed
    Run `wolfssl version` or `cyassl version` or check package manager: `dpkg -l | grep -i wolfssl`, `rpm -qa | grep -i wolfssl`, or look for library files like `libwolfssl.so` or `libcyassl.so` in `/usr/lib/` or `/usr/local/lib/`
    Affected if wolfSSL or CyaSSL library is present in the system
  2. Determine installed version
    Run `wolfssl version` or `cyassl version` command. If not available, check dynamic library version: `ldd /path/to/binary | grep -i wolfssl` or examine library file metadata
    Affected if Version returned is 2.9.0 or lower, or exactly matches any of these: 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.5.5, 0.6.0, 0.6.2, 0.6.3, 0.8.0, 0.9.0, 0.9.6
  3. Verify TLS server or client is in use
    Inspect application configuration or running services that use wolfSSL for TLS. Check configuration files for TLS-enabled services or examine process list for TLS-aware applications linked against wolfSSL
    Affected if Any application uses wolfSSL for TLS server or client functionality, enabling the handshake code path where the vulnerability triggers
  4. Confirm client certificate authentication is enabled (one trigger condition)
    Check TLS configuration for `CA` or `client_cert` options, or examine code that calls `SetCA` or loads client certificates. In wolfSSL, this involves `InitSSL`, `LoadCA`, or `UseCertificate` functions with client certificate settings
    Affected if TLS client certificate authentication is configured, allowing the certificate parsing failure code path to be reached
  5. Confirm ephemeral key exchange is used (alternative trigger condition)
    Check TLS configuration for DHE or ECDHE cipher suites (e.g., DHE-RSA-AES*, ECDHE-*) or examine code using `SetTempDH`, `SetTmpDH`, or ECC curve settings
    Affected if Ephemeral key exchange (DHE/ECDHE) is enabled, allowing the missing ephemeral key code path to be reached

A system is affected if it runs any version of wolfSSL/CyaSSL matching <= 2.9.0 or the listed specific versions AND actively uses TLS with client certificates or ephemeral key exchange enabled.

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 2.9.0
Interim mitigation

Upgrade wolfSSL CyaSSL to version 2.9.4 or later. Additionally, ensure proper certificate validation and key exchange handling is in place before upgrading to prevent triggering the vulnerable code paths.

Fix this in Cyassl Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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