| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in SourceForge putmail up to 1.3. This vulnerability affects unknown code of the component Encryption. The manipulation leads to cleartext storage. This vulnerability is documented as CVE-2007-1137. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in SourceForge putmail up to 1.3. This issue affects an unknown code of the component Encryption. The manipulation with an unknown input leads to a cleartext storage vulnerability. Using CWE to declare the problem leads to CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. Impacted is confidentiality. The summary by CVE is:
putmail.py in Putmail before 1.4 does not detect when a user attempts to use TLS with a server that does not support it, which causes putmail.py to send the username and password in plaintext while the user believes encryption is in use, and allows remote attackers to obtain sensitive information.
The weakness was released 02/24/2007 (Website). It is possible to read the advisory at vupen.com. The identification of this vulnerability is CVE-2007-1137 since 02/27/2007. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1555 according to MITRE ATT&CK.
It is declared as proof-of-concept.
Upgrading to version 1.4 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (32689), SecurityFocus (BID 22718†), OSVDB (33764†) and Secunia (SA24266†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
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: Cleartext storageCWE: CWE-312 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: putmail 1.4
Timeline
02/24/2007 🔍02/25/2007 🔍
02/26/2007 🔍
02/26/2007 🔍
02/27/2007 🔍
03/02/2007 🔍
03/13/2015 🔍
08/20/2018 🔍
Sources
Advisory: vupen.com⛔Status: Confirmed
Confirmation: 🔍
CVE: CVE-2007-1137 (🔍)
GCVE (CVE): GCVE-0-2007-1137
GCVE (VulDB): GCVE-100-35291
X-Force: 32689 - Putmail TLS password plaintext
SecurityFocus: 22718 - Putmail Improper Authentication Weakness
Secunia: 24266 - Putmail TLS Authentication Security Issue, Not Critical
OSVDB: 33764 - Putmail putmail.py TLS Authentication Mismatch Cleartext Credential Disclosure
Vupen: ADV-2007-0753
Entry
Created: 03/13/2015 12:16Updated: 08/20/2018 06:58
Changes: 03/13/2015 12:16 (57), 08/20/2018 06:58 (7)
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.