# CVE-2007-6628: Null dereference in n/a

> Remote attackers can crash the Feng RTSP server via malformed Transport or Range headers, causing a 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:** No
- **Published:** 4 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xw5r-6r86-qg74

## What is CVE-2007-6628?

CVE-2007-6628 is a medium-severity vulnerability in n/a, published on 4 Jan 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LScube Feng 0.1.15 and earlier allows remote attackers to cause a denial of service (NULL dereference and daemon crash) via (1) a malformed Transport header, which triggers misparsing in parse_transport_header in RTSP_setup.c, as demonstrated by a Transport header that contains only a "RTP/AVP;unicast;client_port" sequence; or (2) a malformed Range header, which triggers misparsing in parse_play_time_range in RTSP_Play, as demonstrated by an empty Range header.

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

It affects 1 product.


Products: Feng Feng.

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

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

## Is CVE-2007-6628 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6626](https://insights.sbomify.com/CVE-2007-6626/): Memory corruption in n/a (high 7.5)
- [CVE-2007-6627](https://insights.sbomify.com/CVE-2007-6627/): Integer overflow in n/a (high 7.5)
- [CVE-2007-6629](https://insights.sbomify.com/CVE-2007-6629/): Null dereference in n/a (medium 5.0)
- [CVE-2007-6630](https://insights.sbomify.com/CVE-2007-6630/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6628 is a medium-severity vulnerability in n/a, published on 4 Jan 2008. 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-2007-6628 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-2007-6628/ (Markdown: https://insights.sbomify.com/CVE-2007-6628/index.md)
```

## Sources

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

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