Bug 1635877 – CVE-2018-17540 strongswan: heap buffer overflow using crafted certificates

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1635877 - (CVE-2018-17540) CVE-2018-17540 strongswan: heap buffer overflow using crafted certificates

Summary:	CVE-2018-17540 strongswan: heap buffer overflow using crafted certificates

Status:	NEW

Aliases:	CVE-2018-17540

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

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

URL:
Whiteboard:	impact=low,public=20181002,reported=2...
Keywords:	Security

Depends On:	1635878 1635879
Blocks:	1635880
	Show dependency tree / graph

Reported:	2018-10-03 16:09 EDT by Laura Pardo
Modified:	2018-10-03 16:10 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
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 Laura Pardo 2018-10-03 16:09:24 EDT

A flaw was found in Strongswan caused by the patch that fixes CVE-2018-16151 and CVE-2018-16151 (DSA-4305-1). An attacker could trigger it using crafted certificates with RSA keys with very small moduli. Verifying signatures with such keys would cause an integer underflow and subsequent heap buffer overflow resulting in a crash of the daemon.


References:
https://packetstormsecurity.com/files/149640/dsa-4309-1.txt

Comment 1 Laura Pardo 2018-10-03 16:10:01 EDT

Created strongswan tracking bugs for this issue:

Affects: epel-all [bug 1635878]
Affects: fedora-all [bug 1635879]

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