Multiple stack-based buffer overflows in the NTP time-server interface on Meinberg IMS-LANTIME M3000, IMS-LANTIME M1000, IMS-LANTIME M500, L
Multiple stack-based buffer overflows in the NTP time-server interface on Meinberg IMS-LANTIME M3000, IMS-LANTIME M1000, IMS-LANTIME M500, LANTIME M900, LANTIME M600, LANTIME M400, LANTIME M300, LANTIME M200, LANTIME M100, SyncFire 1100, and LCES devices with firmware before 6.20.004 allow remote attackers to obtain sensitive information, modify data, or cause a denial of service via a crafted parameter in a POST request.
- Published
- Jul 3, 2016
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 65th percentile
- CWE
- CWE-119
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| meinberg | ntp server firmware | cpe:2.3:o:meinberg:ntp_server_firmware |
| meinberg | ims-lantime m1000 | cpe:2.3:h:meinberg:ims-lantime_m1000 |
| meinberg | ims-lantime m3000 | cpe:2.3:h:meinberg:ims-lantime_m3000 |
| meinberg | ims-lantime m500 | cpe:2.3:h:meinberg:ims-lantime_m500 |
| meinberg | lantime m100 | cpe:2.3:h:meinberg:lantime_m100 |
| meinberg | lantime m200 | cpe:2.3:h:meinberg:lantime_m200 |
| meinberg | lantime m300 | cpe:2.3:h:meinberg:lantime_m300 |
| meinberg | lantime m400 | cpe:2.3:h:meinberg:lantime_m400 |
| meinberg | lantime m600 | cpe:2.3:h:meinberg:lantime_m600 |
| meinberg | lantime m900 | cpe:2.3:h:meinberg:lantime_m900 |
| meinberg | lces | cpe:2.3:h:meinberg:lces |
| meinberg | syncfire 1100 | cpe:2.3:h:meinberg:syncfire_1100 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- meinberg ims-lantime m1000all versions
- meinberg ims-lantime m3000all versions
- meinberg ims-lantime m500all versions
- meinberg lantime m100all versions
- meinberg lantime m200all versions
- meinberg lantime m300all versions
- meinberg lantime m400all versions
- meinberg lantime m600all versions
- meinberg lantime m900all versions
- meinberg lcesall versions
- meinberg ntp server firmwareup to 6.0 inclusive
- meinberg syncfire 1100all versions
Same product
meinberg: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-3989The NTP time-server interface on Meinberg IMS-LANTIME M3000, IMS-LANTIME M1000, IMS-LANTIME M500, LANTIME M900, LANTIME M600, LANTIME M400, 34Monitor
- CVE-2016-3962Stack-based buffer overflow in the NTP time-server interface on Meinberg IMS-LANTIME M3000, IMS-LANTIME M1000, IMS-LANTIME M500, LANTIME M9031Monitor
- CVE-2014-5417Meinberg Radio Clocks LANTIME M-Series18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.