# CVE-2007-5036: Memory corruption in n/a

> Remote authenticated users can cause a denial of service in AirDefense Airsensor devices via buffer overflows in HTTPS requests.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-236p-2rjr-h84v

## What is CVE-2007-5036?

CVE-2007-5036 is a medium-severity memory corruption vulnerability in n/a, published on 24 Sep 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple buffer overflows in the AirDefense Airsensor M520 with firmware 4.3.1.1 and 4.4.1.4 allow remote authenticated users to cause a denial of service (HTTPS service outage) via a crafted query string in an HTTPS request to (1) adLog.cgi, (2) post.cgi, or (3) ad.cgi, related to the "files filter."

Weakness: CWE-20 (Improper Input Validation), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2007-5036?

It affects 1 product.


Products: Airdefense Airsensor.

## How do I fix CVE-2007-5036?

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

## Is CVE-2007-5036 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5036 exists.

Public exploit code:

- Airsensor M520 - HTTPd Remote Denial of Service / Buffer Overflow (PoC) (exploitdb)
- Airsensor M520 - HTTPd Unauthenticated Remote Denial of Service / Buffer Overflow (PoC) (github_poc): https://github.com/alt3kx/CVE-2007-5036

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5036 and fix it if it is affected.

What it is: CVE-2007-5036 is a medium-severity memory corruption vulnerability in n/a, published on 24 Sep 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5036 exists.

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-2007-5036/ (Markdown: https://insights.sbomify.com/CVE-2007-5036/index.md)
```

## Sources

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

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