CVE-2006-2324
180solutions Zango downloads "required Adware components" without checking integrity or...
180solutions Zango downloads "required Adware components" without checking integrity or authenticity, which might allow context-dependent attackers to execute arbitrary code by subverting the DNS resolution of static.zangocash.com.
Exploit likelihood
What each source reports
NVD Score used
10.0
180solutions Zango downloads "required Adware components" without checking integrity or authenticity, which might allow context-dependent attackers to execute arbitrary code by subverting the DNS resolution of static.zangocash.com.
- Record
CVE-2006-2324- CVSS 2.0
- 10.0 High
AV:N/AC:L/Au:N/C:C/I:C/A:C - Updated
- 2026-11-02
CVE List No score
180solutions Zango downloads "required Adware components" without checking integrity or authenticity, which might allow context-dependent attackers to execute arbitrary code by subverting the DNS resolution of static.zangocash.com.
- Record
CVE-2006-2324- Updated
- 2026-11-02
EUVDEUVD-2006-2325 No score
180solutions Zango downloads "required Adware components" without checking integrity or authenticity, which might allow context-dependent attackers to execute arbitrary code by subverting the DNS resolution of static.zangocash.com.
- Record
EUVD-2006-2325- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-fm9h-pm3q-jpcr No score
180solutions Zango downloads "required Adware components" without checking integrity or...
180solutions Zango downloads "required Adware components" without checking integrity or authenticity, which might allow context-dependent attackers to execute arbitrary code by subverting the DNS resolution of static.zangocash.com.
- Record
GHSA-fm9h-pm3q-jpcr- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2006-2324 is a high vulnerability (CVSS 10.0) in 180solutions Zango, published May 12, 2006. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 3.18%, the 88th percentile. No source names a fixed version.