liveBook · Manning

Exploit

As explained in Grokking Web Application Security

An exploit is code or a procedure that takes advantage of a vulnerability to perform malicious or unauthorized activity.

An exploit is code that demonstrates how a vulnerability can be used for malicious activity. The practical risk is not merely that a flaw exists: an attacker can use it to turn that flaw into unauthorized action. section 1.1

Proof-of-concept exploits often appear when a vulnerability is published, and sometimes earlier. They make the impact of a flaw concrete, which is why a patch alone is not the whole security story: teams need to know which exposed software and access points an attacker could target. section 1.1

Exploits appear in several security roles:

  • Black hat attackers use tools and scripts to find vulnerabilities they can exploit for malicious or illegal aims. section 1.1
  • White hat hackers use comparable tools during penetration testing to locate vulnerable access points before attackers do. section 1.1
  • Security researchers document vulnerabilities and may demonstrate them before a patch leads to a CVE record. section 1.1

How Grokking Web Application Security covers it

How deep it goes
Defines exploits and proof-of-concept exploits through attacker, researcher, and penetration-testing scenarios without implementation internals.
Examples
Uses Kali Linux scanning, Apache Tomcat vulnerabilities, CVE publication, and proof-of-concept code as examples.
What you can do after
Evaluate/understand how a published vulnerability can be demonstrated as malicious activity.
How it connects
Connects exploits with vulnerabilities, proof-of-concept exploits, CVE records, penetration testing, and bug bounties.

Also explained in

Compare how 3 books explain exploit →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Web Application Security. The section links point to the parts of the book it draws on.