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

> Remote attackers can trigger a buffer overflow in the DOMjudge submit daemon, causing denial of service or unspecified impacts.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jrpj-fwwj-f68f

## What is CVE-2007-2977?

CVE-2007-2977 is a high-severity memory corruption vulnerability in n/a, published on 1 Jun 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the receive function in submit/submitcommon.c in the submit daemon in DOMjudge before 2.0.0RC1 allows remote attackers to cause a denial of service or have other unspecified impact.  NOTE: some of these details are obtained from third party information.

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

It affects 1 product.


Products: Domjudge Domjudge.

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

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

## Is CVE-2007-2977 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2977 is a high-severity memory corruption vulnerability in n/a, published on 1 Jun 2007. 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-2977 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-2977/ (Markdown: https://insights.sbomify.com/CVE-2007-2977/index.md)
```

## Sources

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

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