Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2009-0021: NTP 4.2.4 before 4.2.4p5 and 4.2.5 before 4.2.5p150 does not properly check the return value from the OpenSSL EVP_VerifyFinal function, whic

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 3.2% (FIRST EPSS); higher than 88.1% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: ntp (Debian:11) 1:4.2.4p4+dfsg-8; ntp (Debian:4.0) 1:4.2.2.p4+dfsg-2etch1; ntp (Red Hat:enterprise_linux:4::as) 0:4.2.0.a.20040617-8.el4_7.1.

Low priority for now. Upgrade to ntp (Debian:11) 1:4.2.4p4+dfsg-8; ntp (Debian:4.0) 1:4.2.2.p4+dfsg-2etch1; ntp (Red Hat:enterprise_linux:4::as) 0:4.2.0.a.20040617-8.el4_7.1 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

NTP 4.2.4 before 4.2.4p5 and 4.2.5 before 4.2.5p150 does not properly check the return value from the OpenSSL EVP_VerifyFinal function, which allows remote attackers to bypass validation of the certificate chain via a malformed SSL/TLS signature for DSA and ECDSA keys, a similar vulnerability to CVE-2008-5077.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Jan 7, 2009
Updated
Jun 16, 2026
EPSS
3.2% · 88th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2009-0021

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
ntpntp

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • ntp ntpup to 4.2.4p4 inclusive
  • ntp ntp4.2.0
  • ntp ntp4.2.2
  • ntp ntp4.2.4p1
  • ntp ntp4.2.4p2
  • ntp ntp4.2.4p3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11ntpbefore 1:4.2.4p4+dfsg-81:4.2.4p4+dfsg-8
Debian:4.0ntpbefore 1:4.2.2.p4+dfsg-2etch11:4.2.2.p4+dfsg-2etch1
Red Hat:enterprise_linux:4::asntpbefore 0:4.2.0.a.20040617-8.el4_7.10:4.2.0.a.20040617-8.el4_7.1
Red Hat:enterprise_linux:4::asntp-debuginfobefore 0:4.2.0.a.20040617-8.el4_7.10:4.2.0.a.20040617-8.el4_7.1
Red Hat:enterprise_linux:5::clientntpbefore 0:4.2.2p1-9.el5_3.10:4.2.2p1-9.el5_3.1
Red Hat:enterprise_linux:5::clientntp-debuginfobefore 0:4.2.2p1-9.el5_3.10:4.2.2p1-9.el5_3.1

Same product

ntp: all records

Other highest-scoring records for the same primary product.

  • CVE-2015-7871Crypto-NAK packets in ntpd in NTP 4.2.x before 4.2.8p4, and 4.3.x before 4.3.77 allows remote attackers to bypass authentication.
    64This week
  • CVE-2014-9295Multiple stack-based buffer overflows in ntpd in NTP before 4.2.8 allow remote attackers to execute arbitrary code via a crafted packet, rel
    54Plan
  • CVE-2013-5211The monlist feature in ntp_request.c in ntpd in NTP before 4.2.7p26 allows remote attackers to cause a denial of service (traffic amplificat
    49Plan

Published before and after this one in the same product

  • ← EarlierCVE-2004-0657Aug 6, 2004 · Integer overflow in the NTP daemon (NTPd) before 4.0 causes the NTP server to return the wrong date/time offset when a client requests a dat
    21Monitor
  • Later →CVE-2009-0159Apr 14, 2009 · Stack-based buffer overflow in the cookedprint function in ntpq/ntpq.c in ntpq in NTP before 4.2.4p7-RC2 allows remote NTP servers to execut
    31Monitor
  • Later →CVE-2009-1252May 19, 2009 · Stack-based buffer overflow in the crypto_recv function in ntp_crypto.c in ntpd in NTP before 4.2.4p7 and 4.2.5 before 4.2.5p74, when OpenSS
    33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ntp1:4.2.4p4+dfsg-8 · Debian:11Package registry (OSV)
red hat:ntp0:4.2.0.a.20040617-8.el4_7.1 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:ntp-debuginfo0:4.2.0.a.20040617-8.el4_7.1 · Red Hat:enterprise_linux:4::asPackage registry (OSV)

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.

No history yet (it accumulates with the daily EPSS job).

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.

Finders, 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

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
Low
Confidentiality impact
P
Integrity impact
None
Availability impact
None

CVSS vector

AV:N/AC:L/Au:N/C:P/I:N/A:N

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);

Fixed

ts
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records