The net/http package in Go through 1.6 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect a CGI applications outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an httpoxy issue.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Fedora | Fedoraproject | 23 (including) | 23 (including) |
| Fedora | Fedoraproject | 24 (including) | 24 (including) |
| Red Hat Enterprise Linux 7 | RedHat | golang-0:1.6.3-1.el7_2.1 | * |
| Golang | Ubuntu | precise | * |
| Golang | Ubuntu | trusty | * |
| Golang | Ubuntu | vivid/stable-phone-overlay | * |
| Golang | Ubuntu | vivid/ubuntu-core | * |
| Golang | Ubuntu | wily | * |
| Golang-1.6 | Ubuntu | esm-infra/xenial | * |
| Golang-1.6 | Ubuntu | trusty | * |
| Golang-1.6 | Ubuntu | xenial | * |
| Golang-1.6 | Ubuntu | yakkety | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: