CVE-2013-4376
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 · uneditedThe setgid wrapper libx2go-server-db-sqlite3-wrapper.c in X2Go Server before 4.0.0.2 allows remote attackers to execute arbitrary code via unspecified vectors, related to the path to libx2go-server-db-sqlite3-wrapper.pl.
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 · moderate confidenceThe vulnerability exists in the setgid wrapper (libx2go-server-db-sqlite3-wrapper.c) in X2Go Server versions prior to 4.0.0.2. The wrapper, which runs with elevated privileges, contains a path-related flaw that allows remote attackers to execute arbitrary code by manipulating the path to the libx2go-server-db-sqlite3-wrapper.pl Perl script.
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<= 4.0.0.1= 4.0.0.0CVSS 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Check X2Go Server versionRun command: x2goserver --version or rpm -q x2goserver or dpkg -l x2goserver depending on distributionAffected if Version is 4.0.0.0 or 4.0.0.1 or any version lower than 4.0.0.2
-
Locate the setgid wrapper binarySearch for file named libx2go-server-db-sqlite3-wrapper in typical paths such as /usr/lib/x2go/, /usr/lib64/x2go/, or /usr/local/lib/x2go/Affected if The wrapper binary exists in the system and its version is prior to 4.0.0.2
-
Verify the wrapper permissionsRun: ls -la /path/to/libx2go-server-db-sqlite3-wrapper and check for setgid bit (rwsr-sr-x) and group ownershipAffected if The binary has setgid bit set and runs with elevated privileges, making the path manipulation flaw exploitable
-
Check for the Perl script wrapperSearch for libx2go-server-db-sqlite3-wrapper.pl in the same directory as the wrapper binaryAffected if The Perl script exists and is accessible to be manipulated through path injection
If X2Go Server version is 4.0.0.0 or 4.0.0.1 or any version before 4.0.0.2, and the setgid wrapper binary is present with setgid permissions, the environment is affected by this vulnerability.
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 dataUpgrade X2Go Server to version 4.0.0.2 or later to obtain the patched setgid wrapper. Verify that the wrapper binary has correct ownership and permissions after upgrade.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4376 — 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-2013-4376 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