* Posts by VRocker

2 publicly visible posts • joined 7 Aug 2018

Time to party like it's 2002: Acura and Honda car clocks knocked back 20 years by bug

VRocker

I was waiting for this news article to appear (i was thinking of prodding you guys about it myself but i'm lazy...)

So i have some more info on this as it's affected my CR-Z and i've been looking into it. The date reported by the GPS is May 2002, exactly 1024 weeks ago so it is the rollover issue. It's not due to GPSd though as these units run Windows CE for Automotive. The reason it's going back to 1am every time the car turns on is due to some error handling in the code itself. If the date is before a certain date, it resets to 1st Jan 2002 at midnight. The 1am comes from the auto summer time kicking in (which goes on the date reported by the GPS, not the 'corrected' date) so being May 2002 means it's summer time. Timezones also get applied to the reset time which is why Americans are seeing 4/5am.

The suspected reason why they say it'll fix itself in August is that the date valid check could well be 2003. On 17th August, the unit will think it's 2003 and may say the correct time, although auto summer time won't work for obvious reasons.

I have my doubts that it'll correct itself this August though, as everything i'm seeing in the code seems to point to 2004 being the valid date check... but we'll see.

I currently have Ghidra open with the firmware for my own nav trying to find this check to nop out... we'll see how that goes!

Bank on it: It's either legal to port-scan someone without consent or it's not, fumes researcher

VRocker

I actually noticed this back in 2016 and it put me off banking with them back then. I did find it a bit strange that they were trying all sorts of port scans, including RDP and VNC.

They say its for 'scanning for malware' but they never actually alert the users that they found open ports (or didn't last time i checked). I have RDP enabled on this machine but not to the internet obviously. The port is checked from your machine (Websocket from the check.js) so even if its not open to the internet the scanner should find it 'open' and report back. Nothing flags up in pfsense about any outside scans so they're not checking if it is open to the internet but yet, i get no 'alert' to say they found something suspicious on my machine so what is it actually used for?

I imagine the way they'll get around this thing is that the scan is done by your own browser rather than their servers so they're not technically scanning you...