Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1333378 - (CVE-2016-3728) CVE-2016-3728 foreman: Missing input validation in Smart Proxy allows RCE via TFTP file variant parameter
CVE-2016-3728 foreman: Missing input validation in Smart Proxy allows RCE via...
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 1333405 1333408
Blocks: 1333386
  Show dependency treegraph
Reported: 2016-05-05 08:00 EDT by Adam Mariš
Modified: 2016-09-20 20:26 EDT (History)
23 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
It was found that the “variant” parameter in the TFTP API of Foreman was passed to the eval() function. An attacker could possibly use this flaw to execute arbitrary code with the privileges of the Foreman user.
Story Points: ---
Clone Of:
: 1333405 1333408 (view as bug list)
Last Closed: 2016-09-19 16:26:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2016-05-05 08:00:41 EDT
It was reported that TFTP API module in Smart Proxy is vulnerable to remote code execution via "variant" parameter, which is used to instantiate an implementation class using eval() on the user supplemented input.

Service is usually restricted in a default Foreman installation by requiring client SSL certificates and enforcing access to a configured list of trusted hosts, but may also be configured openly. The TFTP module is enabled in default installation, but may be disabled. Affected versions are 0.2 and higher.

Upstream bug:

Comment 1 Adam Mariš 2016-05-05 08:01:00 EDT

Name: the Foreman project
Upstream: Lukas Zapletal (Red Hat)
Comment 3 Kurt Seifried 2016-09-19 16:26:57 EDT
This issue has been addressed in:

Satellite 6.2

In RHBA-2016:1501

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