CVE-2019-14450
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 · uneditedA directory traversal vulnerability was discovered in RepetierServer.exe in Repetier-Server 0.8 through 0.91 that allows for the creation of a user controlled XML file at an unintended location. When this is combined with CVE-2019-14451, an attacker can upload an "external command" configuration as a printer configuration, and achieve remote code execution. After exploitation, loading of the external command configuration is dependent on a system reboot or service restart.
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 confidenceA directory traversal vulnerability in RepetierServer.exe (versions 0.8-0.91) allows authenticated attackers to write user-controlled XML files to arbitrary filesystem locations. When chained with CVE-2019-14451 (external command configuration upload), this enables remote code execution via malicious printer configurations that execute on service restart or system reboot.
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.80, <= 0.91CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Repetier Server installationLocate RepetierServer.exe on the system - typically found in C:\Program Files\Repetier-Server\ or /usr/local/Repetier-Server/ on LinuxAffected if RepetierServer.exe is present on the system
-
Determine installed versionRight-click RepetierServer.exe, select Properties, then look at the File Version in the Details tab, or run: RepetierServer.exe --versionAffected if Version is >= 0.80 and <= 0.91
-
Check web interface exposureAccess the Repetier Server web interface via browser on port 3344 (default). Verify if it requires authentication or is accessible without credentialsAffected if Web interface is exposed without authentication or uses default credentials
-
Review configuration file locationsInspect the Repetier-Server config directory (typically in the application data folder) for XML configuration files. Check for any recently modified or unexpected XML files in locations outside the normal config directoryAffected if XML files exist outside the intended config directory or show signs of unauthorized modification
-
Audit system for unexpected executable filesSearch the system for newly created executable or script files in unusual locations (root of system drive, Windows folder, startup folders) that may have been placed via the directory traversalAffected if Unexpected executables or scripts are found in arbitrary filesystem locations
The environment is affected if Repetier Server version 0.80 through 0.91 is installed and its web interface is accessible to untrusted users, allowing potential exploitation of the directory traversal to write files outside the intended config directory.
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.
dbcve · scopedUpgrade Repetier-Server to a version beyond 0.91 that includes patched directory traversal protections; until then, restrict network access to the Repetier-Server interface and monitor for unauthorized configuration uploads.
Repetier Server version 0.92 or later
- 1. Identify the current installed version of Repetier Server by checking the application or documentation.
- 2. Backup the current Repetier Server configuration and data to prevent data loss during upgrade.
- 3. Download Repetier Server version 0.92 or later from the official source at www.repetier-server.com.
- 4. Stop the Repetier Server service to ensure a clean upgrade process.
- 5. Install the new version (0.92 or later) following the standard installation procedure.
- 6. After installation, verify the new version number matches the expected fixed release.
- 7. Restart the Repetier Server service.
- 8. Test that the application functions normally and the directory traversal vulnerability is no longer present.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14450 — 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-2019-14450 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