# CVE-2012-1558: Null dereference in n/a

> Remote attackers can crash the application via a crafted X.509 certificate due to a NULL pointer dereference in the SSL library.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cxcp-gx6w-9hj9

## What is CVE-2012-1558?

CVE-2012-1558 is a medium-severity vulnerability in n/a, published on 12 Mar 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

yaSSL CyaSSL before 2.0.8 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted X.509 certificate.

Weakness: CWE-399

## Which versions are affected by CVE-2012-1558?

It affects 1 product.


Products: Yassl Cyassl.

## How do I fix CVE-2012-1558?

No fix has been published for CVE-2012-1558 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-1558 being exploited?

There is no known exploitation of CVE-2012-1558 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-2900](https://insights.sbomify.com/CVE-2014-2900/): Security feature bypass in n/a (medium 5.8)
- [CVE-2014-2899](https://insights.sbomify.com/CVE-2014-2899/): Null dereference in n/a (medium 5.0)
- [CVE-2013-1623](https://insights.sbomify.com/CVE-2013-1623/): The TLS and DTLS implementations in wolfSSL CyaSSL before 2.5.0 do not properly consider timing side-channel attacks on a noncompliant MAC c (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1558 and fix it if it is affected.

What it is: CVE-2012-1558 is a medium-severity vulnerability in n/a, published on 12 Mar 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-1558 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-1558/ (Markdown: https://insights.sbomify.com/CVE-2012-1558/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-1558
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-1558
- OSV: https://osv.dev/vulnerability/CVE-2012-1558

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-1558/
Summaries are generated and may contain mistakes; the official description above is the record.