dbcve.org
ConnectApplication · Openvpn

CVE-2022-3761

MEDIUM · 5.9 CVSS v3.1 Published 2023-10-17
Fix available
A fix is available. Upgrade to 3.4.0.3121 / 3.4.0.4506 or later.
See remediation →
68/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
OpenVPN Connect versions before 3.4.0.4506 (macOS) and OpenVPN Connect before 3.4.0.3100 (Windows) allows man-in-the-middle attackers to intercept configuration profile download requests which contains the users credentials

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

OpenVPN Connect before version 3.4.0.4506 (macOS) and 3.4.0.3100 (Windows) fails to secure configuration profile download requests, allowing man-in-the-middle attackers to intercept network traffic containing user credentials during the profile download process.

MitigationUpdate OpenVPN Connect to version 3.4.0.4506 or later on macOS and version 3.4.0.3100 or later on Windows. Avoid using untrusted networks when downloading configuration profiles until the update 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
ConnectApplication
Affected:< 3.4.0.3121< 3.4.0.4506

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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. Check OpenVPN Connect version on Windows
    Open Control Panel > Programs and Features, find OpenVPN Connect, and note the version. Alternatively, right-click the OpenVPN Connect executable in Program Files, select Properties, and check the File Version.
    Affected if The version is less than 3.4.0.3100 on Windows.
  2. Check OpenVPN Connect version on macOS
    Open Finder, navigate to Applications, right-click OpenVPN Connect, select Get Info, and check the Version field. Alternatively, run 'defaults read /Applications/OpenVPN\ Connect.app/Contents/Info.plist CFBundleShortVersionString' in Terminal.
    Affected if The version is less than 3.4.0.4506 on macOS.
  3. Verify if configuration profile downloads occur
    Review whether OpenVPN Connect is used to import or download VPN configuration profiles. Check the connection logs or profile import history in the application.
    Affected if The user imports or downloads VPN configuration profiles while using a vulnerable version.
  4. Assess network exposure during profile downloads
    Determine if profile downloads were performed on untrusted or public networks (e.g., coffee shop WiFi, hotel networks) where MITM attacks could occur.
    Affected if Profile downloads were performed on untrusted networks with a vulnerable version.

A user is affected if OpenVPN Connect version is below 3.4.0.3100 on Windows or below 3.4.0.4506 on macOS, and configuration profiles containing credentials were downloaded over an untrusted network.

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.4.0.3121 / 3.4.0.4506 or later
Fixed in 3.4.0.31213.4.0.4506
Interim mitigation

Update OpenVPN Connect to version 3.4.0.4506 or later on macOS and version 3.4.0.3100 or later on Windows. Avoid using untrusted networks when downloading configuration profiles until the update is applied.

Recommended fix High confidence

OpenVPN Connect 3.4.0.3100 (Windows) or 3.4.0.4506 (macOS)

  1. 1. Identify the operating system (Windows or macOS) where OpenVPN Connect is installed
  2. 2. For Windows users: Navigate to the official OpenVPN Connect download page and upgrade to version 3.4.0.3100 or later
  3. 3. For macOS users: Navigate to the official OpenVPN Connect download page and upgrade to version 3.4.0.4506 or later
  4. 4. Verify the installed version by checking the application properties or About section
  5. 5. Re-download and import any configuration profiles to ensure they are fetched over a properly validated connection

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

Fix this in Connect Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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