# Ignition Designer 7zip Executable Version Vulnerabilities **URL:** \ **Category:** Ignition\ **Tags:** designer, perspective\ **Created:** [January 22, 2025, 8:19pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-7zip-executable-version-vulnerabilities/101255 "2025-01-22T20:19:04Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dillon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dillon/32/81537_2.png) [@dillon](https://forum.inductiveautomation.com/u/dillon)\ **Post date:** [January 22, 2025, 8:19pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-7zip-executable-version-vulnerabilities/101255/1 "2025-01-22T20:19:04Z")
Do you think this is worth putting in a ticket with IA or [jxbrowser developers](https://teamdev.com/jxbrowser/)? Has anyone else experienced this? Snippet below.... My company's Windows user policies has blocked the standalone executable for 7zip that is used to unpack the files for the chromium browser to allow you to view/edit Perspective views in the designer. This is because that version seems to be flagged due to a known exploit or vulnerability. 7zr.exe This occurred upgrading from 8.1.21 -\> 8.1.42 which I then triggered a designer update. First time I had to since this Windows policy was put in place. Luckily, I was able to just download the same designer version on my PC at home and moved the unpacked files to my cache folder myself. However, this is not favorable 😅 ![RteGetImageHandler](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/f/5f91224aa8b811afafcbf9645a4ad57abbb6ef58.png) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [January 22, 2025, 8:22pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-7zip-executable-version-vulnerabilities/101255/2 "2025-01-22T20:22:14Z")
We're already aware and TeamDev has already released a version of JXBrowser that updates it. Unfortunately upgrading JXBrowser is extremely non-trivial and I don't have a timeline for when the next upgrade will happen. ---
**Author:** ![dillon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dillon/32/81537_2.png) [@dillon](https://forum.inductiveautomation.com/u/dillon)\ **Post date:** [January 22, 2025, 8:25pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-7zip-executable-version-vulnerabilities/101255/3 "2025-01-22T20:25:11Z")
I figured I was not the first to experience this. Especially since my company upgraded to a version released seven months ago haha. Thanks Kevin. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [January 22, 2025, 8:26pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-7zip-executable-version-vulnerabilities/101255/4 "2025-01-22T20:26:32Z")
FWIW, the 7z executable is only used once the first time JXBrowser starts, to unpack the libraries for whatever OS you're on, and then isn't used again. Security software may flag it, but it's not technically a danger because it's not used again after that, and it's not being run against untrusted user input. ---
**Author:** ![dillon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dillon/32/81537_2.png) [@dillon](https://forum.inductiveautomation.com/u/dillon)\ **Post date:** [January 22, 2025, 8:31pm UTC](https://forum.inductiveautomation.com/t/ignition-designer-7zip-executable-version-vulnerabilities/101255/5 "2025-01-22T20:31:46Z")
> [@Kevin.Herron](#): > > I don't have a timeline for when the next upgrade will happen. Fine for me, means less times I have to worry about this because I know my infosec team won't accommodate 😆