dbcve.org
Lantime FirmwareOperating system · Meinbergglobal

CVE-2021-46902

HIGH · 7.2 CVSS v3.1 Published 2024-02-04
Fix available
A fix is available. Upgrade to 6.24.029 / 7.04.008 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
An issue was discovered in LTOS-Web-Interface in Meinberg LANTIME-Firmware before 6.24.029 MBGID-9343 and 7 before 7.04.008 MBGID-6303. Path validation is mishandled, and thus an admin can read or delete files in violation of expected access controls.

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 confidence

A path traversal vulnerability exists in the LTOS-Web-Interface of Meinberg LANTIME-Firmware versions before 6.24.029 and before 7.04.008. The web interface improperly validates file paths, allowing an authenticated admin user to access or delete files outside the intended directory scope, bypassing expected access controls.

MitigationApply vendor firmware updates (6.24.029/7.04.008 or later) to patch the path validation flaw. If patching is immediately unavailable, restrict admin-level access to the web interface and monitor for unauthorized file access attempts.

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:< 6.24.029>= 7.0.0, < 7.04.008

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 LANTIME firmware version
    Access the device web interface system status page or check the firmware version via the admin dashboard to obtain the exact version number
    Affected if The installed version is less than 6.24.029 or is 7.0.0 through 7.04.007 (versions 7.0.0 to 7.04.007 are vulnerable)
  2. Confirm LTOS-Web-Interface is accessible
    Verify the web interface service is enabled and reachable on the device
    Affected if The web interface is active and the firmware version is in the vulnerable range identified above
  3. Verify admin user accounts exist
    Check the web interface user management or authentication configuration to confirm admin-level accounts are configured
    Affected if Admin users exist and can authenticate to a web interface running a vulnerable firmware version

Your environment is affected if the LANTIME firmware version is below 6.24.029 or between 7.0.0 and 7.04.007 and the web interface with admin access is enabled.

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 6.24.029 / 7.04.008 or later
Fixed in 6.24.0297.04.008
Interim mitigation

Apply vendor firmware updates (6.24.029/7.04.008 or later) to patch the path validation flaw. If patching is immediately unavailable, restrict admin-level access to the web interface and monitor for unauthorized file access attempts.

Recommended fix Moderate confidence

6.24.029 (6.x branch) or 7.04.008 (7.x branch) and later

  1. 1. Download the firmware upgrade from the official Meinberg website (www.meinberg.de) - ensure you get version 6.24.029 or later for the 6.x branch, or version 7.04.008 or later for the 7.x branch
  2. 2. Backup the current configuration of the LANTIME device before performing the upgrade
  3. 3. Access the LANTIME web interface as administrator
  4. 4. Navigate to the firmware upgrade section (usually under System or Maintenance settings)
  5. 5. Upload the downloaded firmware file and initiate the upgrade process
  6. 6. Wait for the upgrade to complete and the device to reboot
  7. 7. Verify the firmware version has been updated and the device is functioning normally
  8. 8. Confirm the path traversal vulnerability is resolved by verifying the fix (or checking release notes for MBGID-9343 for 6.x or MBGID-6303 for 7.x)
Caveat Review Meinberg release notes for any configuration or feature changes between your current version and the upgrade version before proceeding

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

Fix this in Lantime Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-46902 — 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-2021-46902 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