CVE-2021-46903
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 · uneditedAn 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. An admin can delete required user accounts (in violation of expected access control).
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 LTOS web interface in Meinberg LANTIME firmware has an access control vulnerability where admin users can delete required system user accounts that should be protected from deletion. This violates expected access control and could lead to loss of critical system accounts.
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.029>= 7.0.0, < 7.04.008CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 LANTIME firmware versionLog into the LANTIME web interface and navigate to System > Status or System > Information to view the firmware version. Alternatively, access the device via SSH and run 'uname -a' or check '/etc/version' if accessible.Affected if The installed version is < 6.24.029 for the v6.x branch, or >= 7.0.0 and < 7.04.008 for the v7.x branch.
-
Confirm the web interface is accessibleVerify the LTOS web interface is reachable by accessing the device IP in a browser on the /lantime or / endpoint.Affected if The web interface is accessible, which is required for the vulnerable code path to be exploitable.
-
Verify admin user privilegesLog in to the web interface with an admin-level account and navigate to the user management or accounts section.Affected if An admin-level user account exists and has access to user deletion functionality.
A system is affected if it runs LANTIME firmware version 6.x below 6.24.029 or version 7.x below 7.04.008 and has the web interface accessible with admin users.
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 · scoped6.24.0297.04.008
Upgrade firmware to version 6.24.029 (for v6) or 7.04.008 (for v7) or later. Until upgrade is possible, implement compensating controls such as restricting admin access and maintaining backups of account configurations.
LANTIME Firmware 6.24.029 or later, or 7.04.008 or later
- Identify the current LANTIME Firmware version installed on the device
- Determine which firmware branch (6.x or 7.x) is in use
- Download the appropriate fixed firmware version from Meinberg's official support portal: version 6.24.029 or later for the 6.x branch, or version 7.04.008 or later for the 7.x branch
- Review Meinberg's firmware upgrade documentation for your specific device model
- Perform a backup of the current device configuration if supported
- Upload and apply the firmware update through the LANTIME web interface or device management interface
- Verify the firmware was applied successfully and the device is operational
- Confirm the upgrade resolved the improper access control issue
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46903 — 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-2021-46903 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