Gateway Plug In For LinuxApplication · Citrix
CVE-2020-8199
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper access control in Citrix ADC Gateway Linux client versions before 1.0.0.137 results in local privilege escalation to root.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceImproper access control in Citrix ADC Gateway Linux client versions before 1.0.0.137 allows a local attacker to escalate privileges to root by exploiting insufficient permission boundaries in the client software.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Gateway Plug In For LinuxApplication
< 1.0.0.137CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Citrix Gateway Plug In for Linux is installedSearch for the Citrix client installation on the system. Common locations include /opt, /usr/local, or the user's home directory. Look for directories or files containing 'citrix', 'gateway', or 'netscaler' in the name.Affected if The Citrix Gateway Plug In for Linux is present on the system
-
Determine the installed version of the clientRun the appropriate version command for the installed Citrix client, such as using the --version flag, checking a version file in the installation directory, or querying the package manager if installed as a package.Affected if The installed version is lower than 1.0.0.137
-
Verify the permission configuration of the client binaries and directoriesExamine file permissions on the Citrix client installation directory and binaries. Specifically check if unprivileged users have write access to directories or files that should be restricted to root or the installing user.Affected if World-writable or group-writable permissions exist on client directories or executables that should be protected
-
Check for setuid binaries within the client installationSearch the Citrix client installation directory for any binaries with the setuid or setgid bit set using 'find . -perm /6000' or similar commands.Affected if Any Citrix client binary has setuid or setgid permissions set
The environment is affected if Citrix Gateway Plug In for Linux is installed with a version number lower than 1.0.0.137 and has insecure file permissions that could allow a local unprivileged user to modify client files or binaries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.0.0.137
Upgrade Citrix ADC Gateway Linux client to version 1.0.0.137 or later to remediate the improper access control vulnerability.
Fix this in Gateway Plug In For Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-8199 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data