CVE-2022-1249 json
A NULL pointer dereference flaw was found in pesign's cms_set_pw_data() function of the cms_common.c file.
published 4y ago modified 4mo ago also EUVD-2022-24582
- cvss
- 3.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
A NULL pointer dereference flaw was found in pesign's cms_set_pw_data() function of the cms_common.c file. The function fails to handle the NULL pwdata invocation from daemon.c, which leads to an explicit NULL dereference and crash on all attempts to daemonize pesign.
Patch / fix
Is CVE-2022-1249 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-1249 updated cvss 4.0
pesign: NULL pointer dereference in cms_set_pw_data()
-
Red Hat Enterprise Linux 7 pesign Red Hat Enterprise Linux 8 pesign Red Hat Enterprise Linux 9 pesignnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- n/a pesign
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
bugzilla.redhat.com
/show_bug.cgi?id=2065771
issue-tracking, patch, third-party-advisory
Sources
- CVE List CVE-2022-1249
- NVD CVE-2022-1249
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.