Security readout for executives and security teams
Plain-English summary
DomainMOD v4.15.0 may leave users logged in after their password is changed. That means changing a compromised password may not immediately remove access from other browsers or devices that already had an active session.
Executive priority
Treat this as a moderate account-security issue. It weakens password reset as a containment step, so teams using DomainMOD v4.15.0 should verify exposure and seek vendor guidance promptly.
Technical view
The CVE describes insufficient session expiration in DomainMOD v4.15.0: password changes do not invalidate sessions using the changed password or old sessions on other devices. No CVSS score, CWE, CPE, patch, or vendor mitigation is provided in the supplied sources.
Likely exposure
Exposure is limited to organizations running DomainMOD v4.15.0. The supplied CVE metadata does not provide CPEs, affected version ranges beyond v4.15.0, or deployment details.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. Practical risk depends on whether an attacker, former user, or lost device already has a valid authenticated session.
Researcher notes
Evidence is thin: the CVE record identifies the behavior and one external reference, but lacks CVSS, CWE, CPEs, exploit status, and remediation details. Avoid assuming broader affected versions without vendor confirmation.
Mitigation direction
- Check DomainMOD project or vendor guidance for fixed releases or advisories.
- Upgrade only to a version confirmed by vendor guidance as addressing this issue.
- Force logout or revoke active sessions after password changes where administratively possible.
- Reduce exposure of DomainMOD to trusted networks until remediation is confirmed.
- Review access logs for continued activity after password reset events.
Validation and detection
- Inventory DomainMOD installations and confirm whether v4.15.0 is present.
- Review session behavior after password changes in a controlled test environment.
- Check whether old browser or device sessions remain authenticated after reset.
- Verify whether administrative controls can revoke all active sessions.
- Document any compensating controls if no fixed version is confirmed.
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.
Credential 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-2020-35358 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://gist.github.com/anku-agar/0fec2ffd98308e550ce9b5d4b395d0d7CVE 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.