OSV-2018-417 UNKNOWN READ in boost::sub_match<std::__1::__wrap_iter<char const*> >::sub_match
Not scored
Published
Check this codebase for OSV-2018-417 and fix it if it is affected.
What it is: OSV-2018-417 is a memory corruption vulnerability in boost, published on 15 Jan 2021.
Exploitation: There is no known exploitation of OSV-2018-417 in the wild and no public exploit code.
Affected packages and fixed versions:
- boost (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-2018-417/ (Markdown: https://insights.sbomify.com/OSV-2018-417/index.md)
An unknown read vulnerability in Boost regex matching can cause application crashes, requiring a patch to ensure stability.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2018-417?
OSV-2018-417 is a memory corruption vulnerability in boost, published on 15 Jan 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9539
Crash type: UNKNOWN READ
Crash state:
boost::sub_match<std::__1::__wrap_iter<char const*> >::sub_match
_ZNSt3__16vectorIN5boost9sub_matchINS_11__wrap_iterIPKcEEEENS_9allocatorIS7_EEE1
boost::match_results<std::__1::__wrap_iter<char const*>, std::__1::allocator<boo
Which versions are affected by OSV-2018-417?
1 open source package ship an affected version, including boost.
| Package | Affected | Fixed in |
|---|---|---|
boost OSS-Fuzz | All versions | None |
How do I fix OSV-2018-417?
No fix has been published for OSV-2018-417 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is OSV-2018-417 being exploited?
There is no known exploitation of OSV-2018-417 in the wild and no public exploit code.