Fix SM2 signature forgery via missing t == 0 rejection in ippsGFpECVerifySM2

F-INTEL-IPP-CRYPTO-SM2-VERIFY-T0-FORGERY-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

intel/cryptography-primitivesReported fixintel/cryptography-primitives

Fix SM2 signature forgery via missing t == 0 rejection in ippsGFpECVerifySM2

fixed publicly

details

Finding IDs: F-INTEL-IPP-CRYPTO-SM2-VERIFY-T0-FORGERY-001
Status: fixed publicly
Reported via: security contact
Note: public fix commit 8c4a863575f9 landed on 2026-05-19 via #899 and shipped in Intel Cryptography Primitives Library v2.2.0, published on 2026-05-28. release notes state: fixed SM2 signature forgery vulnerability by adding missing input validation in ippsGFpECVerifySM2.

F-INTEL-IPP-CRYPTO-SM2-VERIFY-T0-FORGERY-001: Verification failures. SM2 verification omits the required t == 0 rejection. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-INTEL-IPP-CRYPTO-SM2-VERIFY-T0-FORGERY-001

Security area (1seal assessment): Integrity. SM2 verification omits the required t == 0 rejection. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.