An exploit is a concrete practical way of turning a known vulnerability into an effect the owner did not intend to allow.
The word names that misuse of a weakness, and this page stops at the idea, the harm, and the defense.
How it works
A vulnerability is a flaw that may allow an unintended effect, and an exploit is the use of that flaw to cause the effect.
Examples of harm include running unwanted software, reading data the person should not see, or making a service fail.
Defense closes the flaw by update or configuration, reduces who can reach the exposed system, and watches for the effect without publishing steps, code, or commands that would carry the exploit out.
Proof material belongs in a private, authorized fix process, not in a public article.
Concrete examples
- A vendor update closes a flaw that had allowed an outsider to read files the application never meant to serve.
- A team disables an exposed service that cannot be patched this week, shrinking who can reach the weakness.
- Monitoring reports the unwanted effect, and the write up for staff describes impact and patch priority without reproduction steps.
Protective measures
- Patch known vulnerabilities on a schedule, and isolate systems you cannot patch.
- Reduce exposure so fewer people and fewer networks can reach a service that still has a weakness.
- Watch for the unintended effect, and keep any reproduction detail inside a private fix record.
- Tell operators the impact and the required update, not a procedure they could reuse against another system.