New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EnterCriticalSection flagged? #19
Comments
There's no formal position on EOL, I generally ask, "What seems to be common?". For example, while officially Windows 7 is end-of-life, over 30% of all client systems (not just Windows systems) use Windows 7 today. So if something impacts Windows 7, it's a serious issue. Stats here. I take Python in a similar vein. Officially Python 2 is end-of-life, but in practice Python 2 is everywhere & there are still many systems that only have Python2, so I continue to support it. As of August 2005, over 600,000 sites ran Windows Server 2003 even though it was out of support according to Netcraft. I don't know the numbers now, but if the numbers are significant, it seems worth worrying about. Eventually it's not worth worrying about, of course, but what matters is the number of systems actually deployed. Too many people in the tech bubble think that when a new version of software is released, everyone magically updates to it. That's not how things work in the real world, and I want to help people out in the real world. |
Agree - but I think you missed of what I was saying. I'm not asking about Win 7 (the fix as made before Win 7 was released). InitializeCriticalSectionWindows Server 2003 and Windows XP: In low memory situations, InitializeCriticalSection can raise a STATUS_NO_MEMORY exception. According to your stats, XP has a 1.7% market share. Is that enough people to leave it on the list - probably, but the warning message should change to indicate that it does not happen on modern versions of Windows.
EnterCritcalSection
What we are talking about being susceptible is these operating systems: From the list you provided, even if you look at the top 1000 operating systems:
I think the risk is low/non-existent of removing this check. |
This is no longer a vulnerability on widely-used Windows versions. See: #19 Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>
Great points! I've made the change, it'll be in the next release. |
Thanks for following up. |
First - thanks.
Next, a question about a potential false positive (or at least aged out positive)
https://github.com/david-a-wheeler/flawfinder/blob/master/flawfinder#L1266
flags
EnterCriticalSection
asHowever, the doc makes no mention of that.
The page from the book Writing Secure Code describes
EnterCriticalSection
as something that will not throw errors on XP, .NET Server, and later. Considering that XP EOL in April 8, 2014; .Net Server EOL 14 July 2015 if people are using OSes earlier than that - they have bigger issues than what will be flagged with flawfinder...The doc for
InitializeCriticalSection
does indicate:Windows Server 2003 operating system EOL'ed on July 14, 2015.
What's the goal from flawfinder for managing the versions of Windows?
Thanks again.
The text was updated successfully, but these errors were encountered: