Project

General

Profile

Bug #7822

CVE-2014-3691 - Smart proxy doesn't perform verification of client SSL certificate on API requests

Added by Dominic Cleal over 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Dominic Cleal
Category:
SSL
Target version:
1.5.4
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/smart-proxy/pull/217
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Reported to foreman-security by Michael Moll. Also reported by Jon McKenzie in a comment here: http://projects.theforeman.org/issues/5651#note-1, and possibly the same as Michael Messmore's #6677 ticket.

The smart proxy when running in an SSL-secured mode permits incoming API calls to any endpoint without requiring, or performing any verification of an SSL client certificate. This permits any client with access to the API to make requests and perform actions (permitting control of Puppet CA, DHCP, DNS etc.)

Users are strongly recommended to ensure smart proxy ports (typically 8443/tcp) are firewalled so only Foreman hosts can access the service and to set the "trusted_hosts" config setting in /etc/foreman-proxy/settings.yml to a list of Foreman hostnames for host based acccess control.

See https://groups.google.com/forum/#!topic/foreman-announce/jXC5ixybjqo for more information on mitigation.

Related issues

Related to Smart Proxy - Feature #6677: Autosign entry additions should require authenticationResolved2014-07-17
Related to Smart Proxy - Refactor #7832: Integration test for SSL verificationClosed2014-10-07
Related to Smart Proxy - Feature #7849: trusted_hosts should determine hostname from certificate CN on SSL requestsClosed2014-10-08
Related to Installer - Bug #8301: Add a checker script for reverse DNSClosed2014-11-06
Has duplicate Smart Proxy - Bug #5651: The 'trusted_hosts' config key has an unintuitive (and potentially dangerous) behaviorDuplicate2014-05-09

Associated revisions

Revision 52f0bacf (diff)
Added by Dominic Cleal over 8 years ago

fixes #7822 - forbid HTTPS requests with no client SSL certificate

History

#1 Updated by Dominic Cleal over 8 years ago

  • Project changed from Foreman to Smart Proxy
  • Category changed from Security to SSL

#2 Updated by Dominic Cleal over 8 years ago

  • Has duplicate Bug #5651: The 'trusted_hosts' config key has an unintuitive (and potentially dangerous) behavior added

#3 Updated by Dominic Cleal over 8 years ago

  • Related to Feature #6677: Autosign entry additions should require authentication added

#4 Updated by Dominic Cleal over 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Dominic Cleal

#5 Updated by The Foreman Bot over 8 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/217 added
  • Pull request deleted ()

#6 Updated by Dominic Cleal over 8 years ago

  • Related to Refactor #7832: Integration test for SSL verification added

#7 Updated by Dominic Cleal over 8 years ago

  • Related to Feature #7849: trusted_hosts should determine hostname from certificate CN on SSL requests added

#8 Updated by Dominic Cleal over 8 years ago

  • Description updated (diff)

#9 Updated by Dominic Cleal over 8 years ago

  • Legacy Backlogs Release (now unused) set to 26

#10 Updated by Dominic Cleal over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#11 Updated by Dominic Cleal over 8 years ago

We plan on releasing updated foreman-proxy packages as part of 1.5.4 and 1.6.2.

#12 Updated by Dominic Cleal over 8 years ago

  • Subject changed from Smart proxy doesn't perform verification of client SSL certificate on API requests to CVE-2014-3691 - Smart proxy doesn't perform verification of client SSL certificate on API requests

#14 Updated by Dominic Cleal over 8 years ago

  • Related to Bug #8301: Add a checker script for reverse DNS added

Also available in: Atom PDF