• Hi Guest!

    We have posted a new VaM2 dev log on Patreon, starting a monthly cadence of written progress updates between Beta releases. Highlights include the new Gizmos System, Selection Carousel, and Modes System with Context-Specific Editing. Beta1.2 is 15 of 21 items complete.

    Read the full post on Patreon, or follow progress on the public Trello roadmap.

Solved Unity security threat

Aipas

Active member
Joined
Sep 27, 2024
Messages
103
Reactions
137
Anything to worry about?
Not even sure it actually did anything, but I've patched unityPlayer.dll and Vam is still working.

A nagging thing is that apparently the old unity 2018.1.9f2 that I use to make asset bundles with Macgruber's tutorial isn't covered by the security patch rolled out to the editors, so now I'm not sure I should just uninstall that particular editor.
EDIT: Is the editor itself a risk, or just projects it compiles / makes into a program or something? Do assetbundles even get affected by this. They don't "roll out" with unityPlayer.dll, it's just one single file. right?
 
Last edited:
Solution
You have the detail here.

There is nothing to fear about the editor. It's only for the final product itself. Since you don't compile anything for VAM, you have nothing to worry about.
Assetbundles cannot contain code. The only possibility a security flaw could exists with assetbundles is through dll shared with them. We monitor them and the ones on the hub are safe.
You have the detail here.

There is nothing to fear about the editor. It's only for the final product itself. Since you don't compile anything for VAM, you have nothing to worry about.
Assetbundles cannot contain code. The only possibility a security flaw could exists with assetbundles is through dll shared with them. We monitor them and the ones on the hub are safe.
 
Upvote 0
Solution
Back
Top Bottom