You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
This vulnerability has been modified since it was last analyzed by the NVD. It is awaiting reanalysis which may result in further changes to the information provided.
Description
Smart Proxy (aka Smart-Proxy and foreman-proxy) in Foreman before 1.5.4 and 1.6.x before 1.6.2 does not validate SSL certificates, which allows remote attackers to bypass intended authentication and execute arbitrary API requests via a request without a certificate.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to nvd@nist.gov.
CVE Modified by Red Hat, Inc.5/13/2024 11:14:33 PM
Action
Type
Old Value
New Value
CVE Modified by Red Hat, Inc.2/12/2023 7:42:12 PM
Action
Type
Old Value
New Value
Changed
Description
It was discovered that foreman-proxy, when running in SSL-secured mode, did not correctly verify SSL client certificates. This could permit any client with access to the API to make requests and perform actions otherwise restricted.
Smart Proxy (aka Smart-Proxy and foreman-proxy) in Foreman before 1.5.4 and 1.6.x before 1.6.2 does not validate SSL certificates, which allows remote attackers to bypass intended authentication and execute arbitrary API requests via a request without a certificate.
CVE Modified by Red Hat, Inc.2/02/2023 11:16:12 AM
Action
Type
Old Value
New Value
Changed
Description
Smart Proxy (aka Smart-Proxy and foreman-proxy) in Foreman before 1.5.4 and 1.6.x before 1.6.2 does not validate SSL certificates, which allows remote attackers to bypass intended authentication and execute arbitrary API requests via a request without a certificate.
It was discovered that foreman-proxy, when running in SSL-secured mode, did not correctly verify SSL client certificates. This could permit any client with access to the API to make requests and perform actions otherwise restricted.
https://groups.google.com/forum/#%21topic/foreman-announce/jXC5ixybjqo [Third Party Advisory]
CVE Translated by NIST8/31/2016 9:45:00 PM
Action
Type
Old Value
New Value
Added
Translation
Smart Proxy (también conocido como Smart-Proxy y foreman-proxy) en Foreman en versiones anteriores a 1.5.4 y 1.6.x en versiones anteriores a 1.6.2 no valida certificados SSL, lo que permite a atacantes remotos eludir autenticación intencionada y ejecutar peticiones API arbitrarias a través de una petición sin un certificado.
Removed
Translation
Smart Proxy (también conocido como Smart-Proxy y foreman-proxy) en Foreman anterior a 1.5.4 y 1.6.x anterior a 1.6.2 no valida los certificados SSL, lo que permite a atacantes remotos evadir la autenticación y ejecutar solicitudes a la API arbitrarias a través de una solicitud sin certificado.
Modified Analysis by NIST8/31/2016 10:54:22 AM
Action
Type
Old Value
New Value
Changed
CPE Configuration
Configuration 1
OR
*cpe:2.3:a:theforeman:foreman:1.5.3:*:*:*:*:*:*:* (and previous)
*cpe:2.3:a:theforeman:foreman:1.6.0:*:*:*:*:*:*:*
*cpe:2.3:a:theforeman:foreman:1.6.1:*:*:*:*:*:*:*
Configuration 1
OR
*cpe:2.3:a:redhat:openstack:5.0:*:*:*:*:*:*:*
*cpe:2.3:a:redhat:openstack:4.0:*:*:*:*:*:*:*
Configuration 2
OR
*cpe:2.3:a:theforeman:foreman:1.5.3:*:*:*:*:*:*:* (and previous)
*cpe:2.3:a:theforeman:foreman:1.6.0:*:*:*:*:*:*:*
*cpe:2.3:a:theforeman:foreman:1.6.1:*:*:*:*:*:*:*
Changed
Reference Type
http://rhn.redhat.com/errata/RHSA-2015-0287.html No Types Assigned
http://rhn.redhat.com/errata/RHSA-2015-0287.html Third Party Advisory
Changed
Reference Type
http://rhn.redhat.com/errata/RHSA-2015-0288.html No Types Assigned
http://rhn.redhat.com/errata/RHSA-2015-0288.html Third Party Advisory
Changed
Reference Type
https://github.com/theforeman/smart-proxy/pull/217 No Types Assigned
https://groups.google.com/forum/#%21topic/foreman-announce/jXC5ixybjqo No Types Assigned
https://groups.google.com/forum/#%21topic/foreman-announce/jXC5ixybjqo Third Party Advisory
CVE Modified by Red Hat, Inc.3/17/2015 10:01:28 PM
Action
Type
Old Value
New Value
Changed
Description
Smart Proxy (aka Smart-Proxy and foreman-proxy) in Foreman before 1.5.4 and 1.6.x before 1.6.2 does not validate SSL certificates, which allows remote attackers to bypass intended authentication and execute arbitrary API request via a request without a certificate.
Smart Proxy (aka Smart-Proxy and foreman-proxy) in Foreman before 1.5.4 and 1.6.x before 1.6.2 does not validate SSL certificates, which allows remote attackers to bypass intended authentication and execute arbitrary API requests via a request without a certificate.
) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
