Bug 1510985 – CVE-2017-1000231 ldns: Memory corruption in ldns_rr_new_frm_fp_l

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1510985 - (CVE-2017-1000231) CVE-2017-1000231 ldns: Memory corruption in ldns_rr_new_frm_fp_l

Summary:	CVE-2017-1000231 ldns: Memory corruption in ldns_rr_new_frm_fp_l

Status:	CLOSED WONTFIX

Aliases:	CVE-2017-1000231

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20170425,repor...
Keywords:	Security

Depends On:	1511046
Blocks:	1510999
	Show dependency tree / graph

Reported:	2017-11-08 08:47 EST by Adam Mariš
Modified:	2018-03-13 14:01 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	ldns 1.7.1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-11-14 05:44:12 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Adam Mariš 2017-11-08 08:47:20 EST

A memory corruption via double free was found in ldns_rr_new_frm_fp_l() function.

Upstream bug:

https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=1256

Upstream patch:

https://git.nlnetlabs.nl/ldns/commit/?id=c8391790

Comment 1 Adam Mariš 2017-11-08 10:33:12 EST

Created ldns tracking bugs for this issue:

Affects: fedora-all [bug 1511046]

Comment 5 Stefan Cornelius 2017-11-14 05:44:22 EST

Statement:

Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

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