AtMail AtMail Open up to 1.3 Webmail Client compose.php unique path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in AtMail AtMail Open up to 1.3. The affected element is an unknown function of the file compose.php of the component Webmail Client. This manipulation of the argument unique causes path traversal. This vulnerability is tracked as CVE-2012-1917. No exploit exists. You should upgrade the affected component.
Details
A vulnerability classified as problematic was found in AtMail AtMail Open up to 1.3. Affected by this vulnerability is some unknown functionality of the file compose.php of the component Webmail Client. The manipulation of the argument unique with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality. The summary by CVE is:
compose.php in @Mail WebMail Client in AtMail Open-Source before 1.05 does not properly handle ../ (dot dot slash) sequences in the unique parameter, which allows remote attackers to conduct directory traversal attacks and read arbitrary files via a ..././ (dot dot dot slash dot slash) sequence.
The weakness was disclosed 03/27/2012 as confirmed advisory (CERT.org). The advisory is shared at kb.cert.org. This vulnerability is known as CVE-2012-1917 since 03/27/2012. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
By approaching the search of inurl:compose.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.04 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Secunia (SA47012†). The entries VDB-60520, VDB-60519, VDB-60518 and VDB-60516 are pretty similar. 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: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: AtMail Open 1.04
Timeline
03/27/2012 🔍03/27/2012 🔍
03/27/2012 🔍
03/23/2015 🔍
08/09/2024 🔍
Sources
Advisory: kb.cert.orgStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2012-1917 (🔍)
GCVE (CVE): GCVE-0-2012-1917
GCVE (VulDB): GCVE-100-60517
CERT: 🔍
Secunia: 47012
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 08/09/2024 20:46
Changes: 03/23/2015 16:50 (51), 01/24/2018 10:20 (3), 08/09/2024 20:46 (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.