Common Weakness Enumeration

CWE-1255

Allowed

Comparison Logic is Vulnerable to Power Side-Channel Attacks

Abstraction: Variant · Status: Draft

A device's real time power consumption may be monitored during security token evaluation and the information gleaned may be used to determine the value of the reference token.

5 vulnerabilities reference this CWE, most recent first.

CVE-2025-3301 (GCVE-0-2025-3301)

Vulnerability from cvelistv5 – Published: 2025-04-29 13:47 – Updated: 2025-04-29 14:02
VLAI
Title
DPA Countermeasures Unavailable for Certain Cryptographic Operations on Series 2 Devices
Summary
DPA countermeasures are unavailable for ECDH key agreement and EdDSA signing operations on Curve25519 and Curve448 on all Series 2 modules and SoCs due to a lack of hardware and software support. A successful DPA attack may result in exposure of confidential information. The best practice is to use the impacted crypto curves and operations with ephemeral keys to reduce the number of DPA traces that can be collected.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator (v2.0.3)
CWE
  • CWE-1255 - Comparison Logic is Vulnerable to Power Side-Channel Attacks
Assigner
References
URL Tags
https://community.silabs.com/068Vm00000O8qbY vendor-advisorypermissions-required
Impacted products
Vendor Product Version
silabs.com Series 2 SoCs and associated modules Affected: 0 , ≤ all released hardware revisions (custom)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2025-3301",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-04-29T14:01:49.964106Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-04-29T14:02:03.494Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "affected",
          "packageName": "EFR32/EFM32 Series 2 Devices",
          "product": "Series 2 SoCs and associated modules",
          "vendor": "silabs.com",
          "versions": [
            {
              "lessThanOrEqual": "all released hardware revisions",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "DPA countermeasures are unavailable for ECDH key agreement and EdDSA signing operations on Curve25519 and Curve448 on all Series 2 modules and SoCs due to a lack of hardware and software support. A successful DPA attack may result in exposure of confidential information. The best practice is to use the impacted crypto curves and operations with ephemeral keys to reduce the number of DPA traces that can be collected.\u0026nbsp;"
            }
          ],
          "value": "DPA countermeasures are unavailable for ECDH key agreement and EdDSA signing operations on Curve25519 and Curve448 on all Series 2 modules and SoCs due to a lack of hardware and software support. A successful DPA attack may result in exposure of confidential information. The best practice is to use the impacted crypto curves and operations with ephemeral keys to reduce the number of DPA traces that can be collected."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-188",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-188 Reverse Engineering"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "PRESENT",
            "attackVector": "PHYSICAL",
            "baseScore": 1,
            "baseSeverity": "LOW",
            "privilegesRequired": "NONE",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "LOW",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-1255",
              "description": "CWE-1255 Comparison Logic is Vulnerable to Power Side-Channel Attacks",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-04-29T13:47:42.717Z",
        "orgId": "030b2754-1501-44a4-bef8-48be86a33bf4",
        "shortName": "Silabs"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory",
            "permissions-required"
          ],
          "url": "https://community.silabs.com/068Vm00000O8qbY"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "DPA Countermeasures Unavailable for Certain Cryptographic Operations on Series 2 Devices",
      "x_generator": {
        "engine": "Vulnogram 0.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "030b2754-1501-44a4-bef8-48be86a33bf4",
    "assignerShortName": "Silabs",
    "cveId": "CVE-2025-3301",
    "datePublished": "2025-04-29T13:47:42.717Z",
    "dateReserved": "2025-04-04T19:53:07.856Z",
    "dateUpdated": "2025-04-29T14:02:03.494Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

GHSA-39PJ-GQ8Q-9PFJ

Vulnerability from github – Published: 2018-06-07 19:43 – Updated: 2021-08-31 20:54
VLAI
Summary
Authentication Weakness in keystone
Details

Versions of keystone prior to 0.3.16 are affected by a partial authentication bypass vulnerability. In the default sign in functionality, if an attacker provides a full and correct password, yet only provides part of the associated email address, authentication will be granted.

Recommendation

Update to version 0.3.16 or later.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "keystone"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.3.16"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2015-9240"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-1255"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-06-16T20:54:41Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "Versions of `keystone` prior to 0.3.16 are affected by a partial authentication bypass vulnerability. In the default sign in functionality, if an attacker provides a full and correct password, yet only provides part of the associated email address, authentication will be granted.\n\n\n## Recommendation\n\nUpdate to version 0.3.16 or later.",
  "id": "GHSA-39pj-gq8q-9pfj",
  "modified": "2021-08-31T20:54:56Z",
  "published": "2018-06-07T19:43:20Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2015-9240"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-39pj-gq8q-9pfj"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/advisories/60"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/package/keystone"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Authentication Weakness in keystone"
}

GHSA-69GH-8Q3C-PHMC

Vulnerability from github – Published: 2024-02-11 03:30 – Updated: 2024-08-01 15:31
VLAI
Details

