Skip to content

Security: NoiXdev/nfc-keyboard-emulator

Security

SECURITY.md

Security Policy

Supported versions

nfc-keyboard-emulator is distributed as a desktop application. Only the latest released version receives security fixes. Please make sure you are on the most recent release before reporting an issue.

Reporting a vulnerability

Please do not report security vulnerabilities through public GitHub issues.

Instead, use GitHub's private vulnerability reporting:

  1. Go to the Security tab of this repository.
  2. Click Report a vulnerability and fill in the details.

If you are unable to use private reporting, you may email ich@dginx.de instead.

Please include, where possible:

  • A description of the vulnerability and its impact.
  • Steps to reproduce or a proof of concept.
  • The affected version and your operating system.

What to expect

  • We aim to acknowledge new reports within 5 business days.
  • We will keep you informed as we investigate and work on a fix.
  • Once a fix is released, we are happy to credit you in the release notes unless you prefer to remain anonymous.

Scope

The app synthesizes keystrokes (macOS Accessibility API / Windows SendInput) and reads card UIDs over the PC/SC smartcard API. It has no network access and stores only a local settings file; card UIDs never leave the machine. Reports concerning the keystroke-injection path, the reader/worker boundary, or the release/signing pipeline are especially welcome.

There aren't any published security advisories