dbcve.org
Code42Application

CVE-2021-43269

HIGH · 8.8 CVSS v3.1 Published 2022-01-20
Fix available
A fix is available. Upgrade to 8.8.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
In Code42 app before 8.8.0, eval injection allows an attacker to change a device’s proxy configuration to use a malicious proxy auto-config (PAC) file, leading to arbitrary code execution. This affects Incydr Basic, Advanced, and Gov F1; CrashPlan Cloud; and CrashPlan for Small Business. (Incydr Professional and Enterprise are unaffected.)

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

Eval injection vulnerability in Code42 app versions before 8.8.0 allows authenticated attackers to modify device proxy configuration to point to a malicious proxy auto-config (PAC) file, which can then execute arbitrary code on the affected device.

MitigationUpgrade Code42 app to version 8.8.0 or later. Until patched, monitor for unauthorized proxy configuration changes and restrict network access to trusted proxy servers.

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
Code42Application
Affected:< 8.8.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. Check if Code42 app is installed
    Search for Code42 executable or service. On Windows, check Program Files for Code42.exe or look for the Code42 service in Services. On Mac, check /Applications for Code42.app.
    Affected if Code42 app is present on the system
  2. Determine installed Code42 version
    Locate and read the version information from the Code42 app installation. On Windows, right-click Code42.exe and select Properties, then view the Details tab for Version. On Mac, right-click Code42.app, select Get Info, and check the Version field.
    Affected if Installed version is before 8.8.0
  3. Inspect proxy configuration
    Examine the system proxy settings or Code42-specific proxy configuration. On Windows, go to Settings > Network & Internet > Proxy. On Mac, go to System Preferences > Network > Advanced > Proxies. Also check Code42 configuration files for proxy settings.
    Affected if Proxy configuration is enabled and points to an external or unexpected PAC file URL
  4. Review PAC file location
    If proxy is configured with a PAC file, note the URL or file path specified. Validate that it points to a trusted internal server rather than an external or suspicious location.
    Affected if The PAC file URL points to an untrusted or unknown server

A system is affected if the Code42 app version is before 8.8.0 and proxy configuration with a PAC file is enabled pointing to an untrusted location, allowing potential code execution via a malicious PAC file.

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

Upgrade Code42 app to version 8.8.0 or later. Until patched, monitor for unauthorized proxy configuration changes and restrict network access to trusted proxy servers.

Recommended fix Moderate confidence

8.8.0

  1. Check the current version of the Code42 app installed on the device (typically found in the app's About or Settings section)
  2. Navigate to the Code42 support portal at support.code42.com and locate the download for version 8.8.0 or later
  3. Download the appropriate installer for your operating system
  4. Run the installer to upgrade the Code42 app to version 8.8.0 or later
  5. After upgrading, verify the new version is reflected in the app's About section
  6. For managed deployments, ensure the updated version is pushed to all affected devices

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

Fix this in Code42 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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