{"answers":{"affected":"3 open source packages ship an affected version, including pyjwt. It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-11424 in the wild and no public exploit code.","fix":"Upgrade pyjwt to 1.5.1 or later.","what":"CVE-2017-11424 is a high-severity vulnerability in Debian Debian Linux, published on 24 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-11424 and fix it if it is affected.\n\nWhat it is: CVE-2017-11424 is a high-severity vulnerability in Debian Debian Linux, published on 24 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-11424 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pyjwt (PyPI): affected all versions; fixed in 1.5.1\n- pyjwt (PyPI): affected all versions; fixed in 1.5.1\n- pyjwt (PyPI): affected all versions; fixed in 1.5.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-11424/ (Markdown: https://insights.sbomify.com/CVE-2017-11424/index.md)","id":"CVE-2017-11424","markdown":"https://insights.sbomify.com/CVE-2017-11424/index.md","name":"CVE-2017-11424","record":{"aliases":["CVE-2017-12880","DEBIAN-CVE-2017-11424","DSA-3979-1","GHSA-r9jw-mwhq-wp62","PYSEC-2017-24","UBUNTU-CVE-2017-11424","USN-3407-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python JWT library","requires_auth":"none","summary":"Attackers can bypass JWT signature verification using PKCS1 PEM keys, allowing them to forge tokens and impersonate users.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"duo","cpe":[{"product":"debian_linux","vendor":"debian"},{"product":"pyjwt","vendor":"pyjwt_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. This enables symmetric/asymmetric key confusion attacks against users using the PKCS1 PEM encoded public keys, which would allow an attacker to craft JWTs from scratch.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"PyJWT vulnerable to key confusion attacks","id":"CVE-2017-11424","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"debian:debian_linux","products":["debian:debian_linux"],"type":"security_feature_bypass","year":"2017"},"n_packages":3,"n_references":2,"next":{"headline":"Multiple SAML libraries may allow authentication bypass via incorrect XML canonicalization and DOM traversal","id":"CVE-2017-11427"},"packages":[{"ecosystem":"PyPI","fixed":["1.5.1"],"introduced":["0"],"last_affected":[],"package":"pyjwt","purl":null,"source":"GHSA-r9jw-mwhq-wp62"},{"ecosystem":"PyPI","fixed":["1.5.1"],"introduced":["0"],"last_affected":[],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"GHSA-r9jw-mwhq-wp62"},{"ecosystem":"PyPI","fixed":["1.5.1"],"introduced":["0"],"last_affected":[],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"PYSEC-2017-24"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-11423"},"products":["n/a"],"published":"2017-08-24","related":[{"cvss_score":10,"headline":"ProFTPD Improper Access Control","id":"CVE-2015-3306","kev_date_added":"2026-10-08","published":"2015-05-18"},{"cvss_score":9.9,"headline":"RoundCube Webmail Deserialization of Untrusted Data","id":"CVE-2025-49113","kev_date_added":"2026-02-20","published":"2025-06-02"},{"cvss_score":9.8,"headline":"GNU InetUtils Argument Injection","id":"CVE-2026-24061","kev_date_added":"2026-01-26","published":"2026-01-21"},{"cvss_score":9.8,"headline":"Linux Kernel Improper Check for Unusual or Exceptional Conditions","id":"CVE-2025-39682","kev_date_added":"2026-09-18","published":"2025-09-05"},{"cvss_score":9.8,"headline":"Mozilla Firefox Use-After-Free","id":"CVE-2024-9680","kev_date_added":"2024-10-15","published":"2024-10-09"},{"cvss_score":9.8,"headline":"RARLAB UnRAR Directory Traversal","id":"CVE-2022-30333","kev_date_added":"2022-08-09","published":"2022-05-09"},{"cvss_score":9.8,"headline":"Roundcube Webmail SQL Injection","id":"CVE-2021-44026","kev_date_added":"2023-06-22","published":"2021-11-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass JWT signature verification using PKCS1 PEM keys, allowing them to forge tokens and impersonate users.","url":"https://insights.sbomify.com/CVE-2017-11424/"}