CVE-2020-15302 In Argent RecoveryManager before 0xdc350d09f71c48c5D22fBE2741e4d6A03970E192, the executeRecovery function does not require any signatures in
High 7.5
Published
Updated
Check this codebase for CVE-2020-15302 and fix it if it is affected.
What it is: CVE-2020-15302 is a high-severity vulnerability in n/a, published on 25 Jun 2020.
Exploitation: There is no known exploitation of CVE-2020-15302 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-15302/ (Markdown: https://insights.sbomify.com/CVE-2020-15302/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2020-15302?
CVE-2020-15302 is a high-severity vulnerability in n/a, published on 25 Jun 2020.
Official description
In Argent RecoveryManager before 0xdc350d09f71c48c5D22fBE2741e4d6A03970E192, the executeRecovery function does not require any signatures in the zero-guardian case, which allows attackers to cause a denial of service (locking) or a takeover.
Weakness: CWE-347
Which versions are affected by CVE-2020-15302?
It affects 1 product.
Products include Argent Recoverymanager.
How do I fix CVE-2020-15302?
No fix has been published for CVE-2020-15302 yet. Limit exposure of the affected software until one is available.
Is CVE-2020-15302 being exploited?
There is no known exploitation of CVE-2020-15302 in the wild and no public exploit code.
Sources
Also known as GHSA-w62m-q72r-mx47.