Tainted value used to initialize thread count

Bug #1776470 reported by Andrei Bunghez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R5.0
In Progress
High
Andrei Bunghez
Trunk
In Progress
High
Andrei Bunghez
OpenContrail
New
Undecided
Unassigned

Bug Description

Hi all,

Coverity reports a tainted value is used to initialize thread count in TaskScheduler::GetThreadCount. The value read from the environment is not checked for range.

Regards,
Andrei

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R5.0

Review in progress for https://review.opencontrail.org/43734
Submitter: Andrei Bunghez (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/43735
Submitter: Andrei Bunghez (<email address hidden>)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.