Flame through 2.4.0 Information Exposure via GET /api/config
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| pawelmalak | flame | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pawelmalak | Flame |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.425% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pawelmalak
Pawelmalak flame |
|
| Vendors & Products |
Pawelmalak
Pawelmalak flame |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Flame through 2.4.0 contains an information exposure vulnerability in the unauthenticated GET /api/config endpoint that returns the entire configuration object without field redaction. Attackers can retrieve the stored weather API key and internal operational settings by sending a single unauthenticated request to consume provider quota or access sensitive configuration data. | |
| Title | Flame through 2.4.0 Information Exposure via GET /api/config | |
| Weaknesses | CWE-200 | |
| References |
|
|
| Metrics |
cvssV3_1
|