# CVE-2018-9158: Denial of service in n/a

> An attacker can cause a denial of service on AXIS M1033-W IP cameras by performing an IPv4 flood attack, interrupting services.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cp95-cgwv-24g5

## What is CVE-2018-9158?

CVE-2018-9158 is a high-severity denial of service vulnerability in n/a, published on 1 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on AXIS M1033-W (IP camera) Firmware version 5.40.5.1 devices. They don't employ a suitable mechanism to prevent a DoS attack, which leads to a response time delay. An attacker can use the hping3 tool to perform an IPv4 flood attack, and the services are interrupted from attack start to end.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-9158?

It affects 1 product.


Products: Axis M1033-W Firmware.

## How do I fix CVE-2018-9158?

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

## Is CVE-2018-9158 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-9157](https://insights.sbomify.com/CVE-2018-9157/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-9158 and fix it if it is affected.

What it is: CVE-2018-9158 is a high-severity denial of service vulnerability in n/a, published on 1 Apr 2018. 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-2018-9158 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-2018-9158/ (Markdown: https://insights.sbomify.com/CVE-2018-9158/index.md)
```

## Sources

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

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