dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2019-17082

CRITICAL · 9.0 CVSS v4.0 Published 2024-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
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
Insufficiently Protected Credentials vulnerability in OpenText™ AccuRev allows Authentication Bypass. When installed on a Linux or Solaris system the vulnerability could allow anyone who knows a valid AccuRev username can use the AccuRev client to login and gain access to AccuRev source control without knowing the user’s password. This issue affects AccuRev: 2017.1.

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

A critical authentication bypass vulnerability in AccuRev 2017.1 on Linux/Solaris allows attackers with knowledge of any valid username to authenticate without the corresponding password, effectively bypassing the entire authentication mechanism for the source control system.

MitigationUpgrade from AccuRev 2017.1 to a patched version; until then, implement compensating controls such as network segmentation, strict access controls, and monitoring for unauthorized access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
None
Authentication
None
User interaction
P
Scope
P

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:N/R:I/V:C/RE:M/U:Red

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. Verify AccuRev installation exists
    Look for AccuRev installation directory (common paths: /opt/AccuRev, /usr/local/accurev, or check for 'accurev' executable via 'which accurev' or 'find / -name accurev 2>/dev/null')
    Affected if AccuRev is not found on the system - not applicable
  2. Determine installed AccuRev version
    Run 'accurev --version' or check version file in installation directory (often version.txt, RELEASE_NOTES, or similar)
    Affected if Version is 2017.1 exactly (confirms affected release)
  3. Confirm operating system is Linux or Solaris
    Run 'uname -s' or check /etc/os-release for OS type
    Affected if OS is Linux or Solaris (vulnerable platform); not affected if Windows
  4. Check if AccuRev server is running and network accessible
    Run 'ps aux | grep accurev' to check if server process is active, and check open ports (e.g., 'netstat -tlnp | grep -E "5050|5051|5052"' which are common AccuRev ports)
    Affected if Server is running and accessible on network - increases exposure
  5. Inspect authentication configuration
    Check AccuRev server configuration files (typically in install_dir/server/config/ or similar) for auth settings, or review server logs for failed authentication patterns
    Affected if Authentication is handled by the vulnerable AccuRev mechanism (not externalized to LDAP/AD)

System is affected if AccuRev 2017.1 is installed on Linux or Solaris with the native authentication mechanism enabled and the server is accessible.

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 from AccuRev 2017.1 to a patched version; until then, implement compensating controls such as network segmentation, strict access controls, and monitoring for unauthorized access attempts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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