CVE-2018-11060
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 · uneditedRSA Archer, versions prior to 6.4.0.1, contain an authorization bypass vulnerability in the REST API. A remote authenticated malicious Archer user could potentially exploit this vulnerability to elevate their 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 · moderate confidenceRSA Archer versions prior to 6.4.0.1 contain an authorization bypass vulnerability in the REST API that allows authenticated users to elevate their privileges beyond what their account is assigned, enabling potential unauthorized access to sensitive functions or data.
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>= 6.1.0.0, < 6.1.0.3>= 6.2.0.0, < 6.2.0.10>= 6.3.0.0, < 6.3.0.7= 6.4.0.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify RSA Archer installed versionAccess the Archer UI About page or use the Archer Control Panel/Administration tools to view the current software version. This is typically found under Help > About in the web interface or through the installation documentation.Affected if The installed version falls within these ranges: 6.1.0.0 to 6.1.0.2, 6.2.0.0 to 6.2.0.9, 6.3.0.0 to 6.3.0.6, or exactly 6.4.0.0.
-
Confirm REST API is enabledVerify whether the RSA Archer REST API feature is enabled in your environment. This is typically configured through the Archer Administration settings or IIS configuration if the API is exposed via a separate virtual directory.Affected if REST API is enabled and the version check shows a vulnerable version.
-
Review REST API role assignmentsAudit the role-based access control (RBAC) mappings for REST API users in the Archer Administration console. Check which roles are assigned to accounts that use the REST API functionality.Affected if Low-privilege REST API users have unexpectedly elevated permissions or access to sensitive functions beyond their assigned role scope.
-
Check for anomalous API access patternsReview API request logs, IIS logs, or Archer audit logs for any REST API calls that accessed functions or data outside the expected scope for the API user roles.Affected if Logs show REST API calls accessing privileged functions by users assigned to lower-privilege roles.
You are affected if your RSA Archer version is 6.1.0.0-6.1.0.2, 6.2.0.0-6.2.0.9, 6.3.0.0-6.3.0.6, or exactly 6.4.0.0 AND the REST API is enabled and accessible to users.
Generated from the published advisory. Verify against your own configuration.
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 data6.1.0.36.2.0.106.3.0.7
Upgrade RSA Archer to version 6.4.0.1 or later to incorporate the authorization fix. After upgrading, verify that role-based access controls properly enforce privilege boundaries in the REST API.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11060 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-11060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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