FKIE_CVE-2015-20112

Vulnerability from fkie_nvd - Published: 2025-06-29 21:15 - Updated: 2026-06-17 00:23
Severity
3.4 (Low) - CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
Summary
RLPx 5 has two CTR streams based on the same key, IV, and nonce. This can facilitate decryption on a private network.
References
cve@mitre.orghttps://github.com/LaurentMT/go-ethereum/commit/e8cba7283b57280b1bcf5761478f852398365901
cve@mitre.orghttps://github.com/ethereum/devp2p/blob/master/rlpx.md#known-issues-in-the-current-version
cve@mitre.orghttps://github.com/ethereum/devp2p/issues/32
cve@mitre.orghttps://github.com/ethereum/go-ethereum/issues/1315
cve@mitre.orghttps://github.com/hyperledger/besu/issues/7926
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unknown",
          "product": "RLPx",
          "vendor": "Ethereum",
          "versions": [
            {
              "status": "affected",
              "version": "5",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "cve@mitre.org"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "RLPx 5 has two CTR streams based on the same key, IV, and nonce. This can facilitate decryption on a private network."
    },
    {
      "lang": "es",
      "value": "RLPx 5 cuenta con dos flujos CTR basados en la misma clave, IV y nonce. Esto facilita el descifrado en una red privada."
    }
  ],
  "id": "CVE-2015-20112",
  "lastModified": "2026-06-17T00:23:24.777",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "ADJACENT_NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 3.4,
          "baseSeverity": "LOW",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.6,
        "impactScore": 1.4,
        "source": "cve@mitre.org",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2015-20112",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2025-06-30T15:44:27.767688Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2025-06-29T21:15:22.210",
  "references": [
    {
      "source": "cve@mitre.org",
      "url": "https://github.com/LaurentMT/go-ethereum/commit/e8cba7283b57280b1bcf5761478f852398365901"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://github.com/ethereum/devp2p/blob/master/rlpx.md#known-issues-in-the-current-version"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://github.com/ethereum/devp2p/issues/32"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://github.com/ethereum/go-ethereum/issues/1315"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://github.com/hyperledger/besu/issues/7926"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-325"
        }
      ],
      "source": "cve@mitre.org",
      "type": "Secondary"
    }
  ]
}


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.