2 ms·
As it says right on the URL, that CVE is from 2003, not 2019, and it doesn't affect any Windows version past XP.
by icebraining 7y ago
As it says right on the URL, that CVE is from 2003, not 2019, and it doesn't affect any Windows version past XP.
- scarface74 7y agoYes and by then you already had the 7 plus versions of defining a string dating back to Windows 3 (1992). Backwards compatibility was already a problem then. Since then, MS has had 15 more years worth of cruft on top of that s d yet more ways to define a string. If backwards compatibility caused a security vulnerability back then, how much old Windows 95 code do you think is causing issues now?