python-jose through 3.3.0 has algorithm confusion with OpenSSH ECDSA keys and other key formats.
python-jose through 3.3.0 has algorithm confusion with OpenSSH ECDSA keys and other key formats. This is similar to CVE-2022-29217.
- Published
- Apr 25, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 21th percentile
- CWE
- CWE-327
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| python-jose project | python-jose | cpe:2.3:a:python-jose_project:python-jose |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- python-jose project python-joseup to 3.3.0 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | python-jose | all versions | — |
| openSUSE:Tumbleweed | python-cryptography | before 3.3.0-3.1 | 3.3.0-3.1 |
| PyPI | python-jose | before 3.4.0 | 3.4.0 |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | automation-controller | before 0:4.5.10-1.el8ap | 0:4.5.10-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | automation-controller-cli | before 0:4.5.10-1.el8ap | 0:4.5.10-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-zipp | before 0:3.19.2-1.el8ap | 0:3.19.2-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | automation-controller | before 0:4.5.10-1.el9ap | 0:4.5.10-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | automation-controller-cli | before 0:4.5.10-1.el9ap | 0:4.5.10-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-zipp | before 0:3.19.2-1.el9ap | 0:3.19.2-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python3-zipp | before 0:3.19.2-1.el9ap | 0:3.19.2-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-server | before 0:4.5.10-1.el8ap | 0:4.5.10-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-ui | before 0:4.5.10-1.el8ap | 0:4.5.10-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-venv-tower | before 0:4.5.10-1.el8ap | 0:4.5.10-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-django | before 0:4.2.15-1.el8ap | 0:4.2.15-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-grpcio | before 0:1.58.3-1.el8ap | 0:1.58.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-grpcio-debuginfo | before 0:1.58.3-1.el8ap | 0:1.58.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-django | before 0:4.2.15-1.el8ap | 0:4.2.15-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-grpcio | before 0:1.58.3-1.el8ap | 0:1.58.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-grpcio-debugsource | before 0:1.58.3-1.el8ap | 0:1.58.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el9 | automation-controller-server | before 0:4.5.10-1.el9ap | 0:4.5.10-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | automation-controller-ui | before 0:4.5.10-1.el9ap | 0:4.5.10-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | automation-controller-venv-tower | before 0:4.5.10-1.el9ap | 0:4.5.10-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | python-django | before 0:4.2.15-1.el9ap | 0:4.2.15-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | python-grpcio | before 0:1.58.3-1.el9ap | 0:1.58.3-1.el9ap |
+6
Same product
python-jose project: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-7036python-jose before 1.3.2 allows attackers to have unspecified impact by leveraging failure to use a constant time comparison for HMAC keys.40Plan
- CVE-2024-29370In python-jose 3.3.0 (specifically jwe.decrypt), a vulnerability allows an attacker to cause a Denial-of-Service (DoS) condition by crafting21Monitor
- CVE-2024-33664python-jose through 3.3.0 allows attackers to cause a denial of service (resource consumption) during a decode via a crafted JSON Web Encryp21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:python-cryptography | 3.3.0-3.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python-python-jose | 3.0.1-bp155.3.3.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| PyPI:python-jose | 3.4.0 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.5.10-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python-grpcio | 0:1.58.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python-grpcio-debugsource | 0:1.58.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python-zipp | 0:3.19.2-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-grpcio | 0:1.58.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python3-grpcio-debuginfo | 0:1.58.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python3-zipp | 0:3.19.2-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python39-grpcio | 0:1.58.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python39-grpcio-debuginfo | 0:1.58.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python39-zipp | 0:3.19.2-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python3x-grpcio | 0:1.58.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python3x-grpcio-debugsource | 0:1.58.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| suse:python-python-jose | 3.0.1-bp155.3.3.1 · SUSE:Package Hub 15 SP5 | Package 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.
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.
No commit or PR link among the references.
Credits
All researchersFinders, 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).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-327 · Use of a Broken or Risky Cryptographic AlgorithmCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Signature SpoofCAPEC-473
- Signature Spoofing by Improper ValidationCAPEC-475likelihood: Low · High
- Cryptanalysis of Cellular EncryptionCAPEC-608High
- Rooting SIM CardsCAPEC-614High
- CryptanalysisCAPEC-97likelihood: Low · Very High
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →