vulnerability
A weakness in software or configuration that an attacker could use to cause harm.
In more detail
Publicly known vulnerabilities in software packages get a CVE identifier and a severity score, so scanners can check what you run against them. Many vulnerabilities come from ordinary mistakes, such as injection, broken access control or outdated packages, which is why code and dependencies are reviewed, scanned and updated regularly.
Related terms
- OWASP API Security Top 10 — OWASP’s ranked list of the ten most critical security risks specific to APIs, last updated in 2023.
- SQL injection — An attack where untrusted input is joined into a database query so that part of it runs as SQL, letting an attacker read or change data.
- broken access control — A flaw where the server lets a caller act on data or operations it should not, for example by trusting a user name the caller supplied or skipping an ownership check.
- resource exhaustion — Running a service out of memory, time, connections or money by making it do unbounded work, whether by accident or on purpose.
- CVE — A public identifier, such as CVE-2024-21626, given to one known security vulnerability so everyone can refer to it.
- CVSS severity — A standard 0 to 10 score, grouped as low, medium, high or critical, for how dangerous a vulnerability is.
- image scanning — Checking the packages inside an image against lists of known vulnerabilities.
- patching — Updating software to a version that fixes known bugs or vulnerabilities.
- attack surface — Everything an attacker could try to use against a system: open ports, installed programs, accounts and settings.
- exploit — A piece of code or a technique that takes advantage of a vulnerability to make a system do something it should not.
- finding — One problem reported by a scanner or review, with a location, a rule and a reason.
Taught in
- Security Best Practices — Modern API Architecture: REST, GraphQL & gRPC
- AWS Organizations, Account Hierarchies & Azure Management Groups — Cloud Security & DevSecOps Engineering
- Static Application Security Testing with Semgrep — Cloud Security & DevSecOps Engineering
- Software Composition Analysis with Trivy — Cloud Security & DevSecOps Engineering
- Container Hardening: Distroless & Rootless — Cloud Security & DevSecOps Engineering
- Threat Detection with GuardDuty & Anomaly Analytics — Cloud Security & DevSecOps Engineering
- Cloud Security Posture Management & Remediation — Cloud Security & DevSecOps Engineering
- Risk Assessment: Qualitative vs Quantitative — Cybersecurity Fundamentals, GRC & Cryptography
- Public Key Infrastructure: X.509 Certificates & CAs — Cybersecurity Fundamentals, GRC & Cryptography
- Disaster Recovery Sites: Hot, Warm & Cold — Cybersecurity Fundamentals, GRC & Cryptography
- Backup Architectures: 3-2-1, Immutability & Air-Gaps — Cybersecurity Fundamentals, GRC & Cryptography
- FROM, WORKDIR, COPY And ADD — Docker Architecture & Production Containers
- Multi Stage Builds, Targets And Build Secrets — Docker Architecture & Production Containers
- Minimal Bases, Non Root Users And Smaller Images — Docker Architecture & Production Containers
- Scan, Patch And Inspect The Software Supply Chain — Docker Architecture & Production Containers
- Session Architecture: HTTP-Only Cookies vs Tokens — Production Full-Stack Engineering
- Role-Based & Attribute Access Control: RBAC & ABAC — Production Full-Stack Engineering
- Containerization Architecture: Multi-Stage Dockerfiles — Production Full-Stack Engineering
- SQL Injection: The Exploit — Application Security & Threat Modeling for Engineers
- Dependency Risk And Typosquatting — Application Security & Threat Modeling for Engineers
- Software Bill Of Materials — Application Security & Threat Modeling for Engineers
- Image Scanning And Trivy — Application Security & Threat Modeling for Engineers