cve.bz

CVE-2026-102484 ntpsec ntpsec: Heap-based Buffer Overflow

6.4 mediumEPSS 0.2%

Medium (6.4) in ntpsec ntpsec. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Heap-based buffer overflow in the JJY refclock driver in NTPsec ntpd before 1.2.6 allows an attacker who controls the Telephone JJY time source to corrupt memory or crash ntpd via more than six time replies.

Severity

CVSS 3.1

6.4 medium
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-102484 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102484?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102484?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102484 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ntpsecbefore 1.2.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14ntpsecno fix listedDEBIAN-CVE-2026-102484
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 morentpsecno fix listedUBUNTU-CVE-2026-102484
openSUSETumbleweedntpsec1.2.6-1.1openSUSE-SU-2026:12229-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity rather than Important because successful exploitation requires specialized physical access or control over a dedicated telephone modem line to supply malicious responses to the daemon. Red Hat Enterprise Linux utilizes chrony as its default time synchronization provider, and NTPsec is distributed only through community channels such as EPEL. Furthermore, standard deployments do not enable the JJY reference clock driver by default, limiting exposure strictly to systems explicitly configured to receive time signals from a Telephone JJY source.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102484.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON