Skip to content

Commit

Permalink
Merge pull request #516 from bugcrowd/QA-Checks
Browse files Browse the repository at this point in the history
Fixed QA issues
  • Loading branch information
evildaemond authored Nov 20, 2023
2 parents 82db8c5 + 026f2b8 commit 38d1c82
Show file tree
Hide file tree
Showing 48 changed files with 35 additions and 5 deletions.
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Guidance

Provide a step-by-step walkthrough with a screenshot on how you exploited the vulnerability. Your submission must include evidence of the vulnerability and not be theoretical in nature. For an infotainment vulnerability, please include detailed instructions that can be followed to easily demonstrate and reproduce the issue. If data was found using Open Source Intelligence (OSINT), please provide steps to where and how it was found.

Attempt to completely stop the vehicle from functioning if the infotainment system controls a mechanical aspect of the vehicle. If this is possible, provide a full Proof of Concept (PoC) here.
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# OTA Firmware Manipulation

## Overview of the Vulnerability

The In-Vehicle Infotainment (IVI) system, is a central unit in an automotive vehicle's dashboard that centralizes information and entertainment systems and their controls. Misconfigurations in the IVI system can lead to security weaknesses. An attacker can take advantage of IVI misconfiguration and inject a payload into the IVI system, causing the system to not behave as intended.

## Business Impact

This IVI system misconfiguration can result in reputational damage and indirect financial loss for the business through the impact to customers’ trust in the security and safety of the automotive vehicle.

## Steps to Reproduce

1. The IVI system input is identified by using {{hardware}} on {{target}}
1. Connect to {{target}} by using {{application}} with {{hardware}}
1. Inject the following IVI system message payload:

{{payload}}

1. Observe that {{action}} occurs as a result

## Proof of Concept (PoC)

The image(s) below demonstrates the process by which an attacker identifies where the IVI system communication occurs. It also shows how an attacker connects to the {{target}}, and is able to inject the payload(s):

{{screenshot}}
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Alter Sensitive Information - Iterable Object Identifiers
# Edit/Delete Sensitive Information/Iterable Object Identifiers

## Overview of the Vulnerability

Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Manipulate Non-Sensitive Information
# Read/Edit/Delete Non-Sensitive Information

## Overview of the Vulnerability

Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Manipulate Sensitive Information - GUID or Complex Object Identifiers
# Read/Edit/Delete Sensitive Information/Complex Object Identifiers(GUID)

## Overview of the Vulnerability

Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Read Sensitive Information (PII) - Iterable Object Identifiers
# Read/Edit/Delete Sensitive Information/Iterable Object Identifiers

## Overview of the Vulnerability

Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Read Sensitive Information - Iterable Object Identifiers
# Read Sensitive Information/Iterable Object Identifiers

## Overview of the Vulnerability

Expand Down

0 comments on commit 38d1c82

Please sign in to comment.