LiveActive security incident?Get immediate response
CVE Record

CVE-2015-5300: The panic_gate check in NTP before 4.2.8p5 is only re-enabled after the first change to the system clock th...

The panic_gate check in NTP before 4.2.8p5 is only re-enabled after the first change to the system clock that was greater than 128 milliseconds by default, which allows remote attackers to set NTP to an arbitrary time when started with the -g option, or to alter the time by up to 900 seconds otherwise by responding to an unspecified number of requests from trusted sources, and leveraging a resulting denial of service (abort and restart).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw lets an attacker who can influence trusted NTP replies move a system clock unexpectedly. Bad time can disrupt authentication, logging, certificates, scheduled jobs, and distributed systems. The source bundle does not show active exploitation, but the issue was serious enough to receive multiple vendor advisories. Exposure is most likely on systems running ntpd older than 4.2.8p5, including Linux, Unix, appliance, or industrial environments covered by vendor advisories. Risk is higher where NTP trust is weak, time sync is internet-reachable, or services depend tightly on accurate time. Prioritize remediation for identity, logging, financial, certificate, industrial, and distributed systems. Treat unsupported or internet-exposed NTP deployments as higher urgency. Routine endpoints can follow normal patch cycles if vendor-fixed packages are already deployed. Mitigation focus: Upgrade NTP to 4.2.8p5 or a vendor-fixed package.; Apply relevant Red Hat, Ubuntu, Debian, SUSE, Oracle, IBM, or appliance advisories.; Review NTP configuration for unnecessary -g usage and weak trust assumptions..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2015-5300 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
19Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.