Security readout for executives and security teams
acme.sh versions before 3.0.6 could execute commands supplied by a remote server because the client evaluated remote content. The CVE description says this was exploited in the wild in June 2023. Treat affected installations as potentially serious because certificate automation often runs on important servers. Exposure is environments running acme.sh before 3.0.6. The bundle does not identify operating systems, package distributions, or CPEs. Prioritize hosts where acme.sh is installed for certificate issuance or renewal, especially automated jobs that contact remote services. Prioritize remediation as high. The issue involves remote command execution and the CVE record states real-world exploitation. Focus first on internet-facing or production servers using acme.sh automation, then confirm no legacy installations remain. Mitigation focus: Upgrade acme.sh to 3.0.6 or later where installed.; Check the acme.sh 3.0.6 release and vendor issue for current guidance.; Remove or disable obsolete acme.sh installations no longer needed..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-38198 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/acmesh-official/acme.sh/issues/4659CVE reference
- https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/heXVr8o83YsCVE reference
- https://news.ycombinator.com/item?id=36252310CVE reference
- https://github.com/acmesh-official/acme.sh/releases/tag/3.0.6CVE reference
- https://news.ycombinator.com/item?id=36254093CVE reference
- https://www.reddit.com/r/netsec/comments/144ygg7/acmesh_runs_arbitrary_commands_from_a_remote/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.