dbcve.org
Container StationOperating system · Qnap

CVE-2023-32976

HIGH · 7.2 CVSS v3.1 Published 2023-10-13
Fix available
A fix is available. Upgrade to 2.6.7.44 or later.
See remediation →
78/100
Remediation priority · High
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
An OS command injection vulnerability has been reported to affect Container Station. If exploited, the vulnerability could allow authenticated administrators to execute commands via a network. We have already fixed the vulnerability in the following version: Container Station 2.6.7.44 and later

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

QNAP Container Station contains an OS command injection vulnerability that allows authenticated administrators to execute arbitrary operating system commands via network requests. The vulnerability stems from improper input validation when processing user-supplied data that gets passed to system shell execution.

MitigationUpdate Container Station to version 2.6.7.44 or later. Restrict administrative access to trusted personnel only until the patch is applied.

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
Container StationOperating system
Affected:< 2.6.7.44

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm Container Station is installed
    Log into QNAP QTS and open App Center, or use the command ' Container Station --version' via QNAP's command line interface (SSH)
    Affected if Container Station appears in the installed applications list or the version command returns a value
  2. Check the installed version number
    In QTS App Center, click on Container Station and view the version information; or via CLI run 'container-station --version' to retrieve the exact version
    Affected if The version displayed is lower than 2.6.7.44 (e.g., 2.6.6.x, 2.5.x, etc.)
  3. Verify the web management interface is accessible
    Attempt to access the Container Station web interface via the QNAP IP (typically port 8080 or 8081 for the QTS login, then navigate to Container Station)
    Affected if The Container Station web portal is reachable and accepts administrator credentials
  4. Confirm administrative authentication is enabled
    Log into the QNAP admin interface and verify that Container Station requires authenticated administrator access to use its features
    Affected if The application requires a valid administrator username and password to access Container Station functions

If Container Station is installed and its version is below 2.6.7.44, and the web management interface is accessible with administrator credentials, the environment is potentially affected by this OS command injection vulnerability.

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

Update Container Station to version 2.6.7.44 or later. Restrict administrative access to trusted personnel only until the patch is applied.

Recommended fix High confidence

Container Station 2.6.7.44

  1. Log in to the QNAP NAS as an administrator
  2. Open Container Station from the QTS desktop or App Center
  3. Navigate to the settings or check for updates
  4. If Container Station version is below 2.6.7.44, update to version 2.6.7.44 or later
  5. Verify the update was successful by checking the installed version

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

Fix this in Container Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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