Pacs ServerApplication · Meddream

CVE-2025-3480

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
MedDream WEB DICOM Viewer Cleartext Transmission of Credentials Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of MedDream WEB DICOM Viewer. Authentication is not required to exploit this vulnerability. The specific flaw exists within the Web Portal. The issue results from the lack of encryption when transmitting credentials. An attacker can leverage this vulnerability to disclose transmitted credentials, leading to further compromise. Was ZDI-CAN-25842.

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

MedDream WEB DICOM Viewer transmits user credentials in cleartext (unencrypted) over the network. An attacker with network adjacency can intercept these credentials by sniffing network traffic. The vulnerability exists in the Web Portal component where authentication data is sent without TLS encryption.

MitigationEnable HTTPS/TLS encryption on the MedDream WEB DICOM Viewer web server and ensure all authentication endpoints require encrypted connections. Configure the web server to enforce TLS 1.2+ and disable cleartext HTTP access.

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
Pacs ServerApplication
Affected:= 7.3.2.840

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

CVSS:3.1/AV:A/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. Identify MedDream Pacs Server version
    Locate the MedDream installation directory and check the version file or application metadata. Common locations include the root installation folder or within the 'About' section of the web interface.
    Affected if The installed version is exactly 7.3.2.840
  2. Verify web server configuration for TLS/SSL
    Examine the web server configuration files (e.g., nginx.conf, httpd.conf, or the application's config files) to determine if HTTPS/TLS is enabled and configured.
    Affected if TLS/SSL is not enabled or not properly configured for the web portal
  3. Test for cleartext HTTP access
    Attempt to access the MedDream web portal using HTTP (port 80) without encryption. Use a browser or curl command to http://<server>:<port> and observe if the login page loads over unencrypted connection.
    Affected if The web portal is accessible over HTTP without redirecting to HTTPS
  4. Capture network traffic during authentication
    Use a network sniffer (such as Wireshark or tcpdump) to capture traffic while submitting login credentials to the MedDream portal. Analyze the captured packets to identify if credentials are transmitted in plaintext.
    Affected if Login credentials are observed in cleartext within the captured network packets

You are affected if you are running MedDream Pacs Server version 7.3.2.840 AND the web portal accepts unencrypted HTTP connections with credentials transmitted in cleartext.

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

Enable HTTPS/TLS encryption on the MedDream WEB DICOM Viewer web server and ensure all authentication endpoints require encrypted connections. Configure the web server to enforce TLS 1.2+ and disable cleartext HTTP access.

Fix this in Pacs Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-3480 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