# CVE-2017-7578: Memory corruption in n/a

> Remote attackers can cause denial of service or potential code execution via crafted SWF files due to heap-based buffer overflows in libming.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 7 Apr 2017
- **Updated:** 16 Sep 2024
- **Also known as:** DLA-890-1, GHSA-vc5w-cv6h-7r49, MGASA-2017-0108, UBUNTU-CVE-2017-7578

## What is CVE-2017-7578?

CVE-2017-7578 is a high-severity memory corruption vulnerability in Libming Libming, published on 7 Apr 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

Multiple heap-based buffer overflows in parser.c in libming 0.4.7 allow remote attackers to cause a denial of service (listswf application crash) or possibly have unspecified other impact via a crafted SWF file. NOTE: this issue exists because of an incomplete fix for CVE-2016-9831.

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

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

It affects 1 product.


Products: Libming Libming.

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

Apply the vendor's patch.

## Is CVE-2017-7578 being exploited?

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

## Other vulnerabilities in Libming Libming

- [CVE-2023-50628](https://insights.sbomify.com/CVE-2023-50628/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-11894](https://insights.sbomify.com/CVE-2020-11894/): Memory corruption in n/a (critical 9.1)
- [CVE-2020-11895](https://insights.sbomify.com/CVE-2020-11895/): Memory corruption in n/a (critical 9.1)
- [CVE-2019-16705](https://insights.sbomify.com/CVE-2019-16705/): Information disclosure in n/a (critical 9.1)
- [CVE-2023-36239](https://insights.sbomify.com/CVE-2023-36239/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7578 is a high-severity memory corruption vulnerability in Libming Libming, published on 7 Apr 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-7578 in the wild and no public exploit code.

Affected product: Libming Libming. 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-7578/ (Markdown: https://insights.sbomify.com/CVE-2017-7578/index.md)
```

## Sources

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

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