Fortinet FortiMail up to 6.0.11/6.3.7/6.4.5/7.0.1 URI Protection Service cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Fortinet FortiMail up to 6.0.11/6.3.7/6.4.5/7.0.1. This impacts an unknown function of the component URI Protection Service. Executing a manipulation can lead to cross site scripting. The identification of this vulnerability is CVE-2021-43062. The attack may be launched remotely. Furthermore, there is an exploit available.
Details
A vulnerability classified as problematic was found in Fortinet FortiMail up to 6.0.11/6.3.7/6.4.5/7.0.1. This vulnerability affects some unknown functionality of the component URI Protection Service. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity.
The weakness was shared 02/02/2022 as FG-IR-21-185. The advisory is shared for download at fortiguard.com. This vulnerability was named CVE-2021-43062 since 10/28/2021. Successful exploitation requires user interaction by the victim. Technical details are unknown but a public exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.007.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
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 vulnerability database at Exploit-DB (50759). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 6.0.0
- 6.0.1
- 6.0.2
- 6.0.3
- 6.0.4
- 6.0.5
- 6.0.6
- 6.0.7
- 6.0.8
- 6.0.9
- 6.0.10
- 6.0.11
- 6.3.0
- 6.3.1
- 6.3.2
- 6.3.3
- 6.3.4
- 6.3.5
- 6.3.6
- 6.3.7
- 6.4.0
- 6.4.1
- 6.4.2
- 6.4.3
- 6.4.4
- 6.4.5
- 7.0.0
- 7.0.1
License
Website
- Vendor: https://www.fortinet.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.1
CNA Vector (Fortinet, 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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/28/2021 🔍02/02/2022 🔍
02/02/2022 🔍
05/01/2025 🔍
Sources
Vendor: fortinet.comAdvisory: FG-IR-21-185
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2021-43062 (🔍)
GCVE (CVE): GCVE-0-2021-43062
GCVE (VulDB): GCVE-100-192124
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/02/2022 14:28Updated: 05/01/2025 20:52
Changes: 02/02/2022 14:28 (48), 02/04/2022 16:00 (2), 02/04/2022 16:06 (1), 11/23/2024 12:36 (23), 05/01/2025 20:52 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.