PostgresNIO up to 1.14.1 TLS Certificate Verification insufficiently protected credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in PostgresNIO up to 1.14.1. This issue affects some unknown processing of the component TLS Certificate Verification. The manipulation leads to insufficiently protected credentials. This vulnerability is traded as CVE-2023-31136. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in PostgresNIO up to 1.14.1. It has been rated as problematic. This issue affects some unknown functionality of the component TLS Certificate Verification. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. Using CWE to declare the problem leads to CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. Impacted is confidentiality. The summary by CVE is:
PostgresNIO is a Swift client for PostgreSQL. Any user of PostgresNIO prior to version 1.14.2 connecting to servers with TLS enabled is vulnerable to a man-in-the-middle attacker injecting false responses to the client's first few queries, despite the use of TLS certificate verification and encryption. The vulnerability is addressed in PostgresNIO versions starting from 1.14.2. There are no known workarounds for unpatched users.
The weakness was shared 05/09/2023. The identification of this vulnerability is CVE-2023-31136 since 04/24/2023. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
Upgrading to version 1.14.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 2df54bc94607f44584ae6ffa74e3cd754fffafc7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector (GitHub, Inc.): 🔍
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: 🔍
Exploiting
Class: Insufficiently protected credentialsCWE: CWE-522
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: PostgresNIO 1.14.2
Patch: 2df54bc94607f44584ae6ffa74e3cd754fffafc7
Timeline
04/24/2023 🔍05/09/2023 🔍
05/09/2023 🔍
06/01/2023 🔍
Sources
Advisory: 2df54bc94607f44584ae6ffa74e3cd754fffafc7Status: Confirmed
CVE: CVE-2023-31136 (🔍)
GCVE (CVE): GCVE-0-2023-31136
GCVE (VulDB): GCVE-100-228419
Entry
Created: 05/09/2023 16:26Updated: 06/01/2023 08:45
Changes: 05/09/2023 16:26 (51), 06/01/2023 08:45 (2)
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.