A flaw was found in pesign.
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: pesign (AlmaLinux:8) 0.112-27.el8_7; pesign (AlmaLinux:9) 115-6.el9_1; pesign (Debian:13) 116-1.
Low priority for now. Upgrade to pesign (AlmaLinux:8) 0.112-27.el8_7; pesign (AlmaLinux:9) 115-6.el9_1; pesign (Debian:13) 116-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A flaw was found in pesign. The pesign package provides a systemd service used to start the pesign daemon. This service unit runs a script to set ACLs for /etc/pki/pesign and /run/pesign directories to grant access privileges to users in the 'pesign' group. However, the script doesn't check for symbolic links. This could allow an attacker to gain access to privileged files and directories via a path traversal attack.
- Published
- Feb 2, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-22
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pesign project | pesign | cpe:2.3:a:pesign_project:pesign |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora36
- fedoraproject fedora37
- pesign project pesignbefore 116
- redhat enterprise linux7.0
- redhat enterprise linux8.0
- redhat enterprise linux9.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a pesign
- All versions up to pesign-115affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | pesign | before 0.112-27.el8_7 | 0.112-27.el8_7 |
| AlmaLinux:9 | pesign | before 115-6.el9_1 | 115-6.el9_1 |
| Debian:12 | pesign | from 0 | — |
| Debian:13 | pesign | before 116-1 | 116-1 |
| openSUSE:Tumbleweed | pesign | before 113-11.1 | 113-11.1 |
| Red Hat:enterprise_linux:7::client | pesign | before 0:0.109-11.el7_9 | 0:0.109-11.el7_9 |
| Red Hat:enterprise_linux:7::client | pesign-debuginfo | before 0:0.109-11.el7_9 | 0:0.109-11.el7_9 |
| Red Hat:enterprise_linux:8::appstream | pesign | before 0:0.112-27.el8_7 | 0:0.112-27.el8_7 |
| Red Hat:enterprise_linux:8::appstream | pesign-debuginfo | before 0:0.112-27.el8_7 | 0:0.112-27.el8_7 |
| Red Hat:enterprise_linux:8::appstream | pesign-debugsource | before 0:0.112-27.el8_7 | 0:0.112-27.el8_7 |
| Red Hat:enterprise_linux:9::appstream | pesign | before 0:115-6.el9_1 | 0:115-6.el9_1 |
| Red Hat:enterprise_linux:9::appstream | pesign-debuginfo | before 0:115-6.el9_1 | 0:115-6.el9_1 |
| Red Hat:enterprise_linux:9::appstream | pesign-debugsource | before 0:115-6.el9_1 | 0:115-6.el9_1 |
| Red Hat:rhel_aus:8.2::appstream | pesign | before 0:0.112-25.el8_2.1 | 0:0.112-25.el8_2.1 |
| Red Hat:rhel_aus:8.2::appstream | pesign-debuginfo | before 0:0.112-25.el8_2.1 | 0:0.112-25.el8_2.1 |
| Red Hat:rhel_aus:8.2::appstream | pesign-debugsource | before 0:0.112-25.el8_2.1 | 0:0.112-25.el8_2.1 |
| Red Hat:rhel_e4s:8.1::appstream | pesign | before 0:0.112-25.el8_1.1 | 0:0.112-25.el8_1.1 |
| Red Hat:rhel_e4s:8.1::appstream | pesign-debuginfo | before 0:0.112-25.el8_1.1 | 0:0.112-25.el8_1.1 |
| Red Hat:rhel_e4s:8.1::appstream | pesign-debugsource | before 0:0.112-25.el8_1.1 | 0:0.112-25.el8_1.1 |
| Red Hat:rhel_eus:8.4::appstream | pesign | before 0:0.112-25.el8_4.1 | 0:0.112-25.el8_4.1 |
| Red Hat:rhel_eus:8.4::appstream | pesign-debuginfo | before 0:0.112-25.el8_4.1 | 0:0.112-25.el8_4.1 |
| Red Hat:rhel_eus:8.4::appstream | pesign-debugsource | before 0:0.112-25.el8_4.1 | 0:0.112-25.el8_4.1 |
| Red Hat:rhel_eus:8.6::appstream | pesign | before 0:0.112-27.el8_6 | 0:0.112-27.el8_6 |
| Red Hat:rhel_eus:8.6::appstream | pesign-debuginfo | before 0:0.112-27.el8_6 | 0:0.112-27.el8_6 |
+8
Same product
pesign project: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-1249A NULL pointer dereference flaw was found in pesign's cms_set_pw_data() function of the cms_common.c file.13Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:pesign | 115-6.el9_1 · AlmaLinux:9 | Package registry (OSV) |
| debian:pesign | 116-1 · Debian:13 | Package registry (OSV) |
| opensuse:pesign | 0.112-150000.4.15.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:pesign | 0:115-6.el9_0 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:pesign-debuginfo | 0:115-6.el9_0 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| red hat:pesign-debugsource | 0:115-6.el9_0 · Red Hat:rhel_eus:9.0::appstream | Package registry (OSV) |
| rocky linux:pesign | 0:115-6.el9_1.rocky.2 · Rocky Linux:9 | Package registry (OSV) |
| suse:pesign | 0.112-150000.4.15.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) { return res.sendStatus(400);}res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.