What is CVE-2022-35540?

CVE-2022-35540 is a critical-severity use of hard-coded credentials vulnerability in AgileConfig.Client (nuget), affecting versions < 1.6.8. It is fixed in 1.6.8. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.

How severe is CVE-2022-35540?

CVE-2022-35540 has a CVSS score of 9.8 (Critical). 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 AgileConfig.Client are affected by CVE-2022-35540?

AgileConfig.Client (nuget) versions < 1.6.8 is affected.

Is there a fix for CVE-2022-35540?

Yes. CVE-2022-35540 is fixed in 1.6.8. Upgrade to this version or later.

Is CVE-2022-35540 exploitable, and should I be worried?

Whether CVE-2022-35540 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.

What actually determines whether CVE-2022-35540 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.

CVE-2022-35540 in AgileConfig.Client

Q: How severe is CVE-2022-35540?

CVE-2022-35540 has a CVSS score of 9.8 (Critical). 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.

Q: Which versions of AgileConfig.Client are affected by CVE-2022-35540?

AgileConfig.Client (nuget) versions < 1.6.8 is affected.

Q: Is there a fix for CVE-2022-35540?

Yes. CVE-2022-35540 is fixed in 1.6.8. Upgrade to this version or later.

Q: Is CVE-2022-35540 exploitable, and should I be worried?

Whether CVE-2022-35540 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.

Q: What actually determines whether CVE-2022-35540 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.

Q: How do I fix CVE-2022-35540?

Upgrade AgileConfig.Client to 1.6.8 or later.

Summary

Use of Hard-coded Credentials in AgileConfig.Client

Hardcoded JWT Secret in AgileConfig <1.6.8 Server allows remote attackers to use the generated JWT token to gain administrator access.

Impact

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-35540 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no 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 (1.6.8); upgrading removes the vulnerable code path.

Affected versions

AgileConfig.Client (< 1.6.8)

Security releases

AgileConfig.Client → 1.6.8 (nuget)

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 environment New to Kodem? Get a demo →

Remediation advice

Upgrade AgileConfig.Client to 1.6.8 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-35540? CVE-2022-35540 is a critical-severity use of hard-coded credentials vulnerability in AgileConfig.Client (nuget), affecting versions < 1.6.8. It is fixed in 1.6.8. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.
How severe is CVE-2022-35540? CVE-2022-35540 has a CVSS score of 9.8 (Critical). 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 AgileConfig.Client are affected by CVE-2022-35540? AgileConfig.Client (nuget) versions < 1.6.8 is affected.
Is there a fix for CVE-2022-35540? Yes. CVE-2022-35540 is fixed in 1.6.8. Upgrade to this version or later.
Is CVE-2022-35540 exploitable, and should I be worried? Whether CVE-2022-35540 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-35540 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-35540? Upgrade AgileConfig.Client to 1.6.8 or later.