dbcve.org
Hugegraph HubbleApplication · Apache

CVE-2024-27347

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-22
Fix available
A fix is available. Upgrade to 1.3.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Server-Side Request Forgery (SSRF) vulnerability in Apache HugeGraph-Hubble.This issue affects Apache HugeGraph-Hubble: from 1.0.0 before 1.3.0. Users are recommended to upgrade to version 1.3.0, 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

Server-Side Request Forgery (SSRF) vulnerability in Apache HugeGraph-Hubble allows attackers to induce the server to make arbitrary HTTP requests to internal or external resources, potentially exposing internal services, bypassing firewalls, or enabling further attacks.

MitigationUpgrade Apache HugeGraph-Hubble to version 1.3.0 or later, which contains the fix for this SSRF 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
Hugegraph HubbleApplication
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
Low
Integrity
None
Availability
None

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

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. Confirm HugeGraph-Hubble installation
    Identify if Apache HugeGraph-Hubble is installed on the system by checking for its process, service, or installation directory. Common locations include /opt/hugegraph-hubble, /usr/local/hugegraph-hubble, or check running Java processes for hugegraph-hubble.
    Affected if HugeGraph-Hubble is present on the system
  2. Determine installed version
    Check the version of Apache HugeGraph-Hubble by examining the version file in the installation directory, the build metadata, or by querying the application if it exposes version information via API endpoint.
    Affected if Installed version is 1.0.0 or higher but lower than 1.3.0
  3. Identify exposed API endpoints
    Review the application's API endpoints, particularly those that accept URL or URI parameters, as SSRF vulnerabilities typically exploit endpoints that make server-side HTTP requests.
    Affected if API endpoints accepting URL parameters are accessible without proper validation controls
  4. Check network exposure
    Determine if the HugeGraph-Hubble service is accessible from untrusted networks by reviewing firewall rules, reverse proxy configuration, and binding addresses in the service configuration.
    Affected if Service is bound to non-localhost interfaces and accessible from external or untrusted networks
  5. Review request handling configuration
    Inspect the application's configuration files for settings related to request validation, URL allowlists, or SSRF protections, particularly in any proxy or HTTP client configuration.
    Affected if No URL validation or allowlist controls are configured for outbound requests

The environment is affected if Apache HugeGraph-Hubble version 1.0.0 through 1.2.x is installed and accessible, with exposed API endpoints that handle URL parameters without proper validation.

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-Hubble to version 1.3.0 or later, which contains the fix for this SSRF vulnerability.

Recommended fix High confidence

1.3.0

  1. 1. Backup your current HugeGraph Hubble installation, configuration files, and any existing data.
  2. 2. Download Apache HugeGraph-Hubble version 1.3.0 from the official Apache repository (downloads.apache.org) or official distribution channels.
  3. 3. Stop the currently running HugeGraph Hubble service.
  4. 4. Replace the existing installation with the new version 1.3.0 files.
  5. 5. Restore your configuration files from the backup (or reconfigure as needed for 1.3.0).
  6. 6. Start the HugeGraph Hubble service.
  7. 7. Verify the service is running correctly and the SSRF vulnerability is remediated.

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

Fix this in Hugegraph Hubble Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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