Control Room Management SuiteApplication · Barco

CVE-2022-26973

MEDIUM · 5.3 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to 3.14.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Barco Control Room Management Suite web application, which is part of TransForm N before 3.14, is exposing a license file upload mechanism. By tweaking the license file name, the returned error message exposes internal directory path details.

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

Barco TransForm N before version 3.14 contains a license file upload mechanism that exposes internal directory path details through error messages when the license filename is manipulated. This path disclosure vulnerability has a CVSS score of 5.3, indicating an information disclosure risk that could aid further attacks.

MitigationUpgrade TransForm N to version 3.14 or later, which contains the security fix for this vulnerability.

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
Control Room Management SuiteApplication
Affected:< 3.14.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 if Barco TransForm N is installed
    Check the installed applications or program directory for Barco TransForm N or Barco Control Room Management Suite components
    Affected if The software is present on the system but version cannot be determined or is below 3.14.1
  2. Determine the installed TransForm N version
    Locate the TransForm N installation directory and check version information in the application metadata, about dialog, or version file
    Affected if The installed version is below 3.14.1 (or 3.14) and the product is Barco TransForm N or Barco Control Room Management Suite
  3. Verify the license upload feature is accessible
    Access the TransForm N web interface or administrative portal and locate the license file upload mechanism
    Affected if The license upload interface is exposed and accessible to users
  4. Check for path disclosure in license upload errors
    Attempt to upload a license file with a manipulated filename (such as adding path traversal characters or unusual extensions) and observe any error messages returned
    Affected if Error messages reveal internal directory paths or file system structure

You are affected if Barco TransForm N or Barco Control Room Management Suite is installed with a version below 3.14.1 and the license upload feature is accessible, as the manipulated filename will cause internal path disclosure in error responses.

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

Upgrade TransForm N to version 3.14 or later, which contains the security fix for this vulnerability.

Recommended fix Moderate confidence

3.14.1 or later

  1. 1. Back up the current Barco Control Room Management Suite installation and configuration
  2. 2. Verify backup integrity before proceeding
  3. 3. Download Control Room Management Suite version 3.14.1 or later from the official Barco support portal
  4. 4. Install the upgrade following Barco's standard upgrade procedure
  5. 5. Verify the license file upload functionality works correctly
  6. 6. Confirm that error messages no longer expose internal directory path information

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

Fix this in Control Room Management Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26973 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26973 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