Skip to content
Fencer Intel
medium 5.3

CVE-2022-27819 json

Unsafe parsing in SWHKD

published 4y ago modified 4mo ago also GHSA-h6xw-mghq-7523 , EUVD-2022-1755

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

SWHKD 1.1.5 allows unsafe parsing via the -c option. An information leak might occur but there is a simple denial of service (memory exhaustion) upon an attempt to parse a large or infinite file (such as a block or character device).

Patch / fix

  • crates.io Simple-Wayland-HotKey-Daemon 1.2.0

Is CVE-2022-27819 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:H
NVD 2.0 4.0 AV:N/AC:H/Au:N/C:P/I:N/A:P
GitHub 3.1 5.3 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:H

Affected packages

ecosystem package affected fixed in
crates.io Simple-Wayland-HotKey-Daemon
<1.2.0
1.2.0

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

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.