Handler on Duty: Xavier Mertens
Threat Level: green
Podcast Detail
#Shellshock keeps going; Odd #php backdoors? MS15-2 (telnet) details; More 0-days from #Google; #ODB
If you are not able to play the podcast using the player below: Use this direct link to the audio file: https://chrt.fm/track/2748D7/https://traffic.libsyn.com/securitypodcast/4317.mp3
My Next Class
Application Security: Securing Web Apps, APIs, and Microservices | Online | US Eastern | Jan 27th - Feb 1st 2025 |
Network Monitoring and Threat Detection In-Depth | Baltimore | Mar 3rd - Mar 8th 2025 |
Interested in Internet Storm Center stickers? Check here if there are still some available for today.
Shellshock Keeps On Giving
https://isc.sans.edu/forums/diary/Shellshock+keeps+on+giving/19197/
Odd HTTP Requests For PHP Scripts
https://isc.sans.edu/forums/diary/Strange+Random+GET+PHP+Queries/19199/
Details And Possible PoC For Telnet Vulnerability
(Google cache link below. May not survive much longer)
http://webcache.googleusercontent.com/search?q=cache%3Ahttp%3A%2F%2Fdrops.wooyun.org%2Fpapers%2F4621&ie=utf-8&oe=utf-8
Google Releases Additional 0-Days
https://code.google.com/p/google-security-research/issues/detail?id=128
Vulnerable OBD2 Vehicle Ports
http://www.forbes.com/sites/thomasbrewster/2015/01/15/researcher-says-progressive-insurance-dongle-totally-insecure/
https://isc.sans.edu/forums/diary/Shellshock+keeps+on+giving/19197/
Odd HTTP Requests For PHP Scripts
https://isc.sans.edu/forums/diary/Strange+Random+GET+PHP+Queries/19199/
Details And Possible PoC For Telnet Vulnerability
(Google cache link below. May not survive much longer)
http://webcache.googleusercontent.com/search?q=cache%3Ahttp%3A%2F%2Fdrops.wooyun.org%2Fpapers%2F4621&ie=utf-8&oe=utf-8
Google Releases Additional 0-Days
https://code.google.com/p/google-security-research/issues/detail?id=128
Vulnerable OBD2 Vehicle Ports
http://www.forbes.com/sites/thomasbrewster/2015/01/15/researcher-says-progressive-insurance-dongle-totally-insecure/
Discussion
Another thing you can do with that port, without even having to leave the dongle connected permanently, is program additional remote keyfobs that can be used to unlock the car doors in the future. I recently had one of these keyfobs fail, and watched the mechanic connect his computer to that port in order to program the car to accept the replacement keyfob. So physical access to the interior of your car with access to that port is a no-win scenario, basically. If you've ever let a valet park your car, it could be 0wned already.
New Discussions closed for all Podcasts older than two(2) weeks
Please send your comments to our Contact Form
Application Security: Securing Web Apps, APIs, and Microservices | Online | US Eastern | Jan 27th - Feb 1st 2025 |
Network Monitoring and Threat Detection In-Depth | Baltimore | Mar 3rd - Mar 8th 2025 |
Application Security: Securing Web Apps, APIs, and Microservices | Orlando | Apr 13th - Apr 18th 2025 |
Application Security: Securing Web Apps, APIs, and Microservices | San Diego | May 5th - May 10th 2025 |
Network Monitoring and Threat Detection In-Depth | Baltimore | Jun 2nd - Jun 7th 2025 |
I believe you're missing two key points in your discussion. First, Forbes target audience will be middle to upper-class who will own or drive one of these newer model vehicles and potentially utilize services where they regularly give others access to their car (valet, cleaning, etc). Second, just like a server back door exploit you described in this same podcast, this service could leave the reprogrammed dongle for someone else to unlock the door, start the engine and be on their way much later (hours to weeks) which would keep the car owner from linking the two events in their mind.