Open Coverage Agent (OPA) lately patched a essential vulnerability that might have uncovered NTLM credentials of the OPA server’s native person account to distant attackers, which was current in each the OPA CLI and Go SDK.
By exploiting this flaw, attackers might have compromised the OPA server’s authentication mechanisms and probably gained unauthorized entry to delicate sources.
The repair for this vulnerability is offered within the newest launch of OPA.
A essential vulnerability (CVE-2024-8260) was found in Open Coverage Agent (OPA) for Home windows. It permits attackers to use file-related arguments within the OPA CLI or Go bundle to inject arbitrary UNC shares.
By doing so, attackers might steal the native person’s NTLM credentials, probably resulting in unauthorized entry and password cracking. This subject affected all current variations previous to v0.68.0, and a patch has been launched to handle the difficulty.
Defending Your Networks & Endpoints With UnderDefense MDR – Request Free Demo
Open Coverage Agent (OPA) is a flexible coverage engine used for admission management in Kubernetes, amongst different purposes, and employs a declarative coverage language known as Rego.
Whereas OPA presents an open-source model, it additionally has an Enterprise version for high-performance situations. On this version, insurance policies will be fetched from varied sources or handed on to OPA.
A possible vulnerability exists in the way in which insurance policies are handed as arguments to OPA’s CLI or SDK capabilities. This might result in unintended coverage execution or the publicity of delicate data.


Researchers found a vulnerability (CVE-2024-8260) in OPA for Home windows that enables attackers to steal person credentials. The vulnerability exists attributable to improper enter validation in OPA CLI and Go library capabilities.
By offering a UNC path (pointing to a malicious server) as an alternative of a coverage file, they tricked OPA into initiating NTLM authentication with the attacker’s server, revealing the person’s NTLM hash.
In accordance with Tenable, this system labored with varied OPA CLI instructions, together with `eval`, `run`, and `eval -d`, because the vulnerability impacts each Free and Enterprise editions of OPA.


The OPA Go SDK earlier than model 0.68.0 contained vulnerabilities that could possibly be exploited to set off unauthorized community entry.
These vulnerabilities have been attributable to inadequate sanitization of enter paths in capabilities like `rego.LoadBundle` and `AsBundle` throughout the `loader.go` bundle.
By offering a Common Naming Conference (UNC) path, an attacker might drive the SDK to aim to load a bundle from a distant share, probably resulting in unauthorized information entry or execution of malicious code.
Model 0.68.0 resolved the difficulty by including checks to forestall using UNC paths in these capabilities.


A vulnerability (CVE-2024-8260) in OPA for Home windows earlier than v0.68.0 permits attackers to leak native person credentials by the OPA CLI and Go SDK.
These are within the `github.com/open-policy-agent/opa/loader` bundle (all variations earlier than v0.68.0) and deal with coverage and bundle file loading.
To repair this, replace the OPA CLI and Go SDK to the newest model (v0.68.0 or later). This highlights the significance of safety collaboration with engineering groups to determine and mitigate vulnerabilities in broadly used open-source tasks.
Run personal, Actual-time Malware Evaluation in each Home windows & Linux VMs. Get a 14-day free trial with ANY.RUN!