dbcve.org
Rsa Archer EgrcApplication · Emc

CVE-2017-4998

HIGH · 8.8 CVSS v3.0 Published 2017-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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
EMC RSA Archer 5.4.1.3, 5.5.3.1, 5.5.2.3, 5.5.2, 5.5.1.3.1, 5.5.1.1 is potentially affected by a cross-site request forgery vulnerability. A remote low privileged attacker may potentially exploit the vulnerability to execute unauthorized requests on behalf of the victim, using the authenticated user's privileges.

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

EMC RSA Archer contains a cross-site request forgery (CSRF) vulnerability in versions 5.4.1.3 through 5.5.3.1. A remote attacker with low privileges can trick an authenticated user into unknowingly executing unauthorized actions within the application by leveraging the trusted relationship between the server and the victim's browser.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing requests, configure SameSite cookie attributes, and add referer header validation to verify request origin.

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
Rsa Archer EgrcApplication
Affected:= 5.4.1.3= 5.5.1.1= 5.5.1.3.1= 5.5.2= 5.5.2.3= 5.5.3.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 RSA Archer version
    Access the RSA Archer web interface and navigate to About or System Information page, typically found under Administration > System > About. Alternatively, check the installation directory for a version file or review the installer logs.
    Affected if The displayed version matches 5.4.1.3, 5.5.1.1, 5.5.1.3.1, 5.5.2, 5.5.2.3, or 5.5.3.1, or falls within the range between 5.4.1.3 and 5.5.3.1.
  2. Verify Archer version via API or configuration file
    If web UI access is limited, check the archer instances configuration file (typically instances.xml or similar in the installation directory) or query the Archer web services API for the version endpoint.
    Affected if The returned version matches any of the affected versions listed in the CVE.
  3. Confirm application handles state-changing requests
    Review application logs or observe user sessions to identify state-changing operations such as create, update, delete, or workflow actions that modify data.
    Affected if The application processes state-changing requests without requiring additional verification steps beyond authentication.
  4. Inspect request headers for anti-CSRF tokens
    Use browser developer tools or a proxy to intercept a state-changing form submission or AJAX request. Examine the request payload and headers for a CSRF token, anti-CSRF parameter, or custom security token.
    Affected if State-changing requests do not contain a unique, session-bound CSRF token or anti-CSRF token in the request body or headers.
  5. Check SameSite cookie configuration
    Inspect the Set-Cookie headers for the application session cookies. Verify if the SameSite attribute is set to Strict or Lax, or if it is missing entirely.
    Affected if Session cookies lack the SameSite attribute or are set to None without secure flag, indicating incomplete CSRF protection.

The environment is affected if RSA Archer version is 5.4.1.3 through 5.5.3.1 and state-changing requests lack anti-CSRF token validation or proper SameSite cookie attributes.

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

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing requests, configure SameSite cookie attributes, and add referer header validation to verify request origin.

Fix this in Rsa Archer Egrc 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 help mitigating

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-2017-4998 — 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-4998 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