CVE-2018-20957 Other in n/a
High 8.8
Published
Updated
Check this codebase for CVE-2018-20957 and fix it if it is affected.
What it is: CVE-2018-20957 is a high-severity vulnerability in n/a, published on 8 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20957 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-20957/ (Markdown: https://insights.sbomify.com/CVE-2018-20957/index.md)
Attackers can perform replay attacks on Tapplock smart locks via Bluetooth Low Energy, bypassing authentication mechanisms.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2018-20957?
CVE-2018-20957 is a high-severity vulnerability in n/a, published on 8 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
The Bluetooth Low Energy (BLE) subsystem on Tapplock devices before 2018-06-12 allows replay attacks.
Weakness: CWE-284
Which versions are affected by CVE-2018-20957?
It affects 1 product.
Products include Tapplock One\+ Firmware.
How do I fix CVE-2018-20957?
No fix has been published for CVE-2018-20957 yet. Limit exposure of the affected software until one is available.
Is CVE-2018-20957 being exploited?
There is no known exploitation of CVE-2018-20957 in the wild and no public exploit code.
Sources
Also known as GHSA-76xp-j3hr-8ffv.