CVE-2012-3018

CVE-2012-3018 is a medium-severity vulnerability in Iconics Genesis32 with a CVSS 2.0 base score of 4.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-310.

Key facts

Description

The lockout-recovery feature in the Security Configurator component in ICONICS GENESIS32 9.22 and earlier and BizViz 9.22 and earlier uses an improper encryption algorithm for generation of an authentication code, which allows local users to bypass intended access restrictions and obtain administrative access by predicting a challenge response.

Frequently asked questions

What is CVE-2012-3018?
The lockout-recovery feature in the Security Configurator component in ICONICS GENESIS32 9.22 and earlier and BizViz 9.22 and earlier uses an improper encryption algorithm for generation of an authentication code, which allows local users to bypass intended access restrictions and obtain administrative access by predicting a challenge response.
How severe is CVE-2012-3018?
CVE-2012-3018 has a CVSS 2.0 base score of 4.4, rated medium severity.
Is CVE-2012-3018 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-3018?
CVE-2012-3018 primarily affects Iconics Genesis32. In total, 18 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2012-3018?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2012-3018 published?
CVE-2012-3018 was published on 2012-07-31 and last updated on 2026-06-16.

References

Affected products (18)

More vulnerabilities in Iconics Genesis32

All CVEs affecting Iconics Genesis32 →

Other CWE-310 (Cryptographic Issues) vulnerabilities

Browse all CWE-310 (Cryptographic Issues) vulnerabilities →