Bug bounty program · HackerOne
Central Security Project
Most upvoted reports8
- #688270ValidOS Command Injection in Nexus Repository Manager 2.x(bypass CVE-2019-5475)Central Security Project · Command and Code Injection · 2019–34votes
- #654888ValidOS Command Injection in Nexus Repository Manager 2.xCentral Security Project · Command and Code Injection · 2019–28votes
- #683965ValidUnrestricted File Upload Leading to Remote Code ExecutionCentral Security Project · Input Validation and Logic · 2019–12votes
- #724599ValidOS Command Injection in Nexus Repository Manager 2.x -- Bypass for Nexus Repository Manage 2.14.15-01 Command Injection fixCentral Security Project · Command and Code Injection · 2020–7votes
- #509315Validc3p0 may be exploited by a Billion Laughs Attack when loading XML configurationCentral Security Project · Other weaknesses · 2019–5votes
- #917843ValidUnsafe deserialization in Nexus Repository helm pluginCentral Security Project · Deserialization and Object Injection · 2020–5votes
- #506791InformativePippo XML Entity Expansion (Billion Laughs Attack)Central Security Project · Other weaknesses · 2019–1votes
- #879740ValidRepositories of datanucleus are fetched over insecure protocol (http insted of https)Central Security Project · Cryptography · 2020–1votes
Subdomains36
0 covered by the program's own scope · 0 first seen this week
Roots:maven.org 36
36 names
| Name | Scope | First seen |
|---|---|---|
| acme.maven.org | No domain scope published | 2026-11-14 |
| apache.maven.org | No domain scope published | 2026-11-14 |
| repo.apache.maven.orggit | No domain scope published | 2026-11-14 |
| blogs.maven.org | No domain scope published | 2026-11-14 |
| central.maven.org | No domain scope published | 2026-11-14 |
| central-s3.maven.orgdata | No domain scope published | 2026-11-14 |
| central-staging.maven.orgstaging | No domain scope published | 2026-11-14 |
| central02.maven.org | No domain scope published | 2026-11-14 |
| central1.maven.org | No domain scope published | 2026-11-14 |
| gslb.maven.org | No domain scope published | 2026-11-14 |
| a.bad.hostname.maven.org | No domain scope published | 2026-11-14 |
| mail.maven.orgmail | No domain scope published | 2026-11-14 |
| repo1.maven1.maven.orggit | No domain scope published | 2026-11-14 |
| gcp.mirrors.maven.org | No domain scope published | 2026-11-14 |
| repo.maven.orggit | No domain scope published | 2026-11-14 |
| repo1.maven.orggit | No domain scope published | 2026-11-14 |
| insecure.repo1.maven.orggit | No domain scope published | 2026-11-14 |
| ipv6.repo1.maven.orggit | No domain scope published | 2026-11-14 |
| snapshots.repo1.maven.orggit | No domain scope published | 2026-11-14 |
| staging.repo1.maven.orggit, staging | No domain scope published | 2026-11-14 |
| repo2.maven.orggit | No domain scope published | 2026-11-14 |
| staging.repo2.maven.orggit, staging | No domain scope published | 2026-11-14 |
| repol.maven.org | No domain scope published | 2026-11-14 |
| search.maven.org | No domain scope published | 2026-11-14 |
| search-aws.maven.org | No domain scope published | 2026-11-14 |
| search-uk.maven.org | No domain scope published | 2026-11-14 |
| search-us.maven.org | No domain scope published | 2026-11-14 |
| www.search.maven.org | No domain scope published | 2026-11-14 |
| status.maven.orgmonitoring | No domain scope published | 2026-11-14 |
| u003erepo1.maven.org | No domain scope published | 2026-11-14 |
| u003esearch.maven.org | No domain scope published | 2026-11-14 |
| uk.maven.org | No domain scope published | 2026-11-14 |
| uk1.maven.org | No domain scope published | 2026-11-14 |
| unreachable.maven.org | No domain scope published | 2026-11-14 |
| us-float.maven.org | No domain scope published | 2026-11-14 |
| www.maven.org | No domain scope published | 2026-11-14 |
Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. See the subdomains on the Atlas or search the subdomains of every program.
A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-14.