dbcve.org
Quartus PrimeApplication · Intel

CVE-2022-32570

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
Improper authentication 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

Improper authentication in Intel Quartus Prime Pro and Standard edition software allows an authenticated local user to escalate privileges. This vulnerability in the authentication mechanism permits a user who already has valid credentials to gain higher-level access than intended.

MitigationApply Intel-provided patches for Quartus Prime when available. Restrict local access to the software to trusted, authorized users only and implement least-privilege principles.

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. Verify Intel Quartus Prime is installed
    Check the system for Intel Quartus Prime Pro or Standard edition software installation - look in standard application installation directories or use system inventory tools
    Affected if Intel Quartus Prime Pro or Standard edition software is found on the system
  2. Determine the installed version of Quartus Prime
    Locate and inspect the installed Quartus Prime version information - typically found in the software's About section, installation directory, or version metadata files
    Affected if The installed version is earlier than 22.1 or earlier than 22.2 (for Pro edition)
  3. Confirm local authentication is enabled
    Verify that local user authentication for Quartus Prime is configured and active - check the authentication mechanism settings within the software or system
    Affected if Local user authentication is enabled and users have valid credentials to log in
  4. Identify local user privileges
    Review which local users have valid Quartus Prime credentials and determine their current privilege level within the software
    Affected if There are authenticated local users who may have lower privilege access than they could escalate to

A user is affected if Intel Quartus Prime (Pro or Standard edition) is installed with a version lower than 22.1 or 22.2 and local user authentication is enabled, allowing a validated local user to potentially escalate privileges beyond their intended access level.

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 Intel-provided patches for Quartus Prime when available. Restrict local access to the software to trusted, authorized users only and implement least-privilege principles.

Recommended fix Moderate confidence

Intel Quartus Prime version 22.1 or later (Pro and Standard editions)

  1. 1. Identify the current installed version of Intel Quartus Prime (Pro or Standard edition) using the Quartus Prime software or system information
  2. 2. Download Intel Quartus Prime version 22.1 or later from the official Intel website (intel.com) or through your existing Intel distribution
  3. 3. Verify the installer matches your edition (Pro or Standard) and target operating system
  4. 4. Close all Quartus Prime-related applications and tools
  5. 5. Run the installer and follow the on-screen prompts to upgrade the software
  6. 6. After installation, verify the new version is correctly installed by checking the Quartus Prime version information
  7. 7. Test that your existing projects and workflows function correctly with the upgraded version
Caveat Standard upgrade process; ensure project compatibility with the new version before migrating production projects

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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