CVE-2017-11549 The play_midi function in playmidi.c in TiMidity++ 2.14.0 allows remote attackers to cause a denial of service (large loop and CPU consumpti
Medium 5.5
Published
Updated
Check this codebase for CVE-2017-11549 and fix it if it is affected.
What it is: CVE-2017-11549 is a medium-severity vulnerability in n/a, published on 31 Jul 2017.
Exploitation: There is no known exploitation of CVE-2017-11549 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-11549/ (Markdown: https://insights.sbomify.com/CVE-2017-11549/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2017-11549?
CVE-2017-11549 is a medium-severity vulnerability in n/a, published on 31 Jul 2017.
Official description
The play_midi function in playmidi.c in TiMidity++ 2.14.0 allows remote attackers to cause a denial of service (large loop and CPU consumption) via a crafted mid file. NOTE: CPU consumption might be relevant when using the --background option.
Weakness: CWE-834
Which versions are affected by CVE-2017-11549?
It affects 1 product.
Products include Timidity\+\+ Project Timidity\+\+.
How do I fix CVE-2017-11549?
No fix has been published for CVE-2017-11549 yet. Limit exposure of the affected software until one is available.
Is CVE-2017-11549 being exploited?
There is no known exploitation of CVE-2017-11549 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as DEBIAN-CVE-2017-11549, GHSA-4h87-8v24-9f5c, UBUNTU-CVE-2017-11549.