GeoNetwork XSS in AngularJS error pages
geonetwork core-geonetwork
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.geonetwork-opensource:geonetwork Maven |
|
|
geonetwork core-geonetwork
| Product | Affected | Fixed in |
|---|---|---|
| org.geonetwork-opensource:geonetwork Maven |
|
|
GeoNetwork is a catalog application to manage spatially referenced resources. From 3.0.0 until 4.2.15 and 4.4.10, requesting a nonexistent or unauthorized service URL can cause an error page to reflect attacker-controlled request content inside an AngularJS application without adequately neutralizing it for template evaluation. A remote attacker can induce a victim, including an administrator, to open a crafted link so the reflected value is evaluated as an AngularJS template expression. Combined with known AngularJS sandbox-escape techniques, this can execute arbitrary JavaScript in the victim's authenticated browser session, disclose information, or perform actions as the victim. This issue is fixed in versions 4.2.15 and 4.4.10.
From the CVE record · GitHub_M
GeoNetwork error pages can evaluate attacker-controlled content from a nonexistent or unauthorized service URL as an AngularJS template expression. A remote attacker can lure a victim into opening a crafted link, potentially executing JavaScript in the victim’s browser session to disclose information or act as the victim. The attacker does not need authentication; the victim must open the link.
Teams running Maven package org.geonetwork-opensource:geonetwork in versions 3.0.0–3.12.12, 4.0.0-alpha.1–4.0.6, 4.2.0–before 4.2.15, or 4.4.0–before 4.4.10 should check their deployments.