IPFire < v2.29 Stored XSS via Dynamic DNS Host
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| IPFire.org | IPFire | unaffected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Ipfire | Ipfire | — |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 5.3% (5.324% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:ipfire:ipfire:*:*:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update183:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update184:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update185:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update186:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update187:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update188:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update189:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update190:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update191:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update192:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update193:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update194:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update195:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update196:*:*:*:*:*:* cpe:2.3:a:ipfire:ipfire:2.29:core_update197:*:*:*:*:*:* |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ipfire
Ipfire ipfire |
|
| Vendors & Products |
Ipfire
Ipfire ipfire |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | IPFire versions prior to 2.29 (Core Update 198) contain a stored cross-site scripting (XSS) vulnerability that allows an authenticated attacker to inject arbitrary JavaScript code through the SERVICE, LOGIN, and PASSWORD parameters when creating or editing a Dynamic DNS host. When a new Dynamic DNS host is added, the application issues an HTTP POST request to /cgi-bin/ddns.cgi and saves the values of the LOGIN, PASSWORD, and SERVICE parameters. The SERVICE value is displayed after the host entry is created, and the LOGIN and PASSWORD values are displayed when that host entry is edited. The values of these parameters are stored and later rendered in the web interface without proper sanitation or encoding, allowing injected scripts to execute in the context of other users who view or edit the affected Dynamic DNS entries. | |
| Title | IPFire < v2.29 Stored XSS via Dynamic DNS Host | |
| Weaknesses | CWE-79 | |
| References |
| |
| Metrics |
cvssV4_0
|