CVE-2021-3842
nltk is vulnerable to Inefficient Regular Expression Complexity
Overview
Description
nltk is vulnerable to Inefficient Regular Expression Complexity
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness: CWE-1333
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| PyPI | nltk | <3.6.6 | 3.6.6 |
Open a package to see all its vulnerabilities.
Operating systems · 9 fixes
debian 6 releases · 1 package
affected 3
fixed 3
nltk
| Release | Package | Fixed in |
|---|---|---|
| 10 | nltk | affected |
| 11 | nltk | affected |
| 12 | nltk | 3.6.7-1 |
| 13 | nltk | 3.6.7-1 |
| 14 | nltk | 3.6.7-1 |
| 9 | nltk | affected |
echo 1 release · 1 package
fixed 1
nltk
| Release | Package | Fixed in |
|---|---|---|
| nltk | 3.6.7-1 |
ubuntu 2 releases · 1 package
fixed 2
nltk
| Release | Package | Fixed in |
|---|---|---|
| 18.04-ESM | nltk | 3.2.5-1ubuntu0.1+esm2 |
| 20.04-ESM | nltk | 3.4.5-2ubuntu0.1~esm2 |
References
- github.com https://github.com/nltk/nltk
- github.com https://github.com/nltk/nltk/commit/2a50a3edc9d35f57ae42a921c621edc160877f4d
- github.com https://github.com/nltk/nltk/commit/2a50a3edc9d35f57ae42a921c621edc160877f4d (3.6.6)
- github.com https://github.com/nltk/nltk/pull/2906
- github.com https://github.com/pypa/advisory-database/tree/main/vulns/nltk/PYSEC-2022-5.yaml
- huntr.dev https://huntr.dev/bounties/761a761e-2be2-430a-8d92-6f74ffe9866a
- huntr.dev https://huntr.dev/bounties/761a761e-2be2-430a-8d92-6f74ffe9866a/
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2021-3842
- ubuntu.com https://ubuntu.com/security/notices/USN-7365-1
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2021-3842
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.