Security readout for executives and security teams
Plain-English summary
This flaw can cause Office 365 user passwords to be written in plain text inside RSA governance connector debug logs. The attacker must already be an authenticated local user with access to those logs, but exposed credentials could support broader account compromise.
Executive priority
Treat this as a high-priority credential exposure issue for affected RSA identity governance environments. It is not described as remotely exploitable, but exposed Office 365 passwords can create business-wide risk beyond the RSA server.
Technical view
CVE-2019-3763 is CWE-532 information exposure in RSA Identity Governance and Lifecycle and RSA Via Lifecycle and Governance before 7.1.0 P08. The Office 365 connector debug log may record Office 365 user passwords in plain text. CVSS 3.1 is 8.8 with local, low-privilege access and high confidentiality, integrity, and availability impact.
Likely exposure
Organizations using affected RSA Identity Governance and Lifecycle or RSA Via Lifecycle and Governance versions, especially with Office 365 connector debug logging enabled or retained logs accessible to local users.
Exploitation context
The source bundle does not show active exploitation, and KEV status is false. Abuse requires authenticated local access to debug logs, then misuse of any exposed Office 365 password for follow-on activity.
Researcher notes
The available evidence identifies product families, affected pre-7.1.0 P08 versions, CWE-532, and the local authenticated log-access condition. The bundle does not provide exploit evidence, detailed patch notes, or exact log locations, so validation should rely on vendor guidance and internal configuration review.
Mitigation direction
- Upgrade affected RSA products to 7.1.0 P08 or a vendor-supported fixed release.
- Review RSA vendor advisory DOC-106943 for product-specific remediation guidance.
- Restrict access to Office 365 connector debug logs to authorized administrators only.
- If exposure is confirmed, rotate affected Office 365 credentials promptly.
- Reduce debug log retention where operationally acceptable and consistent with vendor guidance.
Validation and detection
- Inventory RSA Identity Governance and Lifecycle and RSA Via deployments and versions.
- Confirm whether any deployment is earlier than 7.1.0 P08.
- Determine whether Office 365 connector debug logs were enabled and retained.
- Review log file permissions for authenticated local user access paths.
- Check retained debug logs for accidental credential exposure using approved internal procedures.
- Review Office 365 account activity if any password exposure is found.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-532: 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-3763 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H26Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://community.rsa.com/docs/DOC-106943CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information into Log File
Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.