Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2018-13458: NULL Pointer Dereference in Nagios Core qh_core

Published Jul 12, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3
EPSS4.5%92nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Nagios Enterprises
IdentifiersCVE-2018-13458CWE-476 · NULL Pointer Dereference

A NULL pointer dereference vulnerability exists in the qh_core component of Nagios Core 4.4.1 and earlier. An attacker can trigger this flaw by sending a specially crafted payload to the listening UNIX socket, causing the application to dereference a NULL pointer.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a local attacker to cause a denial-of-service condition, resulting in the Nagios Core process crashing. This could disrupt monitoring operations until the service is restarted.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the Nagios Core UNIX socket to trusted users only, using file system permissions or other access controls, to reduce the risk of local exploitation.

Remediation

Patch, then assume compromise.

Upgrade to a version of Nagios Core later than 4.4.1 in which this vulnerability has been patched.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Nagios EnterprisesNagios Coreapplication
FAQ

Frequently asked questions

Is CVE-2018-13458 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2018-13458 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2018-13458?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2018-13458.
Is there a patch for CVE-2018-13458?
Upgrade to a version of Nagios Core later than 4.4.1 in which this vulnerability has been patched.
What products are affected by CVE-2018-13458?
Nagios Enterprises Nagios Core.
How severe is CVE-2018-13458?
CVE-2018-13458 has a CVSS v3 score of 5.5 (Medium) and an EPSS score of 4.5% (92nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.