dbcve.org
HamaApplication · Apache

CVE-2022-45470

HIGH · 7.5 CVSS v3.1 Published 2022-11-21
Fix available
A fix is available. Upgrade to after 1.7.1 or later.
See remediation →
84/100
Remediation priority · High
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
missing input validation in Apache Hama may cause information disclosure through path traversal and XSS. Since Apache Hama is EOL, we do not expect these issues to be fixed.

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 · moderate confidence

Apache Hama contains missing input validation vulnerabilities that allow path traversal (leading to unauthorized file system access and information disclosure) and Cross-Site Scripting (XSS) attacks. These issues stem from insufficient sanitization of user-supplied input.

MitigationSince Apache Hama is End-of-Life with no vendor fixes expected, organizations should discontinue use if possible. If continued operation is required, implement compensating controls such as web application firewalls, strict input filtering at upstream proxies, network segmentation, and disable unnecessary interfaces.

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
HamaApplication
Affected:<= 1.7.1

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Identify if Apache Hama is installed
    Check for Apache Hama processes running (ps aux | grep hama) or look for Hama installation directories (commonly in /opt, /usr/lib, or user home directories). Search for files named 'hama-*' or directories containing 'hama'.
    Affected if Apache Hama software is present on the system
  2. Determine the installed version of Apache Hama
    Locate the version file or check the Hama version command output. Common locations include VERSION files in the installation directory, or run 'bin/hama version' if the binary is available. Look for version strings in JAR manifest files under the lib directory.
    Affected if The version is 1.7.1 or lower (any version <= 1.7.1)
  3. Check if the Hama web interface is enabled and accessible
    Apache Hama provides a web UI. Check configuration files (hama-site.xml) for web interface settings. Look for properties like 'hama.webui.enabled' or port configurations (default web UI typically runs on port 8088 or 8090). Attempt to access the web interface via HTTP/HTTPS if exposed.
    Affected if The Hama web interface is enabled and network-accessible (this is the attack surface for both path traversal and XSS)
  4. Inspect web interface for path traversal exposure
    If the web interface is accessible, test whether URL parameters handling file paths are vulnerable. Look for endpoints that accept file or path parameters. Review the underlying servlet or handler code for lack of input validation on path-related parameters.
    Affected if The web interface processes user-supplied paths without sanitization, allowing characters like '../' to traverse directories

You are affected if Apache Hama version 1.7.1 or lower is installed and its web interface is enabled and accessible, allowing unauthenticated users to supply unsanitized input via URL parameters.

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 a release after 1.7.1
Interim mitigation

Since Apache Hama is End-of-Life with no vendor fixes expected, organizations should discontinue use if possible. If continued operation is required, implement compensating controls such as web application firewalls, strict input filtering at upstream proxies, network segmentation, and disable unnecessary interfaces.

Recommended fix High confidence
  1. Accept the risk: Apache Hama is End-of-Life (EOL) and will not receive official security patches
  2. Implement defensive controls: Deploy a WAF (Web Application Firewall) or reverse proxy with path traversal and XSS filtering rules
  3. Restrict network access: Limit exposure to only trusted networks or IP ranges using firewall rules or iptables
  4. Disable unused components: If the web UI or specific endpoints are not required, disable or remove them
  5. Monitor for exploitation: Enable logging and alerting for suspicious path traversal patterns (e.g., '../', '..\') and XSS payloads in HTTP requests
  6. Consider migration: Evaluate moving to an actively maintained alternative such as Apache Hadoop or Apache Spark for graph/cluster computing needs
Caveat No upgrade path available - Apache Hama is EOL with no successor version

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

Fix this in Hama Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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