usn-2919-1
Vulnerability from osv_ubuntu
Published
2016-03-03 15:12
Modified
2026-04-22 07:36
Summary
jasper vulnerabilities
Details

Jacob Baines discovered that JasPer incorrectly handled ICC color profiles in JPEG-2000 image files. If a user were tricked into opening a specially crafted JPEG-2000 image file, a remote attacker could cause JasPer to crash or possibly execute arbitrary code with user privileges. (CVE-2016-1577)

Tyler Hicks discovered that JasPer incorrectly handled memory when processing JPEG-2000 image files. If a user were tricked into opening a specially crafted JPEG-2000 image file, a remote attacker could cause JasPer to consume memory, resulting in a denial of service. (CVE-2016-2116)

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2016-1577",
              "severity": [
                {
                  "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2016-2116",
              "severity": [
                {
                  "score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:14.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "libjasper-runtime",
            "binary_version": "1.900.1-14ubuntu3.3"
          },
          {
            "binary_name": "libjasper1",
            "binary_version": "1.900.1-14ubuntu3.3"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:14.04:LTS",
        "name": "jasper",
        "purl": "pkg:deb/ubuntu/jasper@1.900.1-14ubuntu3.3?arch=source\u0026distro=trusty"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.900.1-14ubuntu3.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.900.1-14",
        "1.900.1-14ubuntu3",
        "1.900.1-14ubuntu3.1",
        "1.900.1-14ubuntu3.2"
      ]
    }
  ],
  "aliases": [],
  "details": "Jacob Baines discovered that JasPer incorrectly handled ICC color profiles\nin JPEG-2000 image files. If a user were tricked into opening a specially\ncrafted JPEG-2000 image file, a remote attacker could cause JasPer to\ncrash or possibly execute arbitrary code with user privileges.\n(CVE-2016-1577)\n\nTyler Hicks discovered that JasPer incorrectly handled memory when\nprocessing JPEG-2000 image files. If a user were tricked into opening a\nspecially crafted JPEG-2000 image file, a remote attacker could cause\nJasPer to consume memory, resulting in a denial of service.\n(CVE-2016-2116)\n",
  "id": "USN-2919-1",
  "modified": "2026-04-22T07:36:33Z",
  "published": "2016-03-03T15:12:28Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-2919-1"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2016-1577"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2016-2116"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "jasper vulnerabilities",
  "upstream": [
    "UBUNTU-CVE-2016-1577",
    "UBUNTU-CVE-2016-2116"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.