CVE-2022-22845
Published: 10 January 2022
Summary
CVE-2022-22845 is a critical-severity Use of Hard-coded Credentials (CWE-798) vulnerability in Qxip Homer Webapp. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 5.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2022-22845 affects QXIP SIPCAPTURE homer-app versions prior to 1.4.28 used with HOMER 7.x. The component ships with a single hardcoded JWT secret (167f0db2-f83e-4baa-9736-d56064a5b415) that is identical across all customer installations, corresponding to CWE-798 use of hard-coded credentials and carrying a CVSS 3.1 score of 9.8.
An unauthenticated remote attacker can exploit the shared secret to forge valid JWT tokens and thereby impersonate any user or service within the affected HOMER deployment. Successful token forgery grants the attacker full control over the application’s authentication and authorization mechanisms, enabling arbitrary data access, modification, or disruption.
Public references point to the upstream fix released in homer-app 1.4.28; the associated commit and version diff indicate that the hardcoded secret was replaced with an installation-specific value. Operators are therefore advised to upgrade immediately and to regenerate any existing tokens or sessions after deployment.
The EPSS score has remained flat at 0.1348 since disclosure, indicating no material increase in observed exploitation interest.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-27983
Vulnerability details
QXIP SIPCAPTURE homer-app before 1.4.28 for HOMER 7.x has the same 167f0db2-f83e-4baa-9736-d56064a5b415 JWT secret key across different customers' installations.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Enables users to notice when hard-coded credentials have been exploited for unauthorized access.
Security training explicitly warns against hard-coded credentials, lowering their use in systems.
Policy and procedures prohibit hard-coded credentials in favor of managed authentication.
External identity providers eliminate the need for hard-coded credentials in applications.
Changing default authenticators prior to first use and protecting content prevents use of hard-coded credentials.
Central credential stores and rotation policies remove the need for hard-coded credentials in configuration files or code.
Intelligence programs surface reports of campaigns that abuse hard-coded credentials in products, prompting removal or replacement and thereby reducing successful exploitation.
Planned investment enables secure credential storage and management systems instead of hard-coded credentials.