CVE-2014-3691
published 2015-03-09CVE-2014-3691: 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…
PriorityP349high7.5CVSS 2.0
AVNACLAuNCPIPAP
EPSS
1.71%
74.8th percentile
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.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| redhat | openstack | — | — |
| redhat | openstack | — | — |
| theforeman | foreman | <= 1.5.3 | — |
| theforeman | foreman | — | — |
| theforeman | foreman | — | — |
CVSS provenance
nvdv2.07.5HIGHAV:N/AC:L/Au:N/C:P/I:P/A:P
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-m4h9-hcv2-hw6h: Smart Proxy (aka Smart-Proxy and foreman-proxy) in Foreman before 1
ghsa_unreviewed·2022-05-14
CVE-2014-3691 [HIGH] GHSA-m4h9-hcv2-hw6h: Smart Proxy (aka Smart-Proxy and foreman-proxy) in Foreman before 1
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.
Red Hat
foreman-proxy: failure to verify SSL certificates
vendor_redhat·2014-10-06·CVSS 7.5
CVE-2014-3691 [HIGH] CWE-295 foreman-proxy: failure to verify SSL certificates
foreman-proxy: failure to verify SSL certificates
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.
No detection rules found.
No public exploits indexed.
http://projects.theforeman.org/issues/7822http://rhn.redhat.com/errata/RHSA-2015-0287.htmlhttp://rhn.redhat.com/errata/RHSA-2015-0288.htmlhttps://github.com/theforeman/smart-proxy/pull/217https://groups.google.com/forum/#%21topic/foreman-announce/jXC5ixybjqohttp://projects.theforeman.org/issues/7822http://rhn.redhat.com/errata/RHSA-2015-0287.htmlhttp://rhn.redhat.com/errata/RHSA-2015-0288.htmlhttps://github.com/theforeman/smart-proxy/pull/217https://groups.google.com/forum/#%21topic/foreman-announce/jXC5ixybjqo
2015-03-09
Published