# CVE-2023-1065: Auth bypass in Snyk Kubernetes Monitor

> Unauthenticated attackers can post irrelevant data to Snyk organizations if they know the Integration ID, potentially obscuring real security issues.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2023
- **Updated:** 7 Mar 2025
- **Also known as:** GHSA-8mxq-fgcq-vh7j

## What is CVE-2023-1065?

CVE-2023-1065 is a medium-severity authentication bypass vulnerability in Snyk Kubernetes Monitor, published on 28 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability in the Snyk Kubernetes Monitor can result in irrelevant data being posted to a Snyk Organization, which could in turn obfuscate other, relevant, security issues. It does not expose the user of the integration to any direct security risk and no user data can be leaked. To exploit the vulnerability the attacker does not need to be authenticated to Snyk but does need to know the target's Integration ID (which may or may not be the same as the Organization ID, although this is an unpredictable UUID in either case).

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-1065?

It affects 1 product.


Products: Snyk Kubernetes Monitor.

## How do I fix CVE-2023-1065?

No fix has been published for CVE-2023-1065 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-1065 being exploited?

There is no known exploitation of CVE-2023-1065 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-1065 and fix it if it is affected.

What it is: CVE-2023-1065 is a medium-severity authentication bypass vulnerability in Snyk Kubernetes Monitor, published on 28 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-1065 in the wild and no public exploit code.

Affected product: Snyk Kubernetes Monitor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-1065/ (Markdown: https://insights.sbomify.com/CVE-2023-1065/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-1065
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-1065
- OSV: https://osv.dev/vulnerability/CVE-2023-1065

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-1065/
Summaries are generated and may contain mistakes; the official description above is the record.