| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in libpam-pgsql 0.6.3. This affects the function this of the file pam_pgsql.c. The manipulation leads to improper authentication.
This vulnerability is documented as CVE-2008-2516. There is not any exploit available.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in libpam-pgsql 0.6.3 and classified as problematic. This issue affects the function this of the file pam_pgsql.c. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
pam_sm_authenticate in pam_pgsql.c in libpam-pgsql 0.6.3 does not properly consider operator precedence when evaluating the success of a pam_get_pass function call, which allows local users to gain privileges via a SIGINT signal when this function is executing, as demonstrated by a CTRL-C sequence at a sudo password prompt in an "auth sufficient pam_pgsql.so" configuration.
The weakness was released 06/03/2008 (Website). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2008-2516 since 06/03/2008. The exploitation is known to be easy. Attacking locally is a requirement. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
It is declared as proof-of-concept.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at X-Force (42653), SecurityFocus (BID 29360†), Secunia (SA30391†) and SecurityTracker (ID 1020111†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.9
VulDB Temp Score: 5.2
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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Proof-of-Concept
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
05/19/2008 🔍05/27/2008 🔍
06/03/2008 🔍
06/03/2008 🔍
06/03/2008 🔍
03/16/2015 🔍
09/25/2018 🔍
Sources
Advisory: securityfocus.com⛔Status: Confirmed
Confirmation: 🔍
CVE: CVE-2008-2516 (🔍)
GCVE (CVE): GCVE-0-2008-2516
GCVE (VulDB): GCVE-100-42611
X-Force: 42653 - libpam-pgsql pam_sm_authenticate() security bypass
SecurityFocus: 29360 - libpam-pgsql 'pam_pgsql.c' Authentication Bypass Vulnerability
Secunia: 30391
SecurityTracker: 1020111
Vupen: ADV-2008-1654
Entry
Created: 03/16/2015 17:00Updated: 09/25/2018 13:05
Changes: 03/16/2015 17:00 (55), 09/25/2018 13:05 (6)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.