# CVE-2024-36264: Apache Submarine Commons Utils: default secret

> Attackers can bypass authentication in Apache Submarine Commons Utils due to a default secret, requiring users to restrict access as the project is retired.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2024
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-jwcg-wv5x-vg3g, PYSEC-2024-97

## What is CVE-2024-36264?

CVE-2024-36264 is a critical vulnerability in Apache Submarine Commons Utils, published on 12 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

** UNSUPPORTED WHEN ASSIGNED ** Improper Authentication vulnerability in Apache Submarine Commons Utils.

If the user doesn't explicitly set `submarine.auth.default.secret`, a default value will be used.

This issue affects Apache Submarine Commons Utils: from 0.8.0.

As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users.

NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-36264?

5 open source packages ship an affected version, including org.apache.submarine:submarine-commons-utils and apache-submarine. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.submarine:submarine-commons-utils` | Maven | All versions to 0.8.0 | None |
| `org.apache.submarine:submarine-commons-utils` | Maven | All versions to 0.8.0 | None |
| `apache-submarine` | PyPI | From 0.8.0 | None |
| `apache-submarine` | PyPI | From 0.8.0 | None |
| `apache-submarine` | PyPI | From 0.8.0 | None |

Products: Apache Submarine.

## How do I fix CVE-2024-36264?

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

## Is CVE-2024-36264 being exploited?

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

## Other vulnerabilities in Apache Submarine Commons Utils

- [CVE-2024-36265](https://insights.sbomify.com/CVE-2024-36265/): Apache Submarine Server Core: authorization bypass (critical 9.8)
- [CVE-2023-37924](https://insights.sbomify.com/CVE-2023-37924/): Apache Submarine: SQL injection from unauthorized login (critical 9.8)
- [CVE-2023-46302](https://insights.sbomify.com/CVE-2023-46302/): Apache Submarine: Fix CVE-2022-1471 SnakeYaml unsafe deserialization (critical 9.8)
- [CVE-2024-36263](https://insights.sbomify.com/CVE-2024-36263/): Apache Submarine Server Core: SQL injection (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36264 and fix it if it is affected.

What it is: CVE-2024-36264 is a critical vulnerability in Apache Submarine Commons Utils, published on 12 Jun 2024. 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-2024-36264 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.submarine:submarine-commons-utils (Maven): affected all versions up to 0.8.0; no fix listed
- org.apache.submarine:submarine-commons-utils (Maven): affected all versions up to 0.8.0; no fix listed
- apache-submarine (PyPI): affected from 0.8.0; no fix listed
- apache-submarine (PyPI): affected from 0.8.0; no fix listed
- apache-submarine (PyPI): affected from 0.8.0; no fix listed

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-2024-36264/ (Markdown: https://insights.sbomify.com/CVE-2024-36264/index.md)
```

## Sources

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

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