dbcve.org
Lantime FirmwareOperating system · Meinbergglobal

CVE-2023-1731

HIGH · 7.2 CVSS v3.1 Published 2023-04-24
Fix available
A fix is available. Upgrade to 7.06.013 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
In Meinbergs LTOS versions prior to V7.06.013, the configuration file upload function would not correctly validate the input, which would allow an remote authenticated attacker with high privileges to execute arbitrary commands.

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 confidence

The configuration file upload function in Meinberg LTOS versions prior to V7.06.013 lacks proper input validation, allowing a remote authenticated attacker with high privileges to inject and execute arbitrary commands through specially crafted configuration files.

MitigationUpgrade Meinberg LTOS to version V7.06.013 or later which implements proper input validation in the configuration file upload function.

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
Lantime FirmwareOperating system
Affected:< 7.06.013

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device as Meinberg Lantime
    Access the device web interface or check the device model through the administrative console or SNMP. Look for 'Lantime' branding or check /status page for device identification.
    Affected if The device is not a Meinberg Lantime product, the vulnerability does not apply.
  2. Determine the firmware version
    Log into the web interface and navigate to Status > System Information, or use the command line and run 'imget -v' or check /etc/version file. Look for a version number starting with 'V' followed by digits (e.g., V7.06.012).
    Affected if The installed version is V7.06.013 or later, the vulnerability does not apply. Versions prior to V7.06.013 (e.g., V7.06.012, V7.04.000, V6.x.x) are affected.
  3. Confirm configuration upload feature is accessible
    Check if the web interface is enabled and accessible. Navigate to Configuration > Import/Export or similar menu where configuration file upload is available. Verify the service is not disabled or blocked by network controls.
    Affected if The configuration file upload function is disabled or the web interface is not accessible, the attack surface is reduced but the vulnerability still exists in the software version.
  4. Verify privilege requirements
    Review user accounts and their privilege levels in the web interface under Administration > Users. The vulnerability requires an account with high/root privileges.
    Affected if Only low-privilege accounts exist or administrative access is properly segmented, the specific attack path is limited but the vulnerable code still exists in unpatched versions.

Your environment is affected if the device is a Meinberg Lantime running firmware version V7.06.012 or earlier, regardless of whether the configuration upload feature is currently in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.06.013 or later
Fixed in 7.06.013
Interim mitigation

Upgrade Meinberg LTOS to version V7.06.013 or later which implements proper input validation in the configuration file upload function.

Recommended fix High confidence

Lantime Firmware V7.06.013

  1. Obtain Lantime Firmware version 7.06.013 from the official Meinberg download portal (www.meinbergglobal.com)
  2. Access the Lantime device web management interface
  3. Navigate to the firmware update or system maintenance section
  4. Upload the version 7.06.013 firmware file
  5. Apply the firmware update and wait for the device to reboot
  6. Verify the device is running version 7.06.013 or higher in the system information page

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lantime Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1731 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1731 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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