Leon J. Breedt pam-pgsql 0.5.1/0.5.2 Authentication Username format string
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Leon J. Breedt pam-pgsql 0.5.1/0.5.2. This issue affects some unknown processing of the component Authentication. Performing a manipulation of the argument Username results in format string. This vulnerability is known as CVE-2003-0672. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Leon J. Breedt pam-pgsql 0.5.1/0.5.2. It has been classified as critical. This affects an unknown functionality of the component Authentication. The manipulation of the argument Username with an unknown input leads to a format string vulnerability. CWE is classifying the issue as CWE-134. The product uses a function that accepts a format string as an argument, but the format string originates from an external source. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Format string vulnerability in pam-pgsql 0.5.2 and earlier allows remote attackers to execute arbitrary code via the username that isp rovided during authentication, which is not properly handled when recording a log message.
The weakness was published 08/27/2003 (Website). The advisory is shared at debian.org. This vulnerability is uniquely identified as CVE-2003-0672 since 08/07/2003. 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.
The vulnerability scanner Nessus provides a plugin with the ID 15207 (Debian DSA-370-1 : pam-pgsql - format string), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l.
Upgrading eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (15207) and SecurityFocus (BID 8379†). 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: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Format stringCWE: CWE-134 / 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: 15207
Nessus Name: Debian DSA-370-1 : pam-pgsql - format string
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍
OpenVAS ID: 53658
OpenVAS Name: Debian Security Advisory DSA 370-1 (pam-pgsql)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
08/07/2003 🔍08/08/2003 🔍
08/09/2003 🔍
08/27/2003 🔍
08/27/2003 🔍
09/29/2004 🔍
08/14/2014 🔍
06/29/2021 🔍
Sources
Advisory: debian.orgStatus: Not defined
CVE: CVE-2003-0672 (🔍)
GCVE (CVE): GCVE-0-2003-0672
GCVE (VulDB): GCVE-100-20805
SecurityFocus: 8379
Entry
Created: 08/15/2014 00:55Updated: 06/29/2021 08:47
Changes: 08/15/2014 00:55 (59), 04/22/2019 06:46 (3), 06/29/2021 08:47 (4)
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.