{"answers":{"affected":"3 open source packages ship an affected version, including indy-node. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11093 in the wild and no public exploit code.","fix":"Upgrade indy-node to 1.12.4 or later.","what":"CVE-2020-11093 is a high-severity missing authorization vulnerability in hyperledger indy-node, published on 24 Dec 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-11093 and fix it if it is affected.\n\nWhat it is: CVE-2020-11093 is a high-severity missing authorization vulnerability in hyperledger indy-node, published on 24 Dec 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-11093 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- indy-node (PyPI): affected all versions; fixed in 1.12.4\n- indy-node (PyPI): affected all versions; fixed in 1.12.4\n- indy-node (PyPI): affected all versions; fixed in 1.12.4\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-11093/ (Markdown: https://insights.sbomify.com/CVE-2020-11093/index.md)","id":"CVE-2020-11093","markdown":"https://insights.sbomify.com/CVE-2020-11093/index.md","name":"CVE-2020-11093","record":{"aliases":["GHSA-wh2w-39f4-rpv2","PYSEC-2020-48"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Hyperledger Indy Node","requires_auth":"none","summary":"Attackers can bypass signature verification to modify other DIDs' aliases and spam the ledger, compromising decentralized identity integrity.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"indy-node","vendor":"linuxfoundation"}],"cvss":{"score":7.5,"severity":"high","source":"cna","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":"Hyperledger Indy Node is the server portion of a distributed ledger purpose-built for decentralized identity. In Hyperledger Indy before version 1.12.4, there is lack of signature verification on a specific transaction which enables an attacker to make certain unauthorized alterations to the ledger. Updating a DID with a nym transaction will be written to the ledger if neither ROLE or VERKEY are being changed, regardless of sender. A malicious DID with no particular role can ask an update for another DID (but cannot modify its verkey or role). This is bad because 1) Any DID can write a nym transaction to the ledger (i.e., any DID can spam the ledger with nym transactions), 2) Any DID can change any other DID's alias, 3) The update transaction modifies the ledger metadata associated with a DID.","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":"Authorization bypass in Hyperledger Indy","id":"CVE-2020-11093","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":3,"n_references":4,"next":{"headline":"Potential unauthorized access to stored request \u0026 session data when plugin is misconfigured in October CMS Debugbar","id":"CVE-2020-11094"},"packages":[{"ecosystem":"PyPI","fixed":["1.12.4"],"introduced":["0"],"last_affected":[],"package":"indy-node","purl":null,"source":"GHSA-wh2w-39f4-rpv2"},{"ecosystem":"PyPI","fixed":["1.12.4"],"introduced":["0"],"last_affected":[],"package":"indy-node","purl":"pkg:pypi/indy-node","source":"GHSA-wh2w-39f4-rpv2"},{"ecosystem":"PyPI","fixed":["1.12.4"],"introduced":["0"],"last_affected":[],"package":"indy-node","purl":"pkg:pypi/indy-node","source":"PYSEC-2020-48"}],"prev":{"headline":"Weave Net clusters susceptible to MitM attacks via IPv6 rogue router advertisements","id":"CVE-2020-11091"},"products":["indy-node"],"published":"2020-12-24","related":[{"cvss_score":8.8,"headline":"Remote code execution in Indy's NODE_UPGRADE transaction","id":"CVE-2022-31020","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":7.5,"headline":"Hyperledger Indy DOS vulnerability","id":"CVE-2022-31006","kev_date_added":null,"published":"2022-09-09"},{"cvss_score":7.5,"headline":"Uncontrolled Resource Consumption in Indy Node","id":"CVE-2020-11090","kev_date_added":null,"published":"2020-06-11"}],"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":"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":["hyperledger"]},"summary":"Attackers can bypass signature verification to modify other DIDs' aliases and spam the ledger, compromising decentralized identity integrity.","url":"https://insights.sbomify.com/CVE-2020-11093/"}