GHSA-rjfv-pjvx-mjgv: Sigs.k8s.io/aws load balancer controller AWS Load Balancer Controller Automatically Vulnerability

LOW
Published
Advisory Summary

GHSA-rjfv-pjvx-mjgv is a LOW aws load balancer controller automatically vulnerability (General Security Weakness) affecting Sigs.k8s.io/aws load balancer controller libraries in the Go ecosystem. The issue involves aws load balancer controller automatically detaches externally associated web acl from application load balancers. Remediation is available by upgrading affected packages to version 2.8.2.

GHSA-rjfv-pjvx-mjgv at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-rjfv-pjvx-mjgv
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Sigs.k8s.io/aws load balancer controller
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-rjfv-pjvx-mjgv

To remediate this vulnerability, upgrade all affected Sigs.k8s.io/aws load balancer controller dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

sigs.k8s.io/aws-load-balancer-controller fixed: 2.8.2
Upgrade sigs.k8s.io/aws-load-balancer-controller to 2.8.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for sigs.k8s.io/aws-load-balancer-controller

How to Check if You Are Affected

To determine whether your application is affected by GHSA-rjfv-pjvx-mjgv, inspect your project dependencies for Sigs.k8s.io/aws load balancer controller:

inspect dependencies for sigs.k8s.io/aws-load-balancer-controller

Analyze the terminal output to locate any version of Sigs.k8s.io/aws load balancer controller in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.8.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Sigs.k8s.io/aws load balancer controller, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary  The AWS Load Balancer Controller includes an optional, default-enabled feature that manages WAF WebACLs on Application Load Balancers (ALBs) on your behalf. In versions 2.8.1 and earlier, if the WebACL annotation [1] [alb.ingress.kubernetes.io/wafv2-acl-arn](http://alb.ingress.kubernetes.io/wafv2-acl-arn) or [alb.ingress.kubernetes.io/waf-acl-id](http://alb.ingress.kubernetes.io/waf-acl-id) was absent on Ingresses, the controller would automatically disassociate any existing WebACL from the ALBs, including those associated by AWS Firewall Manager (FMS). Customers on impacted versions should upgrade to prevent this issue from occurring. ### Impact  WebACLs attached to ALBs managed by the AWS Load Balancer Controller through methods other than Ingress annotations may be automatically removed, leaving the ALBs unprotected by WebACL.  Impacted versions: [>=2.0.0;<2.8.2]  ### Patches  We addressed this issue in version 2.8.2 [2] and recommend customers upgrade. Now, if the WebACL annotation is absent on Ingress objects, any existing WebACL on the ALB will remain intact instead of being removed.  ### Workarounds  If the previous behavior affected you, you can mitigate it by disabling the WebACL management feature using the --enable-waf and --enable-wafv2 command-line flags [3]  ### References  If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [4] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.  [1] https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/ingress/annotations/#addons  [2] https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/tag/v2.8.2  [3] https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/deploy/configurations/#waf-addons  [4] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting

GHSA-rjfv-pjvx-mjgv Affected Sigs.k8s.io/aws load balancer controller Versions

1 component(s)
Fixed Versions:
2.8.2
Product / Package Ecosystem Affected Versions Fixed Version
sigs.k8s.io/aws-load-balancer-controller
Go
≥ 2.0.0
< 2.8.2
2.8.2

References

Frequently Asked Questions

What is GHSA-rjfv-pjvx-mjgv?
GHSA-rjfv-pjvx-mjgv is a security vulnerability in Sigs.k8s.io/aws load balancer controller involving AWS Load Balancer Controller automatically detaches externally associated web ACL from Application Load Balancers under General Security Weakness.
Which Sigs.k8s.io/aws load balancer controller versions are affected?
Affected versions include releases prior to 2.8.2 across affected packages: sigs.k8s.io/aws-load-balancer-controller.
What version fixes GHSA-rjfv-pjvx-mjgv?
Upgrading to 2.8.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is sigs.k8s.io/aws-load-balancer-controller affected?
Yes, sigs.k8s.io/aws-load-balancer-controller is affected in releases prior to 2.8.2. Upgrade your dependency to 2.8.2 or later.
What CWE is associated with GHSA-rjfv-pjvx-mjgv?
GHSA-rjfv-pjvx-mjgv is classified under General Security Weakness.
How can I check Go dependencies for GHSA-rjfv-pjvx-mjgv?
Run the dependency tree command: 'inspect dependencies for sigs.k8s.io/aws-load-balancer-controller'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rjfv-pjvx-mjgv",
  "modified" : "2024-10-24T19:04:45Z",
  "published" : "2024-10-24T19:04:45Z",
  "aliases" : [ ],
  "summary" : "AWS Load Balancer Controller automatically detaches externally associated web ACL from Application Load Balancers",
  "details" : "### Summary \n\nThe AWS Load Balancer Controller includes an optional, default-enabled feature that manages WAF WebACLs on Application Load Balancers (ALBs) on your behalf. In versions 2.8.1 and earlier, if the WebACL annotation [1] [alb.ingress.kubernetes.io/wafv2-acl-arn](http://alb.ingress.kubernetes.io/wafv2-acl-arn) or [alb.ingress.kubernetes.io/waf-acl-id](http://alb.ingress.kubernetes.io/waf-acl-id) was absent on Ingresses, the controller would automatically disassociate any existing WebACL from the ALBs, including those associated by AWS Firewall Manager (FMS). Customers on impacted versions should upgrade to prevent this issue from occurring. \n\n### Impact \n\nWebACLs attached to ALBs managed by the AWS Load Balancer Controller through methods other than Ingress annotations may be automatically removed, leaving the ALBs unprotected by WebACL. \n\nImpacted versions: [>=2.0.0;<2.8.2] \n\n### Patches \n\nWe addressed this issue in version 2.8.2 [2] and recommend customers upgrade. Now, if the WebACL annotation is absent on Ingress objects, any existing WebACL on the ALB will remain intact instead of being removed. \n\n### Workarounds \n\nIf the previous behavior affected you, you can mitigate it by disabling the WebACL management feature using the --enable-waf and --enable-wafv2 command-line flags [3] \n\n### References \n\nIf you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [4] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue. \n\n[1] https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/ingress/annotations/#addons \n\n[2] https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/tag/v2.8.2 \n\n[3] https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/deploy/configurations/#waf-addons \n\n[4] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "sigs.k8s.io/aws-load-balancer-controller"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.8.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/kubernetes-sigs/aws-load-balancer-controller/security/advisories/GHSA-rjfv-pjvx-mjgv"
  }, {
    "type" : "WEB",
    "url" : "https://aws.amazon.com/security/vulnerability-reporting"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/kubernetes-sigs/aws-load-balancer-controller"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/tag/v2.8.2%C2%A0"
  }, {
    "type" : "WEB",
    "url" : "https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/deploy/configurations/#waf-addons"
  }, {
    "type" : "WEB",
    "url" : "https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/ingress/annotations/#addons"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-10-24T19:04:45Z",
    "nvd_published_at" : null
  }
}