Bug 1484938 – CVE-2017-1000034 akka-actor: Java deserialization issue in the Remoting component

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 1484938 - (CVE-2017-1000034) CVE-2017-1000034 akka-actor: Java deserialization issue in the Remoting component

Summary:	CVE-2017-1000034 akka-actor: Java deserialization issue in the Remoting compo...

Status:	CLOSED NOTABUG

Aliases:	CVE-2017-1000034

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

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

URL:
Whiteboard:	impact=important,public=20170210,repo...
Keywords:	Security

Depends On:	1484951
Blocks:	1484941
	Show dependency tree / graph

Reported:	2017-08-24 11:23 EDT by Andrej Nemec
Modified:	2017-09-05 20:42 EDT (History)
CC List:	18 users (show)

See Also:
Fixed In Version:	akka 2.4.17
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-09-05 20:42:35 EDT
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 Andrej Nemec 2017-08-24 11:23:44 EDT

Akka is vulnerable to a java deserialization attack in its Remoting component resulting in remote code execution in the context of the ActorSystem.

External References:

http://doc.akka.io/docs/akka/2.4/security/2017-02-10-java-serialization.html

Comment 1 Andrej Nemec 2017-08-24 11:53:33 EDT

Created opendaylight tracking bugs for this issue:

Affects: openstack-rdo [bug 1484951]

Comment 2 Stephen Kitt 2017-09-05 08:20:39 EDT

In RHOS 12 ODL, we're shipping Akka 2.4.18, which doesn't suffer from this issue.

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