TL;DR
Qualys CEO Sumedh Thakar spotted outdated software and database errors on an airline in‑flight entertainment (IFE) screen earlier this year: the IFE showed Apache HTTP Server version 2.0.42 and what appeared to be MySQL connection problems. The IFE is not directly tied to aircraft avionics; the Apache 2.0 branch reached end-of-life in July 2013 and the specific build dates back to 2002.
What happened
On a recent flight, Qualys CEO Sumedh Thakar noticed error messages on his in‑flight entertainment screen. One error corresponded to a web server failure and the system identified the server as Apache HTTP Server 2.0.42. A separate message suggested problems connecting to a MySQL database. The version shown, 2.0.42, was first released in September 2002; support for the 2.0 branch ended with a final release in July 2013. The report stresses that IFE systems are not directly connected to aircraft avionics, limiting implications for flight controls. Observers noted the MySQL symptoms are consistent with systems made by a known avionics and IFE supplier, and the vendor describes its product as delivering "unique experiences." The discovery underscores that some passenger-facing systems continue to run software that is many years old.
Why it matters
- Long‑unsupported server software no longer receives security fixes, increasing exposure to known vulnerabilities.
- Passenger entertainment systems can store or process data; outdated components can pose privacy or integrity concerns for users.
- Even though IFEs are reportedly isolated from avionics, visible failures and errors undermine passenger confidence and raise supplier oversight questions.
- Suppliers and airlines may face reputational and compliance scrutiny for relying on legacy stacks on public-facing infrastructure.
Key facts
- Qualys CEO Sumedh Thakar observed the errors on his in‑flight entertainment screen.
- The IFE displayed Apache HTTP Server version 2.0.42.
- Apache HTTP Server 2.0.42 first appeared in September 2002.
- The Apache 2.0 branch reached end-of-life with a final release in July 2013.
- The IFE is not directly connected to the aircraft's avionics, according to the report.
- A second error on the screen indicated MySQL connection problems.
- The MySQL symptoms in the report were said to be consistent with a Thales system; the vendor's marketing calls its IFE a provider of "unique experiences."
- The article places the software's origin in cultural context, noting technologies such as Windows XP and early BlackBerry models were contemporary with Apache 2.0.
What to watch next
- Whether the airline or IFE supplier publicly confirms the software versions and addresses updates — not confirmed in the source.
- Any vendor statement from the suspected IFE manufacturer (e.g., confirmation of a Thales system) or a timeline for remediation — not confirmed in the source.
- Regulatory or industry follow-up on use of unsupported software in passenger-facing systems — not confirmed in the source.
Quick glossary
- Apache HTTP Server: A widely used open-source web server that hosts and serves web content; it has multiple major release branches with separate support lifecycles.
- In‑flight entertainment (IFE): Passenger-facing systems on aircraft that provide audio, video, connectivity and user interfaces for entertainment and information.
- End-of-life (EOL) software: Software that no longer receives updates or security patches from its maintainers, increasing exposure to known bugs and vulnerabilities.
- MySQL: An open-source relational database system commonly used to store and retrieve application data.
Reader FAQ
Was the aircraft's flight control affected by these IFE errors?
The report states IFE systems are not directly connected to avionics, so the observed errors did not indicate direct impact on flight controls.
Which airline or aircraft was involved?
not confirmed in the source
Did the IFE vendor acknowledge the issue or name the software vendor?
not confirmed in the source
Will the outdated Apache version be patched?
not confirmed in the source
OFFBEAT We will be cruising at 35,000 feet and failing to update our Apache HTTP Server Now replace the autopilot with Copilot Richard Speed Tue 30 Dec 2025 // 09:45 UTC BORK!BORK!BORK! Bork can…
Sources
- We will be cruising at 35,000 feet and failing to update our Apache HTTP Server
- Cruising at 35000 feet with an ancient Apache server
- Do commercial airlines still reach a normal cruising altitude …
- Aeronautical Information Manual – Change 1
Related posts
- Korean carrier’s femtocell security lapse exposed customers to snooping and fraud
- Reverse-Engineering Washing Machines: Insights from 39c3 Talk (Video)
- Hacking Washing Machines: Reverse-Engineering BSH and Miele Appliances