Question 1

What type of vulnerability was addressed in this update?

Accepted Answer

An input string validation issue was identified that could lead to remote code execution (RCE), allowing an attacker to potentially execute code remotely in the user’s computer.

Question 2

Does this vulnerability affect built games/applications in any way?

Accepted Answer

No. Only the Unity Editor is affected.

Question 3

What platforms are affected?

Accepted Answer

Windows only. Mac and Linux platforms are not affected by the identified vulnerability.

Question 4

What versions of Windows are affected?

Accepted Answer

All versions of Windows.

Question 5

What versions of Unity are affected?

Accepted Answer

All versions of the Unity Editor running on Windows.

Question 6

What versions of the Unity Editor are being patched?

Accepted Answer

We have released a patch for the following Unity versions: 5.3, 5.4, 5.5, 5.6, and 2017.1. The full details are listed on this page.
We will not be patching Unity 4.x, 5.0, 5.1, or 5.2.

Question 7

Will my specific version be patched?

Accepted Answer

Unity will be releasing a single patch to each of the most current dot-releases of Unity. For example, users running an older version of Unity 5.3 will need to update to the patched version of 5.3.8. There will be no patches for 5.3.7, 5.3.6, etc.

Question 8

What about versions older than 5.3?

Accepted Answer

We are providing a workaround tool that disables the identified vulnerable Unity Editor feature, which can be downloaded from Mitigation Tool Guide [7]. Please understand, though, that the workaround is not a patch and has limitations. The workaround will disable the Unity Editor feature identified as vulnerable, but since we can’t control whether the affected functionality becomes re-enabled at some point after applying the workaround (system changes, reinstallations, etc.), we strongly recommend updating to the latest version of Unity to get the benefits of the full patch. You will also no longer be able to use the ‘Open in Unity’ functionality in the web browser version of the Asset Store after applying the workaround.

Question 9

When will the patch be available?

Accepted Answer

The updates are available here, in the Patch Versions section.

Question 10

Does the workaround tool work for versions newer than 5.3? Can I use the workaround tool instead of patching?

Accepted Answer

The workaround tool can be used on all affected versions of Unity. Please understand, though, that the workaround is not a patch and has limitations: the workaround will disable the identified vulnerable Editor features, but since we can’t control whether the affected functionality becomes re-enabled at some point after applying the workaround (system changes, reinstallations, etc.), we strongly recommend updating to a patched version. You will also no longer be able to use the ‘Open in Unity’ functionality in the web browser version of the Asset Store after applying the workaround.

Question 11

I run multiple versions of Unity, do I have to apply the workaround tool for all of them?

Accepted Answer

No, by running it once it deactivates the identified vulnerable component across all of them. Do keep in mind that by re-installing or updating (one) of the versions, it may activate the component again. To check, re-run the workaround tool until all versions are up to date.

Question 12

Can I just use the workaround and never move to a patched version?

Accepted Answer

The workaround will disable the Unity Editor feature identified as vulnerable, but since we can’t control whether the affected functionality becomes re-enabled at some point after applying the workaround (system changes, reinstallations, etc.), we strongly recommend updating to a patched version. You will also no longer be able to use the ‘Open in Unity’ functionality in the web browser version of the Asset Store after applying the workaround.

Question 13

How can I get the workaround (or the patches)?

Accepted Answer

The updates are available here, in the Patch Versions section.

Question 14

I have a locked-down older version of Unity 5.x.x. Will you produce a patch for the exact version of Unity that I’m using?

Accepted Answer

Our focus right now is on addressing the identified vulnerability in the most current version of each dot-release. We don’t have any details to share on patches for other versions at this time.

Question 15

Will I need to rebuild asset bundles due to the update requirement?

Accepted Answer

It depends on the specific version of Unity that you are using. Most customers will be able to update to the patched versions without needing to rebuild their bundles, but some customers may find that asset importers have been updated between the version they’re currently using and the patch for that dot-release. For those customers, asset bundle rebuilding may be necessary.
You definitely won’t need to rebuild bundles if you’re currently using 5.3.8p1, 5.4.5p4, 5.5.4p2, 5.6.3f1, or 2017.1.0p3.

Question 16

How do I know if I’ll need to rebuild my asset bundles?

Accepted Answer

You may need to rebuild your bundles if any assets are re-imported when you first open your project in the patched version of Unity.

2019년 8월 보안 업데이트 권고(CVE-2017-12939)

취약점 세부 정보

문제 해결 단계

Unity 에디터 버전 확인

업데이트 설치

완화 툴

FAQ

참조