CVE-2022-47100 A vulnerability in Sengled Smart bulb 0x0000024 allows attackers to arbitrarily perform a factory reset on the device via a crafted IEEE 802.15.4 frame.
High 7.5
Published
Updated
Check this codebase for CVE-2022-47100 and fix it if it is affected.
What it is: CVE-2022-47100 is a high-severity vulnerability in n/a, published on 24 Jan 2023.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47100 exists.
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-2022-47100/ (Markdown: https://insights.sbomify.com/CVE-2022-47100/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2022-47100?
CVE-2022-47100 is a high-severity vulnerability in n/a, published on 24 Jan 2023.
Official description
A vulnerability in Sengled Smart bulb 0x0000024 allows attackers to arbitrarily perform a factory reset on the device via a crafted IEEE 802.15.4 frame.
Weakness: CWE-20
Which versions are affected by CVE-2022-47100?
It affects 1 product.
Products include Sengled Es21-N1eaw Firmware.
How do I fix CVE-2022-47100?
No fix has been published for CVE-2022-47100 yet. Limit exposure of the affected software until one is available.
Is CVE-2022-47100 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47100 exists.
Sources
Also known as GHSA-mggm-2vjp-mrm8.