RaquestApplication · Halvotec

CVE-2019-19613

MEDIUM · 5.2 CVSS v3.1 Published 2020-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
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
An issue was discovered in Halvotec RaQuest 10.23.10801.0. The login page of the admin application is vulnerable to an Open Redirect attack allowing an attacker to redirect a user to a malicious site after authentication. The attacker needs to be on the same network to modify the victim's request on the wire. Fixed in Release 24.2020.20608.0

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

The admin login page of Halvotec RaQuest version 10.23.10801.0 contains an open redirect vulnerability. An attacker positioned on the same network (man-in-the-middle) can modify the victim's request to inject a malicious URL as a redirect parameter, causing the user to be redirected to an external malicious site after successful authentication.

MitigationUpgrade to Halvotec RaQuest Release 24.2020.20608.0 or later which contains the fix for 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
RaquestApplication
Affected:= 10.23.10801.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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:A/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 Halvotec RaQuest version
    Locate the RaQuest installation directory and check the version information, typically found in the application executable properties, about dialog, or installation logs. Use the software's built-in version check if available.
    Affected if The installed version is exactly 10.23.10801.0
  2. Locate the admin login page URL
    Determine the base URL for the RaQuest web interface (typically http://hostname/raquest or similar). Navigate to the admin login endpoint, commonly at /admin/login, /login, or the default application root.
    Affected if The admin login page is accessible over HTTP/HTTPS
  3. Inspect login page for redirect parameter
    Examine the HTML source code of the login page or capture the HTTP response using browser developer tools or a proxy. Look for a redirect, returnUrl, url, next, or destination parameter in the form action or in hidden fields.
    Affected if A redirect parameter is present in the login page
  4. Test redirect parameter for open redirect behavior
    Modify the suspected redirect parameter value to an external domain (e.g., redirect=example.com). Submit the login form or reload the URL with the modified parameter and observe if the browser redirects to the specified external URL after authentication.
    Affected if The redirect parameter accepts and follows arbitrary URLs to external domains

You are affected if Halvotec RaQuest version 10.23.10801.0 is installed and the admin login page contains a redirect parameter that can be manipulated to send users to external websites.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Halvotec RaQuest Release 24.2020.20608.0 or later which contains the fix for this vulnerability.

Fix this in Raquest Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-19613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2019-19613 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