{"answers":{"affected":"3 open source packages ship an affected version, including gopkg.in/square/go-jose.v1. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-9122 in the wild and no public exploit code.","fix":"Upgrade gopkg.in/square/go-jose.v1 to 1.1.0 or later.","what":"CVE-2016-9122 is a high-severity vulnerability in Go JOSE All versions before 1.0.4, published on 28 Mar 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-2016-9122 and fix it if it is affected.\n\nWhat it is: CVE-2016-9122 is a high-severity vulnerability in Go JOSE All versions before 1.0.4, published on 28 Mar 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-2016-9122 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gopkg.in/square/go-jose.v1 (Go): affected all versions; fixed in 1.1.0\n- gopkg.in/square/go-jose.v1 (Go): affected all versions; fixed in 1.1.0\n- gopkg.in/square/go-jose.v1 (Go): affected all versions; fixed in 1.1.0\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-2016-9122/ (Markdown: https://insights.sbomify.com/CVE-2016-9122/index.md)","id":"CVE-2016-9122","markdown":"https://insights.sbomify.com/CVE-2016-9122/index.md","name":"CVE-2016-9122","record":{"aliases":["DEBIAN-CVE-2016-9122","GHSA-77gc-fj98-665h","GO-2022-0945"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Go JOSE library","requires_auth":"none","summary":"Attackers can exploit multiple signatures to confuse validation logic, potentially bypassing security checks in applications using the go-jose library.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"go-jose","vendor":"go-jose_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":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"go-jose before 1.0.4 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from an attached signature that was different from the one originally validated.","ecosystems":["Go"],"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":"Go JOSE Signature Validation Bypass","id":"CVE-2016-9122","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2016"},"n_packages":3,"n_references":3,"next":{"headline":"Integer Overflow in go-jose","id":"CVE-2016-9123"},"packages":[{"ecosystem":"Go","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"gopkg.in/square/go-jose.v1","purl":null,"source":"GHSA-77gc-fj98-665h"},{"ecosystem":"Go","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"gopkg.in/square/go-jose.v1","purl":"pkg:golang/gopkg.in/square/go-jose.v1","source":"GHSA-77gc-fj98-665h"},{"ecosystem":"Go","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"gopkg.in/square/go-jose.v1","purl":"pkg:golang/gopkg.in/square/go-jose.v1","source":"GO-2022-0945"}],"prev":{"headline":"Elliptic Curve Key Disclosure in go-jose","id":"CVE-2016-9121"},"products":["Go JOSE All versions before 1.0.4"],"published":"2017-03-28","related":[{"cvss_score":9.1,"headline":"Elliptic Curve Key Disclosure in go-jose","id":"CVE-2016-9121","kev_date_added":null,"published":"2017-03-28"},{"cvss_score":7.5,"headline":"Go JOSE affect by a panic in JWE decryption","id":"CVE-2026-34986","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":7.5,"headline":"Integer Overflow in go-jose","id":"CVE-2016-9123","kev_date_added":null,"published":"2017-03-28"}],"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":"Go Vulnerability Database","prefix":"GO"},{"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-06","vendors":["n/a"]},"summary":"Attackers can exploit multiple signatures to confuse validation logic, potentially bypassing security checks in applications using the go-jose library.","url":"https://insights.sbomify.com/CVE-2016-9122/"}