{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15957 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15957 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15957 is a high-severity authentication bypass vulnerability in n/a, published on 30 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15957 and fix it if it is affected.\n\nWhat it is: CVE-2020-15957 is a high-severity authentication bypass vulnerability in n/a, published on 30 Jul 2020. 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-2020-15957 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2020-15957/ (Markdown: https://insights.sbomify.com/CVE-2020-15957/index.md)","id":"CVE-2020-15957","markdown":"https://insights.sbomify.com/CVE-2020-15957/index.md","name":"CVE-2020-15957","record":{"aliases":["GHSA-5m5q-3qw2-3xf3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"DP3T Backend SDK","requires_auth":"none","summary":"Attackers can bypass JWT signature verification in the DP3T Backend SDK by using the 'none' algorithm, allowing unauthorized key uploads.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dp3t-backend-software_development_kit","vendor":"dp3t-backend-software_development_kit_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"An issue was discovered in DP3T-Backend-SDK before 1.1.1 for Decentralised Privacy-Preserving Proximity Tracing (DP3T). When it is configured to check JWT before uploading/publishing keys, it is possible to skip the signature check by providing a JWT token with alg=none.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Auth bypass in n/a","id":"CVE-2020-15957","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-15958"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-15956"},"products":["n/a"],"published":"2020-07-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass JWT signature verification in the DP3T Backend SDK by using the 'none' algorithm, allowing unauthorized key uploads.","url":"https://insights.sbomify.com/CVE-2020-15957/"}