CVE-2007-1083 json
Buffer overflow in the Configuration Checker (ConfigChk) ActiveX control in VSCnfChk.dll 2.0.0.2 for Verisign Managed PKI Service, Secure M…
published 2007-02-23 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-1080
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.3%
- EPSS 8.3% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
Buffer overflow in the Configuration Checker (ConfigChk) ActiveX control in VSCnfChk.dll 2.0.0.2 for Verisign Managed PKI Service, Secure Messaging for Microsoft Exchange, and Go Secure! allows remote attackers to execute arbitrary code via long arguments to the VerCompare method.
Exploit prediction
8.29% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
secunia.com
/advisories/24249
third-party-advisory, vendor-advisory
-
download.verisign.co.jp
/support/announce/20070216.html
vendor-advisory
-
osvdb.org
/33479
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/32639
vdb-entry
-
kb.cert.org
/vuls/id/308087
third-party-advisory, us-government-resource
- jvn.jp /cert/JVNVU%23308087/index.html
-
attrition.org
/pipermail/vim/2007-February/001385.html
mailing-list
-
securitytracker.com
/id?1017693
vdb-entry
-
securityfocus.com
/bid/22676
vdb-entry
-
securityfocus.com
/bid/22671
vdb-entry
-
attrition.org
/pipermail/vim/2007-February/001384.html
mailing-list
- jpcert.or.jp /at/2007/at070006.txt
-
securitytracker.com
/id?1017692
vdb-entry
-
securitytracker.com
/id?1017694
vdb-entry
-
vupen.com
/english/advisories/2007/0702
vdb-entry
-
labs.idefense.com
/intelligence/vulnerabilities/display.php?id=479
third-party-advisory
Sources
- CVE List CVE-2007-1083
- NVD CVE-2007-1083
Fencer Vulns 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.