InstallshieldApplication · Flexera

CVE-2023-29081

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
A vulnerability has been reported in Suite Setups built with versions prior to InstallShield 2023 R2. This vulnerability may allow locally authenticated users to cause a Denial of Service (DoS) condition when handling move operations on local, temporary folders.

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

InstallShield versions prior to 2023 R2 contain a vulnerability in their Suite Setups component where handling move operations on local temporary folders can be exploited by locally authenticated users to cause a Denial of Service condition.

MitigationUpgrade InstallShield to version 2023 R2 or later, and rebuild any existing Suite Setups using the patched version.

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
InstallshieldApplication
Affected:= 2016= 2017= 2018= 2019= 2020= 2021= 2022= 2023

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 InstallShield is installed
    Check Windows Programs and Features (Control Panel > Programs > Programs and Features) or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'InstallShield' or 'Flexera InstallShield'
    Affected if InstallShield appears in the installed programs list
  2. Determine the installed version number
    In Programs and Features, locate the InstallShield entry and note the version shown (for example: 2016, 2017, 2018, 2019, 2020, 2021, 2022, or 2023)
    Affected if The version is any of 2016, 2017, 2018, 2019, 2020, 2021, 2022, or 2023 (versions prior to 2023 R2)
  3. Confirm Suite Setups component is in use
    Search for .issuite project files or Setup.exe files built with the Suite Setup template in your development or build environment
    Affected if Suite Setups (.issuite projects) exist and are configured to run on affected versions of InstallShield
  4. Check for temporary folder operations in setup configurations
    Review the Suite Setup project settings in InstallShield, specifically under 'Temporary Files' or 'Move Operations' in the Direct Editor or Property Manager view
    Affected if Temporary folder move operations are configured and the InstallShield version is in the affected range

A system is affected if InstallShield version 2016 through 2023 (any release prior to 2023 R2) is installed and Suite Setups with temporary folder move operations are being used.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade InstallShield to version 2023 R2 or later, and rebuild any existing Suite Setups using the patched version.

Recommended fix High confidence

InstallShield 2023 R2 or later

  1. 1. Identify all systems running InstallShield versions 2016, 2017, 2018, or 2019
  2. 2. Verify the current InstallShield version by opening the IDE and checking Help > About InstallShield
  3. 3. Download InstallShield 2023 R2 (or later) from the Flexera Customer Portal or official download channels
  4. 4. Run the InstallShield installer with appropriate administrator privileges
  5. 5. Complete the installation wizard, ensuring all components are updated
  6. 6. Open existing Suite Setup projects in the updated InstallShield version
  7. 7. Rebuild all Suite Setup projects to ensure they incorporate the fixed installer framework
  8. 8. Redistribute the rebuilt setups to end users

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

Fix this in Installshield Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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