dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-3560

MEDIUM · 5.5 CVSS v3.1 Published 2023-02-02
Fix available
A fix is available. Upgrade to 116 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The pesign systemd service runs a script to set ACLs on /etc/pki/pesign and /run/pesign directories for the 'pesign' group. The script fails to validate whether these paths are symbolic links before applying ACLs, allowing a local attacker to create symlinks pointing to sensitive files/directories and gain unauthorized privileged access via path traversal.

MitigationModify the ACL script to check for symbolic links before setting permissions, rejecting or resolving symlinks to prevent traversal attacks. Alternatively, ensure the base directories cannot be replaced with symlinks by untrusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 36= 37
Enterprise LinuxOperating system
Affected:= 7.0= 8.0= 9.0
PesignApplication
Affected:< 116

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if pesign is installed
    Run 'rpm -q pesign' (RHEL/Fedora) or 'dpkg -l pesign' (Debian-based)
    Affected if pesign package is not installed - not affected. If installed, continue to next check.
  2. Determine installed pesign version
    Run 'rpm -q --qf "%{VERSION}" pesign' to get the version number, or check the RPM changelog with 'rpm -q --changelog pesign | head -20' for CVE-2022-3560 mention
    Affected if Version is less than 116 (e.g., 115 or earlier) - potentially affected. For Fedora/RHEL, compare against affected versions (7.0, 8.0, 9.0 for RHEL; 36, 37 for Fedora).
  3. Check for systemd service existence
    Run 'systemctl list-unit-files | grep pesign' and 'ls -la /usr/lib/systemd/system/pesign* 2>/dev/null' to find any pesign-related systemd units
    Affected if No pesign systemd service found - not affected by this specific CVE which targets the systemd service script.
  4. Inspect /etc/pki/pesign for symlinks
    Run 'ls -la /etc/pki/pesign' and check the first character of the path entry - if it starts with 'l', it is a symlink
    Affected if The path /etc/pki/pesign is a symbolic link (starts with 'l' in ls -la output) - vulnerable to symlink attack described in CVE.
  5. Inspect /run/pesign for symlinks
    Run 'ls -la /run/pesign' and check the first character - 'l' indicates a symlink
    Affected if The path /run/pesign is a symbolic link - vulnerable to symlink attack.

User is affected if pesign version is less than 116 AND either /etc/pki/pesign or /run/pesign is a symbolic link, allowing an attacker to exploit path traversal via the ACL-setting script.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 116 or later
Fixed in 116
Interim mitigation

Modify the ACL script to check for symbolic links before setting permissions, rejecting or resolving symlinks to prevent traversal attacks. Alternatively, ensure the base directories cannot be replaced with symlinks by untrusted users.

Recommended fix High confidence

pesign >= 116

  1. Update the pesign package to version 116 or later using your distribution's package manager
  2. For Fedora systems: Run 'dnf update pesign' or 'dnf upgrade pesign'
  3. For Enterprise Linux systems: Run 'yum update pesign' or 'dnf update pesign'
  4. Verify the installed version is 116 or higher using 'rpm -q pesign'
  5. Restart the pesign service if it was running: 'systemctl restart pesign'

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3560 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data