Monday, March 24, 2025
HomeCVE/vulnerabilityA Critical Software Bug Turns an Airplane to the Wrong Way -...

A Critical Software Bug Turns an Airplane to the Wrong Way – Turned Right Instead of Left

Published on

SIEM as a Service

Follow Us on Google News

Recently, security researchers have discovered a very distinct software bug that is marked as a very critical software bug, as it turns an airplane in the wrong way. 

Nav Canada firstly identified this bug in 2017 on a Bombardier CRJ-200, which makes the aircraft to switch to the wrong way, in short, this bug turns the airplane to right instead of left if pilots regulate the pre-set height limit.

Soon after the incident, it was reported to the appropriate authority, and the other reason for this software bug is that the pilots used the FMS’s temperature compensation function in a remarkably cold climate.

What’s the problem?

As we said that due to the use of FM’S temperature compensation function by the pilots in a very cold climate, a critical software bug took place as it turns an airplane in the wrong way, or we can say that instead of left they turn towards the right. 

Well, the pilots also said that the airplane just turns to the wrong way as it was heeding the published missed approach, and they also said that this type of misconception generally does not occur.

But, according to one of the professional aviators, selecting the altitude correctly or utilizing temperature compensation does not really alter the flight segment. Thus we can say that just because of the design error, the software imagines the flight division has shifted.  

Moreover, disabling the FMS automatic features are done by the aircraft’s configuration strapping unit (CSU) and reviewing the airplane flight manual (AFM) reservations segment. 

However, Rockwell Collins opposed the FAA and the prescribed steps that are to be perceived regarding it; thus, in Europe this week, it was published that a necessary airworthiness directive organization operators of CRJ-200 aircraft to impair the automatic temperature compensation till mid-June.

After all this discussion, the FAA was not satisfied by this decision, thus disagreed in disabling the FMS feature as it is necessary to address the unsafe condition. And both companies disagreed with the banned of the FMS automatic feature. 

They declared that a software fix would be more accessible to achieve rather than forbidding the use of the electronic calculator.

Well, all have this much idea that all the bugs that took place in the flight are very uncommon. And both Airbus and Boeing have discovered that most of the airline bugs serve to be unexpected memory overflows over the year. 

Moreover, there is a design that is owned by Bombardier, the Airbus A220, that has gone through the same software-induced issues with its engines last year. In contrast, the Boeing 737 was found to have a unique bug that has blanked all cockpit, and it also shows if pilots attempted to land on one of seven distinct runways in the whole world.

So, what do you think about this? Share all your views and thoughts in the comment section below.

Also Read: Radio Tech Used to Hack Everything From Airplanes to Defibrillators

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Chinese ‘Web Shell Whisperer’ Leverages Shells and Tunnels to Establish Stealthy Persistence

A recent cyber espionage operation by a China-nexus threat actor, dubbed "Weaver Ant," has...

FCC Investigates Chinese Entities on US Government’s Prohibited List

The Federal Communications Commission (FCC) has initiated a new investigation into Chinese entities previously...

VanHelsingRaaS Emerges, Targeting Linux, BSD, ARM, and ESXi Systems

VanHelsingRaaS, a newly launched ransomware-as-a-service (RaaS) program, has quickly gained traction in the cybercrime...

WordPress Plugin Vulnerability Opens Door to SQL Injection Exploits

A critical vulnerability in the popular WordPress plugin GamiPress has been uncovered, leaving users...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

WordPress Plugin Vulnerability Opens Door to SQL Injection Exploits

A critical vulnerability in the popular WordPress plugin GamiPress has been uncovered, leaving users...

WordPress Plugin Flaw Exposes 200,000+ Sites at Risk of Code Execution

A critical security vulnerability has been discovered in the popular WordPress plugin, WP Ghost,...

Critical Next.js Middleware Vulnerability Allows Attackers to Bypass Authorization

A severe vulnerability has been identified in Next.js, a popular React framework used for...