CVE-2023-31579 is a high-severity (CVSS 7.5) Hard-coded Credentials vulnerability in top.tangyh.basic:lamp-core. A fix is available for top.tangyh.basic:lamp-core — see the affected versions and patch details below.
Dromara Lamp-Cloud Use of Hard-coded Cryptographic Key
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-31579.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
top.tangyh.basic:lamp-core☕top.tangyh.basic:lamp-utilReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Dromara Lamp-Cloud before v3.8.1 was discovered to use a hardcoded cryptographic key when creating and verifying a Json Web Token. This vulnerability allows attackers to authenticate to the application via a crafted JWT token.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | top.tangyh.basic:lamp-core | all versions | 3.8.1top.tangyh.basic:lamp-core:3.8.1 |
| ☕Maven | top.tangyh.basic:lamp-util | all versions | 3.8.1top.tangyh.basic:lamp-util:3.8.1 |
Affected Products
lamp-cloudtangyhDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for top.tangyh.basic:lamp-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update top.tangyh.basic:lamp-core to 3.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-31579 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2023-31579 in your dependencies?
Find it across Maven, including transitive dependencies.