dbcve.org
Hop EngineApplication · Apache

CVE-2024-24683

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 2.8.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Improper Input Validation vulnerability in Apache Hop Engine.This issue affects Apache Hop Engine: before 2.8.0. Users are recommended to upgrade to version 2.8.0, which fixes the issue. When Hop Server writes links to the PrepareExecutionPipelineServlet page one of the parameters provided to the user was not properly escaped. The variable not properly escaped is the "id", which is not directly accessible by users creating pipelines making the risk of exploiting this low. This issue only affects users using the Hop Server component and does not directly affect the client.

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

Improper input validation in Apache Hop Engine's PrepareExecutionPipelineServlet allows the 'id' parameter to be rendered without proper escaping in links, potentially leading to reflected content injection. The risk is limited because the 'id' variable is not directly accessible to users creating pipelines.

MitigationUpgrade Apache Hop Engine to version 2.8.0 or later, which includes proper escaping of the 'id' parameter in the Hop Server servlet.

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
Hop EngineApplication
Affected:< 2.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Apache Hop Engine version
    Locate the hop-core or hop-engine JAR file in the installation and check its version (typically found in the lib or plugins directory). Alternatively, check for a version file or run 'hop-version' from the command line if available.
    Affected if The installed version is earlier than 2.8.0
  2. Verify Hop Server is enabled
    Check if Hop Server is running or configured. Look for hop-server configuration files, check for running processes on typical web ports (8080, 8081), or examine the server's web.xml deployment descriptor.
    Affected if Hop Server web interface is active and accessible
  3. Confirm PrepareExecutionPipelineServlet is exposed
    Verify the PrepareExecutionPipelineServlet is loaded and available in the Hop Server web application context. This servlet handles pipeline execution preparation requests.
    Affected if The PrepareExecutionPipelineServlet is accessible via the web interface

A user is affected if they are running Apache Hop Engine version earlier than 2.8.0 with the Hop Server web interface enabled and the PrepareExecutionPipelineServlet exposed.

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 2.8.0 or later
Fixed in 2.8.0
Interim mitigation

Upgrade Apache Hop Engine to version 2.8.0 or later, which includes proper escaping of the 'id' parameter in the Hop Server servlet.

Recommended fix High confidence

Apache Hop Engine 2.8.0

  1. 1. Back up your current Apache Hop Engine installation including all custom configurations, pipelines, and workflows.
  2. 2. Download Apache Hop Engine version 2.8.0 from the official Apache download repository (https://hop.apache.org/download/).
  3. 3. Stop the running Hop Server instance if it is currently active.
  4. 4. Install or extract the version 2.8.0 files to replace the existing installation.
  5. 5. Restore any custom configuration files, environment settings, and custom plugins from the backup created in step 1.
  6. 6. Start the Hop Server component.
  7. 7. Verify that the server starts successfully and the PrepareExecutionPipelineServlet is functioning correctly.

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

Fix this in Hop Engine 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-24683 — 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-24683 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