CVE-2021-35482
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 · uneditedAn issue was discovered in Barco MirrorOp Windows Sender before 2.5.4.70. An attacker in the local network is able to achieve Remote Code Execution (with user privileges of the local user) on any device that tries to connect to a WePresent presentation system.
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 confidenceBarco MirrorOp Windows Sender before version 2.5.4.70 contains a vulnerability allowing a local network attacker to execute arbitrary code with the privileges of the local user on any device attempting to connect to a WePresent presentation system. The attack does not require authentication and can be carried out by anyone with network proximity to the WePresent device.
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< 2.5.4.70CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Barco MirrorOp Windows Sender is installedCheck the list of installed programs on the Windows system for 'MirrorOp Windows Sender' or 'Barco MirrorOp' entryAffected if The software is listed as installed on the system
-
Determine the installed version of MirrorOp Windows SenderLocate the MirrorOp Windows Sender installation directory and check the version information of the executable (typically sender.exe or similar), or right-click the application in Add/Remove Programs to view version detailsAffected if The displayed version number is less than 2.5.4.70
-
Verify the product executable versionNavigate to the installation folder (commonly under Program Files or Program Files x86) and locate the main executable. Right-click the .exe file, select Properties, and view the File Version fieldAffected if The file version shown is earlier than 2.5.4.70
-
Confirm usage context with WePresent devicesCheck if the MirrorOp Sender software is configured to connect to any WePresent IP addresses or hostnames, or review any connection logs or configurations that show WePresent device associationsAffected if The system is configured to connect to WePresent presentation systems on the local network
A system is affected if Barco MirrorOp Windows Sender is installed with a version lower than 2.5.4.70 and is used or configured to connect to WePresent presentation devices on the network.
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 data2.5.4.70
Upgrade Barco MirrorOp Windows Sender to version 2.5.4.70 or later. Additionally, network segmentation and isolating WePresent devices on a restricted VLAN can reduce exposure to untrusted network attackers.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35482 — 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-2021-35482 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