Tutorial5 min read

How to Find Exposed Jenkins CI/CD Servers

Discover misconfigured Jenkins instances that may allow unauthorized access to CI/CD pipelines.

1

Search for Jenkins servers

Jenkins commonly runs on port 8080. Many instances are left publicly accessible.

product:jenkins port:8080
2

Find unauthenticated instances

Look for Jenkins servers responding with 200 OK — likely no authentication required.

product:jenkins http.status:200
Jenkins with no auth can allow script console access (RCE).
3

Check for HTTPS Jenkins

Some Jenkins instances run on HTTPS.

product:jenkins port:443
4

Find vulnerable versions

Search for Jenkins with known CVEs.

product:jenkins has_vuln:true
Jenkins CVE-2024-23897 (file read) was widely exploited.

Remediation & Hardening

  • Enable authentication — never run Jenkins with anonymous read/build access

  • Use HTTPS with valid TLS certificates

  • Place Jenkins behind a VPN or reverse proxy

  • Disable Jenkins CLI if not needed

  • Keep Jenkins and all plugins updated

  • Restrict script console access to admins only

Try It Now

Search for Jenkins across 85M+ indexed hosts — free, no registration required.

Search Jenkins

More How-To Guides

How to Find Exposed Redis ServersHow to Find Exposed MongoDB DatabasesHow to Find Exposed Elasticsearch ClustersHow to Find Exposed Docker APIsHow to Find Exposed RDP ServersHow to Find Exposed MySQL DatabasesHow to Find Exposed Kubernetes Clusters