# CVE-2017-6658: Cisco Sourcefire Snort 3.0 before build 233 has a Buffer Overread related to use of a decoder array.


- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 16 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7mxj-982j-3px6

## What is CVE-2017-6658?

CVE-2017-6658 is a high-severity vulnerability in Snort 3.0 All versions prior to build 233., published on 16 May 2017. 

### Official description

Cisco Sourcefire Snort 3.0 before build 233 has a Buffer Overread related to use of a decoder array. The size was off by one making it possible to read past the end of the array with an ether type of 0xFFFF. Increasing the array size solves this problem.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2017-6658?

It affects 1 product.


Products: Cisco Sourcefire Snort.

## How do I fix CVE-2017-6658?

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

## Is CVE-2017-6658 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6658 and fix it if it is affected.

What it is: CVE-2017-6658 is a high-severity vulnerability in Snort 3.0 All versions prior to build 233., published on 16 May 2017. 
Exploitation: There is no known exploitation of CVE-2017-6658 in the wild and no public exploit code.

Affected product: Snort 3.0 All versions prior to build 233.. 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-2017-6658/ (Markdown: https://insights.sbomify.com/CVE-2017-6658/index.md)
```

## Sources

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

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