Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-cxvp-82cq-57h2: blurhash panics on parsing crafted inputs

Impact

The blurhash parsing code may panic due to multiple panic-guarded out-of-bounds accesses on untrusted input.

In a typical deployment, this may get triggered by feeding a maliciously crafted blurhashes over the network. These may include:

  • UTF-8 compliant strings containing multi-byte UTF-8 characters

Patches

The patches will be released under version 0.2.0, which requires user intervention because of slight API churn.

Workarounds

n.a.

References

n.a.

ghsa
#git

Package

cargo blurhash (Rust)

Affected versions

= 0.1.1

Patched versions

0.2.0

Description

Impact

The blurhash parsing code may panic due to multiple panic-guarded out-of-bounds accesses on untrusted input.

In a typical deployment, this may get triggered by feeding a maliciously crafted blurhashes over the network. These may include:

  • UTF-8 compliant strings containing multi-byte UTF-8 characters

Patches

The patches will be released under version 0.2.0, which requires user intervention because of slight API churn.

Workarounds

n.a.

References

n.a.

References

  • GHSA-cxvp-82cq-57h2
  • https://nvd.nist.gov/vuln/detail/CVE-2023-42447
  • https://github.com/whisperfish/blurhash-rs/releases/tag/v0.2.0

rubdos published to whisperfish/blurhash-rs

Sep 19, 2023

Published to the GitHub Advisory Database

Sep 21, 2023

Reviewed

Sep 21, 2023

Last updated

Sep 21, 2023

Related news

CVE-2023-42447: panic on parsing crafted blurhash inputs

blurhash-rs is a pure Rust implementation of Blurhash, software for encoding images into ASCII strings that can be turned into a gradient of colors representing the original image. In version 0.1.1, the blurhash parsing code may panic due to multiple panic-guarded out-of-bounds accesses on untrusted input. In a typical deployment, this may get triggered by feeding a maliciously crafted blurhashes over the network. These may include UTF-8 compliant strings containing multi-byte UTF-8 characters. A patch is available in version 0.2.0, which requires user intervention because of slight API churn. No known workarounds are available.