Skip to content

GHSA-j97g-77fj-9c4p CVE-2023-1976 GO-2023-1719

Answer vulnerable to account takeover because password reset links do not expire

High Go
Severity
8.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.61%
Chance of exploitation in the next 30 days. Higher than 49.04% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-263 Password Aging with Long Expiration
Fix
1.0.6
Upgrade github.com/answerdev/answer to this version or later

Description

answerdev/answer is an open-source knowledge-based community software. Answer prior to 1.0.6 is vulnerable to account takeover because the password reset link does not expire.

Affected versions

Go

PackageVulnerableFixed in
github.com/answerdev/answer
< 1.0.6
1.0.6

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/answerdev/answer Go → 1.0.6

go
go get github.com/answerdev/answer@v1.0.6 && go mod tidy

Severity breakdown

CVSS 3.1 8.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-263: Password Aging with Long Expiration

The product supports password aging, but the expiration period is too long.

How to prevent it
  • Implementation: Previously, "password expiration" was widely advocated as a defense-in-depth approach to minimize the risk of weak passwords, and it has become a common practice. Password expiration requires a password to be changed within a fixed time window (such as every 90 days). However, this approach has significant limitations in the current threat landscape, and its utility has been reduced in light of the adoption of related protection mechanisms (such as password complexity and computational effort), along with the recognition that regular password changes often caused users to generate more predictable passwords. As a result, this is now a Discouraged Common Practice [REF-1488] [REF-1489], especially as the sole factor in protecting passwords. It is still strongly encouraged to force password changes in case of evidence of compromise, but this is not the same as a forced "expiration" on an arbitrary time frame.
  • Architecture and Design: Ensure that password aging is limited so that there is a defined maximum age for passwords. Note that if the expiration window is too short, it can cause users to generate poor or predictable passwords.
  • Architecture and Design: Ensure that the user is notified several times leading up to the password expiration.
  • Architecture and Design: Create mechanisms to prevent users from reusing passwords or creating similar passwords.
  • Implementation: Developers might disable clipboard paste operations into password fields as a way to discourage users from pasting a password into a clipboard. However, this might encourage users to choose less-secure passwords that are easier to type, and it can reduce the usability of password managers [REF-1294].

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-pj2h-85jq-g5vg
Answer Missing Authentication for Critical Function
High Also affects github.com/answerdev/answer
GHSA-52h8-c876-989c
Answer has Race Condition within a Thread
Medium Also affects github.com/answerdev/answer
GHSA-ggcf-hwxp-rc77
Answer Insufficient Session Expiration vulnerability
High Also affects github.com/answerdev/answer
GHSA-j63x-f657-2m9g
Answer has Weak Password Requirements
High Also affects github.com/answerdev/answer
GHSA-v9vc-7x69-c2x8
Answer Missing Authorization vulnerability
Medium Also affects github.com/answerdev/answer
GHSA-qmqw-r4x6-3w2q
Answer Missing Authorization vulnerability
Low Also affects github.com/answerdev/answer
GHSA-65v8-6pvw-jwvq
Answer vulnerable to Insertion of Sensitive Information Into Sent Data
Medium Also affects github.com/answerdev/answer
GHSA-8jg3-rx43-3fv4
Answer vulnerable to Exposure of Sensitive Information Through Metadata
Medium Also affects github.com/answerdev/answer
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor