dbcve.org
QueuemetricsApplication · Loway

CVE-2024-42341

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-08
Fix available
A fix is available. Upgrade to 24.05.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Loway - CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

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

This is an open redirect vulnerability (CWE-601) in a Loway product. The application accepts a user-controlled URL parameter and uses it to redirect the user without proper validation, allowing attackers to craft malicious URLs that redirect victims to untrusted external sites while appearing to originate from the vulnerable application.

MitigationImplement strict allowlist-based validation for redirect URLs, ensuring only trusted and relative paths are permitted. Alternatively, avoid using user-supplied input for redirect destinations entirely.

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
QueuemetricsApplication
Affected:>= 22.11.6, < 24.05.5

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed Queuemetrics version
    Locate the Queuemetrics version file or check the application header/admin interface for the version number. This is typically displayed on the login page or in the administration panel.
    Affected if The installed version is 22.11.6 or higher but lower than 24.05.5
  2. Confirm application is Queuemetrics
    Verify the running application is indeed Loway Queuemetrics by checking the product name in the web interface or application files.
    Affected if The product is Loway Queuemetrics and the version falls within the affected range
  3. Identify redirect-capable endpoints
    Review application logs or capture network traffic while navigating the application to identify any redirects occurring based on URL parameters.
    Affected if The application performs redirects using user-supplied URL parameters without proper validation
  4. Test redirect parameter behavior
    If a redirect parameter is found, observe whether supplying an external URL (such as http://example.com) as the parameter value results in a redirect to that external site.
    Affected if The application redirects to arbitrary URLs provided in the request without validating they are internal or allowlisted

You are affected if running Queuemetrics version 22.11.6 or higher but lower than 24.05.5, and the application uses unsanitized URL parameters for redirect destinations.

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

Implement strict allowlist-based validation for redirect URLs, ensuring only trusted and relative paths are permitted. Alternatively, avoid using user-supplied input for redirect destinations entirely.

Recommended fix Moderate confidence

24.05.5

  1. Verify current Queuemetrics installation version using system administration interface or command line
  2. Review Queuemetrics upgrade documentation for your deployment method
  3. Create complete backup of Queuemetrics database and configuration files
  4. Schedule maintenance window as upgrade may require brief downtime
  5. Download Queuemetrics version 24.05.5 or later from official Loway distribution channels
  6. Execute upgrade procedure following Loway's upgrade instructions for your specific deployment
  7. After upgrade, verify the application starts successfully
  8. Test that the open redirect vulnerability is no longer exploitable by attempting URL manipulation
Caveat Review Loway release notes for 24.05.5 to check for any configuration or feature changes that may affect your deployment

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

Fix this in Queuemetrics Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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