Bug 1036086 – VUL-0: Various vulnerabilities in the Oracle Berkeley DB.

Bug 1036086 - (CVE-2017-3617) VUL-0: Various vulnerabilities in the Oracle Berkeley DB.

(CVE-2017-3617)
Summary:	VUL-0: Various vulnerabilities in the Oracle Berkeley DB.

Status:	RESOLVED WONTFIX

Classification:	Novell Products
Product:	SUSE Security Incidents
Classification:	Novell Products
Component:	Incidents
Version:	unspecified
Hardware:	Other Other

Priority:	P3 - Medium Severity: Normal
Target Milestone:	---
Assigned To:	Pedro Monreal Gonzalez
QA Contact:	Security Team bot

URL:	https://smash.suse.de/issue/184343/
Whiteboard:	CVSSv2:NVD:CVE-2017-3608:3.7:(AV:L/A...
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Create test case

Clone This Bug

Reported:	2017-04-25 15:45 UTC by Marcus Meissner
Modified:	2017-05-03 12:57 UTC (History)
CC List:	4 users (show)

See Also:
Found By:	Security Response Team
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

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

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

Description Marcus Meissner 2017-04-25 15:45:32 UTC

http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixBDB

Oracle Berkeley DB Executive Summary

This Critical Patch Update contains 14 new security fixes for Oracle Berkeley DB.  None of these vulnerabilities may be remotely exploitable without authentication, i.e., none may be exploited over a network without requiring user credentials.  The English text form of this Risk Matrix can be found here. 

CVE-2017-3604   
CVE-2017-3605   
CVE-2017-3606   
CVE-2017-3607   
CVE-2017-3608   
CVE-2017-3609   
CVE-2017-3610   
CVE-2017-3611   
CVE-2017-3612   
CVE-2017-3613   
CVE-2017-3614   
CVE-2017-3615   
CVE-2017-3616   
CVE-2017-3617

Comment 1 Marcus Meissner 2017-04-25 15:46:42 UTC

Tom, this might Berkeley DB or Berkeley Java

e.g. libdb* or libdb_java*

do you know and can check?

Comment 5 Marcus Meissner 2017-05-03 12:57:04 UTC

We currently cannot easily determine nor fix this issues in our older berkeley db packages.