USN-9125-1 (UBUNTU-CVE-2018-20020)

Vulnerability from osv_ubuntu – Published: 2026-11-17 00:06 – Updated: 2026-11-17 00:06 – Source website
VLAI
Summary
ssvnc vulnerabilities
Details

It was discovered that SSVNC incorrectly handled certain CoRRE rectangles, leading to a heap buffer overflow. A malicious VNC server could possibly use this issue to cause SSVNC to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2018-20020)

It was discovered that SSVNC incorrectly handled certain raw rectangles, leading to an infinite loop. A malicious VNC server could possibly use this issue to cause SSVNC to consume excessive resources, leading to a denial of service. (CVE-2018-20021)

It was discovered that SSVNC did not properly initialize certain messages sent to the server. A malicious VNC server could possibly use this issue to obtain sensitive information. (CVE-2018-20022)

It was discovered that SSVNC did not check for memory allocation failures in its zlib and ZRLE decoders, leading to a NULL pointer dereference. A malicious VNC server could possibly use this issue to cause SSVNC to crash, resulting in a denial of service. (CVE-2018-20024)


{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2018-20020",
              "severity": [
                {
                  "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2018-20021",
              "severity": [
                {
                  "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2018-20022",
              "severity": [
                {
                  "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2018-20024",
              "severity": [
                {
                  "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:Pro:18.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "ssvnc",
            "binary_version": "1.0.29-3ubuntu0.1~esm1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:18.04:LTS",
        "name": "ssvnc",
        "purl": "pkg:deb/ubuntu/ssvnc@1.0.29-3ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.0.29-3ubuntu0.1~esm1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.0.29-3",
        "1.0.29-3build1"
      ]
    }
  ],
  "aliases": [],
  "details": "It was discovered that SSVNC incorrectly handled certain CoRRE rectangles,\nleading to a heap buffer overflow. A malicious VNC server could possibly\nuse this issue to cause SSVNC to crash, resulting in a denial of service,\nor possibly execute arbitrary code. (CVE-2018-20020)\n\nIt was discovered that SSVNC incorrectly handled certain raw rectangles,\nleading to an infinite loop. A malicious VNC server could possibly use this\nissue to cause SSVNC to consume excessive resources, leading to a denial of\nservice. (CVE-2018-20021)\n\nIt was discovered that SSVNC did not properly initialize certain messages\nsent to the server. A malicious VNC server could possibly use this issue to\nobtain sensitive information. (CVE-2018-20022)\n\nIt was discovered that SSVNC did not check for memory allocation failures\nin its zlib and ZRLE decoders, leading to a NULL pointer dereference. A\nmalicious VNC server could possibly use this issue to cause SSVNC to crash,\nresulting in a denial of service. (CVE-2018-20024)",
  "id": "USN-9125-1",
  "modified": "2026-11-17T00:06:06Z",
  "published": "2026-11-17T00:06:06Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-9125-1"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2018-20020"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2018-20021"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2018-20022"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2018-20024"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "ssvnc vulnerabilities",
  "upstream": [
    "UBUNTU-CVE-2018-20020",
    "UBUNTU-CVE-2018-20021",
    "UBUNTU-CVE-2018-20022",
    "UBUNTU-CVE-2018-20024"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Loading…

Loading…

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.


Loading…