Skip to content

Conversation

iam-veeramalla
Copy link
Contributor

What type of PR is this?

/kind bug

What does this PR do / why we need it:
Fix CVE-2024-31989

It has been discovered that an unprivileged pod in a different namespace on the same cluster could connect to the Redis server on port 6379. Despite having installed the latest version of the VPC CNI plugin on the EKS cluster, it requires manual enablement through configuration to enforce network policies. This raises concerns that many clients might unknowingly have open access to their Redis servers. This vulnerability could lead to Privilege Escalation to the level of cluster controller, or to information leakage, affecting anyone who does not have strict access controls on their Redis instance. This issue has been patched in version(s) 2.8.19, 2.9.15 and 2.10.10.

Have you updated the necessary documentation?
NA

Which issue(s) this PR fixes:

Fixes CVE-2024-31989

How to test changes / Special notes to the reviewer:

@openshift-ci openshift-ci bot requested review from jannfis and mehabhalodiya May 22, 2024 09:09
@iam-veeramalla
Copy link
Contributor Author

/retest

@varshab1210
Copy link
Member

/test v4.12-images

@varshab1210
Copy link
Member

Hi @iam-veeramalla @svghadi seeing this error with 4.12-image test

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
error: build error: building at STEP "RUN yum -y install dnf httpd-tools podman docker": while running runtime: exit status 1
INFO[2024-05-22T11:54:50Z] Image ci-op-wxt3qptm/pipeline:gitops-operator created  for-build=gitops-operator

https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/redhat-developer_gitops-operator/710/pull-ci-redhat-developer-gitops-operator-master-v4.12-images/1793249103853916160

@svghadi
Copy link
Member

svghadi commented May 22, 2024

@varshab1210 - It looks like an intermittent issue. Let's try a rerun before debugging further.

@varshab1210
Copy link
Member

Tests are failing as pods are taking unusual amount of time to come up. Looking into it

@varshab1210
Copy link
Member

/test v4.14-kuttl-parallel

@varshab1210
Copy link
Member

/test unit

Copy link

openshift-ci bot commented May 23, 2024

@iam-veeramalla: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/v4.12-kuttl-parallel 92780ab link true /test v4.12-kuttl-parallel
ci/prow/v4.12-kuttl-sequential 92780ab link true /test v4.12-kuttl-sequential
ci/prow/v4.12-e2e 92780ab link true /test v4.12-e2e
ci/prow/v4.13-e2e 92780ab link true /test v4.13-e2e
ci/prow/v4.13-kuttl-parallel 92780ab link true /test v4.13-kuttl-parallel
ci/prow/v4.13-kuttl-sequential 92780ab link true /test v4.13-kuttl-sequential
ci/prow/v4.14-kuttl-parallel 92780ab link true /test v4.14-kuttl-parallel
ci/prow/v4.14-kuttl-sequential 92780ab link true /test v4.14-kuttl-sequential
ci/prow/v4.14-e2e 92780ab link true /test v4.14-e2e

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link

openshift-ci bot commented May 23, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants