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

> Buffer overflow in libsrtp affects Ingate Firewall and SIParator, with unknown impact and attack vectors.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 22 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7cpw-g28r-26j6

## What is CVE-2007-6092?

CVE-2007-6092 is a critical memory corruption vulnerability in n/a, published on 22 Nov 2007. 

### Official description

Buffer overflow in libsrtp in Ingate Firewall before 4.6.0 and SIParator before 4.6.0 has unknown impact and attack vectors.  NOTE: it is not clear whether this issue crosses privilege boundaries.

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

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

It affects 2 products.


Products: Ingate Ingate Firewall, Ingate Ingate Siparator.

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

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

## Is CVE-2007-6092 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6097](https://insights.sbomify.com/CVE-2007-6097/): Other in n/a (critical 10.0)
- [CVE-2007-6099](https://insights.sbomify.com/CVE-2007-6099/): Security feature bypass in n/a (critical 10.0)
- [CVE-2007-6098](https://insights.sbomify.com/CVE-2007-6098/): Information disclosure in n/a (high 7.5)
- [CVE-2003-1112](https://insights.sbomify.com/CVE-2003-1112/): Denial of service in n/a (high 7.5)
- [CVE-2007-6093](https://insights.sbomify.com/CVE-2007-6093/): Denial of service in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6092 is a critical memory corruption vulnerability in n/a, published on 22 Nov 2007. 
Exploitation: There is no known exploitation of CVE-2007-6092 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-6092/ (Markdown: https://insights.sbomify.com/CVE-2007-6092/index.md)
```

## Sources

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

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