Sam2p vulnerabilitiesRanked by how likely they are to be used.

Product2 versions
The short answer

Sam2p is made by Sam2p Project. We track 18 published vulnerabilities in it, across 2 versions. None of them is on the list of flaws known to be exploited today. If you run Sam2p, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Sam2p vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Sam2p's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Sam2p flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 2.5%

    The DGifDecompressLine function in dgif_lib.c in GIFLIB (possibly version 3.0.x), as later shipped in cgif.c in sam2p 0.49.4, has a heap-based buffer overflow because a certain CrntCode array index is not checked.

    CVSS8.8Published26 May 2018
  2. 2.5%

    There is a heap-based buffer overflow in the pcxLoadRaster function of in_pcx.cpp in sam2p 0.49.4.

    CVSS9.8Published28 Feb 2018
  3. 2.2%

    There is an invalid free in ReadImage in input-bmp.ci that leads to a Segmentation fault in sam2p 0.49.4.

    CVSS9.8Published28 Feb 2018
  4. 2.2%

    There is an invalid free in MiniPS::delete0 in minips.cpp that leads to a Segmentation fault in sam2p 0.49.4.

    CVSS9.8Published28 Feb 2018
  5. 2.2%

    There is an invalid free in Mapping::DoubleHash::clear in mapping.cpp that leads to a Segmentation fault in sam2p 0.49.4.

    CVSS9.8Published28 Feb 2018
  6. 2.1%

    There is a heap-based buffer overflow in ReadImage in input-tga.ci in sam2p 0.49.4 that leads to a denial of service or possibly unspecified other impact.

    CVSS9.8Published20 Jun 2018
  7. 2.1%

    There is a heap-based buffer overflow in bmp_compress1_row in appliers.cpp in sam2p 0.49.4 that leads to a denial of service or possibly unspecified other impact.

    CVSS9.8Published19 Jun 2018
  8. 1.7%

    In sam2p 0.49.3, there is an invalid read of size 2 in the parse_rgb function in in_xpm.cpp.

    CVSS9.8Published22 Sep 2017
  9. 1.7%

    In sam2p 0.49.3, an integer overflow exists in the pcxLoadImage24 function of the file in_pcx.cpp, leading to an invalid write operation.

    CVSS9.8Published21 Sep 2017
Precursor Intelligence

Running Sam2p? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 18 published vulnerabilities listed under the name Sam2p, across 2 versions.

None of Sam2p's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Sam2p. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.