/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Researchers find a vulnerability in Intel and AMD CPUs that could let hackers steal encryption keys via a side channel attack on power management feature DVFS

Dan Goodin / Ars Technica :

Ars Technica Dan Goodin

Context & Ripple Effects

The disclosure follows Intel-specific research into a remote data-extraction path through a power-monitor interface and the earlier Meltdown and Spectre flaws, which established that hardware behavior can expose data held by otherwise separate workloads.

By naming both Intel and AMD, the DVFS finding broadens the security focus from individual processor families to a power-management mechanism used across leading CPU vendors.

First-order effects

  • Intel and AMD face a newly disclosed route for attackers to target encryption keys through DVFS, putting their processor security mitigations under immediate scrutiny.
  • Organizations using Intel- and AMD-based systems must account for a hardware side channel that can expose cryptographic material rather than merely compromise an application’s own code.

Second-order effects

  • The finding extends the attack-surface review prompted by Intel’s earlier power-monitor-interface vulnerability: power-management controls now warrant the same attention as processor execution paths.
  • Security teams evaluating CPU-based cryptography must treat isolation between workloads as contingent on the underlying hardware behavior, a concern first made prominent by Meltdown and Spectre.

Third-order effects

  • Repeated disclosures involving execution, power monitoring, and DVFS point toward hardware side channels becoming a persistent design-security category rather than isolated vendor-specific defects.
  • If cross-vendor findings continue, processor competition will increasingly include how vendors limit leakage from shared physical resources while retaining performance features.

The trend: CPU security is moving toward sustained scrutiny of physical and power-management behavior that can leak secrets across software isolation boundaries.

Discussion

  • @arekfurt @arekfurt on x
    This is fairly comprehensible analysis from Intel of the so-called Hertzbleed side-channel cryptographic attack. The long and short of it is that there are likely to be very, very few organizations/people who should actually be worried about this. https://www.intel.com/...
  • @kennwhite Kenn White on x
    This is difficult, painstaking work and the team should be lauded. That said, I'm not losing sleep over the practical risk given the exploit prerequisites & cost/payoff ratio, which appears to require a LAN and (I think) doesn't affect OpenSSL. Absolutely love the name though. ht…
  • @campuscodi Catalin Cimpanu on x
    Per the researchers: “Hertzbleed is a real, and practical, threat to the security of cryptographic software.” Intel's security advisory states that all Intel processors are affected: https://www.intel.com/... Top AMD CPUs are also impacted: https://www.amd.com/...
  • @dangillmor Dan Gillmor on x
    About as bad as it gets, and who knows what goes on inside Intel's “Management Engine” (a totally opaque computer inside the CPU). https://twitter.com/...