{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3756 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3756 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3756 is a high-severity vulnerability in n/a, published on 1 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-3756 and fix it if it is affected.\n\nWhat it is: CVE-2018-3756 is a high-severity vulnerability in n/a, published on 1 Jun 2018. 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-2018-3756 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-2018-3756/ (Markdown: https://insights.sbomify.com/CVE-2018-3756/index.md)","id":"CVE-2018-3756","markdown":"https://insights.sbomify.com/CVE-2018-3756/index.md","name":"CVE-2018-3756","record":{"aliases":["GHSA-jmw4-vrcr-pppg"],"analysis":{"component_type":"other","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Hyperledger Iroha","requires_auth":"none","summary":"Attackers can bypass signature verification in Hyperledger Iroha by submitting multiple signatures with random nonces, compromising transaction integrity.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"iroha","vendor":"hyperledger"}],"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-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Hyperledger Iroha versions v1.0_beta and v1.0.0_beta-1 are vulnerable to transaction and block signature verification bypass in the transaction and block validator allowing a single node to sign a transaction and/or block multiple times, each with a random nonce, and have other validating nodes accept them as separate valid signatures.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2018-3756","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Command Injection in pdf-image","id":"CVE-2018-3757"},"packages":[],"prev":{"headline":"Cross-Site Scripting in sexstatic","id":"CVE-2018-3755"},"products":["n/a"],"published":"2018-06-01","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-09-17","vendors":["n/a"]},"summary":"Attackers can bypass signature verification in Hyperledger Iroha by submitting multiple signatures with random nonces, compromising transaction integrity.","url":"https://insights.sbomify.com/CVE-2018-3756/"}