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

> Remote attackers can cause a denial of service in NuFW via a heap-based buffer overflow in the SASL authentication module.

- **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:** Yes
- **Published:** 30 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DTSA-82-1, GHSA-hv7f-x5m2-phcj

## What is CVE-2007-5723?

CVE-2007-5723 is a medium-severity memory corruption vulnerability in n/a, published on 30 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in the samp_send function in nuauth/sasl.c in NuFW before 2.2.7 allows remote attackers to cause a denial of service via unspecified input on which base64 encoding is performed. NOTE: some of these details are obtained from third party information.

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

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

It affects 1 product.


Products: Nufw Nufw.

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

Upgrade to a fixed version.

## Is CVE-2007-5723 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3950](https://insights.sbomify.com/CVE-2005-3950/): nuauth in NuFW 1.0.x before 1.0.16 and 1.1 allows authenticated users to cause a denial of service via malformed packets. (medium 6.8)
- [CVE-2007-4461](https://insights.sbomify.com/CVE-2007-4461/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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