CVE-2013-2132

CVE-2013-2132 is a medium-severity security vulnerability in pymongo (pip), affecting versions < 2.5.2. It is fixed in 2.5.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Use of NullPointerException Catch to Detect NULL Pointer Dereference in Pymongo

bson/_cbsonmodule.c in the mongo-python-driver (aka. pymongo) before 2.5.2, as used in MongoDB, allows context-dependent attackers to cause a denial of service (NULL pointer dereference and crash) via vectors related to decoding of an "invalid DBRef."

Impact

Affected versions

pymongo (< 2.5.2)

Security releases

pymongo → 2.5.2 (pip)

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 environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade pymongo to 2.5.2 or later to resolve this vulnerability.

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

Frequently Asked Questions

  1. What is CVE-2013-2132? CVE-2013-2132 is a medium-severity security vulnerability in pymongo (pip), affecting versions < 2.5.2. It is fixed in 2.5.2.
  2. Which versions of pymongo are affected by CVE-2013-2132? pymongo (pip) versions < 2.5.2 is affected.
  3. Is there a fix for CVE-2013-2132? Yes. CVE-2013-2132 is fixed in 2.5.2. Upgrade to this version or later.
  4. Is CVE-2013-2132 exploitable, and should I be worried? Whether CVE-2013-2132 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
  5. What actually determines whether CVE-2013-2132 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.
  6. How do I fix CVE-2013-2132? Upgrade pymongo to 2.5.2 or later.

Other vulnerabilities in pymongo

Stop the waste.
Protect your environment with Kodem.