CVE-2012-6429 in the critical feed json
Buffer overflow in the PrepareSync method in the SyncService.dll ActiveX control in Samsung Kies before 2.5.1.12123_2_7 allows remote attac…
published 2014-04-04 12 y ago modified 2026-06-16 4 mo ago also EUVD-2012-6284
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 15.8%
- EPSS 15.8% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Buffer overflow in the PrepareSync method in the SyncService.dll ActiveX control in Samsung Kies before 2.5.1.12123_2_7 allows remote attackers to execute arbitrary code via a long string to the password argument.
Timeline
- First public exploit (EDB-38206)
- Published
Exploit prediction
15.76% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-38206 Samsung Kies - Remote Buffer Overflow remote, 2013-01-09
- htbridge.com https://www.htbridge.com/advisory/HTB23136 referenced PoC, tagged "exploit" by a source, unverified
- archives.neohapsis.com http://archives.neohapsis.com/archives/bugtraq/2013-01/0036.html referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/119423/Samsung-Kies-2.5.0.12114_1-Buffer-Overflow.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
htbridge.com
/advisory/HTB23136
exploit
-
archives.neohapsis.com
/archives/bugtraq/2013-01/0036.html
mailing-list, exploit
-
packetstormsecurity.com
/files/119423/Samsung-Kies-2.5.0.12114_1-Buffer-Overflow.html
exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/81160
vdb-entry
-
securityfocus.com
/bid/57249
vdb-entry
-
osvdb.org
/89118
vdb-entry
Sources
- CVE List CVE-2012-6429
- NVD CVE-2012-6429
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.