GHSA-pj2h-85jq-g5vg CVE-2023-4815 GO-2023-2051
Answer Missing Authentication for Critical Function
High
Go
- Severity
- 8.3 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 0.82%
- Chance of exploitation in the next 30 days. Higher than 57.36% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-306 Missing Authentication for Critical Function
- Fix
1.1.3- Upgrade github.com/answerdev/answer to this version or later
Description
Missing Authentication for Critical Function in GitHub repository answerdev/answer prior to v1.1.3.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/answerdev/answer | < 1.1.3 |
1.1.3 |
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.1.3
- go
go get github.com/answerdev/answer@v1.1.3 && go mod tidy
Severity breakdown
CVSS 3.0 8.3
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
Weakness
CWE-306: Missing Authentication for Critical Function
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How to prevent it
- Architecture and Design: Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability. Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected, including those channels that are assumed to be accessible only by authorized parties. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port. In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate credential management need to be used throughout.
- Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Architecture and Design: Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment. These capabilities may avoid common weaknesses that are unique to authentication; support automatic auditing and tracking; and make it easier to provide a clear separation between authentication tasks and authorization tasks. In environments such as the World Wide Web, the line between authentication and authorization is sometimes blurred. If custom authentication routines are required instead of those provided by the server, then these routines must be applied to every single page, since these pages could be requested directly.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator [REF-45].
- Implementation, System Configuration, Operation: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data [REF-1297] [REF-1298] [REF-1302].
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| 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 |
| GHSA-8jg3-rx43-3fv4 Answer vulnerable to Exposure of Sensitive Information Through Metadata | 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