USN-4536-1 (UBUNTU-CVE-2017-15736)

Vulnerability from osv_ubuntu – Published: 2020-09-24 16:01 – Updated: 2026-04-27 14:11 – Source website
VLAI
Summary
spip vulnerabilities
Details

Youssouf Boulouiz discovered that SPIP incorrectly handled login error messages. A remote attacker could potentially exploit this to conduct cross-site scripting (XSS) attacks. (CVE-2019-16392)

Gilles Vincent discovered that SPIP incorrectly handled password reset requests. A remote attacker could possibly use this issue to cause SPIP to enumerate registered users. (CVE-2019-16394)

Guillaume Fahrner discovered that SPIP did not properly sanitize input. A remote authenticated attacker could possibly use this issue to execute arbitrary code on the host server. (CVE-2019-11071)

Sylvain Lefevre discovered that SPIP incorrectly handled user authorization. A remote attacker could possibly use this issue to modify and publish content and modify the database. (CVE-2019-16391)

It was discovered that SPIP did not properly sanitize input. A remote attacker could, through cross-site scripting (XSS) and PHP injection, exploit this to inject arbitrary web script or HTML. (CVE-2017-15736)

Alexis Zucca discovered that SPIP incorrectly handled the media plugin. A remote authenticated attacker could possibly use this issue to write to the database. (CVE-2019-19830)

Christophe Laffont discovered that SPIP incorrectly handled redirect URLs. An attacker could use this issue to cause SPIP to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2019-16393)

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2017-15736",
              "severity": [
                {
                  "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2019-11071",
              "severity": [
                {
                  "score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2019-16391",
              "severity": [
                {
                  "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2019-16392",
              "severity": [
                {
                  "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2019-16393",
              "severity": [
                {
                  "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2019-16394",
              "severity": [
                {
                  "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:18.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "spip",
            "binary_version": "3.1.4-4~deb9u3build0.18.04.1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "spip",
        "purl": "pkg:deb/ubuntu/spip@3.1.4-4~deb9u3build0.18.04.1?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.1.4-4~deb9u3build0.18.04.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.4-3"
      ]
    }
  ],
  "aliases": [],
  "details": "Youssouf Boulouiz discovered that SPIP incorrectly handled login error\nmessages. A remote attacker could potentially exploit this to conduct\ncross-site scripting (XSS) attacks. (CVE-2019-16392)\n\nGilles Vincent discovered that SPIP incorrectly handled password reset\nrequests. A remote attacker could possibly use this issue to cause SPIP to\nenumerate registered users. (CVE-2019-16394)\n\nGuillaume Fahrner discovered that SPIP did not properly sanitize input. A\nremote authenticated attacker could possibly use this issue to execute\narbitrary code on the host server. (CVE-2019-11071)\n\nSylvain Lefevre discovered that SPIP incorrectly handled user\nauthorization. A remote attacker could possibly use this issue to modify\nand publish content and modify the database. (CVE-2019-16391)\n\nIt was discovered that SPIP did not properly sanitize input. A remote\nattacker could, through cross-site scripting (XSS) and PHP injection,\nexploit this to inject arbitrary web script or HTML. (CVE-2017-15736)\n\nAlexis Zucca discovered that SPIP incorrectly handled the media plugin. A\nremote authenticated attacker could possibly use this issue to write to\nthe database. (CVE-2019-19830)\n\nChristophe Laffont discovered that SPIP incorrectly handled redirect URLs.\nAn attacker could use this issue to cause SPIP to crash, resulting in a\ndenial of service, or possibly execute arbitrary code. (CVE-2019-16393)\n",
  "id": "USN-4536-1",
  "modified": "2026-04-27T14:11:25Z",
  "published": "2020-09-24T16:01:23Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-4536-1"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2017-15736"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2019-11071"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2019-16391"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2019-16392"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2019-16393"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2019-16394"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2019-19830"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "spip vulnerabilities",
  "upstream": [
    "UBUNTU-CVE-2017-15736",
    "UBUNTU-CVE-2019-11071",
    "UBUNTU-CVE-2019-16391",
    "UBUNTU-CVE-2019-16392",
    "UBUNTU-CVE-2019-16393",
    "UBUNTU-CVE-2019-16394",
    "UBUNTU-CVE-2019-19830"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.