Skip to content

Netmaker has Hardcoded DNS Secret Key

High severity GitHub Reviewed Published Aug 24, 2023 in gravitl/netmaker • Updated Nov 8, 2023

Package

gomod github.com/gravitl/netmaker (Go)

Affected versions

< 0.17.1
>= 0.18.0, < 0.18.6

Patched versions

0.17.1
0.18.6

Description

Impact

Hardcoded DNS key usage has been found in Netmaker allowing unauth users to interact with DNS API endpoints.

Patches

Issue is patched in 0.17.1, and fixed in 0.18.6+.

If Users are using 0.17.1, they should run "docker pull gravitl/netmaker:v0.17.1" and "docker-compose up -d". This will switch them to the patched users

If users are using v0.18.0-0.18.5, they should upgrade to v0.18.6 or later.

Workarounds

If using 0.17.1, can just pull the latest docker image of backend and restart server.

References

Credit to Project Discovery, and in particular https://github.com/rootxharsh , https://github.com/iamnoooob, and https://github.com/projectdiscovery

References

@afeiszli afeiszli published to gravitl/netmaker Aug 24, 2023
Published by the National Vulnerability Database Aug 24, 2023
Published to the GitHub Advisory Database Aug 25, 2023
Reviewed Aug 25, 2023
Last updated Nov 8, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

22.850%
(97th percentile)

Weaknesses

CVE ID

CVE-2023-32077

GHSA ID

GHSA-8x8h-hcq8-jwwx

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.