# CVE-2015-8954: Security feature bypass in n/a

> Remote attackers can bypass intrusion-prevention functionality in Suricata via crafted HTTP requests due to improper byte comparison logic.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-8954, GHSA-m68q-w483-4j98

## What is CVE-2015-8954?

CVE-2015-8954 is a critical vulnerability in n/a, published on 20 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MemcmpLowercase function in Suricata before 2.0.6 improperly excludes the first byte from comparisons, which might allow remote attackers to bypass intrusion-prevention functionality via a crafted HTTP request.

Weakness: CWE-264

## Which versions are affected by CVE-2015-8954?

It affects 1 product.


Products: Openinfosecfoundation Suricata.

## How do I fix CVE-2015-8954?

Upgrade to a fixed version.

## Is CVE-2015-8954 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-15377](https://insights.sbomify.com/CVE-2017-15377/): Denial of service in n/a (high 7.5)
- [CVE-2017-7177](https://insights.sbomify.com/CVE-2017-7177/): Suricata before 3.2.1 has an IPv4 defragmentation evasion issue caused by lack of a check for the IP protocol during fragment matching. (high 7.5)
- [CVE-2014-6603](https://insights.sbomify.com/CVE-2014-6603/): The SSHParseBanner function in SSH parser (app-layer-ssh.c) in Suricata before 2.0.4 allows remote attackers to bypass SSH rules, cause a de (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8954 and fix it if it is affected.

What it is: CVE-2015-8954 is a critical vulnerability in n/a, published on 20 Mar 2017. 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-2015-8954 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-2015-8954/ (Markdown: https://insights.sbomify.com/CVE-2015-8954/index.md)
```

## Sources

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

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