GHSA-6x5v-cxpp-pc5x CVE-2023-1540 GO-2023-1654
Answer has Observable Response Discrepancy
Medium
Go
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.64%
- Chance of exploitation in the next 30 days. Higher than 50.63% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
1.0.6- Upgrade github.com/answerdev/answer to this version or later
Description
Observable Response Discrepancy in GitHub repository answerdev/answer prior to 1.0.6.
Affected versions
Go
| Package | Vulnerable | Fixed 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 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-203: Observable Discrepancy
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
How to prevent it
- 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.
- Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
CWE-204: Observable Response Discrepancy
The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
How to prevent it
- 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.
- Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
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