AgileConfig up to 1.6.7 JWT Secret hard-coded key

Summaryinfo

A vulnerability was found in AgileConfig up to 1.6.7. It has been classified as problematic. Affected by this issue is some unknown functionality of the component JWT Secret Handler. Performing a manipulation results in hard-coded key. This vulnerability is reported as CVE-2022-35540. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic has been found in AgileConfig up to 1.6.7. This affects an unknown code block of the component JWT Secret Handler. The manipulation with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality. The summary by CVE is:

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

The weakness was disclosed 08/19/2022 as 91. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-35540 since 07/11/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

Upgrading to version 1.6.8 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• AgileConfig

Version

• 1.6.0
• 1.6.1
• 1.6.2
• 1.6.3
• 1.6.4
• 1.6.5
• 1.6.6
• 1.6.7

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion