| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Echoping 6.0.2. Impacted is the function SSL_readline of the file readline.c. Performing a manipulation results in memory corruption.
This vulnerability was named CVE-2010-5111. There is no available exploit.
Details
A vulnerability was found in Echoping 6.0.2. It has been classified as critical. This affects the function SSL_readline of the file readline.c. 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 summary by CVE is:
Multiple buffer overflows in readline.c in Echoping 6.0.2 allow remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted reply in the (1) TLS_readline or (2) SSL_readline function, related to the EchoPingHttps Smokeping probe.
The weakness was presented 06/16/2014 (Website). The advisory is shared at bugs.debian.org. This vulnerability is uniquely identified as CVE-2010-5111 since 04/30/2012. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 74372 (GLSA-201406-07 : Echoping: Buffer Overflow Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Tenable (74372) and Vulnerability Center (SBV-45064†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 74372
Nessus Name: GLSA-201406-07 : Echoping: Buffer Overflow Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/11/2010 🔍04/30/2012 🔍
06/07/2014 🔍
06/16/2014 🔍
06/16/2014 🔍
06/18/2014 🔍
03/26/2015 🔍
03/22/2022 🔍
Sources
Advisory: bugs.debian.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2010-5111 (🔍)
GCVE (CVE): GCVE-0-2010-5111
GCVE (VulDB): GCVE-100-70053
SecurityFocus: 45394
Vulnerability Center: 45064 - Echoping <= 6.0.2 Remote DoS and Code Execution due to Buffer Overflow, Medium
Entry
Created: 03/26/2015 12:07Updated: 03/22/2022 16:57
Changes: 03/26/2015 12:07 (56), 05/31/2017 08:53 (2), 03/22/2022 16:57 (4)
Complete: 🔍
Cache ID: 216:CFF: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.