Skip to content

GHSA-79hx-g43v-xfmr CVE-2023-1543 GO-2023-1655

Answer vulnerable to Insufficient Session Expiration

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

Description

Insufficient Session Expiration in GitHub repository answerdev/answer prior to 1.0.6.

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-613: Insufficient Session Expiration

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

How to prevent it
  • Implementation: Set sessions/credentials expiration date.

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-j97g-77fj-9c4p
Answer vulnerable to account takeover because password reset links do not expire
High 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
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