dbcve.org
SubmarineApplication · Apache

CVE-2024-36265

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
** 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Submarine Server Core contains an incorrect authorization vulnerability allowing attackers to bypass authentication by sending specially crafted REST requests. This enables unauthenticated access to the server's functionality, potentially leading to full system compromise.

MitigationSince Apache Submarine is retired with no planned fix, organizations should either migrate to an alternative solution or implement strict network access controls to limit exposure to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SubmarineApplication
Affected:>= 0.8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Apache Submarine is installed
    Search for submarine-related processes, services, or directories on the system. Look for 'submarine' in running processes or installed applications.
    Affected if Apache Submarine server process or installation is found on the system
  2. Determine the installed version
    Check the version of Apache Submarine by examining its version file, pom.xml, or by querying the server's API endpoint if accessible. Compare the version number to the affected range of >= 0.8.0.
    Affected if The installed version is 0.8.0 or higher
  3. Verify network exposure of the Submarine server
    Check if the Submarine server port (default 8080 or configured port) is listening on a network interface accessible from untrusted networks. Use netstat or similar tools to identify binding addresses.
    Affected if The server is bound to a publicly accessible IP or an untrusted network segment
  4. Test for authentication bypass
    Send a crafted REST request to the Submarine server without providing authentication credentials. Observe if the request succeeds in accessing protected endpoints.
    Affected if The server accepts and processes REST requests without requiring authentication
  5. Review server configuration for security controls
    Examine the Submarine server configuration files (typically in conf/ or config/ directories) to identify if any authentication or authorization mechanisms are properly configured and enforced.
    Affected if Authentication is not properly enforced or is missing from the configuration

The environment is affected if Apache Submarine version 0.8.0 or higher is running and is accessible to untrusted users without proper authentication enforcement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since Apache Submarine is retired with no planned fix, organizations should either migrate to an alternative solution or implement strict network access controls to limit exposure to trusted users only.

Recommended fix High confidence
  1. Since Apache Submarine is retired with no planned patch, the recommended remediation is to restrict network access to the Submarine Server instance
  2. Limit access to the Submarine Server to only trusted users and networks via firewall rules or network segmentation
  3. If the Submarine Server is exposed publicly, immediately block or remove public access
  4. Evaluate migrating to an alternative solution for submarine workflow management as the project is no longer maintained
  5. If Submarine must remain in use, implement additional authentication layers such as VPN access or reverse proxy with authentication in front of the service
Caveat No upgrade path available - Apache Submarine is retired and unsupported

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Submarine Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36265 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36265 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data