dbcve.org
Quartus PrimeApplication · Intel

CVE-2022-41693

HIGH · 7.8 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to 22.3 or later.
See remediation →
80/100
Remediation priority · High
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
Uncontrolled search path in the Intel(R) Quartus(R) Prime Pro edition software before version 22.3 may allow an authenticated user to potentially enable escalation of privilege via local access.

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

Intel Quartus Prime Pro edition software before version 22.3 contains an uncontrolled search path vulnerability that allows an authenticated local user to potentially escalate privileges by placing malicious files in locations the application searches for resources.

MitigationUpgrade to Intel Quartus Prime Pro version 22.3 or later to remediate 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
Quartus PrimeApplication
Affected:< 22.3

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Intel Quartus Prime Pro is installed
    Check for the presence of Intel Quartus Prime Pro in the system. On Windows, look in the default installation directory (typically C:\intelFPGA_pro\) or check Programs and Features in Control Panel for an entry named 'Intel Quartus Prime Pro Edition'.
    Affected if Intel Quartus Prime Pro is found installed on the system.
  2. Locate the installed version number
    Navigate to the Intel Quartus Prime Pro installation directory (e.g., C:\intelFPGA_pro\quartus\) and locate the version information. The version is often stored in a README, version.txt file, or can be obtained by running 'quartus_sh --version' or 'quartus --version' from the installation's bin64 directory.
    Affected if The version cannot be determined or the retrieved version is below 22.3.
  3. Compare installed version against the affected range
    Review the discovered version number against the affected range (versions before 22.3). Intel Quartus Prime Pro versions are typically formatted as major.minor (e.g., 22.2, 22.1, 21.4). Any version number lower than 22.3 indicates the system is running a vulnerable version.
    Affected if The installed version is any release prior to 22.3 (e.g., 22.2, 22.1, 21.4, 21.3, etc.).

A system is affected if Intel Quartus Prime Pro Edition software is installed and the installed version is any release prior to version 22.3.

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

Upgrade to Intel Quartus Prime Pro version 22.3 or later to remediate this vulnerability.

Recommended fix High confidence

Quartus Prime Pro edition 22.3

  1. 1. Uninstall the current version of Intel(R) Quartus(R) Prime Pro edition software that is prior to version 22.3
  2. 2. Navigate to the official Intel website (intel.com) or Intel FPGA download page to obtain Quartus Prime Pro edition version 22.3 or later
  3. 3. Download the installer for Quartus Prime Pro edition version 22.3
  4. 4. Verify the integrity of the downloaded installer using checksums if provided
  5. 5. Run the installer and follow the installation wizard to install the fixed version
  6. 6. After installation, verify that the installed version is 22.3 or later by checking the Quartus Prime software version

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

Fix this in Quartus Prime Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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