OSV-2023-225 Heap-buffer-overflow in std::__1::enable_if<true, void>::type APFSBtreeNodeIterator<APFSBtreeNode<apfs_o

Not scored Published

A heap-buffer-overflow in the APFS B-tree iterator allows attackers to cause denial of service or potentially execute code via crafted filesystem images.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is OSV-2023-225?

OSV-2023-225 is a memory corruption vulnerability in sleuthkit, published on 24 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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

Crash type: Heap-buffer-overflow READ 2
Crash state:
std::__1::enable_if&lt;true, void&gt;::type APFSBtreeNodeIterator&lt;APFSBtreeNode&lt;apfs_o
APFSBtreeNodeIterator&lt;APFSBtreeNode&lt;apfs_omap_key, apfs_omap_value&gt; &gt;::APFSBtree
APFSBtreeNodeIterator&lt;APFSBtreeNode&lt;apfs_omap_key, apfs_omap_value&gt; &gt; APFSBtreeN

Which versions are affected by OSV-2023-225?

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

PackageAffectedFixed in
sleuthkit OSS-FuzzAll versionsNone

How do I fix OSV-2023-225?

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

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

Sources

Is OSV-2023-225 in your software?

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

Check your SBOMs for free