LiveActive security incident?Get immediate response
CVE Record

CVE-2019-3758: RSA Archer, versions prior to 6.6 P2 (6.6.0.2), contain an improper authentication vulnerability.

RSA Archer, versions prior to 6.6 P2 (6.6.0.2), contain an improper authentication vulnerability. The vulnerability allows sysadmins to create user accounts with insufficient credentials. Unauthenticated attackers could gain unauthorized access to the system using those accounts.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

RSA Archer before 6.6 P2 could allow administrator-created accounts to exist with insufficient credentials. If such an account exists, an unauthenticated attacker could use it to access Archer without authorization. Because Archer often supports governance, risk, and compliance workflows, unauthorized access could expose or alter sensitive business risk data.

Executive priority

Prioritize remediation for any pre-6.6 P2 Archer system that is internet-accessible or widely reachable internally. The issue can affect confidentiality, integrity, and availability of GRC data, but the provided evidence does not establish active exploitation.

Technical view

CVE-2019-3758 is an improper authentication issue, mapped to CWE-288, affecting RSA Archer versions prior to 6.6 P2 (6.6.0.2). The CVSS 3.0 score is 8.1 with network attack vector, no privileges, no user interaction, high complexity, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to RSA Archer deployments running versions earlier than 6.6 P2 (6.6.0.2), particularly instances reachable over a network. Risk depends on whether vulnerable account-creation behavior produced accounts with insufficient credentials.

Exploitation context

The provided sources do not show CISA KEV status or cited evidence of active exploitation. The CVSS vector indicates exploitation is network-reachable and unauthenticated, but high complexity. Treat internet-accessible or broadly reachable Archer systems as higher priority.

Researcher notes

Validation should focus on version confirmation and account-state review, not exploit reproduction. The source bundle does not provide technical root-cause details, proof-of-concept material, or vendor mitigation specifics beyond the fixed-version boundary implied by the affected range.

Mitigation direction

  • Upgrade RSA Archer to 6.6 P2 (6.6.0.2) or later.
  • Review the RSA advisory for vendor-specific remediation guidance.
  • Audit administrator-created accounts for insufficient or abnormal credential state.
  • Disable or correct accounts that do not meet authentication requirements.
  • Restrict network access to Archer while remediation is pending.

Validation and detection

  • Inventory RSA Archer instances and confirm exact installed versions.
  • Verify no production instance is earlier than 6.6 P2 (6.6.0.2).
  • Review account records created by sysadmins for weak or incomplete credentials.
  • Confirm authentication policy prevents accounts with insufficient credentials.
  • Check Archer access logs for unexpected use of suspect accounts.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-3758 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.0HighCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.1High
CVSS 3.0 vector shape for CVE-2019-3758Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
DellRSA Archerprior to 6.6 P2 (6.6.0.2)Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.