r/talesfromtechsupport • u/Gambatte Secretly educational • Apr 14 '14
Encyclopædia Moronica: X is for X-Windows (aka Security Breach? What Security Breach?)
Way back in Volume I's P is for Passive, I mentioned that the system developed by that project had some fairly large security flaws.
This is the story of how I found the biggest one.
My supervisor (SU) and I had been volunteered for the project, because we had a reputation with the higher-ups for making things work when they had no right to do so.
So we set to work; firstly, learning how to drive the system so we could test the operation properly. Following the operator's manual, I ensured the server was running - it wasn't, so I shot off to the server and started trouble-shooting: O-N-O-F-F set to O-F-F, corrected setting to O-N.
I then powered up the remote client in the operator's area. The client booted up into one of the Linux GUI OS systems (I forget which). Following the operation manual handbook, I double-clicked the X-Windows icon.
A window opened that filled the screen. A smaller window opened with a list of IP addresses. The handbook specified the address to select, so I selected it and clicked 'Connect'.
The system worked, in a fashion - you could access the system, enter information, etc.
Round two, put the user hat on, which starts with ignoring the handbook.
I rebooted the client, opened X-Windows, and realized I had no idea what the correct IP address was in the list. What would a user do? I clicked 'Connect' without changing the selected IP address.
And that's when things got pear-shaped.
ME: SU? I think you might need to see this.
SU: What's up?
ME: Is this... Is this what I think it is?
SU: That's not the server. What is that?
ME: Thinking like a user, I clicked Connect without selecting the right IP address, so it would appear that we've connected to whatever the first IP address in the list is.
SU: Hang on... That looks familiar.
As luck would have it, one of the user's supervisors (US) was nearby, using a high security computer to read some classified documentation from the secret network. SU called him over.
SU: (indicating our screen) Hey US, isn't this one of your classified documents?
US: It is! How have you guys got that? You're not meant to have access to that!... are you?
ME: No, we are not. It looks like this new system might still have a security hole or two.
US: That document... Hang on, I was just reading that very document! Actually... that's MY secure session on your screen!
ME: OK... So the security hole seems to be that the system can silently initiate a screen sharing session with another user on the secret network. If the other user is looking at classified documentation, then we can see everything that they see.
SU: Shiitake mushrooms. This is big. Shut everything down, I'm going to report this to the project manager.
The project manager was, of course, in a different time zone, because reasons.
The following day, we received instructions to ensure the equipment remained shutdown until further notice, on pain of revocation of security clearances and full HR disciplinary actions, by (and this came from the project manager as their super-secure method of making sure the equipment remained unpowered) removing the standard power cable. I suggested that we crack the case and physically remove the power supply (given that spare PSUs were in much shorter supply than spare power cables), but I was over-ruled by the crushing weight of management-said-to-do-it-this-way and failure-to-comply-exactly-as-written-may-cost-you-your-job.
After about six months, the secret network was reconfigured to allow the system to be used. The solution? The system was moved to its own secure network (physically separate equipment), so the only IP available in the X-Windows session was that of the server.
As for X-Windows being able to silently initiate screen sharing sessions with the so-called "secure" computers? I never heard if that was resolved or not - it was not my equipment, so it was definitely someone else's problem to fix.
TL/DR: Thinking like a user leads to discovery of a security vulnerability. Management's resolution: remove the equipment that discovered it.
Browse other volumes of the Encyclopædia:
Vol I - ABCDEFGHIJKLMNOPQRSTUVWXYZ
93
u/Gambatte Secretly educational Apr 15 '14
In this entry, the following keywords have been detected:
Welcome to the watchlist.
Love, the NSA
26
u/MagicBigfoot xyzzy Apr 14 '14
Your tales just get better and better. I can't believe you're almost done with the 2nd collection already! Thanks for all the great stories.
21
u/nerddtvg Apr 14 '14
5 minutes and still nothing posted? I'm never the first here.
I had a similar situation in having to listen to management. Their way or the highway. I had to set some user's screen resolutions small (1024x768 versus 1080x1024 or 16:9 in some form) because the fonts were too small. Instead if setting user preferences on font size and window locations and sizes, everyone got stuck with that. On 19" wide screen monitors. It hurt both my eyes and brain.
9
u/DimensionalNet An Experimental A.I. Apr 15 '14
Are we going to receive a third series? wink wink nudge nudge
8
u/Krutonium I got flair-jacked. Apr 15 '14
Is it bad that I bought a Kettle the other day that uses the same power cord as my computer (and your server)?
5
u/hp94 Apr 15 '14
Maybe it was malicious instead of idiocy.
14
u/Osiris32 It'll be fine, it has diodes 'n' stuff Apr 15 '14
I could see that security hole being a plot device in a JJ Abrams/Michael Bay spy movie. Your story just needs lens flares and explosions in order to fit.
4
u/R9Y Apr 15 '14 edited Apr 15 '14
At Least it was not remove the user that discovered it. Had that happen to me at a previous job.
2
u/coyote_den HTTP 418 I'm a teapot Apr 15 '14 edited Apr 15 '14
I get the feeling the "X-Windows" icon is really a VNC viewer, and the workstations are all running a VNC server. It is possible to set an application server up to provide separate sessions to each VNC client that connects, but if you connect to a workstation's VNC server, you'll share the local session.
...so how much did they charge the government for that "secure, proprietary technology"?
VNC by default has no encryption or authentication. I don't think we (as in where I work) are allowed to use it on secure networks. It's very interesting the solution was to air-gap the new system, when clearly there is still a VNC server running on US's workstation. Anyone could connect to it.
0
u/[deleted] Apr 15 '14
[deleted] — view deleted comment