Jump to content
SAU Community

Recommended Posts

Another one here for a whole lot of characters appearing when clicking on an image.

Also noticed when i first logged in today this site wanted to install an Active X control, some Microsoft Data something or other. I didnt install it as i didnt see a notice to say that it was okay to run on the bulletin board.

Some of the fonts are showing up larger than they usually do aswell

Are these related?

I still can't upload images into private messages.

I browse, double click and the image name appears but when I ckick on add attachment it goes to a blank page rather than show the attachment in the pm.

Anyone else have this problem or have I picked up a virus or something?

i stil cant upload, and now i cant even login to msn.. that dsb.exe must have infected my pc, and now i feel like taking SAU to court.. :\

lol, if you read the conditions when you join the site there is a bit in there about SAU not being liable for such actions as you should have adequate protection.

lol, if you read the conditions when you join the site there is a bit in there about SAU not being liable for such actions as you should have adequate protection.

im just mucking around, relax.. but i suggest u get someone to fix this crap.. the exploit is still there..

We realise there is an issue.

Its a lot harder to fix something than you realise because there are limited people with access.

And the people with access are busy, they have thier own personal lives as SAU Admins/Mods are unpaid...

If your own PC is correctly protected then you wont have an issue.

Please be patient. Constantly posting about the fact it isnt fixed, simply is not going to help the issue especially when your not even a donor :D

For the exploit to work it *needs* Microsoft XML Core Services to be installed. Microsoft XML Core Services are not installed by default on Windows XP, but there seems to be a lot of packages using it, Visual Studio appears to be one common one. You can check in the Add or Remove Programs applet if you have it installed.

> The exploit works in both IE6 and IE7, which makes sense since it's exploiting a vulnerability in an ActiveX object, not in the browser itself. When executed the exploit creates an MSXML 4.0 ActiveX object (88d969c5-f192-11d4-a65f-0040963251e5). It then uses multiple setRequestHeader() method calls to execute shellcode which is included with the exploit. Once executed the shellcode (of course) first downloads the first stage downloader. At the moment it's a file called tester.dat:

16ac9982d177a47a20c4717183493e95 tester.dat

This downloader then downloads subsequent files (yet to be analysed). It looks like some AV vendors are beggining to detect the exploit. At this moment it is being detected by McAfee as Exploit-XMLCoreSrvcs and Symantec as Bloodhound.Exploit.96*. Microsoft also detects it as Exploit:HTML/Xmlreq.A. The best protection, is to prevent the XMLHTTP 4.0 ActiveX Control from running in Internet Explorer, as stated in Microsoft's advisory: http://www.microsoft.com/technet/security/...ory/927892.mspx ."

* http://www.symantec.com/security_response/...-110611-5730-99

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • This. As for your options - I suggest remote mounting the Nissan sensor further away on a length of steel tube. That tube to have a loop in it to handle vibration, etc etc. You will need to either put a tee and a bleed fitting near the sensor, or crack the fitting at the sensor to bleed it full of oil when you first set it up, otherwise you won't get the line filled. But this is a small problem. Just needs enough access to get it done.
    • The time is always correct. Only the date is wrong. It currently thinks it is January 19. Tomorrow it will say it is January 20. The date and time are ( should be ! ) retrieved from the GPS navigation system.
    • Buy yourself a set of easy outs. See if they will get a good bite in and unthread it.   Very very lucky the whole sender didn't let go while on the track and cost you a motor!
    • Well GTSBoy, prepare yourself further. I did a track day with 1/2 a day prep on Friday, inpromptu. The good news is that I got home, and didn't drive the car into a wall. Everything seemed mostly okay. The car was even a little faster than it was last time. I also got to get some good datalog data too. I also noticed a tiny bit of knock which was (luckily?) recorded. All I know is the knock sensors got recalibrated.... and are notorious for false knock. So I don't know if they are too sensitive, not sensitive enough... or some other third option. But I reduced timing anyway. It wasn't every pull through the session either. Think along the lines of -1 degree of timing for say, three instances while at the top of 4th in a 20 minute all-hot-lap session. Unfortunately at the end of session 2... I noticed a little oil. I borrowed some jack stands and a jack and took a look under there, but as is often the case, messing around with it kinda half cleaned it up, it was not conclusive where it was coming from. I decided to give it another go and see how it was. The amount of oil was maybe one/two small drops. I did another 20 minute session and car went well, and I was just starting to get into it and not be terrified of driving on track. I pulled over and checked in the pits and saw this: This is where I called it, packed up and went home as I live ~20 min from the track with a VERY VERY CLOSE EYE on Oil Pressure on the way home. The volume wasn't much but you never know. I checked it today when I had my own space/tools/time to find out what was going on, wanted to clean it up, run the car and see if any of the fittings from around the oil filter were causing it. I have like.. 5 fittings there, so I suspected one was (hopefully?) the culprit. It became immediately apparent as soon as I looked around more closely. 795d266d-a034-4b8c-89c9-d83860f5d00a.mp4       This is the R34 GTT oil sender connected via an adapter to an oil cooler block I have installed which runs AN lines to my cooler (and back). There's also an oil temp sensor on top.  Just after that video, I attempted to unthread the sensor to see if it's loose/worn and it disintegrated in my hand. So yes. I am glad I noticed that oil because it would appear that complete and utter catastrophic engine failure was about 1 second of engine runtime away. I did try to drill the fitting out, and only succeeded in drilling the middle hole much larger and now there's a... smooth hole in there with what looks like a damn sleeve still incredibly tight in there. Not really sure how to proceed from here. My options: 1) Find someone who can remove the stuck fitting, and use a steel adapter so it won't fatigue? (Female BSPT for the R34 sender to 1/8NPT male - HARD to find). IF it isn't possible to remove - Buy a new block ($320) and have someone tap a new 1/8NPT in the top of it ($????) and hope the steel adapter works better. 2) Buy a new block and give up on the OEM pressure sender for the dash entirely, and use the supplied 1/8 NPT for the oil temp sender. Having the oil pressure read 0 in the dash with the warning lamp will give me a lot of anxiety driving around. I do have the actual GM sensor/sender working, but it needs OBD2 as a gauge. If I'm datalogging I don't actually have a readout of what the gauge is currently displaying. 3) Other? Find a new location for the OEM sender? Though I don't know of anywhere that will work. I also don't know if a steel adapter is actually functionally smart here. It's clearly leveraged itself through vibration of the motor and snapped in half. This doesn't seem like a setup a smart person would replicate given the weight of the OEM sender. Still pretty happy being lucky for once and seeing this at the absolute last moment before bye bye motor in a big way, even if an adapter is apparently 6 weeks+ delivery and I have no way to free the current stuck/potentially destroyed threads in the current oil block.
×
×
  • Create New...