dbcve.org
Admin By RequestApplication · Fasttracksoftware

CVE-2019-17202

HIGH · 7.8 CVSS v3.1 Published 2020-01-23
Fix available
A fix is available. Upgrade to 6.2.0.0 or later.
See remediation →
80/100
Remediation priority · High
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
FastTrack Admin By Request 6.1.0.0 supports group policies that are supposed to allow only a select range of users to elevate to Administrator privilege at will. If a user does not have direct access to the elevation feature through group policies, they are prompted to enter a PIN code in a challenge-response manner upon attempting to elevate privileges. The challenge's response uses a simple algorithm that can be easily emulated via data (customer ID and device name) available to all users, and thus any user can elevate to Administrator privilege.

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

FastTrack Admin By Request 6.1.0.0 has a privilege escalation vulnerability where the challenge-response PIN authentication mechanism uses a weak, reversible algorithm. The challenge parameters (customer ID and device name) are available to all users, allowing any user to compute the correct response and bypass group policy restrictions to gain Administrator privileges.

MitigationImplement a cryptographically secure authentication mechanism (e.g., TPM-backed authorization, secure token server, or properly salted hash verification) to replace the flawed challenge-response algorithm. Enforce strict group policy enforcement independent of client-side PIN verification.

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
Admin By RequestApplication
Affected:< 6.2.0.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 version of Admin By Request
    Check the installed version through Windows Add/Remove Programs, or query the application executable for its version property (right-click the Admin By Request executable, select Properties, view the Details tab for Version information). Compare the version number to the affected range: versions below 6.2.0.0 are vulnerable.
    Affected if The installed version is below 6.2.0.0 (e.g., 6.1.0.0 or any 6.x.x version prior to 6.2.0.0).
  2. Verify PIN-based challenge-response authentication is in use
    Examine the Admin By Request configuration settings or policy files to confirm whether PIN/challenge-response authentication is enabled as an authentication method. Look for configuration options related to PIN verification or challenge-response within the application settings or associated policy files.
    Affected if PIN/challenge-response authentication is enabled as a primary or secondary verification method.
  3. Confirm user access to challenge parameters
    Determine whether standard (non-Administrator) users can access the customer ID and device name values used in the challenge-response algorithm. This may be observable through application logs, configuration files readable by all users, or the application interface when viewed from a standard user account.
    Affected if Standard users can view or retrieve the customer ID and device name (challenge parameters) without elevated privileges.
  4. Review group policy enforcement configuration
    Check the group policy settings applied to Admin By Request to determine whether privilege elevation is reliant on client-side PIN verification for Administrator access, or whether enforcement is handled server-side independent of the PIN mechanism.
    Affected if Group policy enforcement for Administrator privileges depends on or relies upon the client-side PIN verification.

A user is affected if the installed Admin By Request version is below 6.2.0.0 AND PIN-based challenge-response authentication is enabled, allowing standard users to compute valid responses from accessible challenge parameters and bypass group policy to gain Administrator privileges.

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
Upgrade available Upgrade to 6.2.0.0 or later
Fixed in 6.2.0.0
Interim mitigation

Implement a cryptographically secure authentication mechanism (e.g., TPM-backed authorization, secure token server, or properly salted hash verification) to replace the flawed challenge-response algorithm. Enforce strict group policy enforcement independent of client-side PIN verification.

Fix this in Admin By Request Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,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 $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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