# What is CVE-2016-3711? > CVE-2016-3711 is a low-severity flaw (CVSS 3.3) in Openshift from Red Hat, published on 8 June 2016. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.4%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2016-3711 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 12 out of 100 (Info); action: Track. Kept up to date as the evidence changes. - **Severity:** Low (CVSS 3.3 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 0.4% (latest exploit-likelihood forecast) - **Published:** 8 June 2016 - **Record last updated:** 12 April 2025 - **Main product:** Openshift from Red Hat - **Affected products:** 2 ## What is CVE-2016-3711? In plain terms An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read some data. ### The official description HAproxy in Red Hat OpenShift Enterprise 3.2 and OpenShift Origin allows local users to obtain the internal IP address of a pod by reading the "OPENSHIFT_[namespace]_SERVERID" cookie. ### What kind of flaw is it? - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor ### How an attack on it works - Where an attacker can be: Already on the device - How hard it is to pull off: Easy: no special conditions - Login needed first: An ordinary user account - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can read some data Severity vector: `CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N` ## Is CVE-2016-3711 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 0.4%, 0.4%, 0.4%, 0.4%, 0.4%, 0.4%, 0.4%. ### Timeline - 8 June 2016: Published - 12 April 2025: Record last updated ### How Precursor Intelligence ranks it CVE-2016-3711 scores **12 out of 100 (Info)**, with the action "Track". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2016-3711? The published record lists 2 products. - [Openshift](https://www.precursorintelligence.com/product/redhat/openshift) by [Red Hat](https://www.precursorintelligence.com/vendors/redhat) (Application): 3.2 - [Openshift Origin](https://www.precursorintelligence.com/product/redhat/openshift_origin) by [Red Hat](https://www.precursorintelligence.com/vendors/redhat) (Application): version not specified ## How do I fix CVE-2016-3711? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [github.com](https://github.com/openshift/origin/pull/8334) (Patch) - [access.redhat.com](https://access.redhat.com/errata/RHSA-2016:1064) (Vendor advisory) ## Questions ### What is CVE-2016-3711? CVE-2016-3711 is a low-severity flaw in Openshift from Red Hat, published on 8 June 2016. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read some data. ### How serious is CVE-2016-3711? It scores 3.3 out of 10 on the CVSS severity scale, which is low. Our risk score for CVE-2016-3711 is 12 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2016-3711 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2016-3711 affect? For Openshift from Red Hat: 3.2. The record lists 2 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2016-3711? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2016-3711 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact