UBUNTU-CVE-2025-59729 (CVE-2025-59729)

Vulnerability from osv_ubuntu – Published: 2025-10-06 08:15 – Updated: 2026-04-22 07:56 – Source website
VLAI
Details

When parsing the header for a DHAV file, there's an integer underflow in offset calculation that leads to reading the duration from before the start of the allocated buffer. If we load a DHAV file that is larger than MAX_DURATION_BUFFER_SIZE bytes (0x100000) for example 0x101000 bytes, then at [0] we have size = 0x101000. At [1] we have end_buffer_size = 0x100000, and at [2] we have end_buffer_pos = 0x1000. The loop then scans backwards through the buffer looking for the dhav tag; when it is found, we'll calculate end_pos based on a 32-bit offset read from the buffer. There is subsequently a check [3] that end_pos is within the section of the file that has been copied into end_buffer, but it only correctly handles the cases where end_pos is before the start of the file or after the section copied into end_buffer, and not the case where end_pos is within the the file, but before the section copied into end_buffer. If we provide such an offset, (end_pos - end_buffer_pos) can underflow, resulting in the subsequent access at [4] occurring before the beginning of the allocation. We recommend upgrading to version 8.0 or beyond.


{
  "affected": [
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libav-tools",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavcodec-extra",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavcodec-extra-54",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavcodec54",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavdevice-extra-53",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavdevice53",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavfilter-extra-3",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavfilter3",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavformat-extra-54",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavformat54",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavresample1",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavutil-extra-52",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libavutil52",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libswscale-extra-2",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          },
          {
            "binary_name": "libswscale2",
            "binary_version": "6:9.20-0ubuntu0.14.04.1+esm1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:14.04:LTS",
        "name": "libav",
        "purl": "pkg:deb/ubuntu/libav@6:9.20-0ubuntu0.14.04.1+esm1?arch=source\u0026distro=esm-infra-legacy/trusty"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6:0.8.7-1ubuntu2",
        "6:9.10-1ubuntu1",
        "6:9.10-1ubuntu2",
        "6:9.10-1ubuntu5",
        "6:9.10-1ubuntu6",
        "6:9.10-1ubuntu7",
        "6:9.11-2ubuntu1",
        "6:9.11-2ubuntu2",
        "6:9.13-0ubuntu0.14.04.1",
        "6:9.14-0ubuntu0.14.04.1",
        "6:9.16-0ubuntu0.14.04.1",
        "6:9.18-0ubuntu0.14.04.1",
        "6:9.20-0ubuntu0.14.04.1",
        "6:9.20-0ubuntu0.14.04.1+esm1"
      ]
    }
  ],
  "aliases": [],
  "details": "When parsing the header for a DHAV file, there\u0027s an integer underflow in offset calculation that leads to reading the duration from before the start of the allocated buffer. If we load a DHAV file that is larger than MAX_DURATION_BUFFER_SIZE\u00a0bytes (0x100000) for example 0x101000 bytes, then at [0] we have size = 0x101000. At [1] we have end_buffer_size = 0x100000, and at [2] we have end_buffer_pos = 0x1000. The loop then scans backwards through the buffer looking for the dhav\u00a0tag; when it is found, we\u0027ll calculate end_pos\u00a0based on a 32-bit offset read from the buffer. There is subsequently a check [3] that end_pos\u00a0is within the section of the file that has been copied into end_buffer, but it only correctly handles the cases where end_pos\u00a0is before the start of the file\u00a0or after the section copied into end_buffer, and not the case where end_pos\u00a0is within the the file, but before the section copied into end_buffer. If we provide such an offset, (end_pos - end_buffer_pos)\u00a0can underflow, resulting in the subsequent access at [4] occurring before the beginning of the allocation. We recommend upgrading to version 8.0 or beyond.",
  "id": "UBUNTU-CVE-2025-59729",
  "modified": "2026-04-22T07:56:55Z",
  "published": "2025-10-06T08:15:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2025-59729"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-59729"
    },
    {
      "type": "REPORT",
      "url": "https://issuetracker.google.com/433513232"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:P/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N",
      "type": "CVSS_V4"
    },
    {
      "score": "medium",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2025-59729"
  ]
}



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…