Skip to content
Fencer Intel
medium 6.1

GHSA-3w9w-9833-gcpv json

Security bug in ConvertToSinglePlane when used with untrusted content from the DDS loader

published 3y ago modified last yr.

cvss
6.1
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact A memory overwrite bug was reported by a security researcher in the **ConvertToSinglePlane** method via the *texconv* command-line tool when given an invalid height for planar video textures such as NV12. This can be a potential security bug for any clients of the library who follow the same pattern.

This issue *does not* impact use of the DDS texture loader itself, only when combined with `ConvertToSinglePlane` for converting multi-planar video formats. All other functions in the library fail immediately if given images in planar formats.

### Patches The fix to the specific area as well as general hardening can be found in [this PR](https://github.com/microsoft/DirectXTex/pull/307) and will be included in the This bug has been fixed in the January 31, 2023 or later release of DirectXTex.

### Workarounds If your code makes use of **ConvertToSinglePlane**, you can validate that the width & height alignment requirements are met for the input image before calling the function.

Patch / fix

  • nuget directxtex_desktop_2019 2023.1.31.1
  • nuget directxtex_desktop_win10 2023.1.31.1
  • nuget directxtex_uwp 2023.1.31.1

Is GHSA-3w9w-9833-gcpv in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 6.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L

Affected packages

ecosystem package affected fixed in
nuget directxtex_desktop_2019
<2023.1.31.1
2023.1.31.1
nuget directxtex_desktop_win10
<2023.1.31.1
2023.1.31.1
nuget directxtex_uwp
<2023.1.31.1
2023.1.31.1

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.