Vulnerability & Exploit Database

Displaying all 6 entries

Results for: CVE-2018-4700 Back to search

Ubuntu: USN-3842-1 (CVE-2018-4700): CUPS vulnerability Vulnerability

  • Severity: 4
  • Published: December 10, 2018

Details for this vulnerability have not been published by NIST at this point. Descriptions from software vendor advisories for this issue are provided below.

From USN-3842-1:

Jann Horn discovered that CUPS incorrectly handled session cookie

randomness. A remote attacker could possibly use this issue to pe...

SUSE: CVE-2018-4700: SUSE Linux Security Advisory Vulnerability

  • Severity: 4
  • Published: December 10, 2018

Details for this vulnerability have not been published by NIST at this point. Descriptions from software vendor advisories for this issue are provided below.

From SUSE_CVE-2018-4700:

This CVE is addressed in the SUSE advisories SUSE-SU-2018:4059-1, SUSE-SU-2018:4089-1, openSUSE-SU-2018:4105-1, openSUSE-SU-2018:4141-...

Vulnerabilities deemed not relevant on Red Hat Enterprise Linux 7 Vulnerability

  • Severity: 1
  • Published: June 10, 2014

This is a placeholder for all CVEs that are not relevant for one reason or another on Red Hat Enterprise Linux 7. Oftentimes Red Hat makes this determination because the affected software was shipped, built or configured in a manner that it made it invulnerable to a given vulnerability.

Vulnerabilities deemed not relevant on Red Hat Enterprise Linux 6 Vulnerability

  • Severity: 1
  • Published: November 10, 2010

This is a placeholder for all CVEs that are not relevant for one reason or another on Red Hat Enterprise Linux 6. Oftentimes Red Hat makes this determination because the affected software was shipped, built or configured in a manner that it made it invulnerable to a given vulnerability.

Vulnerabilities deemed not relevant on Red Hat Enterprise Linux 5 Vulnerability

  • Severity: 1
  • Published: March 15, 2007

This is a placeholder for all CVEs that are not relevant for one reason or another on Red Hat Enterprise Linux 5. Oftentimes Red Hat makes this determination because the affected software was shipped, built or configured in a manner that it made it invulnerable to a given vulnerability.