dbcve.org
Pacs ServerApplication · Meddream

CVE-2025-3483

HIGH · 7.8 CVSS v3.1 Published 2025-05-22
Fix available
A fix is available. Upgrade to 7.3.5.860 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 PACS Server DICOM File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of MedDream PACS Server. Authentication is not required to exploit this vulnerability. The specific flaw exists within the parsing of DICOM files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-25825.

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

Stack-based buffer overflow vulnerability in MedDream PACS Server's DICOM file parsing function. The flaw results from insufficient validation of user-supplied data length before copying to a fixed-size stack buffer, allowing remote unauthenticated attackers to execute arbitrary code in the context of the service account.

MitigationApply vendor-supplied patches for MedDream PACS Server when available. Until patched, restrict network access to PACS services and implement network segmentation to limit exposure to untrusted networks.

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.5.860

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 MedDream PACS Server installation
    Locate the MedDream PACS Server installation directory and find the version information file or use the product's built-in version query mechanism (typically available via the admin interface or a version info endpoint)
    Affected if The installed version is below 7.3.5.860
  2. Verify DICOM parsing functionality is accessible
    Confirm that the DICOM parsing service endpoint/module is enabled and accepting connections. This is typically exposed via the PACS server's DICOM listener port (commonly port 104 or configured custom port)
    Affected if The DICOM service is exposed and processing incoming DICOM files without additional authentication layers
  3. Check network accessibility of PACS service
    Review firewall rules and network configuration to determine if the PACS DICOM service port is accessible from untrusted network segments or the internet
    Affected if The service is reachable from untrusted networks or the internet without network segmentation or access controls
  4. Confirm service account context
    Identify the Windows service or Linux daemon running MedDream PACS Server and note the account it executes under (visible in Services.msc on Windows or via 'ps' command on Linux)
    Affected if The service runs under a privileged account (such as SYSTEM, root, or any account with elevated permissions), meaning successful exploitation would grant those privileges

You are affected if your MedDream PACS Server version is below 7.3.5.860 AND the DICOM parsing service is accessible to untrusted networks.

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 7.3.5.860 or later
Fixed in 7.3.5.860
Interim mitigation

Apply vendor-supplied patches for MedDream PACS Server when available. Until patched, restrict network access to PACS services and implement network segmentation to limit exposure to untrusted networks.

Recommended fix High confidence

MedDream PACS Server 7.3.5.860 or later

  1. 1. Identify the current MedDream PACS Server version installed in your environment
  2. 2. Download MedDream PACS Server version 7.3.5.860 or later from the official vendor (Softneta or authorized distributor)
  3. 3. Review vendor release notes and migration documentation for version 7.3.5.860
  4. 4. Create a full backup of the current PACS Server configuration, database, and DICOM data
  5. 5. Schedule a maintenance window as the upgrade may require service interruption
  6. 6. Stop the MedDream PACS Server service
  7. 7. Install version 7.3.5.860 or later following the vendor's upgrade procedure
  8. 8. Verify the service starts successfully
Caveat Standard minor version upgrade - review release notes for any configuration changes; test in non-production environment first

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

Fix this in Pacs Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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