3.7

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-522r-9946-fw43

GHSA-522r-9946-fw43: Duplicate Advisory: CIRCL-Fourq: Missing and wrong validation can lead to incorrect results

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-2x5j-vhc8-9cwm. This link is maintained to preserve external references.

Original Description

A flaw was found in CIRCL's implementation of the FourQ elliptic curve. This vulnerability allows an attacker to compromise session security via low-order point injection and incorrect point validation during Diffie-Hellman key exchange.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-522r-9946-fw43

GHSA-522r-9946-fw43:

3.7

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
github.com/cloudflare/circl	go	< 1.6.1	1.6.1

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability in cloudflare/circl (GHSA-2x5j-vhc8-9cwm) stems from improper validation of elliptic curve points in its FourQ implementation. My analysis of the patches between the vulnerable version (1.6.0) and the fixed version (1.6.1) confirms this. The root cause is spread across several functions responsible for point creation, validation, and use in cryptographic protocols.

An attacker could exploit these flaws in a few ways:

Low-Order Point Injection: By providing a specially crafted public key during a Diffie-Hellman key exchange, an attacker could force the shared secret to become a predictable, non-secret value (the identity point). The curve4q.Shared function was vulnerable as it lacked a check to prevent this.
Invalid Point Acceptance: The fourq.Point.Unmarshal function could be tricked into creating an invalid point from a malicious byte string. Furthermore, the fourq.pointR1.IsOnCurve and fourq.pointR1.isEqual functions contained logic flaws, particularly around handling points at infinity (where Z=0), that would allow these invalid points to be treated as valid within the system.

These vulnerabilities would be triggered during cryptographic operations involving the FourQ curve, such as key generation, key exchange, or signature verification. A runtime profile during an exploit would likely show calls to curve4q.Shared when targeting the key exchange, and calls to fourq.Point.Unmarshal, fourq.pointR1.IsOnCurve, and fourq.pointR1.isEqual when processing malicious point data. The patches address these issues by adding strict checks for point identity, ensuring correctness during unmarshalling, and fixing the mathematical validation within IsOnCurve and isEqual.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.