CVE-2019-6445: An issue was discovered in NTPsec before 1.1.3.
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 14.6% (FIRST EPSS); higher than 96.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: ntpsec (Alpine:v3.10) 1.1.3-r0; ntpsec (Debian:12) 1.1.3+dfsg1-1; ntpsec (openSUSE:Tumbleweed) 1.2.1-1.2.
Low priority for now. Upgrade to ntpsec (Alpine:v3.10) 1.1.3-r0; ntpsec (Debian:12) 1.1.3+dfsg1-1; ntpsec (openSUSE:Tumbleweed) 1.2.1-1.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in NTPsec before 1.1.3. An authenticated attacker can cause a NULL pointer dereference and ntpd crash in ntp_control.c, related to ctl_getitem.
- Published
- Jan 16, 2019
- Updated
- Jun 16, 2026
- EPSS
- 14.6% · 96th percentile
- CWE
- CWE-476
Report tools
Action score
30
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 14.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ntpsec | ntpsec | cpe:2.3:a:ntpsec:ntpsec |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ntpsec ntpsecbefore 1.1.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | ntpsec | before 1.1.3-r0 | 1.1.3-r0 |
| Debian:12 | ntpsec | before 1.1.3+dfsg1-1 | 1.1.3+dfsg1-1 |
| openSUSE:Tumbleweed | ntpsec | before 1.2.1-1.2 | 1.2.1-1.2 |
Same product
ntpsec: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-6443An issue was discovered in NTPsec before 1.1.3.56Plan
- CVE-2019-6444An issue was discovered in NTPsec before 1.1.3.50Plan
- CVE-2026-102486Out-of-bounds Read in ntpsec30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-6442Jan 16, 2019 · An issue was discovered in NTPsec before 1.1.3.30Monitor
- Later →CVE-2021-22212Jun 8, 2021 · ntpkeygen can generate keys that ntpd fails to parse.29Monitor
- Later →CVE-2023-4012Aug 7, 2023 · Incomplete Internal State Distinction in ntpsec30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:ntpsec | 1.1.3-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:ntpsec | 1.1.3+dfsg1-1 · Debian:12 | Package registry (OSV) |
| opensuse:ntpsec | 1.2.1-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | dos | 2019-01-16 |
| Exploit-DB entry | dos | 2019-01-16 |
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.
- First PoCsame day
- Published
- TodayNov 16, 2026+2861 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.