dbcve.org
Authentication Agent For WebApplication · Rsa

CVE-2017-14377

CRITICAL · 9.8 CVSS v3.0 Published 2017-11-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
EMC RSA Authentication Agent for Web: Apache Web Server version 8.0 and RSA Authentication Agent for Web: Apache Web Server version 8.0.1 prior to Build 618 have a security vulnerability that could potentially lead to authentication bypass.

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

Authentication bypass vulnerability in EMC RSA Authentication Agent for Web (Apache Web Server versions 8.0 and 8.0.1 prior to Build 618). The flaw allows potential attackers to circumvent authentication mechanisms in the RSA authentication agent, likely due to improper validation during the authentication process.

MitigationUpgrade RSA Authentication Agent for Web to Build 618 or later. This is a critical severity issue (CVSS 9.8) requiring immediate attention given the potential for complete authentication bypass.

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
Authentication Agent For WebApplication
Affected:= 8.0= 8.0.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 if RSA Authentication Agent for Web is installed
    Check for the product installation directory (commonly C:\Program Files\RSA\Authentication Agent for Web on Windows or /opt/rsa/auth_agent/web on Linux). Alternatively, query installed packages: on Windows use 'Get-WmiObject -Class Win32_Product' or check Add/Remove Programs; on Linux use 'rpm -qa | grep -i rsa' or 'dpkg -l | grep -i rsa'.
    Affected if The product is not found (not affected). If found, proceed to version check.
  2. Determine the installed version and build number
    Locate the version or build file in the installation directory. Common locations include: version.txt, build.info, or the agent's main configuration file. On Windows, also check the registry key HKLM\SOFTWARE\RSA\Authentication Agent for Web\Version. On Linux, check /opt/rsa/auth_agent/web/version or similar.
    Affected if The installed version cannot be determined (uncertain - further investigation needed).
  3. Compare version against affected range
    Verify if the installed version is 8.0 or 8.0.1. Then check the build number (must be Build 618 or later to be fixed). Look for version strings like '8.0 Build 618', '8.0.1 Build 600', etc.
    Affected if Version is 8.0 or 8.0.1 AND build number is below 618 (for example, Build 600, Build 615, or no build number shown). This means the system is affected.

The environment is affected if RSA Authentication Agent for Web version 8.0 or 8.0.1 is installed with a build number prior to 618.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade RSA Authentication Agent for Web to Build 618 or later. This is a critical severity issue (CVSS 9.8) requiring immediate attention given the potential for complete authentication bypass.

Recommended fix Moderate confidence

Build 618 or later of RSA Authentication Agent for Web 8.0.1

  1. Verify current installed version of RSA Authentication Agent for Web (Apache)
  2. Contact Dell EMC RSA/ RSA Customer Support to obtain Build 618 or later which contains the security fix
  3. Schedule a maintenance window for the upgrade
  4. Backup current agent configuration
  5. Apply the updated agent version (Build 618 or later)
  6. Verify the authentication bypass vulnerability is remediated
  7. Confirm normal authentication flow is functioning correctly

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

Fix this in Authentication Agent For Web Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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