dbcve.org
OrthancApplication · Orthanc Server

CVE-2023-33466

HIGH · 8.8 CVSS v3.1 Published 2023-06-29
Fix available
A fix is available. Upgrade to 1.12.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Orthanc before 1.12.0 allows authenticated users with access to the Orthanc API to overwrite arbitrary files on the file system, and in specific deployment scenarios allows the attacker to overwrite the configuration, which can be exploited to trigger Remote Code Execution (RCE).

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

Orthanc before 1.12.0 contains a path traversal vulnerability allowing authenticated API users to write arbitrary files to the filesystem. In certain deployment configurations, attackers can overwrite configuration files, leading to remote code execution.

MitigationUpgrade to Orthanc 1.12.0 or later. Review API access controls and monitor for unauthorized configuration changes.

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
OrthancApplication
Affected:< 1.12.0

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Orthanc version
    Locate the installed Orthanc Server version (typically via the /system endpoint in the REST API, or check the software version displayed in the Orthanc Explorer web interface, or review the package/changelog documentation from the installation source)
    Affected if The installed version is any release before 1.12.0 (e.g., 1.11.x, 1.10.x, earlier)
  2. Confirm API access is enabled
    Verify that the Orthanc REST API is accessible (by default on ports 8042 or 8043). Check the configuration file for 'HttpPort' or 'HttpSecurePort' settings, or test connectivity to the /tools/echo endpoint
    Affected if The REST API port is open and reachable from untrusted networks, or the API is exposed without network segmentation
  3. Review authentication configuration
    Inspect the Orthanc configuration file for 'AuthenticationEnabled' setting and verify whether the 'RegisteredUsers' option is configured with strong, restricted credentials
    Affected if Authentication is disabled (AuthenticationEnabled set to false) or weak/blank credentials are configured, allowing anonymous or trivial API access

You are affected if Orthanc Server is installed at a version earlier than 1.12.0 AND the REST API is accessible with authenticated user access that could be exploited for path traversal.

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

Upgrade to Orthanc 1.12.0 or later. Review API access controls and monitor for unauthorized configuration changes.

Recommended fix High confidence

1.12.0

  1. Download Orthanc version 1.12.0 or later from the official Orthanc server website or your distribution's package repository
  2. Stop the Orthanc service before upgrading
  3. Upgrade the Orthanc package using your system's package manager (e.g., apt-get update && apt-get install orthanc, or yum/dnf update orthanc)
  4. Verify the new version is installed by checking orthanc --version
  5. Review the Orthanc 1.12.0 release notes for any configuration changes that may affect your deployment
  6. Restart the Orthanc service
  7. Verify the service is running correctly and accessible
Caveat Review the 1.12.0 release notes for any configuration or API changes that may require adjustments to your existing setup

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

Fix this in Orthanc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
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,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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