Skip to content
Fencer Intel
medium 6.7

GHSA-pv22-fqcj-7xwh json

Inspektor Gadget Security Policies Can be Bypassed

published last yr. modified 8mo ago also GO-2025-3665

cvss
6.7
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Security policies like [`allowed-gadgets`](https://inspektor-gadget.io/docs/latest/reference/restricting-gadgets), [`disallow-pulling`](https://inspektor-gadget.io/docs/latest/reference/disallow-pulling), [`verify-image`](https://inspektor-gadget.io/docs/latest/reference/verify-assets#verify-image-based-gadgets) can be bypassed by a malicious client.

### Impact

Users running `ig` in daemon mode or IG on Kubernetes that rely on any of the features mentioned above are vulnerable to this issue. In order to exploit this, the client needs access to the server, like the correct TLS certificates on the `ig daemon` case or access to the cluster in the Kubernetes case.

### Patches

The issue has been fixed in v0.40.0

### Workarounds

There is not known workaround to fix it.

Patch / fix

  • go github.com/inspektor-gadget/inspektor-gadget 0.40.0

Is GHSA-pv22-fqcj-7xwh in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 6.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:H

Affected packages

ecosystem package affected fixed in
go github.com/inspektor-gadget/inspektor-gadget
>=0.31.0, <0.40.0
0.40.0

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.