dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-24230

HIGH · 7.5 CVSS v3.1 Published 2024-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Komm.One CMS 10.4.2.14 has a Server-Side Template Injection (SSTI) vulnerability via the Velocity template engine. It allows remote attackers to execute arbitrary code via a URL that specifies java.lang.Runtime in conjunction with getRuntime().exec followed by an OS command.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Komm.One CMS 10.4.2.14 is vulnerable to Server-Side Template Injection (SSTI) via the Velocity template engine. Attackers can achieve remote code execution by injecting Java code (java.lang.Runtime.getRuntime().exec) into template parameters, allowing execution of arbitrary OS commands.

MitigationApply the vendor patch or upgrade to a patched version of Komm.One CMS that addresses the SSTI vulnerability in the Velocity template engine. If no patch exists, consider disabling or sandboxing the Velocity template engine, implementing strict input validation, and/or deploying a WAF rule to block malicious template injection patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Komm.One CMS installation version
    Locate the version file or check the admin dashboard for the installed CMS version. Common locations include a version info file in the installation directory, the about page in the admin panel, or the HTTP response headers from the server.
    Affected if The installed version is 10.4.2.14 or falls within the affected version range around this release.
  2. Verify Velocity template engine is enabled
    Check the Komm.One CMS configuration files (such as configuration.xml, web.xml, or similar) for Velocity-related settings. Look for template engine configurations, Velocity servlet mappings, or template resolver settings.
    Affected if The Velocity template engine is enabled and configured as the default or alternate template processor.
  3. Identify template endpoints that accept user input
    Review the web application's URL patterns and form parameters that handle template rendering. Check template files (.vm files or similar) for parameters that accept user-supplied values and are passed to the template engine.
    Affected if The application renders user-controlled input through Velocity templates without sanitization.
  4. Inspect template configuration for unsandboxed execution
    Examine Velocity configuration files (velocity.properties or similar) for sandbox settings. Check if the Velocity engine has security manager restrictions or sandboxing disabled.
    Affected if Velocity is configured without sandboxing or security manager restrictions, allowing execution of Java code.
  5. Review application logs for injection patterns
    Search web server and application logs for patterns resembling template injection payloads such as '${', '#{', or Java method calls like 'Runtime.getRuntime()'.
    Affected if Suspicious template injection patterns appear in request logs or error logs.

A system is affected if it runs Komm.One CMS version 10.4.2.14 (or an equivalent vulnerable version) with the Velocity template engine enabled and processing user input without sanitization or sandboxing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch or upgrade to a patched version of Komm.One CMS that addresses the SSTI vulnerability in the Velocity template engine. If no patch exists, consider disabling or sandboxing the Velocity template engine, implementing strict input validation, and/or deploying a WAF rule to block malicious template injection patterns.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24230 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24230 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data