Skip to content

GHSA-65v8-6pvw-jwvq CVE-2023-1975 GO-2023-1716

Answer vulnerable to Insertion of Sensitive Information Into Sent Data

Medium Go
Severity
6.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.59%
Chance of exploitation in the next 30 days. Higher than 48.05% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-201 Insertion of Sensitive Information Into Sent Data
Fix
1.0.8
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.8 does not strip EXIF geolocation data from user-uploaded logos. As a result, anyone can get sensitive information like a user's device ID, geolocation, system information, system version, etc.

Affected versions

Go

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

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.8

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

Severity breakdown

CVSS 3.1 6.5

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

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

Weakness

CWE-201: Insertion of Sensitive Information Into Sent Data

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

How to prevent it
  • Requirements: Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
  • Implementation: Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
  • System Configuration: Setup default error messages so that unexpected errors do not disclose sensitive information.
  • 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

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-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