Remote code execution via insecure Log4j component
Published Feb 5, 2024 · Updated Jun 17, 2025
Command injection in B3log Symphony 3.6.3 and earlier allows remote attackers to execute arbitrary code through its Log4j component. The upstream issue identifies /activity/character/submit as the trigger and attributes execution to an insecure Log4j version, but it does not disclose the exact logging call or input transformation. Network access without authentication or user interaction is sufficient, and successful exploitation permits server takeover.
Summary
What happened
Command injection in B3log Symphony 3.6.3 and earlier allows remote attackers to execute arbitrary code through its Log4j component. The upstream issue identifies /activity/character/submit as the trigger and attributes execution to an insecure Log4j version, but it does not disclose the exact logging call or input transformation. Network access without authentication or user interaction is sufficient, and successful exploitation permits server takeover.
The record
- CVE
- CVE-2024-23049
- Published
- Feb 5, 2024
- Updated
- Jun 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, CAPEC-248, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo