CERT-In warns of vulnerabilities in Tata Motors connected vehicle applications
Read more
YourStory [india, en]
yourstory.com

CERT-In warns of vulnerabilities in Tata Motors connected vehicle applications

The Indian Computer Emergency Response Team (CERT-In) identified several high-severity vulnerabilities in specific versions of Tata Motors' connected vehicle applications, namely iRA 2.0 and iRA.ev, on Wednesday. The warning states that these flaws could lead to the disclosure of sensitive user credentials, impersonation capabilities, and unauthorized access to vehicle-related information and services.

The vulnerabilities affect iRA 2.0 versions below 26.7.3 and iRA.ev versions below 26.7.2. These applications are designed for Tata Motors customers using Internal Combustion Engine (ICE) vehicles and Electric Vehicles (EVs), respectively, providing access to connected features such as remote vehicle control, vehicle status information, health monitoring, and trip data.

CERT-In discovered four types of vulnerabilities related to hardcoded credentials, insufficient URL validation, leakage of authentication tokens in application logs, and improper implementation of SSL certificate pinning.

According to the notification, these shortcomings potentially allow attackers to extract credentials and gain access to backend services, as well as obtain authentication tokens to mimic user actions or intercept and modify communication between the applications and their backend systems.

The vulnerabilities found by CERT-In come amid growing global concerns about cybersecurity in connected cars. In recent years, security researchers have found flaws in connected car platforms operated by manufacturers such as Kia and Subaru, which could potentially expose customer information and allow unauthorized access to vehicle functions.

Furthermore, researchers have discovered vulnerabilities in Bluetooth software used in Mercedes-Benz, Volkswagen, and Skoda vehicles, which could potentially allow remote code execution through infotainment systems. These incidents highlight increasing security risks as automakers increasingly rely on mobile applications, cloud infrastructure, and connected services to provide digital features to vehicle owners.

Similar stories

State Agency Warns of Threat to Hack TATA Cars
Read more
www.aajtak.in

State Agency Warns of Threat to Hack TATA Cars

The Indian Computer Emergency Response Team (CERT-In) has issued a warning regarding TATA vehicles. This alert concerns vehicles from Tata Motors that are linked to the connected vehicle application.

A vulnerability was discovered in the iRA 2.0 and iRA.ev connected vehicle applications. By exploiting this vulnerability, hackers can gain access to a TATA car quite easily.

The state agency has issued a high-level security advisory on this matter. The agency states that by utilizing this vulnerability, attackers can gain access to necessary credentials, as well as all information and services associated with the vehicle.

How to validate identities digitally without hindering the user experience
Read more
g1.globo.com

How to validate identities digitally without hindering the user experience

Digital security must be adaptable to the specific circumstances of each access. Logging into an account using a daily-use mobile phone differs significantly from executing a delicate transaction from a device never seen before.

For this reason, corporations need to find a balance between identity verification and maintaining a fluid digital experience, preventing every interaction from becoming a series of obstacles.

In addition to determining who is accessing, it is possible to analyze data related to the equipment, behavioral patterns, and the operating environment. Device intelligence, for example, helps identify the characteristics of the device, its usage history, and any indicators that might suggest suspicious behavior.

By cross-referencing this data with biometric and identity information, it becomes possible to make a more complete assessment of the situation, without a single sign being sufficient to define, in isolation, whether the interaction is fraudulent.

A significant change in context may justify the inclusion of an extra authentication phase. Examples include changing devices, exhibiting behavior different from the usual, or executing a higher-sensitivity operation.

The principle adopted is to apply stricter controls only when the risk requires it, instead of imposing the same procedure on all interactions performed.

Popular