nerdexam
GIAC

GCIH · Question #356

Prior to restoring clean data from backups, what are the recommended activities for bringing a server's operating system and applications back online following a buffer overflow exploit that allowed…

The correct answer is D. Rebuild the server OS and application from original media, change exposed user passwords, and. After a buffer overflow that granted an attacker administrator access, the OS and applications cannot be trusted and must be rebuilt from clean, original media before restoring data from backups.

Incident Response & Cyber Kill Chain

Question

Prior to restoring clean data from backups, what are the recommended activities for bringing a server's operating system and applications back online following a buffer overflow exploit that allowed the attacker to create a new administrator account?

Options

  • ARemove the rogue administrator account, change exposed user passwords, and implement a
  • BRebuild the server OS and applications from the latest backup, change exposed user passwords,
  • CRemove the rogue administrator account, change exposed user passwords, and apply all missing
  • DRebuild the server OS and application from original media, change exposed user passwords, and

How the community answered

(46 responses)
  • A
    2% (1)
  • B
    15% (7)
  • C
    7% (3)
  • D
    76% (35)

Why each option

After a buffer overflow that granted an attacker administrator access, the OS and applications cannot be trusted and must be rebuilt from clean, original media before restoring data from backups.

ARemove the rogue administrator account, change exposed user passwords, and implement a

Removing only the rogue administrator account does not eliminate backdoors or rootkits that the attacker may have installed during the period of unauthorized admin access.

BRebuild the server OS and applications from the latest backup, change exposed user passwords,

Rebuilding from the latest backup risks restoring a system that was already compromised before the backup was taken, since the attacker had admin-level access and could have altered system files or introduced persistence mechanisms.

CRemove the rogue administrator account, change exposed user passwords, and apply all missing

Removing the rogue account and applying missing patches does not address deeply embedded malware or kernel-level rootkits that may have been installed while the attacker held elevated privileges.

DRebuild the server OS and application from original media, change exposed user passwords, andCorrect

Rebuilding from original installation media provides a known-good, trusted baseline that eliminates any rootkits, backdoors, or persistent malware installed by the attacker while they held administrator privileges. Backups may predate the discovery but not the compromise itself, and are therefore unreliable as a starting point. Changing exposed passwords and applying all missing patches after the clean rebuild prevents re-exploitation of the same vulnerability.

Concept tested: Post-compromise server recovery using original installation media

Source: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r2.pdf

Topics

#buffer overflow recovery#system rebuild#incident recovery#post-exploitation remediation

Community Discussion

No community discussion yet for this question.

Full GCIH Practice