Google Go crypto-elliptic p256NegCond information exposure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.6$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Google Go. Affected by this issue is the function p256NegCond of the component crypto-elliptic. The manipulation leads to information exposure. This vulnerability is listed as CVE-2025-22866. The attack may be initiated remotely. There is no available exploit. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in Google Go (version now known). It has been rated as problematic. This issue affects the function p256NegCond of the component crypto-elliptic. The manipulation with an unknown input leads to a information exposure vulnerability. Using CWE to declare the problem leads to CWE-203. The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not. Impacted is confidentiality. The summary by CVE is:

Due to the usage of a variable time instruction in the assembly implementation of an internal function, a small number of bits of secret scalars are leaked on the ppc64le architecture. Due to the way this function is used, we do not believe this leakage is enough to allow recovery of the private key when P-256 is used in any well known protocols.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-22866 since 01/08/2025. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 216178 (SUSE SLED15 / SLES15 / openSUSE 15 Security Update : go1.22 (SUSE-SU-2025:0392-1)), which helps to determine the existence of the flaw in a target environment.

Applying a patch is able to eliminate this problem.

The vulnerability is also documented in the databases at Tenable (216178) and CERT Bund (WID-SEC-2025-0263). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • Golang Go
  • Open Source Gitea
  • IBM Business Automation Workflow

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.7
VulDB Meta Temp Score: 3.6

VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Information exposure
CWE: CWE-203 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 216178
Nessus Name: SUSE SLED15 / SLES15 / openSUSE 15 Security Update : go1.22 (SUSE-SU-2025:0392-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/08/2025 🔍
02/05/2025 +28 days 🔍
02/05/2025 +0 days 🔍
09/11/2025 +218 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: github.com
Status: Confirmed

CVE: CVE-2025-22866 (🔍)
GCVE (CVE): GCVE-0-2025-22866
GCVE (VulDB): GCVE-100-294713
CERT Bund: WID-SEC-2025-0263 - Golang Go: Schwachstelle ermöglicht Offenlegung von Informationen

Entryinfo

Created: 02/05/2025 10:03
Updated: 09/11/2025 20:38
Changes: 02/05/2025 10:03 (53), 02/13/2025 01:21 (2), 02/22/2025 04:31 (2), 09/11/2025 20:38 (7)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!