dbcve.org
DolphinschedulerApplication · Apache

CVE-2023-48796

HIGH · 7.5 CVSS v3.1 Published 2023-11-24
Fix available
A fix is available. Upgrade to 3.0.2 or later.
See remediation →
84/100
Remediation priority · High
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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache DolphinScheduler. The information exposed to unauthorized actors may include sensitive data such as database credentials. Users who can't upgrade to the fixed version can also set environment variable `MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE=health,metrics,prometheus` to workaround this, or add the following section in the `application.yaml` file ``` management:   endpoints:     web:       exposure:         include: health,metrics,prometheus ``` This issue affects Apache DolphinScheduler: from 3.0.0 before 3.0.2. Users are recommended to upgrade to version 3.0.2, which fixes the issue.

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

Apache DolphinScheduler versions 3.0.0 through before 3.0.2 expose management endpoints to unauthorized actors by default, potentially leaking sensitive information including database credentials. This occurs because the Spring Boot management endpoints are exposed without proper access controls.

MitigationUpgrade to version 3.0.2 or apply the documented workaround by restricting management endpoint exposure to only health, metrics, and prometheus endpoints via environment variable or application.yaml configuration.

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
DolphinschedulerApplication
Affected:>= 3.0.0, < 3.0.2

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Check installed DolphinScheduler version
    Locate the version file or check the Docker image tag. Common locations: look for a VERSION file in the installation directory, check docker-compose.yml for image tags, or check pom.xml if source-built. Command example: grep -r 'version' <install-dir>/conf/ or docker images | grep dolphinscheduler
    Affected if version is 3.0.0, 3.0.1, or 3.1.x (any version >= 3.0.0 and < 3.0.2)
  2. Verify management endpoint exposure configuration
    Examine the application.yaml or application.properties file in the config directory. Look for property: management.endpoints.web.exposure.include. If this property is absent, Spring Boot exposes all endpoints by default. Also check for management.endpoints.web.base-path.
    Affected if management.endpoints.web.exposure.include is not set, or includes sensitive endpoints like 'env', 'heapdump', 'configprops', or is set to '*' (wildcard)
  3. Confirm network accessibility of management endpoints
    Test if management endpoints respond on the network. Common endpoints: /actuator/health, /actuator/env, /actuator/heapdump, /actuator/configprops. Use curl or a browser to check: curl -k http://<host>:<port>/actuator/env
    Affected if management endpoints are reachable from untrusted network locations or the public internet

You are affected if running DolphinScheduler version 3.0.0 or 3.0.1 AND management endpoints are exposed (either by default configuration or explicit misconfiguration) to untrusted network access.

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.

dbcve · scoped
Upgrade available Upgrade to 3.0.2 or later
Fixed in 3.0.2
Interim mitigation

Upgrade to version 3.0.2 or apply the documented workaround by restricting management endpoint exposure to only health, metrics, and prometheus endpoints via environment variable or application.yaml configuration.

Recommended fix High confidence

3.0.2

  1. Upgrade Apache DolphinScheduler from version 3.0.0-3.0.1 to version 3.0.2 to resolve the sensitive information exposure vulnerability
  2. If immediate upgrade is not possible, apply one of the workarounds: Set environment variable `MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE=health,metrics,prometheus` on the host running DolphinScheduler
  3. Alternatively, add the following configuration to the `application.yaml` file under the `management.endpoints.web.exposure` section: `include: health,metrics,prometheus`
  4. After applying the workaround or upgrade, verify that sensitive information such as database credentials is no longer exposed through the management endpoints

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dolphinscheduler Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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