CVE-2015-0934
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 · uneditedCommon LaTeX Service Interface (CLSI) before 0.1.3, as used in ShareLaTeX before 0.1.3, allows remote authenticated users to execute arbitrary code via ` (backtick) characters in a filename.
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 confidenceThe Common LaTeX Service Interface (CLSI) before version 0.1.3, as used in ShareLaTeX, contains a command injection vulnerability where authenticated users can execute arbitrary code by including backtick characters in filenames processed by the LaTeX compilation service.
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<= 0.1.2CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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.
-
Identify ShareLaTeX installation and versionLocate the ShareLaTeX installation directory and check the version file or package.json for the installed version numberAffected if The installed version is 0.1.2 or lower, or the version cannot be determined but the product is ShareLaTeX Community Edition prior to 0.1.3
-
Identify CLSI versionLocate the CLSI (Common LaTeX Service Interface) component within the ShareLaTeX installation and check its version identifierAffected if The CLSI version is 0.1.2 or lower, indicating the command injection patch has not been applied
-
Confirm authentication is enabledCheck the ShareLaTeX configuration to verify that user authentication is required for accessing the LaTeX compilation serviceAffected if Authentication is disabled or improperly configured, making the service accessible to unauthenticated users (note: even with auth, authenticated users can exploit this vulnerability in unpatched versions)
-
Verify LaTeX compilation service is accessibleConfirm that the CLSI API endpoint is exposed and reachable via network or local accessAffected if The CLSI service is running and accessible to users who can submit LaTeX compilation requests
You are affected if ShareLaTeX or CLSI versions are 0.1.2 or lower AND the LaTeX compilation service is accessible to authenticated users who can submit filenames containing backtick characters.
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 to CLSI 0.1.3 or ShareLaTeX 0.1.3 or later. If immediate upgrading is not feasible, implement filename validation to reject or sanitize backtick characters before processing.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0934 — 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-2015-0934 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