OSV-2021-1745 Heap-buffer-overflow in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch

Not scored Published

A heap buffer overflow in the SMILES parser allows attackers to cause a denial of service via crafted input.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Not stated
Victim action needed
Not needed
Fix
None listed

What is OSV-2021-1745?

OSV-2021-1745 is a memory corruption vulnerability in rdkit, published on 24 Dec 2021.

Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=42862

Crash type: Heap-buffer-overflow READ 1
Crash state:
std::__1::basic_string&lt;char, std::__1::char_traits&lt;char&gt;, std::__1::allocator&lt;ch
bool SmilesParseOps::parser::parse_data_sgroup&lt;std::__1::__wrap_iter&lt;char const*
bool SmilesParseOps::parser::parse_it&lt;std::__1::__wrap_iter&lt;char const*&gt; &gt;

Which versions are affected by OSV-2021-1745?

1 open source package ship an affected version, including rdkit.

PackageAffectedFixed in
rdkit OSS-FuzzAll versionsNone

How do I fix OSV-2021-1745?

No fix has been published for OSV-2021-1745 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-2021-1745 being exploited?

There is no known exploitation of OSV-2021-1745 in the wild and no public exploit code.

Sources

Is OSV-2021-1745 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free