CVE-2022-2272
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 · uneditedThis vulnerability allows remote attackers to bypass authentication on affected installations of Sante PACS Server 3.0.4. Authentication is not required to exploit this vulnerability. The specific flaw exists within the processing of calls to the login endpoint. When parsing the username element, the process does not properly validate a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-17331.
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 vulnerability in the Sante PACS Server login endpoint allows remote attackers to bypass authentication by injecting malicious SQL through the username parameter. The application fails to validate user-supplied input before constructing SQL queries, enabling attackers to manipulate query logic and gain unauthorized access without valid credentials.
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.0.4CVSS 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.1/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 Sante PACS Server installationLocate the Sante PACS Server application on the system - check for installation directories, services, or running processes named 'Sante PACS', 'SantePacsServer', or similar. On Windows, check Program Files; on Linux, check /opt or standard application directories.Affected if The software is not present or is a different product entirely, then not affected.
-
Determine installed versionAccess the application's version information through its administrative interface, about page, or check installation manifests/config files for version metadata. Compare the found version to the affected version 3.0.4.Affected if The installed version is exactly 3.0.4 - this is the specific affected version.
-
Verify login endpoint is accessibleConfirm the web-based login interface or API endpoint for Sante PACS Server is accessible on the network. Check if the application exposes its authentication service externally or internally via HTTP/HTTPS.Affected if The login endpoint is not exposed or not accessible, the attack surface may be reduced but the software vulnerability still exists in the code.
-
Check for recent security updatesReview the application's change logs, release notes, or vendor security advisories to determine if version 3.0.4 has been patched. Look for entries mentioning SQL injection, authentication bypass, or CVE-2022-2272.Affected if The software remains at version 3.0.4 with no security patches applied - the vulnerability is present.
The environment is affected if Santesoft Sante PACS Server version 3.0.4 is installed and the login endpoint is accessible, regardless of network exposure the SQL injection vulnerability exists in the code.
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.
From vendor dataImplement parameterized queries or prepared statements for all database operations, especially authentication-related queries. Additionally, implement strict input validation on the username field and apply vendor-supplied patches if available.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2272 — 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-2022-2272 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