CVE-2024-36265: Apache Submarine Server Core: authorization bypass
** UNSUPPORTED WHEN ASSIGNED ** Incorrect Authorization vulnerability in Apache Submarine Server Core.
This issue affects Apache Submarine Server Core: from 0.8.0.
An attacker can bypass authentication by sending specially crafted REST requests.
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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-36265 is a critical access-control flaw in Apache Submarine Server Core. An unauthenticated attacker may bypass authentication using specially crafted REST requests. The project is retired and Apache does not plan a fixed release. Any exposed instance should be treated as high urgency, especially if reachable from untrusted networks.
Executive priority
Prioritize removal or isolation. This is a critical unauthenticated server-side access-control issue in a retired project with no planned fix. Business risk is highest where Submarine is internet-facing or used in sensitive data and ML workflows.
Technical view
Apache describes an incorrect authorization vulnerability in Submarine Server Core affecting versions from 0.8.0. The issue is reachable over the network, requires no privileges or user interaction, and has CVSS 9.8 with high confidentiality, integrity, and availability impact. The advisory states attackers can bypass authentication via crafted REST requests.
Likely exposure
Exposure is limited to organizations still running Apache Submarine Server Core from 0.8.0, particularly where REST interfaces are reachable by untrusted users. The maintainer marks the project unsupported and retired.
Exploitation context
The provided sources do not show active exploitation, and this CVE is not marked KEV. However, the flaw is remotely reachable, unauthenticated, low complexity, and affects an unsupported product, making internet-facing instances especially risky.
Researcher notes
Evidence is limited to the CVE record and Apache advisory. No patch is named because the project is retired. Do not assume affected versions beyond the stated Apache Submarine Server Core from 0.8.0 without confirming deployment details.
Mitigation direction
Identify and retire Apache Submarine Server Core deployments where possible.
Migrate to an actively supported alternative recommended by your architecture team.
Restrict instance access to trusted users and trusted networks only.
Remove public internet exposure for Submarine REST interfaces.
Monitor Apache guidance in case additional retirement or migration advice appears.
Validation and detection
Inventory systems for Apache Submarine Server Core from version 0.8.0 onward.
Confirm whether any Submarine REST endpoints are reachable from untrusted networks.
Review access controls, network ACLs, and reverse proxy rules around Submarine instances.
Check dependency inventories for org.apache.submarine:submarine-server-core.
Document compensating controls because no vendor fix is planned.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.