fkie_cve-2022-3924
Vulnerability from fkie_nvd
Published
2023-01-26 21:16
Modified
2024-11-21 07:20
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero. If the resolver receives many queries that require recursion, there will be a corresponding increase in the number of clients that are waiting for recursion to complete. If there are sufficient clients already waiting when a new client query is received so that it is necessary to SERVFAIL the longest waiting client (see BIND 9 ARM `recursive-clients` limit and soft quota), then it is possible for a race to occur between providing a stale answer to this older client and sending an early timeout SERVFAIL, which may cause an assertion failure. This issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.12-S1 through 9.16.36-S1.
References
security-officer@isc.orghttps://kb.isc.org/docs/cve-2022-3924Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://kb.isc.org/docs/cve-2022-3924Vendor Advisory
Impacted products
Vendor Product Version
isc bind *
isc bind *
isc bind *
isc bind 9.16.12
isc bind 9.16.13
isc bind 9.16.14
isc bind 9.16.21
isc bind 9.16.32
isc bind 9.16.36


To clipboard 

{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:a:isc:bind:*:*:*:*:-:*:*:*",
                     matchCriteriaId: "FC5F91EF-B660-42FF-9B48-880299C9A128",
                     versionEndExcluding: "9.16.37",
                     versionStartIncluding: "9.16.12",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:isc:bind:*:*:*:*:-:*:*:*",
                     matchCriteriaId: "92119B97-ADE6-47C0-B3E2-3B05C08A0B99",
                     versionEndExcluding: "9.18.11",
                     versionStartIncluding: "9.18.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:isc:bind:*:*:*:*:-:*:*:*",
                     matchCriteriaId: "CB820E6D-F56C-4222-A3FF-3A02266FD68B",
                     versionEndExcluding: "9.19.9",
                     versionStartIncluding: "9.19.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:isc:bind:9.16.12:s1:*:*:supported_preview:*:*:*",
                     matchCriteriaId: "1B20F152-D0C3-4F07-83B3-5EA6B116F005",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:isc:bind:9.16.13:s1:*:*:supported_preview:*:*:*",
                     matchCriteriaId: "94661BA2-27F8-4FFE-B844-9404F735579D",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:isc:bind:9.16.14:s1:*:*:supported_preview:*:*:*",
                     matchCriteriaId: "53593603-E2AF-4925-A6E6-109F097A0FF2",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:isc:bind:9.16.21:s1:*:*:supported_preview:*:*:*",
                     matchCriteriaId: "751E37C2-8BFD-4306-95C1-8C01CE495FA4",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:isc:bind:9.16.32:s1:*:*:supported_preview:*:*:*",
                     matchCriteriaId: "CC432820-F1A2-4132-A673-2620119553C5",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:isc:bind:9.16.36:s1:*:*:supported_preview:*:*:*",
                     matchCriteriaId: "F70347F2-6750-4497-B8F4-2036F4F4443A",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero.\n\nIf the resolver receives many queries that require recursion, there will be a corresponding increase in the number of clients that are waiting for recursion to complete. If there are sufficient clients already waiting when a new client query is received so that it is necessary to SERVFAIL the longest waiting client (see BIND 9 ARM `recursive-clients` limit and soft quota), then it is possible for a race to occur between providing a stale answer to this older client and sending an early timeout SERVFAIL, which may cause an assertion failure.\nThis issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.12-S1 through 9.16.36-S1.",
      },
      {
         lang: "es",
         value: "Este problema puede afectar a los solucionadores BIND 9 con `stale-answer-enable yes;` que también utilizan la opción `stale-answer-client-timeout`, configurada con un valor mayor que cero. Si el solucionador recibe muchas consultas que requieren recursividad, habrá un aumento correspondiente en la cantidad de clientes que están esperando que se complete la recursividad. Si ya hay suficientes clientes esperando cuando se recibe una nueva consulta de cliente, por lo que es necesario SERVFAIL al cliente que espera más tiempo (consulte el límite y la cuota suave de `clientes recursivos` de BIND 9 ARM), entonces es posible que se produzca una carrera. entre proporcionar una respuesta obsoleta a este cliente anterior y enviar un SERVFAIL de tiempo de espera anticipado, que puede provocar un error de aserción. Este problema afecta a las versiones de BIND 9, 9.16.12 a 9.16.36, 9.18.0 a 9.18.10, 9.19.0 a 9.19.8 y 9.16.12-S1 a 9.16.36-S1.",
      },
   ],
   id: "CVE-2022-3924",
   lastModified: "2024-11-21T07:20:32.627",
   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",
         },
         {
            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: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2023-01-26T21:16:03.273",
   references: [
      {
         source: "security-officer@isc.org",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://kb.isc.org/docs/cve-2022-3924",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://kb.isc.org/docs/cve-2022-3924",
      },
   ],
   sourceIdentifier: "security-officer@isc.org",
   vulnStatus: "Modified",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-617",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.