First published: Sat Jun 17 2017(Updated: )
SPIP 3.1.x before 3.1.6 and 3.2.x before Beta 3 does not remove shell metacharacters from the host field, allowing a remote attacker to cause remote code execution.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Spip | =3.1.0 | |
Spip | =3.1.0-alpha | |
Spip | =3.1.0-beta | |
Spip | =3.1.0-rc | |
Spip | =3.1.0-rc2 | |
Spip | =3.1.0-rc3 | |
Spip | =3.1.1 | |
Spip | =3.1.2 | |
Spip | =3.1.3 | |
Spip | =3.1.4 | |
Spip | =3.1.5 | |
Spip | =3.2-alpha-1 | |
Spip | =3.2.0-beta | |
Spip | =3.2.0-beta2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-9736 has been classified as a critical vulnerability as it allows remote code execution.
To fix CVE-2017-9736, upgrade your SPIP installation to version 3.1.6 or 3.2 Beta 3 or later.
CVE-2017-9736 affects SPIP versions 3.1.x before 3.1.6 and 3.2.x before Beta 3.
CVE-2017-9736 allows remote attackers to execute arbitrary code on vulnerable SPIP installations.
Yes, a patch is included in SPIP versions 3.1.6 and 3.2 Beta 3 to mitigate CVE-2017-9736.