GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

OESA-2022-1993 (CVE-2021-25215)

Vulnerability from osv_openeuler – Published: 2022-10-14 11:05 – Updated: 2026-08-06 11:05 – Source website
VLAI
Summary
dhcp security update
Details

The Dynamic Host Configuration Protocol (DHCP) is a network management protocol used on UDP/IP networks whereby a DHCP server dynamically assigns an IP address and other network configuration parameters to each device on a network so they can communicate with other IP networks.

Security Fix(es):

In BIND 9.0.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND 9.17 development branch, when a vulnerable version of named receives a query for a record triggering the flaw described above, the named process will terminate due to a failed assertion check. The vulnerability affects all currently maintained BIND 9 branches (9.11, 9.11-S, 9.16, 9.16-S, 9.17) as well as all other versions of BIND 9.(CVE-2021-25215)

In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND 9.17 development branch, when a vulnerable version of named receives a malformed IXFR triggering the flaw described above, the named process will terminate due to a failed assertion the next time the transferred secondary zone is refreshed.(CVE-2021-25214)

In BIND 9.3.0 -> 9.11.35, 9.12.0 -> 9.16.21, and versions 9.9.3-S1 -> 9.11.35-S1 and 9.16.8-S1 -> 9.16.21-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.18 of the BIND 9.17 development branch, exploitation of broken authoritative servers using a flaw in response processing can cause degradation in BIND resolver performance. The way the lame cache is currently designed makes it possible for its internal data structures to grow almost infinitely, which may cause significant delays in client query processing.(CVE-2021-25219)

BIND 9.11.0 -> 9.11.36 9.12.0 -> 9.16.26 9.17.0 -> 9.18.0 BIND Supported Preview Editions: 9.11.4-S1 -> 9.11.36-S1 9.16.8-S1 -> 9.16.26-S1 Versions of BIND 9 earlier than those shown - back to 9.1.0, including Supported Preview Editions - are also believed to be affected but have not been tested as they are EOL. The cache could become poisoned with incorrect records leading to queries being made to the wrong servers, which might also result in false information being returned to clients.(CVE-2021-25220)


