# CVE-2013-5680: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via a heap-based buffer overflow in HylaFAX+ when LDAP authentication is enabled.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-429p-2j54-mp97

## What is CVE-2013-5680?

CVE-2013-5680 is a medium-severity memory corruption vulnerability in n/a, published on 6 Apr 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Heap-based buffer overflow in hfaxd in HylaFAX+ 5.2.4 through 5.5.3, when using LDAP authentication, might allow remote attackers to cause a denial of service (child hang) or execute arbitrary code via a long USER command.

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

## Which versions are affected by CVE-2013-5680?

It affects 1 product.


Products: Lee Howard Hylafax\+.

## How do I fix CVE-2013-5680?

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

## Is CVE-2013-5680 being exploited?

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

Public exploit code:

- HylaFAX+ 5.2.4 > 5.5.3 - Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5680 and fix it if it is affected.

What it is: CVE-2013-5680 is a medium-severity memory corruption vulnerability in n/a, published on 6 Apr 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-5680 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-2013-5680/ (Markdown: https://insights.sbomify.com/CVE-2013-5680/index.md)
```

## Sources

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

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