dbcve.org
JeewmsApplication · Huayi Tec

CVE-2024-12347

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
A vulnerability was found in Guangzhou Huayi Intelligent Technology Jeewms up to 1.0.0 and classified as critical. This issue affects some unknown processing of the file /jeewms_war/webpage/system/druid/index.html of the component Druid Monitoring Interface. The manipulation leads to improper authorization. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

Improper authorization vulnerability in the Druid monitoring interface at /jeewms_war/webpage/system/druid/index.html in Jeewms up to 1.0.0 allows remote unauthenticated attackers to access sensitive monitoring data and potentially database information exposed through the Druid console.

MitigationRestrict or disable the Druid monitoring interface in production environments through network access controls, authentication requirements, or complete removal of the exposed endpoint.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JeewmsApplication
Affected:all versions

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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. Confirm Jeewms installation
    Identify if Jeewms is deployed in your environment by checking for jeewms_war directory, JAR files, or the application running on expected ports (typically 8080 or 8081)
    Affected if Jeewms from Huayi Tec is installed
  2. Locate the Druid console endpoint
    Access or probe http(s)://<your-server>:<port>/jeewms_war/webpage/system/druid/index.html or check if the path /jeewms_war/webpage/system/druid/ exists in the deployed web application
    Affected if The /jeewms_war/webpage/system/druid/ endpoint is present and reachable
  3. Test unauthenticated access to Druid console
    Attempt to access the Druid monitoring interface directly without providing any credentials or session token
    Affected if The Druid console loads and displays monitoring data without requiring authentication
  4. Check Druid console configuration
    Inspect the Druid configuration files (typically in WEB-INF/classes or application properties) for druid.web.username, druid.web.password settings, and verify if enable=true for the DruidStatView servlet
    Affected if Druid console is enabled without proper authentication enforcement or authentication is disabled in config
  5. Assess network exposure
    Verify if the Druid endpoint is accessible from untrusted networks by testing external IP access or reviewing firewall/load balancer rules
    Affected if The interface is accessible from public or untrusted networks without network-level access controls

If Jeewms is installed and the Druid console at /jeewms_war/webpage/system/druid/ is accessible without authentication, the environment is vulnerable to CVE-2024-12347.

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

Restrict or disable the Druid monitoring interface in production environments through network access controls, authentication requirements, or complete removal of the exposed endpoint.

Fix this in Jeewms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12347 — 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-12347 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