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

FKIE_CVE-2021-4239

Vulnerability from fkie_nvd - Published: 2022-12-27 22:15 - Updated: 2026-06-17 04:19
Severity
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Summary
The Noise protocol implementation suffers from weakened cryptographic security after encrypting 2^64 messages, and a potential denial of service attack. After 2^64 (~18.4 quintillion) messages are encrypted with the Encrypt function, the nonce counter will wrap around, causing multiple messages to be encrypted with the same key and nonce. In a separate issue, the Decrypt function increments the nonce state even when it fails to decrypt a message. If an attacker can provide an invalid input to the Decrypt function, this will cause the nonce state to desynchronize between the peers, resulting in a failure to encrypt all subsequent messages.
References
security@golang.orghttps://github.com/flynn/noise/pull/44Patch, Third Party Advisory
security@golang.orghttps://pkg.go.dev/vuln/GO-2022-0425Patch, Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/flynn/noise/pull/44Patch, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://pkg.go.dev/vuln/GO-2022-0425Patch, Vendor Advisory
Impacted products
Vendor Product Version
noiseprotocol noise -
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "collectionURL": "https://pkg.go.dev",
          "defaultStatus": "unaffected",
          "packageName": "github.com/flynn/noise",
          "product": "github.com/flynn/noise",
          "programRoutines": [
            {
              "name": "CipherState.Encrypt"
            },
            {
              "name": "CipherState.Decrypt"
            },
            {
              "name": "symmetricState.EncryptAndHash"
            },
            {
              "name": "HandshakeState.ReadMessage"
            },
            {
              "name": "HandshakeState.WriteMessage"
            },
            {
              "name": "symmetricState.DecryptAndHash"
            }
          ],
          "vendor": "github.com/flynn/noise",
          "versions": [
            {
              "lessThan": "1.0.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "source": "security@golang.org"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:noiseprotocol:noise:-:*:*:*:*:go:*:*",
              "matchCriteriaId": "09D5D86A-ADA9-4223-B806-D248CD55F94A",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "The Noise protocol implementation suffers from weakened cryptographic security after encrypting 2^64 messages, and a potential denial of service attack. After 2^64 (~18.4 quintillion) messages are encrypted with the Encrypt function, the nonce counter will wrap around, causing multiple messages to be encrypted with the same key and nonce. In a separate issue, the Decrypt function increments the nonce state even when it fails to decrypt a message. If an attacker can provide an invalid input to the Decrypt function, this will cause the nonce state to desynchronize between the peers, resulting in a failure to encrypt all subsequent messages."
    },
    {
      "lang": "es",
      "value": "La implementaci\u00f3n del protocolo Noise sufre de seguridad criptogr\u00e1fica debilitada despu\u00e9s de cifrar 2^64 mensajes y un posible ataque de denegaci\u00f3n de servicio. Despu\u00e9s de cifrar 2^64 (~18,4 quintillones) de mensajes con la funci\u00f3n Encrypt , el contador nonce se ajustar\u00e1, lo que provocar\u00e1 que se cifren varios mensajes con la misma clave y nonce. En un tema aparte, la funci\u00f3n Decrypt incrementa el estado nonce incluso cuando no logra descifrar un mensaje. Si un atacante puede proporcionar una entrada no v\u00e1lida a la funci\u00f3n Decrypt, esto har\u00e1 que el estado nonce se desincronice entre los pares, lo que resultar\u00e1 en un fallo al cifrar todos los mensajes posteriores."
    }
  ],
  "id": "CVE-2021-4239",
  "lastModified": "2026-06-17T04:19:19.820",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "NONE",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6,
        "source": "nvd@nist.gov",
        "type": "Primary"
      },
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "NONE",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2021-4239",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2025-04-14T16:59:11.062582Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2022-12-27T22:15:12.123",
  "references": [
    {
      "source": "security@golang.org",
      "tags": [
        "Patch",
        "Third Party Advisory"
      ],
      "url": "https://github.com/flynn/noise/pull/44"
    },
    {
      "source": "security@golang.org",
      "tags": [
        "Patch",
        "Vendor Advisory"
      ],
      "url": "https://pkg.go.dev/vuln/GO-2022-0425"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Patch",
        "Third Party Advisory"
      ],
      "url": "https://github.com/flynn/noise/pull/44"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Patch",
        "Vendor Advisory"
      ],
      "url": "https://pkg.go.dev/vuln/GO-2022-0425"
    }
  ],
  "sourceIdentifier": "security@golang.org",
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-311"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.


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.