EnterCriticalSection flagged? about flawfinder HOT 4 CLOSED

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.

from flawfinder.

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).

InitializeCriticalSection

Windows Server 2003 and Windows XP: In low memory situations, InitializeCriticalSection can raise a STATUS_NO_MEMORY exception.
Starting with Windows Vista, this exception was eliminated and InitializeCriticalSection always succeeds, even in low memory situations.

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.

On old versions of Windows (including and before XP and Server 2003), exceptions can be
thrown in low-memory situations. Use InitializeCriticalSectionAndSpinCount instead

EnterCritcalSection

EnterCriticalSection - as something that will not throw errors on XP (released October 25, 2001), .NET Server (released April 24, 2003), and later _(including Win 7 (released October 22, 2009).

What we are talking about being susceptible is these operating systems:
Windows 1.0 (November 20, 1985), Windows 2.0 (December 9, 1987), Windows 2.10 (May 27, 1988), Windows 2.11 (March 13, 1989), Windows 3.0 (May 22, 1990), Windows 3.0 with Multimedia Extensions (October 20, 1991), Windows 3.1 (April 6, 1992), Windows for Workgroups 3.1 (October 27, 1992), Windows NT 3.1 (July 27, 1993), Windows for Workgroups 3.11 (November 8, 1993), Windows NT 3.5 (September 21, 1994), Windows NT 3.51 (May 30, 1995), Windows 95 (August 24, 1995), Windows NT 4.0 (August 24, 1996), Windows 98 (June 25, 1998), Windows 98 SE (May 5, 1999), Windows 2000 (February 17, 2000). Windows Me (September 14, 2000)

From the list you provided, even if you look at the top 1000 operating systems:

• Windows Me doesn't even make the list
• Windows 2000, Windows 98, Windows NT, Windows, 95 all have zero percent.
• The older ones - also doesn't make the list.

I think the risk is low/non-existent of removing this check.

from flawfinder.

Great points! I've made the change, it'll be in the next release.

from flawfinder.

Thanks for following up.

from flawfinder.