CVE-2019-16391
First published: Tue Sep 17 2019(Updated: )
Last updated 24 July 2024
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Spip Spip | <3.1.11 | |
| Spip Spip | >=3.2.0<3.2.5 | |
| Canonical Ubuntu Linux | =18.04 | |
| Debian Debian Linux | =8.0 | |
| Debian Debian Linux | =9.0 | |
| Debian Debian Linux | =10.0 | |
| debian/spip | 3.2.11-3+deb11u10 3.2.11-3+deb11u7 4.3.2+dfsg-1 4.3.3+dfsg-1 |
Remedy
https://blog.spip.net/Mise-a-jour-CRITIQUE-de-securite-Sortie-de-SPIP-3-2-5-et-SPIP-3-1-11.html
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://blog.spip.net/Mise-a-jour-CRITIQUE-de-securite-Sortie-de-SPIP-3-2-5-et-SPIP-3-1-11.html
- https://blog.spip.net/Mise-a-jour-CRITIQUE-de-securite-Sortie-de-SPIP-3-2-5-et-SPIP-3-1-11.html?lang=fr
- https://git.spip.net/SPIP/spip/commit/187952ce85e73b52c2753f2d54fc2c44807b8f79
- https://git.spip.net/SPIP/spip/commit/3cbc758400323ab006c00ea78eacdb8f76aa5f66
- https://lists.debian.org/debian-lts-announce/2019/10/msg00038.html
- https://seclists.org/bugtraq/2019/Sep/40
- https://usn.ubuntu.com/4536-1/
- https://www.debian.org/security/2019/dsa-4532
- https://launchpad.net/bugs/cve/CVE-2019-16391
- https://security-tracker.debian.org/tracker/CVE-2019-16391
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16391
- https://nvd.nist.gov/vuln/detail/CVE-2019-16391
- https://ubuntu.com/security/CVE-2019-16391
Frequently Asked Questions
What is the severity of CVE-2019-16391?
The severity of CVE-2019-16391 is medium with a CVSS score of 6.5.
How can authenticated visitors modify content in SPIP before version 3.1.11 and 3.2 before 3.2.5?
Authenticated visitors can modify any published content in SPIP before version 3.1.11 and 3.2 before 3.2.5 by exploiting vulnerabilities in ecrire/inc/meta.php and ecrire/inc/securiser_action.php.
Which versions of SPIP are affected by CVE-2019-16391?
Versions of SPIP before 3.1.11 and 3.2 before 3.2.5 are affected by CVE-2019-16391.
How can I fix CVE-2019-16391?
To fix CVE-2019-16391, update SPIP to version 3.1.11 or 3.2.5.
Where can I find more information about CVE-2019-16391?
You can find more information about CVE-2019-16391 on the SPIP blog and the SPIP git repository.
- collector/nvd-index
- agent/type
- agent/remedy
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- agent/severity
- agent/description
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/references
- agent/tags
- collector/security-tracker-debian
- source/Debian
- agent/softwarecombine
- collector/usn-cve
- source/Ubuntu
- vendor/spip
- canonical/spip spip
- version/spip spip/3.2.0
- vendor/canonical
- canonical/canonical ubuntu linux
- version/canonical ubuntu linux/18.04
- vendor/debian
- canonical/debian debian linux
- version/debian debian linux/8.0
- version/debian debian linux/9.0
- version/debian debian linux/10.0
- package-manager/debian