# CVE-2017-9130: Denial of service in n/a

> Remote attackers can cause a denial of service via a crafted WAV file due to an invalid memory read in the FAAC library.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-9130, GHSA-4vg3-jccf-v87h, UBUNTU-CVE-2017-9130

## What is CVE-2017-9130?

CVE-2017-9130 is a medium-severity denial of service vulnerability in n/a, published on 21 Jun 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The faacEncOpen function in libfaac/frame.c in Freeware Advanced Audio Coder (FAAC) 1.28 allows remote attackers to cause a denial of service (invalid memory read and application crash) via a crafted wav file.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2017-9130?

It affects 1 product.


Products: Freeware Advanced Audio Coder Project Freeware Advanced Audio Coder.

## How do I fix CVE-2017-9130?

Apply the vendor's patch.

## Is CVE-2017-9130 being exploited?

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

Public exploit code:

- Freeware Advanced Audio Coder (FAAC) 1.28 - Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9130 and fix it if it is affected.

What it is: CVE-2017-9130 is a medium-severity denial of service vulnerability in n/a, published on 21 Jun 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-9130 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-2017-9130/ (Markdown: https://insights.sbomify.com/CVE-2017-9130/index.md)
```

## Sources

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

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