Skip to content

← Public intelligence

crates.io package

Simple-Wayland-HotKey-Daemon

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

5 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 3.3crates.ioPublished

    Exposure of Resource to Wrong Sphere in Simple-Wayland-HotKey-Daemon

    CVE-2022-27814 · GHSA-x446-3xhq-5xfp

    Affected
    • crates.io Simple-Wayland-HotKey-Daemon < 1.2.0
    Fixed in
    1.2.0· Vendor fix available
    Issue
    SWHKD 1.1.5 allows arbitrary file-existence tests via the -c option.

    Recommended action: Upgrade to 1.2.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.3crates.ioPublished

    Unsafe parsing in SWHKD

    CVE-2022-27819 · GHSA-h6xw-mghq-7523

    Affected
    • crates.io Simple-Wayland-HotKey-Daemon < 1.2.0
    Fixed in
    1.2.0· Vendor fix available
    Issue
    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).

    Recommended action: Upgrade to 1.2.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Critical, CVSS 9.1crates.ioPublished

    Insecure temporary file usage in SWHKD

    CVE-2022-27818 · GHSA-r3r5-jhw6-4634

    Affected
    • crates.io Simple-Wayland-HotKey-Daemon < 1.2.0
    Fixed in
    1.2.0· Vendor fix available
    Issue
    SWHKD 1.1.5 unsafely uses the /tmp/swhkd.sock pathname. There can be an information leak or denial of service.

    Recommended action: Upgrade to 1.2.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. High, CVSS 7.1crates.ioPublished

    Data Loss/Denial of Service in SWHKD

    CVE-2022-27816 · GHSA-8m49-2xj8-67v9

    Affected
    • crates.io Simple-Wayland-HotKey-Daemon < 1.2.0
    Fixed in
    1.2.0· Vendor fix available
    Issue
    SWHKD 1.1.5 unsafely uses the /tmp/swhks.pid pathname. There can be data loss or a denial of service. A patch is available on the 1.1.0 branch of the repository.

    Recommended action: Upgrade to 1.2.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  5. Critical, CVSS 9.1crates.ioPublished

    Insecure Temporary File in SWHKD

    CVE-2022-27815 · GHSA-p4jg-pccf-h82c

    Affected
    • crates.io Simple-Wayland-HotKey-Daemon < 1.2.0
    Fixed in
    1.2.0· Vendor fix available
    Issue
    SWHKD is a display protocol-independent hotkey daemon made in Rust. In SWHKD versions 1.1.5 and prior, SWHKD uses the /tmp/swhkd.pid pathname. As /tmp is accessible to all users, there can be an information leak or denial of service. No known workarounds exist. A patch is available on the 1.1.0 branch of the repository.

    Recommended action: Upgrade to 1.2.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →