dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 9 Oct 2024.
HugegraphApplication · Apache

CVE-2024-27348

CRITICAL · 9.8 CVSS v3.1 Published 2024-04-22
Fix available
A fix is available. Upgrade to 1.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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
RCE-Remote Command Execution vulnerability in Apache HugeGraph-Server.This issue affects Apache HugeGraph-Server: from 1.0.0 before 1.3.0 in Java8 & Java11 Users are recommended to upgrade to version 1.3.0 with Java11 & enable the Auth system, which fixes the issue.

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

Critical RCE vulnerability in Apache HugeGraph-Server allows remote attackers to execute arbitrary commands on the server. The flaw affects versions 1.0.0 through versions prior to 1.3.0 when running on Java8 or Java11. The vulnerability has a CVSS score of 9.8, indicating severe impact potential.

MitigationUpgrade Apache HugeGraph-Server to version 1.3.0 or later, migrate to Java 11, and enable the Auth system to remediate this vulnerability.

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
HugegraphApplication
Affected:>= 1.0.0, < 1.3.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 HugeGraph-Server is installed
    Look for the HugeGraph installation directory, typically under /opt/hugegraph or /usr/local/hugegraph, or check for the hugegraph-server process running: ps aux | grep hugegraph
    Affected if HugeGraph-Server process is running or installation directory exists
  2. Determine the installed HugeGraph-Server version
    Check the version file or startup logs. Common locations: <hugegraph-dir>/hugegraph-core-x.x.x.jar in the lib folder, or grep for version in release notes or pom.xml if source is present
    Affected if Version is 1.0.0 through 1.2.0 (any version >= 1.0.0 and < 1.3.0)
  3. Verify the Java version in use by the HugeGraph process
    Find the Java process: ps aux | grep hugegraph, then check the JAVA_HOME or run: java -version from the Java binary used by HugeGraph
    Affected if Java 8 or Java 11 is in use (Java 17+ is not affected)
  4. Confirm the Gremlinremlin gremlin] gremlin-server endpoint is exposed
    Check hugegraph.properties or hugegraph.conf for gremlin server configuration, typically port 8080, and verify it is accessible over network
    Affected if Gremlin Server port is bindable to non-localhost interfaces (0.0.0.0)
  5. Check if authentication is enabled
    Inspect hugegraph.properties for: auth.authenticator=org.apache.hugegraph.auth.StandardAuthenticator or similar authenticator configuration
    Affected if Auth system is disabled or not configured (auth.authenticator is set to null or not present)

User is affected if HugeGraph-Server version is 1.0.0-1.2.0, running on Java 8 or Java 11, with the Gremlin endpoint exposed and authentication disabled

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
Upgrade available Upgrade to 1.3.0 or later
Fixed in 1.3.0
Interim mitigation

Upgrade Apache HugeGraph-Server to version 1.3.0 or later, migrate to Java 11, and enable the Auth system to remediate this vulnerability.

Recommended fix High confidence

1.3.0

  1. 1. Stop the currently running Apache HugeGraph-Server instance
  2. 2. Ensure Java 11 is installed on the system (Java 8 is also vulnerable)
  3. 3. Download Apache HugeGraph-Server version 1.3.0 from the official Apache repository
  4. 4. Upgrade the HugeGraph-Server installation to version 1.3.0 following the standard upgrade procedure
  5. 5. Configure and enable the Auth system for authentication and authorization
  6. 6. Verify the upgrade was successful and the Auth system is functioning
  7. 7. Restart the HugeGraph-Server service
Caveat Upgrading from Java 8 to Java 11 may introduce compatibility issues with custom code or plugins; enabling Auth system changes authentication behavior

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

Fix this in Hugegraph Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27348 — 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-27348 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