CVE-2017-16788
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 · uneditedDirectory traversal vulnerability in the "Upload Groupkey" functionality in the Web Configuration Utility in Meinberg LANTIME devices with firmware before 6.24.004 allows remote authenticated users with Admin-User access to write to arbitrary files and consequently gain root privileges by uploading a file, as demonstrated by storing a file in the cron.d directory.
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 confidenceDirectory traversal vulnerability in the 'Upload GroupKey' function of the Meinberg LANTIME Web Configuration Utility allows authenticated Admin-User accounts to write files to arbitrary locations on the device filesystem. By uploading malicious files to directories like cron.d, attackers can achieve root privilege escalation.
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< 6.24.004CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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.
-
Check installed LANTIME firmware versionLog into the Meinberg LANTIME web interface and navigate to Status > System Information, or access the device console and run 'lmversion' or check /etc/version to retrieve the firmware build number.Affected if The displayed firmware version is below 6.24.004 (e.g., 6.22.000, 6.23.001, etc.)
-
Verify web configuration utility is enabledAttempt to access the LANTIME web interface at the device IP address (default port 80/443). Confirm the 'Upload GroupKey' function exists under the Administration or Network settings menu.Affected if The web interface is accessible and the 'Upload GroupKey' feature is present in the navigation.
-
Confirm admin-level access existsCheck for existing admin user accounts in the LANTIME web interface under Administration > User Management, or via console access using 'ltapi' or similar management commands.Affected if At least one admin-level user account is configured and enabled on the device.
The device is affected if the LANTIME firmware version is below 6.24.004, the web configuration utility is accessible, and an admin user account exists to access the vulnerable Upload GroupKey function.
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 data6.24.004
Upgrade Meinberg LANTIME firmware to version 6.24.004 or later. Prior to patching, restrict administrative access to trusted IPs only and monitor for unauthorized file upload activity.
- Consultation3.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16788 — 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-2017-16788 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