Linksys X3000 1.0.03 build 001 apply.cgi ping_ip/Add_Account_Password memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linksys X3000 1.0.03 build 001. It has been rated as critical. Affected is the function ping_ip/Add_Account_Password of the file apply.cgi. Performing a manipulation results in memory corruption.
This vulnerability is identified as CVE-2013-3307. Additionally, an exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability classified as critical has been found in Linksys X3000 1.0.03 build 001 (Router Operating System). This affects the function ping_ip/Add_Account_Password of the file apply.cgi. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability.
The bug was discovered 01/28/2013. The weakness was released 06/22/2013 by devnull as not defined mailinglist post (Bugtraq). The advisory is shared at seclists.org. This vulnerability is uniquely identified as CVE-2013-3307 since 04/29/2013. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
A public exploit has been developed by m-1-k-3 and been published immediately after the advisory. The exploit is shared for download at seclists.org. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 144 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.0.05 build 002 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Exploit-DB (26415) and OSVDB (94518†). Entry connected to this vulnerability is available at VDB-9260. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.linksys.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.0
VulDB Base Score: 10.0
VulDB Temp Score: 9.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: m-1-k-3
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Upgrade: X3000 1.0.05 build 002
Timeline
01/28/2013 🔍04/29/2013 🔍
06/21/2013 🔍
06/22/2013 🔍
06/22/2013 🔍
06/24/2013 🔍
06/25/2013 🔍
09/21/2024 🔍
Sources
Vendor: linksys.comAdvisory: seclists.org
Researcher: devnull
Status: Not defined
CVE: CVE-2013-3307 (🔍)
GCVE (CVE): GCVE-0-2013-3307
GCVE (VulDB): GCVE-100-9261
OSVDB: 94518
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 06/25/2013 15:34Updated: 09/21/2024 10:24
Changes: 06/25/2013 15:34 (56), 09/03/2017 14:54 (1), 09/21/2024 10:24 (14)
Complete: 🔍
Committer:
Cache ID: 216:629:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.