eIQNetworks Enterprise Security Analyzer 2.5 memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in eIQNetworks Enterprise Security Analyzer 2.5. The impacted element is an unknown function. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2007-5699. In addition, an exploit is available.
Details
A vulnerability was found in eIQNetworks Enterprise Security Analyzer 2.5. It has been classified as critical. This affects an unknown functionality. 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:
Stack-based buffer overflow in eIQNetworks Enterprise Security Analyzer (ESA) 2.5 allows remote attackers to execute arbitrary code via certain data on TCP port 10616 that results in a long argument to the SEARCHREPORT command, a different vector than CVE-2007-2059.
The weakness was presented 10/29/2007 (Website). The advisory is shared at milw0rm.com. This vulnerability is uniquely identified as CVE-2007-5699 since 10/29/2007. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.
A public exploit has been developed in Ruby. The exploit is shared for download at securityfocus.com. It is declared as functional.
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 X-Force (38139), Exploit-DB (4566) and SecurityFocus (BID 26189†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.8
VulDB Base Score: 7.3
VulDB Temp Score: 6.8
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: 🔍
Access: Public
Status: Functional
Programming Language: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/24/2007 🔍10/29/2007 🔍
10/29/2007 🔍
10/29/2007 🔍
03/16/2015 🔍
10/09/2024 🔍
Sources
Advisory: milw0rm.com⛔Status: Not defined
CVE: CVE-2007-5699 (🔍)
GCVE (CVE): GCVE-0-2007-5699
GCVE (VulDB): GCVE-100-39453
X-Force: 38139 - eIQnetworks Enterprise Security Analyzer SEARCHREPORT buffer overflow
SecurityFocus: 26189 - eIQnetworks Enterprise Security Analyzer SEARCHREPORT Command Remote Buffer Overflow Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/16/2015 12:18Updated: 10/09/2024 08:16
Changes: 03/16/2015 12:18 (49), 10/29/2017 14:19 (8), 10/09/2024 08:16 (17)
Complete: 🔍
Cache ID: 216::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.