dbcve.org
AgileconfigApplication · Dotnetcore

CVE-2022-35540

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-18
Fix available
A fix is available. Upgrade to 1.6.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

AgileConfig versions prior to 1.6.8 contain a hardcoded JWT secret embedded in the server code. An attacker who obtains this secret can craft valid JWT tokens with administrator privileges, bypassing authentication and gaining full administrative access to the configuration management system.

MitigationUpgrade AgileConfig to version 1.6.8 or later, replace the hardcoded JWT secret with a strong, randomly generated secret stored securely (e.g., environment variable or secrets manager), and invalidate all existing JWT tokens by rotating the signing key.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AgileconfigApplication
Affected:< 1.6.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check AgileConfig version
    Locate the AgileConfig installation and identify its version number (check the application binary, DLL file metadata, or any version file). Compare your version against the affected range: versions prior to 1.6.8 are vulnerable.
    Affected if Your installed version is lower than 1.6.8
  2. Inspect configuration files for JWT settings
    Examine AgileConfig configuration files such as appsettings.json, appsettings.Development.json, or any custom configuration for JWT-related settings (Jwt:Secret, JWT key, or similar).
    Affected if A static JWT secret value is hardcoded directly in the configuration file instead of being loaded from an environment variable or secure secrets manager
  3. Search application binaries or source code for hardcoded secret
    Inspect the compiled AgileConfig binaries (.dll files) or decompiled source code for the hardcoded JWT secret string. Look for any static string assigned to JWT configuration that remains consistent across deployments.
    Affected if A hardcoded JWT secret string is found embedded in the application code or binaries (the same secret exists in every installation)
  4. Verify JWT authentication is enabled
    Check if the AgileConfig instance has JWT-based authentication enabled. Review the authentication configuration in the application to confirm JWT is the active authentication mechanism.
    Affected if JWT authentication is enabled and the system relies on the embedded secret for token validation

You are affected if your AgileConfig version is prior to 1.6.8 and a hardcoded JWT secret is present in the application code, binaries, or configuration files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.6.8 or later
Fixed in 1.6.8
Interim mitigation

Upgrade AgileConfig to version 1.6.8 or later, replace the hardcoded JWT secret with a strong, randomly generated secret stored securely (e.g., environment variable or secrets manager), and invalidate all existing JWT tokens by rotating the signing key.

Recommended fix High confidence

AgileConfig version 1.6.8 or later

  1. 1. Back up your current AgileConfig configuration and database data
  2. 2. Stop the AgileConfig service
  3. 3. Upgrade AgileConfig to version 1.6.8 or later
  4. 4. Start the AgileConfig service
  5. 5. Verify that authentication works correctly with the new installation
  6. 6. Confirm that the JWT secret is no longer hardcoded in the configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Agileconfig Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,624.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-35540 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-35540 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data