CVE-2019-3758
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.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.
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 confidenceRSA Archer versions prior to 6.6 P2 (6.6.0.2) contain an improper authentication vulnerability that allows sysadmins to create user accounts with insufficient credentials. Unauthenticated attackers can exploit these weakly configured accounts to gain unauthorized system access.
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.6.0.2CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify RSA Archer installation versionAccess the RSA Archer Administration menu, navigate to About or System Settings to view the installed version number. Alternatively, check the installation directory for version metadata or the software release notes.Affected if The displayed version is prior to 6.6.0.2 (6.6.0.0, 6.6.0.1, or any 6.5.x/6.4.x release)
-
Review user account password policy settingsIn RSA Archer Administration, go to User Management or Account Settings and inspect the password complexity requirements. Check if minimum length, character type, and expiration settings are configured.Affected if Password policy is set to weak or minimal requirements, or is disabled entirely
-
Audit existing user accounts for weak credentialsGenerate a user account report from the Administration panel. Review accounts for weak passwords, default passwords, or accounts that have never required password changes.Affected if Any user accounts exist with weak, default, or never-expired passwords
-
Check for accounts with insufficient credential enforcementIn User Management, examine individual account settings to determine if password requirements are being enforced. Look for accounts marked as 'Password Never Expires' or accounts with bypassing authentication settings.Affected if Accounts exist that bypass or circumvent standard credential requirements
You are affected if your RSA Archer version is below 6.6.0.2 AND any user accounts exist with weak, insufficient, or unenforced credentials that could be exploited by an unauthenticated attacker.
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.
dbcve · scoped6.6.0.2
Upgrade RSA Archer to version 6.6 P2 (6.6.0.2) or later to patch the improper authentication vulnerability. Additionally, audit existing user accounts to ensure they enforce strong credential requirements.
6.6.0.2 (6.6 P2)
- Perform a complete backup of the RSA Archer database and configuration files
- Plan a maintenance window for the upgrade process
- Upgrade RSA Archer to version 6.6.0.2 (6.6 P2) following the official upgrade documentation
- After upgrade, verify that the system is operational and the vulnerability is resolved
- Review user account configurations to ensure strong authentication credentials are enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3758 — 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-2019-3758 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