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

Routine

MEDIUM 5.5DOWNGRADE

CVE-2011-2916 is a medium-severity flaw (CVSS 5.5) affecting qtnx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 84%)
CISA exploited list	No
Weakness	CWE-312
Published	2019-11-15
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: qtnx project

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-11-15 18:15 UTCPublished CVE record published
2026-06-16 23:32 UTCUpdated Record last modified

qtnx project qtnx DOWNGRADE

Affected: 0.9

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.9

1. Check installed version

apt-cache policy qtnx || rpm -q qtnx || qtnx --version

2. No fixed release: DOWNGRADE to a release before 0.9 (Debian / Ubuntu)

apt-cache madison qtnx sudo apt install qtnx=<VERSION_BEFORE_0.9> sudo apt-mark hold qtnx

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list qtnx sudo dnf downgrade qtnx-<VERSION_BEFORE_0.9> sudo dnf versionlock add qtnx

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2011-2916?

qtnx: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2011-2916 being exploited?

CVE-2011-2916 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2011-2916 affect?

CVE-2011-2916 affects qtnx. Severity is medium (CVSS 5.5). 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.

How urgent is CVE-2011-2916?

Priority 23/100. No elevated risk signals yet.

References

← Back to latest CVEs