Quartus PrimeApplication · Intel

CVE-2022-33892

HIGH · 7.8 CVSS v3.1 Published 2023-02-16
Fix available
A fix is available. Upgrade to 22.1 / 22.2 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
Path traversal in the Intel(R) Quartus Prime Pro and Standard edition software 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 · moderate confidence

A path traversal vulnerability in Intel Quartus Prime Pro and Standard edition software allows an authenticated local user to escape the intended directory restrictions and access files outside the restricted path, potentially leading to privilege escalation.

MitigationApply the Intel-provided security update for Quartus Prime Pro and Standard editions. Until patched, limit local access to trusted authenticated users only and monitor for unauthorized file access attempts.

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.1< 22.2

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. Locate Intel Quartus Prime installation
    Search for 'quartus' or 'intel' directories in common installation paths such as C:\Program Files\Intel or /opt/intel, or check for Quartus Prime executable in system PATH
    Affected if Quartus Prime software is found on the system
  2. Determine installed Quartus Prime version
    Run 'quartus_sh --version' from the installation directory, or check the 'version.txt' or 'qii_version.txt' file typically located in the Quartus installation root folder
    Affected if Version number returned is below 22.1 for Pro edition or below 22.2 for Standard edition
  3. Verify Quartus Prime edition type
    Check the edition in the installation directory name or version information (look for 'Pro' or 'Standard' in the path or version file)
    Affected if Edition is Pro and version < 22.1, or Edition is Standard and version < 22.2
  4. Confirm local authenticated access exists
    Verify that local user accounts exist on the system with permissions to run Quartus Prime software
    Affected if Local authenticated users have access to run Quartus Prime applications

System is affected if Intel Quartus Prime Pro < 22.1 or Standard < 22.2 is installed and local authenticated users can access the software.

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.1 / 22.2 or later
Fixed in 22.122.2
Interim mitigation

Apply the Intel-provided security update for Quartus Prime Pro and Standard editions. Until patched, limit local access to trusted authenticated users only and monitor for unauthorized file access attempts.

Recommended fix Moderate confidence

Quartus Prime Pro >= 22.1, Quartus Prime Standard >= 22.2

  1. 1. Identify which Quartus Prime edition is installed (Pro or Standard) by opening the Quartus Prime software and checking the welcome screen or Help > About
  2. 2. For Quartus Prime Pro edition: Download and install version 22.1 or later from the Intel FPGA download center
  3. 3. For Quartus Prime Standard edition: Download and install version 22.2 or later from the Intel FPGA download center
  4. 4. Ensure the upgrade is performed by an administrator with appropriate local access permissions
  5. 5. After installation, verify the version by checking Help > About in the Quartus Prime software
Caveat Review Intel Quartus Prime release notes for version 22.1/22.2 for any design migration requirements or deprecated features before upgrading

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

Fix this in Quartus Prime Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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