What is CVE-2023-42447?

CVE-2023-42447 is a high-severity security vulnerability in blurhash (rust), affecting versions = 0.1.1. It is fixed in 0.2.0.

How severe is CVE-2023-42447?

CVE-2023-42447 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of blurhash are affected by CVE-2023-42447?

blurhash (rust) versions = 0.1.1 is affected.

Is there a fix for CVE-2023-42447?

Yes. CVE-2023-42447 is fixed in 0.2.0. Upgrade to this version or later.

Is CVE-2023-42447 exploitable, and should I be worried?

Whether CVE-2023-42447 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-42447 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2023-42447?

Upgrade blurhash to 0.2.0 or later.

CVE-2023-42447 in blurhash

Summary

blurhash panics on parsing crafted inputs

Workarounds

n.a.

References

n.a.

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

CVE-2023-42447 has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.2.0); upgrading removes the vulnerable code path.

Affected versions

blurhash (= 0.1.1)

Security releases

blurhash → 0.2.0 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2023-42447? CVE-2023-42447 is a high-severity security vulnerability in blurhash (rust), affecting versions = 0.1.1. It is fixed in 0.2.0.
How severe is CVE-2023-42447? CVE-2023-42447 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of blurhash are affected by CVE-2023-42447? blurhash (rust) versions = 0.1.1 is affected.
Is there a fix for CVE-2023-42447? Yes. CVE-2023-42447 is fixed in 0.2.0. Upgrade to this version or later.
Is CVE-2023-42447 exploitable, and should I be worried? Whether CVE-2023-42447 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-42447 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-42447? Upgrade blurhash to 0.2.0 or later.