Gdata's vulnerability footprint centers on consumer antivirus and internet security products spanning the late 2000s release cycle, with observed weaknesses concentrating in race conditions, input validation failures, and memory-buffer handling issues typical of native security software. Treat this as a compact vendor profile rather than a broad exposure trend; live severity, exploitation, and current CVE counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Gdata over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2007-5436HIGH Buffer overflow in a certain ActiveX control in ScanObjectBrowser.DLL in G DATA Antivirus 2007 might allow remote attackers to execute arbitrary code via unspecified parameters to | Oct 13, 2007 | 7.6 | 21 | NO | NO |
CVE-2010-5162MEDIUM Race condition in G DATA TotalCare 2010 on Windows XP allows local users to bypass kernel-mode hook handlers, and execute dangerous code that would otherwise be blocked by a handle | Aug 25, 2012 | 6.2 | 19 | NO | NO |
CVE-2008-6000HIGH The GDTdiIcpt.sys driver in G DATA AntiVirus 2008, InternetSecurity 2008, and TotalCare 2008 populates kernel registers with IOCTL 0x8317001c input values, which allows local users | Jan 28, 2009 | 7.2 | 19 | NO | NO |
CVE-2007-5041MEDIUM G DATA InternetSecurity 2007 does not properly validate certain parameters to System Service Descriptor Table (SSDT) function handlers, which allows local users to cause a denial o | Sep 24, 2007 | 4.6 | 14 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Gdata.
Media articles that mention a CVE ID that affects a product developed by Gdata — matched by CVE ID, not by vendor name.