Slashdot Mirror
Vulnerable SAP Deployments Make Prime Attack Targets
wiredmikey writes "Using a combination of TCP scans and Google, security researchers found that nearly a quarter of the organizations running vulnerable versions of SAP are tempting fate by leaving them exposed to the Internet. This discovery, researchers from ERPScan say, dispels the myth that SAP systems are only available from the internal network, leading to the misconception that they are protected by design. By March 2012, there were more than 2,000 security advisories published by SAP. Of those, about 7% (124) have publicly available PoC (proof-of-concept) exploit code available to the public. Many of the issues discovered are related to poor configuration or poor deployment planning. For example, 212 SAP Routers were found in Germany, which were created mainly to route access to internal SAP systems. Another issue with the vulnerable and exposed SAP installations is that many of them run on Windows NT, creating a twin set of risks for the organization, as they have to contend with a bad SAP deployment and unsupported OS that is full of security issues all by itself."
I have no idea what the hell SAP is, but it sounds really dangerous.
Better known as 318230.
I cant find it anywhere on the SAP site!
If you think that a 'demo' is an executable you download, rather than something delivered by a besuited sales team, you might not be a potential customer...
If you are an individual, you don't want it and if you are a company, you REALLY don't want it.
Sorry, but gray text on gray background is making my eyes bleed.
Having only grazed over the article, Windows NT is Microsoft's current flagship operating system. Windows NT 6.1 being their latest "stable" release marketed under the names Windows 7 and Windows Server 2008 R2
But if they really meant "Windows NT" as in Windows NT 4.0, then I agree, that is pretty darn bad
I suspect that the JVM(s) involved in some of these deployments might be a bit behind the curve, as well...
Having only grazed over the article, Windows NT is Microsoft's current flagship operating system. Windows NT 6.1 being their latest "stable" release marketed under the names Windows 7 and Windows Server 2008 R2
But if they really meant "Windows NT" as in Windows NT 4.0, then I agree, that is pretty darn bad
Given that the paper from ERPScan lists the OSes atop which SAP runs as "Windows NT", "AIX", "Linux", "SunOS", "HP-UX", and "OS/400", I suspect that when they say "Windows NT" they mean, as you suggest, "Windows NT the family of operating systems, older ones of which were sold under the name "Windows NT" and newer versions of which aren't", not "Windows NT 3.x and 4.0", i.e. Windows Server 20xx (and Windows 2000/XP/Vista/7, if anybody's running it on their desktop) are lumped under "Windows NT" (and Solaris N is lumped under "SunOS").
If I were a somewhat serious security researcher, I would install a couple of SAP and SCADA honeypots.
Perhaps fishing for executables that run, check the environment and then do nothing.
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
Having pretty good success wrapping Baby SAP, aka SAP Business One in WCF (Windows Communication Foundation) through the SAP B1 DI API then consuming the resulting WCF IIS service through BCS (Business Connectivity Services) in SharePoint 2010, architecturally a very secure solution thats scalable to the cloud ie. SAP B1 on premise and SharePoint Online in cloud , and it just works !, especially when you present the required Business screens via forms server based InfoPath froms and handle the business logic via WF (Workflow Foundation) SharePoint workflow .... actually haven't seen anyone else do this and its very Elegant, I would recommend ... obiously there is Duet Enterprise for the big SAP R3 version and SharePoint, but less common than B1
bæ8Ã0sÃOE?5r©oÂÃ?âz:ÃÃAÃ?ÃOEÂ6fXÃ?]Â
All the pieces and parts are hard enough to keep running on a good day. Thing takes weekly downtime just to cycle modules....even simple patches shut your business users out for hours. Upgrading your version and OS shuts your business down for a week just to properly test. Sure you can use Dev boxes an HA, but you have to have ALL the users PROVE IT WORKS. So you waste terrible amounts of their TIME the could be selling stuff!!
And of course, SAP doesn't INSTALL anything THEMSELVES. You have to use some fly-by-night third party. So just like Microsoft, it's YOUR fault when you didn't include hiring an extra $1m per year in employees to run the thing and use all the "secret settings" after they all leave you.
Windows NT has been out of support for a very long time. Even windows 2000 has been out of support for a while.
Given how much SAP costs, you think they could afford to upgrade to win2003 at least.
Given how much SAP costs, I'm guessing a lot of companies haven't been able to get budget approval for an upgrade that runs on a supported version of Windows. (Particularly in light of the epic cost overruns that are typical of a SAP deployment.)
Any insufficiently advanced magic is indistinguishable from technology.
The only exception is completely isolated networks. But even those are vulnerable, even if you shoot people that breach the security. Just ask the Iranians about that.
Thinking that anything visible in parts of a corporate LAN is not reachable over the Internet is stupid and highly incompetent. Of course, you can have very tight network security and very isolated LAN segments. But until you invested a lot of effort and had competent external review of the security measures and have no direct reachability from the general LAN, that is not really going to help either.
What I strongly suspect here is just stupid management not willing to invest any money to even find out whether they have a problem. The general rule is that anything has to be considered insecure unless proven otherwise, not the other way round. Just stupidity, incompetence and greed, as usual. This high level of exposure is no surprise to any competent security expert.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
I know of at least one large company that thinks giving potential applicants a login on their SAP installation to "streamline the application process" is a good idea. Through a public-facing SAP web front-end.
How I know? I tried to apply there. Got rejected by some faceless jerk behind a SAP terminal somewhere far away, then needed HR to play helpdesk because removing my details from the system didn't work as promised. Think of it as an exit interview by email before you've even started.
Of course that system also made all sorts of assumptions about what sort of enterprise-blessed desktop and browser I would be using. Except that I wasn't an employee and I was applying for a unix position, so, er, that didn't work out very well.
Let me tell you how wonderful a first impression I got from that company: Never again. In fact, I won't ever again apply to companies that require webforms (on possibly third-party platforms, without SSL, with the wrong domain name, etc.) and that sort of crap. If you're that institutionally-stupid, well, be that way but without me, TYVM.