answerdev answer up to 1.0.7 exposure of sensitive information through metadata
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in answerdev answer up to 1.0.7. It has been classified as problematic. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in exposure of sensitive information through metadata. This vulnerability is cataloged as CVE-2023-1974. The attack must be initiated from a local position. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, was found in answerdev answer up to 1.0.7. This affects an unknown code block. The manipulation with an unknown input leads to a exposure of sensitive information through metadata vulnerability. CWE is classifying the issue as CWE-1230. The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information. This is going to have an impact on confidentiality. The summary by CVE is:
Exposure of Sensitive Information Through Metadata in GitHub repository answerdev/answer prior to 1.0.8.
The weakness was shared 04/11/2023. The advisory is shared at huntr.dev. This vulnerability is uniquely identified as CVE-2023-1974 since 04/11/2023. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 1.0.8 eliminates this vulnerability. Applying the patch ac3f2f047ee00b4edaea7530e570ab67ff87cd6a is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-1239). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/answerdev/answer/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 2.8
VulDB Temp Score: 2.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 7.7
CNA Vector (huntr.dev): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Exposure of sensitive information through metadataCWE: CWE-1230 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: answer 1.0.8
Patch: ac3f2f047ee00b4edaea7530e570ab67ff87cd6a
Timeline
04/11/2023 🔍04/11/2023 🔍
04/11/2023 🔍
07/07/2025 🔍
Sources
Product: github.comAdvisory: ac3f2f047ee00b4edaea7530e570ab67ff87cd6a
Status: Confirmed
CVE: CVE-2023-1974 (🔍)
GCVE (CVE): GCVE-0-2023-1974
GCVE (VulDB): GCVE-100-225489
EUVD: 🔍
Entry
Created: 04/11/2023 12:33Updated: 07/07/2025 15:45
Changes: 04/11/2023 12:33 (50), 04/27/2023 00:33 (1), 04/27/2023 00:43 (11), 07/07/2025 15:45 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.