OSV-2017-126 Bad-cast to const std::__1::__less<unsigned long, unsigned long> *_start
Not scored
Published
Check this codebase for OSV-2017-126 and fix it if it is affected.
What it is: OSV-2017-126 is a vulnerability in libtsm, published on 15 Jan 2021.
Exploitation: There is no known exploitation of OSV-2017-126 in the wild and no public exploit code.
Affected packages and fixed versions:
- libtsm (OSS-Fuzz): affected all versions; no fix listed
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/OSV-2017-126/ (Markdown: https://insights.sbomify.com/OSV-2017-126/index.md)
A bad cast error in the C++ standard library can cause a crash, potentially leading to denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is OSV-2017-126?
OSV-2017-126 is a vulnerability in libtsm, published on 15 Jan 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=606
Crash type: Bad-cast
Crash state:
Bad-cast to const std::__1::__less<unsigned long, unsigned long> *_start
Which versions are affected by OSV-2017-126?
1 open source package ship an affected version, including libtsm.
| Package | Affected | Fixed in |
|---|---|---|
libtsm OSS-Fuzz | All versions | None |
How do I fix OSV-2017-126?
No fix has been published for OSV-2017-126 yet. Limit exposure of the affected software until one is available.
Is OSV-2017-126 being exploited?
There is no known exploitation of OSV-2017-126 in the wild and no public exploit code.