Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2022-21699: Execution with Unnecessary Privileges in ipython

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.65% (FIRST EPSS); higher than 51% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: ipython (Debian:10) 5.8.0-1+deb10u1; ipython (Debian:11) 7.20.0-1+deb11u1; ipython (Debian:12) 7.31.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to ipython (Debian:10) 5.8.0-1+deb10u1; ipython (Debian:11) 7.20.0-1+deb11u1; ipython (Debian:12) 7.31.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

IPython (Interactive Python) is a command shell for interactive computing in multiple programming languages, originally developed for the Python programming language. Affected versions are subject to an arbitrary code execution vulnerability achieved by not properly managing cross user temporary files. This vulnerability allows one user to run code as another on the same machine. All users are advised to upgrade.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Jan 19, 2022
Updated
Jun 17, 2026
EPSS
0.6% · 51th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · GitHub_M
8.2
0.6 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-21699

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for ipython records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
ipythonipython
debiandebian linux
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • debian debian linux11.0
  • debian debian linux9.0
  • fedoraproject fedora34
  • fedoraproject fedora35
  • ipython ipython8.0.0 and later · before 8.0.1
  • ipython ipython7.17.0 and later · before 7.31.1
  • ipython ipython6.0.0 and later · before 7.16.3
  • ipython ipythonup to 5.10.0 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • ipython ipython

    • < 5.11, >= 6.0.0, < 7.16.3, >= 7.17.0, < 7.31.1, >= 8.0.0, < 8.0.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10ipythonbefore 5.8.0-1+deb10u15.8.0-1+deb10u1
Debian:11ipythonbefore 7.20.0-1+deb11u17.20.0-1+deb11u1
Debian:12ipythonbefore 7.31.1-17.31.1-1
Debian:9ipythonbefore 5.1.0-3+deb9u15.1.0-3+deb9u1
openSUSE:Leap 15.3python-ipythonbefore 7.13.0-bp153.2.6.17.13.0-bp153.2.6.1
openSUSE:Leap 15.3python-ipython-testbefore 7.13.0-bp153.2.6.67.13.0-bp153.2.6.6
openSUSE:Tumbleweedpython-ipythonbefore 8.31.0-1.18.31.0-1.1
PyPIipythonfrom 6.0.0 · before 7.16.37.16.3
PyPIipythonfrom 7.17.0 · before 7.31.17.31.1
PyPIipythonfrom 8.0.0 · before 8.0.18.0.1
PyPIipythonbefore 5.115.11
PyPIipythonbefore 6.0.0rc16.0.0rc1
SUSE:Package Hub 15 SP3python-ipythonbefore 7.13.0-bp153.2.6.17.13.0-bp153.2.6.1
SUSE:Package Hub 15 SP3python-ipython-testbefore 7.13.0-bp153.2.6.67.13.0-bp153.2.6.6

Same product

ipython: all records

Other highest-scoring records for the same primary product.

  • CVE-2015-5607Cross-site request forgery in the REST API in IPython 2 and 3.
    35Monitor
  • CVE-2023-24816set_term_title command injection in ipython
    28Monitor
  • CVE-2015-4706Cross-site scripting (XSS) vulnerability in IPython 3.x before 3.2 allows remote attackers to inject arbitrary web script or HTML via vector
    25Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2015-4707Sep 20, 2017 · Cross-site scripting (XSS) vulnerability in IPython before 3.2 allows remote attackers to inject arbitrary web script or HTML via vectors in
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ipython7.31.1-1 · Debian:12Package registry (OSV)
opensuse:python-ipython7.13.0-bp153.2.6.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:python-ipython-test7.13.0-bp153.2.6.6 · openSUSE:Leap 15.3Package registry (OSV)
PyPI:ipython5.11Package registry (OSV)
PyPI:ipython6.0.0rc1Package registry (OSV)
PyPI:ipython7.16.3Package registry (OSV)
PyPI:ipython7.31.1Package registry (OSV)
PyPI:ipython8.0.1Package registry (OSV)
suse:python-ipython7.13.0-bp153.2.6.1 · SUSE:Package Hub 15 SP3Package registry (OSV)
suse:python-ipython-test7.13.0-bp153.2.6.6 · SUSE:Package Hub 15 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-250 · Execution with Unnecessary Privileges

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records