Bug 1690246

Summary:	CVE-2019-3855 CVE-2019-3856 CVE-2019-3857 CVE-2019-3858 CVE-2019-3859 CVE-2019-3860 CVE-2019-3861 CVE-2019-3862 CVE-2019-3863 libssh: various flaws [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Dhananjay Arunesh <darunesh>
Component:	libssh2	Assignee:	Paul Howarth <paul>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	high
Version:	29	CC:	ansasaki, asn, djuran, jfch, kdudka, negativo17, paul, rdieter, redhat-bugzilla
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-19 14:10:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dhananjay Arunesh 2019-03-19 06:46:54 UTC

This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

Comment 1 Dhananjay Arunesh 2019-03-19 06:46:56 UTC

Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# low, medium, high, urgent (required)
severity=high

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1687303,1687304,1687305,1687306,1687307,1687310,1687311,1687312,1687313,1690246

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

Comment 2 Andreas Schneider 2019-03-19 12:05:06 UTC

Is this about libssh [1] or about libssh2 [2]?

[1] https://www.libssh.org/
[2] https://www.libssh2.org/

Comment 3 Dhananjay Arunesh 2019-03-19 12:57:45 UTC

(In reply to Andreas Schneider from comment #2)
> Is this about libssh [1] or about libssh2 [2]?
> 
> [1] https://www.libssh.org/
> [2] https://www.libssh2.org/

libssh2 is only affected and please follow the below link with fixed whiteboard for the same bug:
http://127.0.0.1:5600/static/#/tracker/bugzilla/1690408

Comment 4 Andreas Schneider 2019-03-19 13:50:36 UTC

Changing the component to libssh2 ...

Comment 5 Kamil Dudka 2019-03-19 14:10:12 UTC

(In reply to Dhananjay Arunesh from comment #3)
> libssh2 is only affected and please follow the below link with fixed
> whiteboard for the same bug:
> http://127.0.0.1:5600/static/#/tracker/bugzilla/1690408

I am afraid that the above link works as expected only on your computer.


(In reply to Andreas Schneider from comment #4)
> Changing the component to libssh2 ...

We already have [fedora-all] tracking bug for those CVEs.

*** This bug has been marked as a duplicate of bug 1690408 ***