Ethereum Client Teku Warns Validators After Certificate Authority Keys Exposed
CMC Crypto News

Ethereum Client Teku Warns Validators After Certificate Authority Keys Exposed

Teku warned Ethereum validators that compromised eMudhra certificate keys could let attackers impersonate HTTPS endpoints, but default mainnet nodes are safe.

Ethereum Client Teku Warns Validators After Certificate Authority Keys Exposed

İçindekiler

Key Facts

  • The team behind Ethereum consensus client Teku warned that compromised keys from eight eMudhra intermediate certificate authorities could let an attacker who can intercept traffic impersonate HTTPS endpoints Teku connects to on Java runtimes without OpenJDK's fixes.

  • A default Teku node on mainnet with no HTTPS URLs in its configuration is not affected, and no exploitation has been reported, according to the notice.

  • Every Teku Docker image up to and including version 26.10.2 ships a Java runtime without either OpenJDK fix, the team said.

The team behind Ethereum (ETH) consensus client Teku has warned validator operators that compromised certificate authority keys could let attackers impersonate services their nodes connect to over HTTPS.

The issue matters for operators who point Teku at HTTPS endpoints such as remote signers or beacon nodes on a Java runtime without the fixes.

"A default Teku node on mainnet is not affected and needs no action," the team said in a security notice last updated on Wednesday. Teku is affected only when it connects to an HTTPS endpoint, the notice said.
The summary of Teku's security notice on the eMudhra certificate authority compromise. Source: Teku

What Happened With the eMudhra Certificates

On Oct. 17, the private keys of eight eMudhra (emSign) intermediate certificate authorities were shown to be recoverable from their public certificates, according to the notice. They were revoked on Oct. 18, and browsers, operating systems and Go have since blocked them.

Java does not check revocation by default, so Java runtimes need their own fix. OpenJDK shipped two, on Oct. 20 and Oct. 23.

On a runtime with neither fix, an attacker who can intercept Teku's traffic can impersonate an HTTPS endpoint it connects to.

"Anyone can derive the compromised keys from the public certificates, so that network position is the only real barrier," the team said. "No exploitation has been reported."

Which Teku Validators Are at Risk

The external signer is the highest-risk endpoint. An attacker impersonating it could obtain signatures for voluntary exits, which are irreversible, or for builder registrations that redirect fees, as well as slashable signatures if the signer's own slashing protection is off, the notice said.

A signer that requires a client certificate from Teku limits the impact to a denial of service.

The notice rates an attack through a remote beacon node as medium likelihood, since a validator client using one over the internet is a common setup.
An impersonated node could have validators propose blocks that pay fees to the attacker. Teku's slashing protection still blocks slashable signatures in that case.

Every Teku Docker image up to and including 26.10.2, including the -jdk25 and -jdk26 tags, ships a Java runtime with neither fix, so Docker users who rely on any affected option remain exposed until a fixed image is released.

The team also told them to move to the -jdk25 tags, since Java 26 is end of life and no fixed Java 26 build is coming.

The warning comes amid other Ethereum staking news this month, including a Glamsterdam fix for builder deposits that Ethereum developers merged on Monday. Bitcoin wallet Electrum also patched a bug exploited by malicious servers this week.
This article contains links to third-party websites or other content for information purposes only ("Third-Party Sites"). The Third-Party Sites are not under the control of CoinMarketCap, and CoinMarketCap is not responsible for the content of any Third-Party Site, including without limitation any link contained in a Third-Party Site, or any changes or updates to a Third-Party Site. CoinMarketCap is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement, approval or recommendation by CoinMarketCap of the site or any association with its operators. This article is intended to be used and must be used for informational purposes only. It is important to do your own research and analysis before making any material decisions related to any of the products or services described. This article is not intended as, and shall not be construed as, financial advice. The views and opinions expressed in this article are the author's [company's] own and do not necessarily reflect those of CoinMarketCap.
0 people liked this article