# CVE-2018-3756: Security feature bypass in n/a

> Attackers can bypass signature verification in Hyperledger Iroha by submitting multiple signatures with random nonces, compromising transaction integrity.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jmw4-vrcr-pppg

## What is CVE-2018-3756?

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.

### Official 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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2018-3756?

It affects 1 product.


Products: Hyperledger Iroha.

## How do I fix CVE-2018-3756?

No fix has been published for CVE-2018-3756 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-3756 being exploited?

There is no known exploitation of CVE-2018-3756 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3756 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2018-3756 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-3756/ (Markdown: https://insights.sbomify.com/CVE-2018-3756/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-3756
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-3756
- OSV: https://osv.dev/vulnerability/CVE-2018-3756

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-3756/
Summaries are generated and may contain mistakes; the official description above is the record.