CVE-2024-1863
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 · uneditedSante PACS Server Token Endpoint SQL Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Sante PACS Server. Authentication is not required to exploit this vulnerability. The specific flaw exists within the processing of HTTP requests on port 3000. When parsing the token parameter, the process does not properly validate a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of NETWORK SERVICE. Was ZDI-CAN-21539.
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 confidenceSQL injection in Sante PACS Server's token endpoint (port 3000) allows remote attackers to inject malicious SQL queries via the token parameter without authentication, leading to remote code execution in the context of NETWORK SERVICE.
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< 3.3.6CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Sante PACS Server is installedLook for Sante PACS Server process or service running on the system, or check for installation directories commonly used by Santesoft productsAffected if Sante PACS Server is found running on the system
-
Check the installed versionLocate the version information for Sante PACS Server (typically in application files, registry, or about dialog) and compare it to the affected range: versions prior to 3.3.6 are vulnerableAffected if Installed version is lower than 3.3.6
-
Verify if port 3000 is exposedUse netstat, nmap, or PowerShell to check if port 3000 is listening on network interfaces, especially external or untrusted interfacesAffected if Port 3000 is open and accessible from network
-
Test token endpoint accessibilitySend an HTTP request to the token endpoint (typically /token or /api/token on port 3000) without credentials to verify if the endpoint responds without authenticationAffected if Token endpoint responds without requiring authentication
-
Review access logs for suspicious token parameter patternsExamine HTTP access logs for the token endpoint for unusual or SQL injection patterns in the token parameterAffected if Logs show attempts with SQL-like characters or patterns in token parameter
Environment is affected if Sante PACS Server version is below 3.3.6 and the token endpoint on port 3000 is accessible from the network without authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.3.6
Apply vendor patch when available; as interim measure, restrict network access to port 3000 and implement WAF rules to block suspicious token parameter patterns until proper fix is deployed.
Sante PACS Server 3.3.6 or later
- 1. Back up your current Sante PACS Server configuration and database before proceeding with any upgrade.
- 2. Download Sante PACS Server version 3.3.6 or later from the official Sante PACS vendor website.
- 3. Install the upgrade following the vendor's standard upgrade procedure.
- 4. Verify the upgrade was successful by checking the installed version number.
- 5. Confirm the token endpoint on port 3000 is now properly validating input and not vulnerable to SQL injection.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1863 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1863 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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