FKIE_CVE-2025-11232

Vulnerability from fkie_nvd - Published: 2025-10-29 18:15 - Updated: 2026-09-30 23:10
Summary
To trigger the issue, three configuration parameters must have specific settings: "hostname-char-set" must be left at the default setting, which is "[^A-Za-z0-9.-]"; "hostname-char-replacement" must be empty (the default); and "ddns-qualifying-suffix" must *NOT* be empty (the default is empty). DDNS updates do not need to be enabled for this issue to manifest. A client that sends certain option content would then cause kea-dhcp4 to exit unexpectedly. This issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2.
Impacted products
Vendor Product Version

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Kea",
          "vendor": "ISC",
          "versions": [
            {
              "lessThanOrEqual": "3.0.1",
              "status": "affected",
              "version": "3.0.1",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "3.1.2",
              "status": "affected",
              "version": "3.1.1",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "2.6.4",
              "status": "unaffected",
              "version": "2.6.0",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "2.7.9",
              "status": "unaffected",
              "version": "2.7.0",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "3.0.0",
              "status": "unaffected",
              "version": "3.0.0",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "3.1.0",
              "status": "unaffected",
              "version": "3.1.0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "security-officer@isc.org"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "To trigger the issue, three configuration parameters must have specific settings: \"hostname-char-set\" must be left at the default setting, which is \"[^A-Za-z0-9.-]\"; \"hostname-char-replacement\" must be empty (the default); and \"ddns-qualifying-suffix\" must *NOT* be empty (the default is empty). DDNS updates do not need to be enabled for this issue to manifest. A client that sends certain option content would then cause kea-dhcp4 to exit unexpectedly.\nThis issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2."
    },
    {
      "lang": "es",
      "value": "Para desencadenar el problema, tres par\u00e1metros de configuraci\u00f3n deben tener ajustes espec\u00edficos: \u0027hostname-char-set\u0027 debe dejarse en la configuraci\u00f3n predeterminada, que es \u0027[^A-Za-z0-9.-]\u0027; \u0027hostname-char-replacement\u0027 debe estar vac\u00edo (el valor predeterminado); y \u0027ddns-qualifying-suffix\u0027 NO debe estar vac\u00edo (el valor predeterminado es vac\u00edo). Las actualizaciones DDNS no necesitan estar habilitadas para que este problema se manifieste. Un cliente que env\u00eda cierto contenido de opci\u00f3n provocar\u00eda entonces que kea-dhcp4 se cierre inesperadamente. Este problema afecta a las versiones de Kea 3.0.1 a 3.0.1 y 3.1.1 a 3.1.2."
    }
  ],
  "id": "CVE-2025-11232",
  "lastModified": "2026-09-30T23:10:00.237",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6,
        "source": "security-officer@isc.org",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-11232",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2025-10-29T18:22:07.119804Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2025-10-29T18:15:40.197",
  "references": [
    {
      "source": "security-officer@isc.org",
      "url": "https://kb.isc.org/docs/cve-2025-11232"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "http://www.openwall.com/lists/oss-security/2025/10/29/5"
    }
  ],
  "sourceIdentifier": "security-officer@isc.org",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-823"
        }
      ],
      "source": "security-officer@isc.org",
      "type": "Secondary"
    }
  ]
}



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…