CyberRota Analysis
AI-GeneratedThe vulnerability arises from improper validation of pod identifier uniqueness in the AWS Network Policy Agent, potentially allowing authenticated remote users to bypass NetworkPolicy enforcement on co-located pods across different namespaces. This could lead to unauthorized access and manipulation of sensitive data within affected environments. Organizations utilizing Amazon EKS should prioritize upgrading to version 1.4.0 of the Network Policy Agent and version 1.22.4 of the VPC CNI Managed Add-on to mitigate the risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Improper validation of pod identifier uniqueness in aws-network-policy-agent in Amazon EKS Network Policy Agent before v1.4.0 might allow an authenticated remote user to bypass NetworkPolicy enforcement on co-located pods in other namespaces via crafted pod and namespace names that produce pod identifier collisions. To remediate this issue, users should upgrade to Amazon EKS Network Policy Agent 1.4.0 or later and Amazon VPC CNI Managed Add-on v1.22.4 or later (which includes Network Policy Agent v1.4.0).