# CVE-2013-5919: Denial of service in n/a

> Remote attackers can crash Suricata by sending a malformed SSL record, requiring an upgrade to mitigate the denial of service.

- **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:** Yes
- **Published:** 30 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-5919, GHSA-7h5g-v8pf-26hq

## What is CVE-2013-5919?

CVE-2013-5919 is a medium-severity denial of service vulnerability in Oisf Suricata, published on 30 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Suricata before 1.4.6 allows remote attackers to cause a denial of service (crash) via a malformed SSL record.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-5919?

It affects 2 products.


Products: Oisf Suricata, Openinfosecfoundation Suricata.

## How do I fix CVE-2013-5919?

Upgrade to a fixed version.

## Is CVE-2013-5919 being exploited?

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

## Other vulnerabilities in Oisf Suricata

- [CVE-2023-35853](https://insights.sbomify.com/CVE-2023-35853/): Code injection in n/a (critical 9.8)
- [CVE-2021-37592](https://insights.sbomify.com/CVE-2021-37592/): Other in n/a (critical 9.8)
- [CVE-2018-10244](https://insights.sbomify.com/CVE-2018-10244/): Integer overflow in n/a (critical 9.8)
- [CVE-2026-94083](https://insights.sbomify.com/CVE-2026-94083/): Memory corruption in Suricata (critical 9.4)
- [CVE-2026-94084](https://insights.sbomify.com/CVE-2026-94084/): Use after free in Suricata (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5919 and fix it if it is affected.

What it is: CVE-2013-5919 is a medium-severity denial of service vulnerability in Oisf Suricata, published on 30 May 2014. 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-2013-5919 in the wild and no public exploit code.

Affected product: Oisf Suricata. 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-2013-5919/ (Markdown: https://insights.sbomify.com/CVE-2013-5919/index.md)
```

## Sources

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

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