Formmail.php 5.0 formmail.php (auto-reply) information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Formmail.php 5.0. It has been declared as problematic. This affects an unknown part of the file formmail.php. The manipulation of the argument (auto-reply) results in information disclosure. This vulnerability was named CVE-2004-1431. There is no available exploit.
Details
A vulnerability, which was classified as problematic, was found in Formmail.php 5.0 (Programming Language Software). Affected is some unknown processing of the file formmail.php. The manipulation of the argument (auto-reply) with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:
FormMail.php 5.0, and possibly other versions, allows remote attackers to read arbitrary files via a full pathname in the ar_file (auto-reply) parameter.
The weakness was presented 12/31/2004 as not defined posting (Bugtraq). The advisory is shared for download at marc.theaimsgroup.com. This vulnerability is traded as CVE-2004-1431 since 02/12/2005. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
By approaching the search of inurl:formmail.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (18724), SecurityFocus (BID 12145†) and Secunia (SA10815†). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/09/2004 🔍12/31/2004 🔍
12/31/2004 🔍
01/01/2005 🔍
02/12/2005 🔍
02/27/2015 🔍
07/15/2017 🔍
Sources
Advisory: marc.theaimsgroup.comStatus: Not defined
CVE: CVE-2004-1431 (🔍)
GCVE (CVE): GCVE-0-2004-1431
GCVE (VulDB): GCVE-100-22728
X-Force: 18724 - Jack`s FormMail.php ar_file view files
SecurityFocus: 12145 - Joe Lumbroso FormMail.php Arbitrary Remote File Access Vulnerability
Secunia: 10815 - Jacks FormMail.php Two Vulnerabilities, Highly Critical
Entry
Created: 02/27/2015 15:50Updated: 07/15/2017 08:42
Changes: 02/27/2015 15:50 (53), 07/15/2017 08:42 (6)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.