CVE-2020-19765 An issue in the noReentrance() modifier of the Ethereum-based contract Accounting 1.0 allows attackers to carry out a reentrancy attack.
High 7.5
Published
Updated
Check this codebase for CVE-2020-19765 and fix it if it is affected.
What it is: CVE-2020-19765 is a high-severity vulnerability in n/a, published on 7 Sep 2021.
Exploitation: There is no known exploitation of CVE-2020-19765 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-2020-19765/ (Markdown: https://insights.sbomify.com/CVE-2020-19765/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2020-19765?
CVE-2020-19765 is a high-severity vulnerability in n/a, published on 7 Sep 2021.
Official description
An issue in the noReentrance() modifier of the Ethereum-based contract Accounting 1.0 allows attackers to carry out a reentrancy attack.
Weakness: CWE-863
Which versions are affected by CVE-2020-19765?
It affects 1 product.
Products include Proofofdiligencetoken Project Proofofdiligencetoken.
How do I fix CVE-2020-19765?
No fix has been published for CVE-2020-19765 yet. Limit exposure of the affected software until one is available.
Is CVE-2020-19765 being exploited?
There is no known exploitation of CVE-2020-19765 in the wild and no public exploit code.
Sources
Also known as GHSA-f5m5-9gwg-wj8v.