CVE-2012-3810 Other in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2012-3810 and fix it if it is affected.
What it is: CVE-2012-3810 is a high-severity vulnerability in n/a, published on 9 Jan 2020. 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-2012-3810 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-2012-3810/ (Markdown: https://insights.sbomify.com/CVE-2012-3810/index.md)
Samsung Kies allows unauthorized registry modification, potentially altering system settings or application behavior.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2012-3810?
CVE-2012-3810 is a high-severity vulnerability in n/a, published on 9 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Samsung Kies before 2.5.0.12094_27_11 has registry modification.
Which versions are affected by CVE-2012-3810?
It affects 1 product.
Products include Samsung Kies.
How do I fix CVE-2012-3810?
No fix has been published for CVE-2012-3810 yet. Limit exposure of the affected software until one is available.
Is CVE-2012-3810 being exploited?
There is no known exploitation of CVE-2012-3810 in the wild and no public exploit code.
Public exploit code: 1 Exploit-DB entry.
Other vulnerabilities in n/a
Sources
Also known as GHSA-cr94-vrpx-83vx.