GPU VulnDB

Database/Kernel, userspace & hypervisor

OpenSSL CMP: unchecked protectionAlg parameter type is dereferenced as a PBMParameter and crashes the process

CVE-2026-63076Kernel, userspace & hypervisorcurated

Impact

When verifying password-based MAC protection on a CMP message, OpenSSL checks only that the protectionAlg parameter pointer is non-NULL, never its ASN.1 type, then casts it and treats it as a PBMParameter. A crafted message supplies a parameter of a different type and the invalid pointer is dereferenced. This happens before any MAC is computed, so the attacker does not need the PBM shared secret. It reaches CMP servers that accept PBM-protected messages via OSSL_CMP_SRV_process_request(), and CMP clients validating responses from a malicious or on-path server. The reliable consequence is a crash - no memory disclosure, no controlled write, no path to code execution. Narrow by construction: CMP is a specialised certificate-enrolment feature an application must explicitly enable, so this matters only if you run internal PKI enrolment infrastructure on OpenSSL's CMP support.

Who can reach it

For servers, any remote unauthenticated party that can send a CMP message to an endpoint accepting PBM-protected messages. For clients, a malicious or on-path CMP server. No shared secret needed either way.

What to do

Upgrade to the fixed OpenSSL release named in the 2026-08-25 advisory and restart your CMP server or client processes - typically a small set of PKI/enrolment hosts, not the whole fleet. If you do not enable CMP anywhere, no action is needed for this CVE beyond your normal OpenSSL update. The record does not name a fixed version for this CVE.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.