SquirrelMail 1.4.0 To Field parseAddress privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in SquirrelMail 1.4.0 and classified as critical. Affected is the function parseAddress of the component To Field Handler. This manipulation causes privileges management.
This vulnerability appears as CVE-2003-0990. In addition, an exploit is available.
Details
A vulnerability classified as critical was found in SquirrelMail 1.4.0 (Mail Client Software). Affected by this vulnerability is the function parseAddress of the component To Field Handler. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The parseAddress code in (1) SquirrelMail 1.4.0 and (2) GPG Plugin 1.1 allows remote attackers to execute commands via shell metacharacters in the "To:" field.
The weakness was presented 01/20/2004 as not defined posting (Bugtraq). The advisory is shared at marc.theaimsgroup.com. This vulnerability is known as CVE-2003-0990 since 12/16/2003. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1068 for this issue.
It is possible to download the exploit at exploit-db.com. It is declared as highly functional.
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 (14079), Exploit-DB (16888) and SecurityFocus (BID 9296†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
MetaSploit ID: squirrelmail_pgp_plugin.rb
MetaSploit Name: SquirrelMail PGP Plugin Command Execution (SMTP)
MetaSploit File: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/16/2003 🔍12/25/2003 🔍
01/20/2004 🔍
01/20/2004 🔍
09/30/2014 🔍
12/08/2024 🔍
Sources
Advisory: marc.theaimsgroup.comStatus: Not defined
CVE: CVE-2003-0990 (🔍)
GCVE (CVE): GCVE-0-2003-0990
GCVE (VulDB): GCVE-100-21493
X-Force: 14079 - SquirrelMail parseAddress command execution
SecurityFocus: 9296 - Squirrelmail G/PGP Encryption Plugin Remote Command Execution Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/30/2014 15:35Updated: 12/08/2024 16:24
Changes: 09/30/2014 15:35 (52), 07/05/2017 08:58 (6), 12/08/2024 16:24 (24)
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.