Bug 1954780 (CVE-2019-25035) - CVE-2019-25035 unbound: out-of-bounds write in sldns_bget_token_par
Summary: CVE-2019-25035 unbound: out-of-bounds write in sldns_bget_token_par
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-25035
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1968662 1968663 1968664 1859933
Blocks: 1954811
TreeView+ depends on / blocked
 
Reported: 2021-04-28 18:44 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-06-14 07:14 UTC (History)
5 users (show)

Fixed In Version: unbound 1.9.6
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in unbound. An out-of-bounds write in the sldns_bget_token_par function may be abused by a remote attacker. The highest threat from this vulnerability is to data confidentiality and integrity as well as service availability.
Clone Of:
Environment:
Last Closed: 2021-05-18 20:39:00 UTC


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2021-04-28 18:44:09 UTC
Unbound before 1.9.5 allows an out-of-bounds write in sldns_bget_token_par.

Reference:
https://ostif.org/our-audit-of-unbound-dns-by-x41-d-sec-full-results/

Comment 3 Riccardo Schirone 2021-05-06 14:52:12 UTC
Statement:

There is no available reproducer or proof of concept for this issue, nor it was ever proven the out-of-bounds write can happen in practice. Indeed in the original report this issue was considered one that might not be triggered and for this reason its Impact is Moderate.

Comment 5 errata-xmlrpc 2021-05-18 15:37:36 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2021:1853 https://access.redhat.com/errata/RHSA-2021:1853

Comment 6 Product Security DevOps Team 2021-05-18 20:39:00 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2019-25035


Note You need to log in before you can comment on or make changes to this bug.