GHSA-4cwh-8w4g-jxxh CVE-2023-0744 GO-2023-1550
Answer contains Improper Access Control vulnerability
- Severity
- 9.8 / 10
- Critical · CVSS 3.1
- Exploit chance (EPSS)
- 6.37%
- Chance of exploitation in the next 30 days. Higher than 93.66% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-284 Improper Access Control
- Fix
1.0.4- Upgrade github.com/answerdev/answer to this version or later
Description
Improper Access Control in GitHub repository answerdev/answer prior to 1.0.4.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/answerdev/answer | < 1.0.4 |
1.0.4 |
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.4
- go
go get github.com/answerdev/answer@v1.0.4 && go mod tidy
Severity breakdown
CVSS 3.1 9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-284: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How to prevent it
- Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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