Skip to content

Product

cbl-mariner moby-engine vulnerabilities

11 published CVES affecting cbl-mariner moby-engine, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
11
Critical
1
High
5
Medium
4
Low
1
Unscored
0
CISA KEV
0

Latest cbl-mariner moby-engine CVEs

Newest publication first

  1. MediumCVSS 4.3 EPSS 0.44%

    tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files. A maliciously-crafted archive containing a large number of sparse regions can cause a Reader to read an unbounded amount of data from the archive into memory. When r...

  2. HighCVSS 7.5 EPSS 0.81%

    golang-jwt is a Go implementation of JSON Web Tokens. Starting in version 3.2.0 and prior to versions 5.2.2 and 4.5.2, the function parse.ParseUnverified splits (via a call to strings.Split) its argument (which is untrusted data) on periods. As a result, in the face of a maliciou...

  3. HighCVSS 7.5 EPSS 0.94%

    SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

  4. HighCVSS 8.1 EPSS 0.64%

    moby through v25.0.3 has a Race Condition vulnerability in the streamformatter package which can be used to trigger multiple concurrent write operations resulting in data corruption or application crashes.

  5. MediumCVSS 6.5 EPSS 0.62%

    moby v25.0.5 is affected by a Race Condition in builder/builder-next/adapters/snapshot/layer.go. The vulnerability could be used to trigger concurrent builds that call the EnsureLayer function resulting in resource leaks/exhaustion.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.