Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
5 added 53 characters in body
source | link

Let's assume the worst possible attacker. And for some reason, attacking without teamviewer isn't an option (like, the SMB bug, AMT in the CPU, any 0day from that angle, deliberate backdoors from MS and US government, ...).

Step 1: Using another 0day that only works if the attacker already has access to the desktop (but no admin) to get admin permissions. Then...

  • Configuring Intels AMT (or AMDs counterpart). Result: Total control as long as a network connection is possible (even when the computer is turned off etc.).
  • Flashing the BIOS/UEFI with something worse (because that usually needs a reboot, configuring Teamviewer to start at boot is helpful). Eg. to prevent that AMT is turned off again.
  • Writing something to the hard disks spare sector area (that's not part of formatting) and/or flashing the hard disks firmware. To prevent you just switching the mainboard.
  • Replacing some other firmwares, just to be sure.

...

And without 0days to get admin permissions? Or if the attacker just wants an more easy way? Well ... downloading child p*rn and then suing you. (And while sad, in some countries an IP is enough to go to jail. Even if you have evidence that you weren't at home where your DSL cable is, or anything like that.).
(Because the focus is on the computer: While you're in jail, the attacker enters your home and does whatever he wants with direct access to the hardware).

Let's assume the worst possible attacker. And for some reason, attacking without teamviewer isn't an option (like, the SMB bug, AMT in the CPU, any 0day from that angle, deliberate backdoors from MS and US government, ...).

Step 1: Using another 0day that only works if the attacker already has access to the desktop (but no admin) to get admin permissions. Then...

  • Configuring Intels AMT (or AMDs counterpart). Result: Total control as long as a network connection is possible (even when the computer is turned off etc.).
  • Flashing the BIOS/UEFI with something worse (because that usually needs a reboot, configuring Teamviewer to start at boot is helpful). Eg. to prevent that AMT is turned off again.
  • Writing something to the hard disks spare sector area (that's not part of formatting) and/or flashing the hard disks firmware. To prevent you just switching the mainboard.
  • Replacing some other firmwares, just to be sure.

...

And without 0days to get admin permissions? Well ... downloading child p*rn and suing you. (And while sad, in some countries an IP is enough to go to jail. Even if you have evidence that you weren't at home where your DSL cable is, or anything like that.).
(Because the focus is on the computer: While you're in jail, the attacker enters your home and does whatever he wants with direct access to the hardware).

Let's assume the worst possible attacker. And for some reason, attacking without teamviewer isn't an option (like, the SMB bug, AMT in the CPU, any 0day from that angle, deliberate backdoors from MS and US government, ...).

Step 1: Using another 0day that only works if the attacker already has access to the desktop (but no admin) to get admin permissions. Then...

  • Configuring Intels AMT (or AMDs counterpart). Result: Total control as long as a network connection is possible (even when the computer is turned off etc.).
  • Flashing the BIOS/UEFI with something worse (because that usually needs a reboot, configuring Teamviewer to start at boot is helpful). Eg. to prevent that AMT is turned off again.
  • Writing something to the hard disks spare sector area (that's not part of formatting) and/or flashing the hard disks firmware. To prevent you just switching the mainboard.
  • Replacing some other firmwares, just to be sure.

...

And without 0days to get admin permissions? Or if the attacker just wants an more easy way? Well ... downloading child p*rn and then suing you. (And while sad, in some countries an IP is enough to go to jail. Even if you have evidence that you weren't at home where your DSL cable is, or anything like that.).
(Because the focus is on the computer: While you're in jail, the attacker enters your home and does whatever he wants with direct access to the hardware).

4 deleted 1 character in body
source | link

Let's assume the worst possible attacker. And for some reason, attacking without teamviewer isn't an option (like, the SMB bug, AMT in the CPU, any 0day from that angle, deliberate backdoors from MS and US government, ...).

Step 1: Using another 0day that only works if the attacker already has access to the desktop (but no admin) to get admin permissions. Then...

  • Configuring Intels AMT (or AMDs counterpart). Result: Total control as long as a network connection is possible (even when the computer is turned off etc.).
  • Flashing the BIOS/UEFI with something worse (because that usually needs a reboot, configuring Teamviewer to start at boot is helpful). Eg. to prevent that AMT is turned off again.
  • Writing something to the hard disks spare sector area (that's not part of formatting) and/or flashing the hard disks firmware. To prevent you just switching the mainboard.
  • Replacing some other firmwares, just to be sure.

...

And without 0days to get admin permissions? Well ... downloading child p*rn and suing you. (And while sad, in some countries an IP is enough to go to jail. Even if you have evidence that you weren't at home where your DSL cable is, or anything like that.).
(Because the focus is on the computer: While you're in jail, the attacker enters your home and doingdoes whatever he wants with direct access to the hardware).

Let's assume the worst possible attacker. And for some reason, attacking without teamviewer isn't an option (like, the SMB bug, AMT in the CPU, any 0day from that angle, deliberate backdoors from MS and US government, ...).

Step 1: Using another 0day that only works if the attacker already has access to the desktop (but no admin) to get admin permissions. Then...

  • Configuring Intels AMT (or AMDs counterpart). Result: Total control as long as a network connection is possible (even when the computer is turned off etc.).
  • Flashing the BIOS/UEFI with something worse (because that usually needs a reboot, configuring Teamviewer to start at boot is helpful). Eg. to prevent that AMT is turned off again.
  • Writing something to the hard disks spare sector area (that's not part of formatting) and/or flashing the hard disks firmware. To prevent you just switching the mainboard.
  • Replacing some other firmwares, just to be sure.

...

And without 0days to get admin permissions? Well ... downloading child p*rn and suing you. (And while sad, in some countries an IP is enough to go to jail. Even if you have evidence that you weren't at home where your DSL cable is, or anything like that.).
(Because the focus is on the computer: While you're in jail, the attacker enters your home and doing whatever he wants with direct access to the hardware).

Let's assume the worst possible attacker. And for some reason, attacking without teamviewer isn't an option (like, the SMB bug, AMT in the CPU, any 0day from that angle, deliberate backdoors from MS and US government, ...).

Step 1: Using another 0day that only works if the attacker already has access to the desktop (but no admin) to get admin permissions. Then...

  • Configuring Intels AMT (or AMDs counterpart). Result: Total control as long as a network connection is possible (even when the computer is turned off etc.).
  • Flashing the BIOS/UEFI with something worse (because that usually needs a reboot, configuring Teamviewer to start at boot is helpful). Eg. to prevent that AMT is turned off again.
  • Writing something to the hard disks spare sector area (that's not part of formatting) and/or flashing the hard disks firmware. To prevent you just switching the mainboard.
  • Replacing some other firmwares, just to be sure.

...

And without 0days to get admin permissions? Well ... downloading child p*rn and suing you. (And while sad, in some countries an IP is enough to go to jail. Even if you have evidence that you weren't at home where your DSL cable is, or anything like that.).
(Because the focus is on the computer: While you're in jail, the attacker enters your home and does whatever he wants with direct access to the hardware).

3 added 172 characters in body
source | link

Let's assume the worst possible attacker. And for some reason, attacking without teamviewer isn't an option (like, the SMB bug, AMT in the CPU, any 0day from that angle, deliberate backdoors from MS and US government, ...).

Step 1: Using another 0day that only works if the attacker already has access to the desktop (but no admin) to get admin permissions. Then...

  • Configuring Intels AMT (or AMDs counterpart). Result: Total control as long as a network connection is possible (even when the computer is turned off etc.).
  • Flashing the BIOS/UEFI with something worse (because that usually needs a reboot, configuring Teamviewer to start at boot is helpful). Eg. to prevent that AMT is turned off again.
  • Writing something to the hard disks spare sector area (that's not part of formatting) and/or flashing the hard disks firmware. To prevent you just switching the mainboard.
  • Replacing some other firmwares, just to be sure.

...

And without 0days to get admin permissions? Well ... downloading child p*rn and suing you. (And while sad, in some countries an IP is enough to go to jail. Even if you have evidence that you weren't at home where your DSL cable is, or anything like that.).
(Because the focus is on the computer: While you're in jail, the attacker enters your home and doing whatever he wants with direct access to the hardware).

Let's assume the worst possible attacker. And for some reason, attacking without teamviewer isn't an option (like, the SMB bug, AMT in the CPU, any 0day from that angle, deliberate backdoors from MS and US government, ...).

Step 1: Using another 0day that only works if the attacker already has access to the desktop (but no admin) to get admin permissions. Then...

  • Configuring Intels AMT (or AMDs counterpart). Result: Total control as long as a network connection is possible (even when the computer is turned off etc.).
  • Flashing the BIOS/UEFI with something worse (because that usually needs a reboot, configuring Teamviewer to start at boot is helpful). Eg. to prevent that AMT is turned off again.
  • Writing something to the hard disks spare sector area (that's not part of formatting) and/or flashing the hard disks firmware. To prevent you just switching the mainboard.
  • Replacing some other firmwares, just to be sure.

...

And without 0days to get admin permissions? Well ... downloading child p*rn and suing you. (And while sad, in some countries an IP is enough to go to jail. Even if you have evidence that you weren't at home where your DSL cable is, or anything like that.)

Let's assume the worst possible attacker. And for some reason, attacking without teamviewer isn't an option (like, the SMB bug, AMT in the CPU, any 0day from that angle, deliberate backdoors from MS and US government, ...).

Step 1: Using another 0day that only works if the attacker already has access to the desktop (but no admin) to get admin permissions. Then...

  • Configuring Intels AMT (or AMDs counterpart). Result: Total control as long as a network connection is possible (even when the computer is turned off etc.).
  • Flashing the BIOS/UEFI with something worse (because that usually needs a reboot, configuring Teamviewer to start at boot is helpful). Eg. to prevent that AMT is turned off again.
  • Writing something to the hard disks spare sector area (that's not part of formatting) and/or flashing the hard disks firmware. To prevent you just switching the mainboard.
  • Replacing some other firmwares, just to be sure.

...

And without 0days to get admin permissions? Well ... downloading child p*rn and suing you. (And while sad, in some countries an IP is enough to go to jail. Even if you have evidence that you weren't at home where your DSL cable is, or anything like that.).
(Because the focus is on the computer: While you're in jail, the attacker enters your home and doing whatever he wants with direct access to the hardware).

2 added 165 characters in body
source | link
1
source | link