{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "dhcp-devel-4.4.2-8.oe1.aarch64.rpm",
          "dhcp-debuginfo-4.4.2-8.oe1.aarch64.rpm",
          "dhcp-4.4.2-8.oe1.aarch64.rpm",
          "dhcp-debugsource-4.4.2-8.oe1.aarch64.rpm"
        ],
        "noarch": [
          "dhcp-help-4.4.2-8.oe1.noarch.rpm"
        ],
        "src": [
          "dhcp-4.4.2-8.oe1.src.rpm"
        ],
        "x86_64": [
          "dhcp-4.4.2-8.oe1.x86_64.rpm",
          "dhcp-debugsource-4.4.2-8.oe1.x86_64.rpm",
          "dhcp-debuginfo-4.4.2-8.oe1.x86_64.rpm",
          "dhcp-devel-4.4.2-8.oe1.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP1",
        "name": "dhcp",
        "purl": "pkg:rpm/openEuler/dhcp\u0026distro=openEuler-20.03-LTS-SP1"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.4.2-8.oe1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "dhcp-devel-4.4.2-8.oe1.aarch64.rpm",
          "dhcp-debugsource-4.4.2-8.oe1.aarch64.rpm",
          "dhcp-debuginfo-4.4.2-8.oe1.aarch64.rpm",
          "dhcp-4.4.2-8.oe1.aarch64.rpm"
        ],
        "noarch": [
          "dhcp-help-4.4.2-8.oe1.noarch.rpm"
        ],
        "src": [
          "dhcp-4.4.2-8.oe1.src.rpm"
        ],
        "x86_64": [
          "dhcp-devel-4.4.2-8.oe1.x86_64.rpm",
          "dhcp-debugsource-4.4.2-8.oe1.x86_64.rpm",
          "dhcp-debuginfo-4.4.2-8.oe1.x86_64.rpm",
          "dhcp-4.4.2-8.oe1.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP3",
        "name": "dhcp",
        "purl": "pkg:rpm/openEuler/dhcp\u0026distro=openEuler-20.03-LTS-SP3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.4.2-8.oe1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "dhcp-debuginfo-4.4.2-14.oe2203.aarch64.rpm",
          "dhcp-devel-4.4.2-14.oe2203.aarch64.rpm",
          "dhcp-4.4.2-14.oe2203.aarch64.rpm",
          "dhcp-debugsource-4.4.2-14.oe2203.aarch64.rpm"
        ],
        "noarch": [
          "dhcp-help-4.4.2-14.oe2203.noarch.rpm"
        ],
        "src": [
          "dhcp-4.4.2-14.oe2203.src.rpm"
        ],
        "x86_64": [
          "dhcp-debugsource-4.4.2-14.oe2203.x86_64.rpm",
          "dhcp-4.4.2-14.oe2203.x86_64.rpm",
          "dhcp-devel-4.4.2-14.oe2203.x86_64.rpm",
          "dhcp-debuginfo-4.4.2-14.oe2203.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:22.03-LTS",
        "name": "dhcp",
        "purl": "pkg:rpm/openEuler/dhcp\u0026distro=openEuler-22.03-LTS"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.4.2-14.oe2203"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "High"
  },
  "details": "The Dynamic Host Configuration Protocol (DHCP) is a network management protocol used on UDP/IP networks whereby a DHCP server dynamically assigns an IP address and other network configuration parameters to each device on a network so they can communicate with other IP networks.\r\n\r\nSecurity Fix(es):\r\n\r\nIn BIND 9.0.0 -\u0026gt; 9.11.29, 9.12.0 -\u0026gt; 9.16.13, and versions BIND 9.9.3-S1 -\u0026gt; 9.11.29-S1 and 9.16.8-S1 -\u0026gt; 9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -\u0026gt; 9.17.11 of the BIND 9.17 development branch, when a vulnerable version of named receives a query for a record triggering the flaw described above, the named process will terminate due to a failed assertion check. The vulnerability affects all currently maintained BIND 9 branches (9.11, 9.11-S, 9.16, 9.16-S, 9.17) as well as all other versions of BIND 9.(CVE-2021-25215)\r\n\r\nIn BIND 9.8.5 -\u0026gt; 9.8.8, 9.9.3 -\u0026gt; 9.11.29, 9.12.0 -\u0026gt; 9.16.13, and versions BIND 9.9.3-S1 -\u0026gt; 9.11.29-S1 and 9.16.8-S1 -\u0026gt; 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -\u0026gt; 9.17.11 of the BIND 9.17 development branch, when a vulnerable version of named receives a malformed IXFR triggering the flaw described above, the named process will terminate due to a failed assertion the next time the transferred secondary zone is refreshed.(CVE-2021-25214)\r\n\r\nIn BIND 9.3.0 -\u0026gt; 9.11.35, 9.12.0 -\u0026gt; 9.16.21, and versions 9.9.3-S1 -\u0026gt; 9.11.35-S1 and 9.16.8-S1 -\u0026gt; 9.16.21-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -\u0026gt; 9.17.18 of the BIND 9.17 development branch, exploitation of broken authoritative servers using a flaw in response processing can cause degradation in BIND resolver performance. The way the lame cache is currently designed makes it possible for its internal data structures to grow almost infinitely, which may cause significant delays in client query processing.(CVE-2021-25219)\r\n\r\nBIND 9.11.0 -\u0026gt; 9.11.36 9.12.0 -\u0026gt; 9.16.26 9.17.0 -\u0026gt; 9.18.0 BIND Supported Preview Editions: 9.11.4-S1 -\u0026gt; 9.11.36-S1 9.16.8-S1 -\u0026gt; 9.16.26-S1 Versions of BIND 9 earlier than those shown - back to 9.1.0, including Supported Preview Editions - are also believed to be affected but have not been tested as they are EOL. The cache could become poisoned with incorrect records leading to queries being made to the wrong servers, which might also result in false information being returned to clients.(CVE-2021-25220)",
  "id": "OESA-2022-1993",
  "modified": "2026-08-06T11:05:18Z",
  "published": "2022-10-14T11:05:18Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2022-1993"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-25215"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-25214"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-25219"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-25220"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "dhcp security update",
  "upstream": [
    "CVE-2021-25215",
    "CVE-2021-25214",
    "CVE-2021-25219",
    "CVE-2021-25220"
  ]
}



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…

Detection rules are retrieved from Rulezet.

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…