Summary
Use of Hard-coded Cryptographic Key in Netmaker
Additional Information
If you are running any other version, you will need to upgrade to one of these three versions. If you have a special circumstance that requires running a different version, let us know and we may be able to build a custom patch.
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Impact
There is a hard-coded cryptographic key in the code base which can be exploited to run admin commands on a remote server, if you know the address and username of the admin. This effects the server (netmaker) component, and not clients.
Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact. Typical impact: unauthorized access using the static credential.
CVE-2022-23650 has a CVSS score of 7.2 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.8.5, 0.9.4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This has been patched in Netmaker v0.8.5, v0.9.4, and v0.10.0. If you are running these versions, the fix is to perform the following:
- docker-compose down
- docker pull gravitl/netmaker:( version )
- docker-compose up -d
Frequently Asked Questions
- What is CVE-2022-23650? CVE-2022-23650 is a high-severity use of hard-coded credentials vulnerability in github.com/gravitl/netmaker (go), affecting versions < 0.8.5. It is fixed in 0.8.5, 0.9.4. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.
- How severe is CVE-2022-23650? CVE-2022-23650 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/gravitl/netmaker are affected by CVE-2022-23650? github.com/gravitl/netmaker (go) versions < 0.8.5 is affected.
- Is there a fix for CVE-2022-23650? Yes. CVE-2022-23650 is fixed in 0.8.5, 0.9.4. Upgrade to this version or later.
- Is CVE-2022-23650 exploitable, and should I be worried? Whether CVE-2022-23650 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-23650 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-23650?
- Upgrade
github.com/gravitl/netmakerto 0.8.5 or later - Upgrade
github.com/gravitl/netmakerto 0.9.4 or later
- Upgrade