C-Note Squid Auth LDAP up to 2.0.2 Log Message logging memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in C-Note Squid Auth LDAP up to 2.0.2. This impacts the function logging of the component Log Message Handler. Performing a manipulation results in memory corruption.
This vulnerability is identified as CVE-2002-0735. There is not any exploit available.
Details
A vulnerability classified as critical has been found in C-Note Squid Auth LDAP up to 2.0.2 (Firewall Software). This affects the function logging of the component Log Message Handler. 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:
Format string vulnerability in the logging() function in C-Note Squid LDAP authentication module (squid_auth_LDAP) 2.0.2 and earlier allows remote attackers to cause a denial of service and possibly execute arbitrary code by triggering log messages.
The weakness was released 08/12/2002 with Shell (Website). The advisory is shared at marc.theaimsgroup.com. This vulnerability is uniquely identified as CVE-2002-0735. The exploitability is told to be easy. 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.
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 SecurityFocus (BID 4679†) and Vulnerability Center (SBV-6747†). Entry connected to this vulnerability is available at VDB-18200. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/06/2002 🔍08/12/2002 🔍
08/12/2002 🔍
07/22/2014 🔍
07/06/2024 🔍
Sources
Advisory: marc.theaimsgroup.comOrganization: Shell
Status: Not defined
CVE: CVE-2002-0735 (🔍)
GCVE (CVE): GCVE-0-2002-0735
GCVE (VulDB): GCVE-100-18621
SecurityFocus: 4679 - PAM_LDAP And Squid_Auth_LDAP Logging Format String Vulnerabilities
Vulnerability Center: 6747
See also: 🔍
Entry
Created: 07/22/2014 23:05Updated: 07/06/2024 11:03
Changes: 07/22/2014 23:05 (53), 07/06/2024 11:03 (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.