In Rhonabwy through 1.1.13, HMAC signature verification uses a strcmp function that is vulnerable to side-channel attacks, because it stops the comparison when the first difference is spotted in the two signatures. (The fix uses gnutls_memcmp, which has constant-time execution.)

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-25714"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-1255",
      "CWE-203"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-02-11T03:15:09Z",
    "severity": "CRITICAL"
  },
  "details": "In Rhonabwy through 1.1.13, HMAC signature verification uses a strcmp function that is vulnerable to side-channel attacks, because it stops the comparison when the first difference is spotted in the two signatures. (The fix uses gnutls_memcmp, which has constant-time execution.)",
  "id": "GHSA-69gh-8q3c-phmc",
  "modified": "2024-08-01T15:31:26Z",
  "published": "2024-02-11T03:30:17Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-25714"
    },
    {
      "type": "WEB",
      "url": "https://github.com/babelouest/rhonabwy/commit/f9fd9a1c77e48b514ebb3baf0360f87eef3d846e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-796P-JR7H-8VMQ

Vulnerability from github – Published: 2024-07-03 18:47 – Updated: 2024-08-05 21:31
VLAI
Details

The TCP protocol in RFC 9293 has a timing side channel that makes it easier for remote attackers to infer the content of one TCP connection from a client system (to any server), when that client system is concurrently obtaining TCP data at a slow rate from an attacker-controlled server, aka the "SnailLoad" issue. For example, the attack can begin by measuring RTTs via the TCP segments whose role is to provide an ACK control bit and an Acknowledgment Number.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-39920"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-1255"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-07-03T04:15:04Z",
    "severity": "MODERATE"
  },
  "details": "The TCP protocol in RFC 9293 has a timing side channel that makes it easier for remote attackers to infer the content of one TCP connection from a client system (to any server), when that client system is concurrently obtaining TCP data at a slow rate from an attacker-controlled server, aka the \"SnailLoad\" issue. For example, the attack can begin by measuring RTTs via the TCP segments whose role is to provide an ACK control bit and an Acknowledgment Number.",
  "id": "GHSA-796p-jr7h-8vmq",
  "modified": "2024-08-05T21:31:19Z",
  "published": "2024-07-03T18:47:58Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39920"
    },
    {
      "type": "WEB",
      "url": "https://github.com/IAIK/SnailLoad"
    },
    {
      "type": "WEB",
      "url": "https://news.ycombinator.com/item?id=40809629"
    },
    {
      "type": "WEB",
      "url": "https://twitter.com/tugraz/status/1805272833322299412"
    },
    {
      "type": "WEB",
      "url": "https://www.instagram.com/p/C8wpO1UtExw"
    },
    {
      "type": "WEB",
      "url": "https://www.rfc-editor.org/rfc/rfc9293.txt"
    },
    {
      "type": "WEB",
      "url": "https://www.snailload.com"
    },
    {
      "type": "WEB",
      "url": "https://www.snailload.com/snailload.pdf"
    },
    {
      "type": "WEB",
      "url": "https://www.tugraz.at/en/tu-graz/services/news-stories/tu-graz-news/singleview/article/neue-sicherheitsluecke-erlaubt-ueberwachung-besuchter-websites-und-angesehener-videos"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-H3WR-2JPV-P235

Vulnerability from github – Published: 2025-04-29 15:31 – Updated: 2025-04-29 15:31
VLAI
Details

DPA countermeasures are unavailable for ECDH key agreement and EdDSA signing operations on Curve25519 and Curve448 on all Series 2 modules and SoCs due to a lack of hardware and software support. A successful DPA attack may result in exposure of confidential information. The best practice is to use the impacted crypto curves and operations with ephemeral keys to reduce the number of DPA traces that can be collected.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-3301"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-1255"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-04-29T14:15:32Z",
    "severity": "LOW"
  },
  "details": "DPA countermeasures are unavailable for ECDH key agreement and EdDSA signing operations on Curve25519 and Curve448 on all Series 2 modules and SoCs due to a lack of hardware and software support. A successful DPA attack may result in exposure of confidential information. The best practice is to use the impacted crypto curves and operations with ephemeral keys to reduce the number of DPA traces that can be collected.",
  "id": "GHSA-h3wr-2jpv-p235",
  "modified": "2025-04-29T15:31:52Z",
  "published": "2025-04-29T15:31:52Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-3301"
    },
    {
      "type": "WEB",
      "url": "https://community.silabs.com/068Vm00000O8qbY"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

Mitigation
Architecture and Design

The design phase must consider each check of a security token against a standard and the amount of power consumed during the check of a good token versus a bad token. The alternative is an all at once check where a retry counter is incremented PRIOR to the check.

Mitigation
Architecture and Design

Another potential mitigation is to parallelize shifting of secret data (see example 2 below). Note that the wider the bus the more effective the result.

Mitigation
Architecture and Design

An additional potential mitigation is to add random data to each crypto operation then subtract it out afterwards. This is highly effective but costly in performance, area, and power consumption. It also requires a random number generator.

Mitigation
Implementation

If the architecture is unable to prevent the attack, using filtering components may reduce the ability to implement an attack, however, consideration must be given to the physical removal of the filter elements.

Mitigation
Integration

During integration, avoid use of a single secret for an extended period (e.g. frequent key updates). This limits the amount of data compromised but at the cost of complexity of use.

CAPEC-189: Black Box Reverse Engineering

An adversary discovers the structure, function, and composition of a type of computer software through black box analysis techniques. 'Black Box' methods involve interacting with the software indirectly, in the absence of direct access to the executable object. Such analysis typically involves interacting with the software at the boundaries of where the software interfaces with a larger execution environment, such as input-output vectors, libraries, or APIs. Black Box Reverse Engineering also refers to gathering physical side effects of a hardware device, such as electromagnetic radiation or sounds.