gin up to 1.5.x Default Logger neutralization for logs
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in gin up to 1.5.x. Affected is an unknown function of the component Default Logger. The manipulation leads to neutralization for logs. This vulnerability is documented as CVE-2020-36567. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in gin up to 1.5.x and classified as problematic. This issue affects an unknown code of the component Default Logger. The manipulation with an unknown input leads to a neutralization for logs vulnerability. Using CWE to declare the problem leads to CWE-117. The product does not neutralize or incorrectly neutralizes output that is written to logs. Impacted is integrity, and availability. The summary by CVE is:
Unsanitized input in the default logger in github.com/gin-gonic/gin before v1.6.0 allows remote attackers to inject arbitrary log lines.
The weakness was released 12/28/2022. The advisory is shared at github.com. The identification of this vulnerability is CVE-2020-36567 since 07/29/2022. Neither technical details nor an exploit are publicly available.
Upgrading to version 1.6.0 eliminates this vulnerability. Applying the patch a71af9c144f9579f6dbe945341c1df37aaf09c0d 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: Neutralization for logsCWE: CWE-117 / CWE-116 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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: gin 1.6.0
Patch: a71af9c144f9579f6dbe945341c1df37aaf09c0d
Timeline
07/29/2022 🔍12/28/2022 🔍
12/28/2022 🔍
04/11/2025 🔍
Sources
Advisory: a71af9c144f9579f6dbe945341c1df37aaf09c0dStatus: Confirmed
CVE: CVE-2020-36567 (🔍)
GCVE (CVE): GCVE-0-2020-36567
GCVE (VulDB): GCVE-100-216941
Entry
Created: 12/28/2022 09:35Updated: 04/11/2025 19:34
Changes: 12/28/2022 09:35 (40), 01/25/2023 14:10 (1), 01/25/2023 14:13 (11), 04/11/2025 19:34 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.