Description
A path traversal attack when using a "configName" parameter in qSnapper before version 1.3.3 allowed a local attacker to use malicious config files for snapper and so cause a denial of service or potentially escalate privileges to root.
Published: 2026-06-22
Score: 7.3 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A path traversal vulnerability exists in the configName parameter of qSnapper before version 1.3.3. The flaw permits a local attacker to supply a path that escapes the intended configuration directory, allowing the attacker to place arbitrary configuration files in snapper’s directory. By doing so, the attacker can trigger a denial of service or, if privileged operations are invoked from these files, potentially elevate privileges to root. This weakness aligns with CWE‑23, a classic path traversal vulnerability that can compromise file confidentiality, integrity, and availability.

Affected Systems

Products affected are qSnapper versions released by Presire that are older than 1.3.3. Users running any pre‑1.3.3 build are vulnerable. The vulnerability was identified in the code base that handles the configName argument, so any deployment of qSnapper that accepts user‑specified configuration names without validation is impacted.

Risk and Exploitability

Using the available CVSS score of 7.3 the flaw is considered high severity. The EPSS score is not published, and the vulnerability is not listed in the CISA KEV catalog, indicating no known in‑the‑wild exploitation yet. Nonetheless, the local attack requirement means that only users with access to the machine can exploit the flaw, but such local attackers can leverage the path traversal to overwrite configuration files that may lead to denial of service or privilege escalation. The official fix in v1.3.3 removes the uncontrolled path handling; until that update is applied the risk remains.

Generated by OpenCVE AI on June 22, 2026 at 16:24 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the vendor‑released update qSnapper v1.3.3 or later to eliminate the traversal fault.
  • Restrict the use of the configName parameter to trusted service accounts only and enforce file‑system permissions on the snapper configuration directory so that only the application and privileged users can write there.
  • Review local user accounts that have permission to execute qSnapper and remove any that are unnecessary, limiting the pool of potential local attackers.

Generated by OpenCVE AI on June 22, 2026 at 16:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 22 Jun 2026 15:45:00 +0000

Type Values Removed Values Added
Description A path traversal attack when using a "configName" parameter in qSnapper before version 1.3.3 allowed a local attacker to use malicious config files for snapper and so cause a denial of service or potentially escalate privileges to root.
Title path traversal via `config` parameter in qSnapper
Weaknesses CWE-23
References
Metrics cvssV3_1

{'score': 7.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: suse

Published:

Updated: 2026-06-22T15:20:30.872Z

Reserved: 2026-04-16T13:37:50.679Z

Link: CVE-2026-41046

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-22T16:30:08Z

Weaknesses
  • CWE-23

    Relative Path Traversal