The OpenShift image import whitelist failed to enforce restrictions correctly when running commands such as "oc tag", for example. This could allow a user with access to OpenShift to run images from registries that should not be allowed.
The image import whitelist is enforced when running "oc import-image someregistry.com/someimage"
but the whitelist is not enforced when running
"oc tag someregistry.com:foo some:tag"
nor is it enforced when directly creating an imagestream tag that references a non-whitelisted registry.
Name: Ben Parees (Red Hat)
This was fixed in the release of OpenShift 3.9 via RHBA-2018:0489
Is OpenShift 3.7 affected as well?
Dominik: Yes, Would you like to request a backport of this issue? It is only rated moderate so please provide the reason while you require it.
Thanks for confirmation, Jason. Please have the corresponding security advisory (https://access.redhat.com/security/cve/cve-2017-15137) updated with this information, then. I'll open a case requesting a backport.
According to our support lifecycle for Openshift Container Platform Red Hat not obliged to backport moderate issues to earlier minor versions. It states "Customers are expected to upgrade their OpenShift environment to the most current supported version". Is there any reason you can't upgrade, or do you think the impact rating needs to be reviewed?
I've confirmed that this vulnerability doesn't affect OCP 3.7 because the ability to whitelist image repositories was only added in 3.9. I've added a statement to https://access.redhat.com/security/cve/cve-2017-15137 to that affect.