# CVE-2007-6103: Denial of service in n/a

> Remote attackers can crash the I Hear U server or cause an infinite loop by sending malformed packets with zero size or missing mode fields.

- **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:** 23 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7fv3-c8f2-2c73

## What is CVE-2007-6103?

CVE-2007-6103 is a medium-severity denial of service vulnerability in n/a, published on 23 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

I Hear U (IHU) 0.5.6 and earlier allows remote attackers to cause (1) a denial of service (infinite loop) via a packet that contains zero in the size field in its header, which is improperly handled by the Receiver::processPacket function; and (2) a denial of service (daemon crash) via an (a) IHU_INFO_INIT or a (b) IHU_INFO_RING packet that does not specify the mode, which is improperly handled by the Player::ring function in Player.cpp.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Ihu I Hear U.

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

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

## Is CVE-2007-6103 being exploited?

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

Public exploit code:

- I Hear U 0.5.6 - Multiple Remote Denial of Service Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6103 is a medium-severity denial of service vulnerability in n/a, published on 23 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6103 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-6103/ (Markdown: https://insights.sbomify.com/CVE-2007-6103/index.md)
```

## Sources

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

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