CVE-2024-46612
First published: Tue Sep 24 2024(Updated: )
IceCMS v3.4.7 and before was discovered to contain a hardcoded JWT key, allowing an attacker to forge JWT authentication information.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| iceCMS | <3.4.7 | |
| iCMS | <3.4.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-46612?
CVE-2024-46612 has been classified as a high severity vulnerability due to the potential for authentication forgery.
How do I fix CVE-2024-46612?
To mitigate CVE-2024-46612, update IceCMS to version 3.4.8 or later, which removes the hardcoded JWT key.
What damages can CVE-2024-46612 cause?
CVE-2024-46612 can allow attackers to bypass authentication mechanisms, potentially leading to unauthorized access to sensitive data.
Which versions of IceCMS are affected by CVE-2024-46612?
CVE-2024-46612 affects IceCMS versions 3.4.7 and earlier.
Is there a workaround for CVE-2024-46612 if I cannot upgrade?
If upgrading is not possible, consider implementing additional security measures, such as strict API access controls, until the application can be updated.
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/weakness
- agent/author
- agent/severity
- agent/event
- agent/last-modified-date
- collector/mitre-cve
- source/MITRE
- agent/source
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/tags
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- vendor/icecms
- canonical/icecms
- vendor/thecosy
- canonical/icms