CVE-2014-8243
3.3 · LOWOverview
CVE-2014-8243 is a low-severity vulnerability affecting linksys ea4500_firmware. It was published on November 1, 2014 and has a CVSS 2.0 base score of 3.3 (LOW).
This vulnerability has a CVSS 2.0 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.
Technical Description
Linksys SMART WiFi firmware on EA2700 and EA3500 devices; before 2.1.41 build 162351 on E4200v2 and EA4500 devices; before 1.1.41 build 162599 on EA6200 devices; before 1.1.40 build 160989 on EA6300, EA6400, EA6500, and EA6700 devices; and before 1.1.42 build 161129 on EA6900 devices allows remote attackers to obtain the administrator's MD5 password hash via a direct request for the /.htpasswd URI.
Remediation
Check the references section for vendor advisories and patches from linksys. Update ea4500_firmware to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| linksys | ea4500_firmware | 0 | Affected |
| linksys | ea6500_firmware | 0 | Affected |
| linksys | ea6400_firmware | 0 | Affected |
| linksys | e4200v2_firmware | 0 | Affected |
| linksys | ea6300_firmware | 0 | Affected |
| linksys | ea6900_firmware | 0 | Affected |
| linksys | ea2700_firmware | 0 | Affected |
| linksys | ea3500_firmware | 0 | Affected |
| linksys | ea6200_firmware | 0 | Affected |
| linksys | ea6700_firmware | 0 | Affected |
Frequently Asked Questions
What is CVE-2014-8243?
CVE-2014-8243 is a low-severity vulnerability affecting linksys ea4500_firmware. It was published on November 1, 2014 and has a CVSS 2.0 base score of 3.3 (LOW).
How severe is CVE-2014-8243?
This vulnerability has a CVSS 2.0 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2014-8243?
Check the references section for vendor advisories and patches from linksys. Update ea4500_firmware to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2014-8243?
CyberStrike's AI-powered security agents can automatically detect CVE-2014-8243 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related LOW CVEs from 2014
View all →Unspecified vulnerability in HP HP-UX Whitelisting (aka WLI) before A.01.02.02 on HP-UX B.11.31 allo
Luci in Red Hat Conga stores the user's username and password in a Base64 encoded string in the __ac
Luci in Red Hat Conga does not properly enforce the user session timeout, which might allow attacker
Red Hat JBoss Operations Network (JON) before 3.0.1 uses 0777 permissions for the root directory whe
Unspecified vulnerability in the Oracle Transportation Management component in Oracle Supply Chain P
The slapper function in chkrootkit before 0.50 does not properly quote file paths, which allows loca
Secunia CSI Agent 6.0.0.15017 and earlier, 6.0.1.1007 and earlier, and 7.0.0.21 and earlier, when ru
The lock-counter implementation in utils/mount.ecryptfs_private.c in ecryptfs-utils before 90 allows
CFNetwork in Apple OS X through 10.8.5 does not remove session cookies upon a Safari reset action, w
The Ubuntu AccountsService package before 0.6.14-1git1ubuntu1.1 does not properly drop privileges wh
The smart proxy in Foreman before 1.1 uses a umask set to 0, which allows local users to modify file
pyxtrlock before 0.1 uses an incorrect variable name, which allows physically proximate attackers to