LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25035: Unbound before 1.9.5 allows an out-of-bounds write in sldns_bget_token_par.

Unbound before 1.9.5 allows an out-of-bounds write in sldns_bget_token_par. NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running Unbound installation cannot be remotely or locally exploited

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This CVE concerns a possible memory write bug in Unbound before 1.9.5. The practical urgency is reduced because the CVE text says the vendor disputes exploitability and states that a running Unbound installation cannot be exploited remotely or locally. Treat it as a hygiene update unless your vendor advisory says otherwise.

Executive priority

Low priority for emergency response, but still appropriate for routine patch management. The main business action is to confirm whether legacy Unbound or vendor-embedded Unbound exists and apply supported updates during the normal maintenance cycle.

Technical view

The reported issue is an out-of-bounds write in sldns_bget_token_par in Unbound before 1.9.5. Public metadata does not provide CVSS, CWE, exploit evidence, or a confirmed exploitation path. Debian issued an LTS security update, while the CVE note records the vendor dispute over whether this is exploitable in deployed Unbound.

Likely exposure

Exposure is primarily systems running Unbound before 1.9.5 or products that embed affected Unbound code. The bundle does not identify specific vulnerable CPEs. Because the vendor dispute says deployed Unbound is not exploitable remotely or locally, operational exposure appears limited from the provided evidence.

Exploitation context

No active exploitation is cited, and the CVE is not in KEV. The source bundle says the code may be vulnerable but a running Unbound installation cannot be remotely or locally exploited. Evidence is therefore insufficient to claim real-world exploitability.

Researcher notes

Focus on version and vendor context rather than exploit reproduction. The key nuance is the vendor dispute: the function may contain unsafe behavior, but the provided CVE text says deployed Unbound cannot be exploited. No CVSS, CWE, PoC, or KEV signal is available in the bundle.

Mitigation direction

  • Inventory Unbound deployments and embedded vendor products.
  • Upgrade Unbound to 1.9.5 or later where applicable.
  • Apply Debian LTS security updates for affected Debian systems.
  • Review NetApp advisory applicability for managed appliances or storage products.
  • Monitor vendor guidance because exploitability is disputed.

Validation and detection

  • Confirm installed Unbound package and version on relevant systems.
  • Check vendor advisories for embedded Unbound exposure.
  • Verify Debian systems include the referenced LTS security update.
  • Document systems below 1.9.5 and their compensating vendor status.
  • Do not report active exploitation without KEV or source evidence.
Prepared
Confidence
medium
Sources
5

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-2019-25035 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
4Source links

CVSS and timeline data

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

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.