Toyota: Is There A Problem Here?: Toyota

Showing posts with label Toyota. Show all posts

20100206

Problem ID: 6767578961503585980
Entered by: Ben Simo

Toyota Accelerates

"'I’m afraid of killing somebody – or myself' — Hull senior fears car’s sudden acceleration;
Toyota of Braintree says downloading new software part of recall process.
'I have instructed my children that if I get killed driving this car, that they can sue Toyota,' Anna Brackett said while sitting on the sofa in her Hull home Friday afternoon.

- Cathleen Jeffrey, The Hull Sun

"Indeed there are two issues that lead to the same complaint. ... There is no electronic malfunction whatever. These are both mechanical issues. ... Toyota is also making a change in the software programming that leads to a brake override."

- Mike Jackson, Autonation CEO on CNBC
(Starting at ~5:56 in video below.)

More:

Sudden Acceleration: Automakers' "Fail-Safe" Systems Guard Against Electronic Interference
Jim Motavalli, BNET
The key points here are that the driver’s foot was nowhere near the accelerator pedal, and the floormats were not at issue. So what’s going on here?

Car electronics are great, but they have their risks
News & Observer
Dennis Virag, president of the Automotive Consulting Group, said Toyota has erred in not adopting a brake override system for all its cars that shuts off fuel if the brakes are engaged with the accelerator down. Most other manufacturers have such systems.

Toyota did not install brake override systems despite complaints
Washington Post
Toyota Motor began facing complaints of runaway cars years ago, but the company did not install "brake override" systems in those vehicles, even as several other automakers deployed the technology to address such malfunctions.

Edit

20100205

Problem ID: 868826655806829694
Entered by: Ben Simo

Your car computer can kill you?

"It's in the software. It's not a bad accelerator pedal."

- Steve Wozniak, Co-founder of Apple Computer

Your car computer may kill you

John Dvorak

Commentary: Software has to be able to recognize a panic situation

The Perfect Storm May Rain 1's and 0's
Brian Cooley, CBS News
Now an already scary story has a spooky, virusy, cyber-something flavor added to it. Umm, did we forget to tell car buyers that they don't really control their cars any more – computers do?

Edit

20100204

Problem ID: 7349493190807064470
Entered by: Ben Simo

Stop & Go

"The computer can fail, send an inappropriate signal and boom, you go...
And if the computer sends an inappropriate signal and the throttle opens and the car runs away, that's a software glitch."

- Forrest Folck,

motor vehicle forensic investigator

"So now, after decades invested in metrics-driven verification, formal verification, and methodology management, we find that our chips don't work as expected because the software is still being 'verified' by feeding it test cases until the schedule expires. And we find that our cars run into things for the same reason, and the press of course will blame the problem on 'electronics.'"

- Ron Wilson,

EDN Executive Editor

More:

Is Toyota's Accelerator Problem Caused by Embedded Software Bugs?

Barr Code

So what's the story? Are embedded software bugs to blame for this massive recall?

Toyota Acknowledges Software Problem with 2010 Prius Brakes

Car and Driver

The software problem reportedly manifests itself as a feeling of slipping during the switch and is being noticed more now that drivers are using ABS as a result of winter road conditions.

Ford to Upgrade Brake Software On 18,000 Hybrids

Wall Street Journal

While the vehicles maintain full braking capability, customers may initially perceive the condition as loss of brakes.

US to Investigate Prius Brakes

Wall Street Journal

Ford Says Its Hybid Cars Also Have Problem

Toyota Recall – Is it the Computer, not the Gas Pedal?

Dvorak Uncensored

As someone who has been in software for over 30 years, I have to ask Toyota this question, “Have you ruled out the computer?”

Ford offers fix for Fusion hybrid brake glitch

Reuters

17,600 Fusion, Milan hybrids may have software glitch

Toyota Admits Software Problem With 2010 Hybrid Prius

ABC News

Toyota Admits Software Problem With Braking System, Deny Withholding Information From the Public

Edit

Usability Heuristics

• Visibility of system status Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

• Match between system and the real world Match between system and the real world: The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

• User control and freedom User control and freedom: Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

• Consistency and standards Consistency and standards: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

• Error prevention Error prevention: Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

• Recognition rather than recall Recognition rather than recall: Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.

• Flexibility and efficiency of use Flexibility and efficiency of use: Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

• Aesthetic and minimalist design Aesthetic and minimalist design: Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

• Help users recognize, diagnose, and recover from errors Help users recognize, diagnose, and recover from errors: Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

• Help and documentation Help and documentation: Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Consistency Heuristics

-F amiliar Familiar: The product is not consistent with the pattern of any familiar problem.

E xplainable Explainable: The product is explainable.

W orld World: The product is consistent with the real world.

H istory History: The present version of the product is consistent with past versions of it.

I mage Image: The product is consistent with an image that the organization wants to project.

C omparable Products Comparable Products: The product is consistent with comparable systems.

C laims Claims: The product is consistent with what important people say it’s supposed to be.

U ser Expectations User Expectations: The product is consistent with what users want.

P roduct Product: Each element of the product is consistent with comparable elements in the same system.

P urpose Purpose: The product is consistent with its purposes, both explicit and implicit.

S tatutes Statutes: The product is consistent with applicable laws.

FAILURE Heuristics

F unctional Functional: The error detecting, reporting, and handling functions properly.

A ppropriate Appropriate: Errors are reported at the appropriate time in an appropriate manner.

I mpact Impact: The impact of the failure is communicated to those impacted.

L og Log: The error is appropriately logged; or not logged.

U ser Interface User Interface: The error is reported in the user interface in terms that the user understands.

R ecovery Recovery: The user is informed of what they need to do to recover from the error.

E motions Emotions: The error handling and reporting has a positive influence on user emotions.

Security Vulnerabilities

1. Injection Injection: Injection flaws occur when untrusted data is sent to an interpreter as part of a command. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without authorization.

2. Broken authentication and session management Broken authentication and session management: Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities.

3. Cross-Site Scripting Cross-Site Scripting (XSS): XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.

4. Insecure Direct Object References Insecure Direct Object References: A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to gain unauthorized access to data.

5. Security Misconfiguration Security Misconfiguration: Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.

6. Sensitive Data Exposure Sensitive Data Exposure: Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.

7. Missing Function Level Access Control Missing Function Level Access Control: Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.

8. Cross-Site Request Forgery Cross-Site Request Forgery (CSRF): A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.

9. Using Components with Known Vulnerabilities Using Components with Known Vulnerabilities: Running software components with known vulnerabilities can compromise the vulnerable components and anything those components can access -- undermining defenses.

10. Unvalidated Redirects and Forwards Unvalidated Redirects and Forwards: Using untrusted data, without validation, to determine the destination of redirects and forwards can enable attackers to redirect victims to phisihing or malware sites.

Is There A Problem Here?

20100206

Toyota Accelerates

20100205

Your car computer can kill you?

20100204

Stop & Go

Problem or no problem?

Usability Heuristics

Consistency Heuristics

FAILURE Heuristics

Security Vulnerabilities

Popular

Recent Problems

Recent Comments