Microsoft Azure Front Door HTTP Header Content-Length Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Microsoft Azure Front Door. This issue affects some unknown processing of the component HTTP Header Handler. This manipulation of the argument Content-Length causes an unknown weakness. The attack is possible to be carried out remotely. No exploit exists. This product is a managed service, so users do not have direct control over vulnerability countermeasures.
Details
A vulnerability has been found in Microsoft Azure Front Door (Cloud Software) (affected version not known) and classified as critical. Affected by this vulnerability is some unknown functionality of the component HTTP Header Handler. The manipulation of the argument Content-Length with an unknown input leads to a unknown weakness. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 09/25/2023. The advisory is shared at blog.jeti.pw. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/25/2023).
This product is available as a managed service. Users are not able to maintain vulnerability countermeasures themselves.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Managed Service
- yes
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.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: 🔍
Exploiting
Class: Remote Code ExecutionCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
Status: 🔍0-Day Time: 🔍
Timeline
09/25/2023 🔍09/25/2023 🔍
09/25/2023 🔍
Sources
Vendor: microsoft.comAdvisory: blog.jeti.pw
Status: Not defined
CVE: Not possible due to CNA Operational Rules
GCVE (VulDB): GCVE-100-240277
Entry
Created: 09/25/2023 16:34Changes: 09/25/2023 16:34 (38)
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.