muhammara

CVE-2022-39381

CVE-2022-39381 is a high-severity null pointer dereference vulnerability in muhammara (npm), affecting versions < 2.6.0. It is fixed in 2.6.0, 1.0.111.

Key facts
CVSS score
7.5
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
muhammara
Fixed in
2.6.0, 1.0.111
Disclosed
2022

Summary

Impact The package muhammara before 2.6.0; all versions of package hummus are vulnerable to Denial of Service (DoS) when supplied with a maliciously crafted PDF file to be appended to another. Patches It has been patched in 2.6.0 for muhammara and not at all for hummus Workarounds Do not process files from untrusted sources References PR: https://github.com/julianhille/MuhammaraJS/pull/194 Issue: https://github.com/julianhille/MuhammaraJS/issues/191 Issue in hummus: https://github.com/galkahana/HummusJS/issues/293 Outline differences to https://nvd.nist.gov/vuln/detail/CVE-2022-25892 The difference is one is in src/deps/PDFWriter/PDFParser.cpp and the other is PDFDocumentHandler.cpp both is a null pointer but for different cases These are totally diffent issues, one is in reading a pdf the other is in appendending a maliciously crafted one. The function calls are different the versions in which they are solved are diffent.

Impact

What is null pointer dereference?

The application dereferences a null pointer, causing a crash. Typical impact: denial of service via crash.

Severity and exposure

CVE-2022-39381 has a CVSS score of 7.5 (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 (2.6.0, 1.0.111). Upgrading removes the vulnerable code path.

Affected versions

npm

  • muhammara (< 2.6.0)
  • hummus (< 1.0.111)

Security releases

  • muhammara → 2.6.0 (npm)
  • hummus → 1.0.111 (npm)
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 instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2022-39381 is reachable in your applications. Explore open-source security for your team.

See if CVE-2022-39381 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2022-39381 in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade muhammara to 2.6.0 or later
  • Upgrade hummus to 1.0.111 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2022-39381

What is CVE-2022-39381?

CVE-2022-39381 is a high-severity null pointer dereference vulnerability in muhammara (npm), affecting versions < 2.6.0. It is fixed in 2.6.0, 1.0.111. The application dereferences a null pointer, causing a crash.

How severe is CVE-2022-39381?

CVE-2022-39381 has a CVSS score of 7.5 (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 packages are affected by CVE-2022-39381?
  • muhammara (npm) (versions < 2.6.0)
  • hummus (npm) (versions < 1.0.111)
Is there a fix for CVE-2022-39381?

Yes. CVE-2022-39381 is fixed in 2.6.0, 1.0.111. Upgrade to this version or later.

Is CVE-2022-39381 exploitable, and should I be worried?

Whether CVE-2022-39381 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-2022-39381 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-2022-39381?
  • Upgrade muhammara to 2.6.0 or later
  • Upgrade hummus to 1.0.111 or later

Stop the waste.
Protect your environment with Kodem.