APNIC (Asia Pacific Network Information Centre) is an open, membership-based, not-for-profit organization providing Internet addressing services to the Asia Pacific region.
As the Regional Internet Registry, our primary role is to provide Internet number resources (IPv4, IPv6 and ASNs) to our Members.
APNIC strives to support the security of its Members, but to do this APNIC must ensure it maintains strong security on its own network infrastructure.
APNIC looks forward to working with the security community towards these goals.
Response Targets
APNIC will make a best effort to meet the following response targets for hackers participating in our program:
- Time to first response (from report submit) - 2 business days
- Time to triage (from report submit) - 5 business days
- Time to Resolution - depends on severity and complexity
We’ll try to keep you informed about our progress throughout the process.
Disclosure Policy
- Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
Program Rules
- Please provide detailed reports with reproducible steps.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.
- Third-party services such as Lets Encrypt, Okta, Cloudflare, Zoom, or similar applications are not in-scope for the program and will not be accepted.
Test Plan
Some services (e.g. academy.apnic.net and my.apnic.net) use an “APNIC Login” SSO account to access them. To create an “APNIC Login”, please go to https://my.apnic.net/ and complete the new user registration using your HackerOne email alias: [H1username]@wearehackerone.com.
Note: The user creation and profile editing are done on login.apnic.net which is currently out of scope for this program (see Scope section below). You of course may use login.apnic.net as a user would for accessing other sites.
-
orbit.apnic.net hosts live mailing lists. Please only use the Testing list at https://orbit.apnic.net/postorius/lists/testing.lists.apnic.net/ which was created specifically for vulnerability testing. We don't want testing messages going out to legitimate public subscribers. The testing list is accessible via email and WebUI.
-
submission.apnic.net hosts live conference events. Please use the "Test Only" event at https://submission.apnic.net/user/login.php?event=163 which was setup specifically for vulnerability testing.
Out of scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- FTP, HTTP, or rsync directory listing on the following: (working as intended)
- ftp.apnic.net
- rpki.apnic.net
- rsync.apnic.net (same server as ftp.apnic.net)
- nori.apnic.net (same server as ftp.apnic.net)
- submit.origin.apnic.net (same server as ftp.apnic.net)
- aso.apnic.net
- Information disclosure and HTML injection vulnerabilities including XSS vulnerabilities for *.rand.apnic.net and *.labs.apnic.net
- Any activity that could lead to the disruption of our service (DoS)
- Clickjacking on pages with no sensitive actions
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Attacks requiring MITM or physical access to a user's device
- Previously known vulnerable libraries without a working Proof of Concept
- Comma Separated Values (CSV) injection without demonstrating a vulnerability
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Rate limiting or brute-force issues on non-authentication endpoints
- Missing HttpOnly or Secure flags on cookies that don’t relate to user authentication/credentials
- Missing email best practices (invalid, incomplete, or missing SPF/DKIM/DMARC records, etc.)
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)
- Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis
- Tabnabbing
- Open redirect - unless an additional security impact can be demonstrated
- Issues that require unlikely user interaction
- Self Cross Site Scripting (XSS)
Safe Harbor
When conducting vulnerability research that is:
- In scope as stipulated in the above; and
- Subject to a report with the required information being submitted to us in a timely manner
We will consider this research conducted to be:
- Authorized in view of any applicable anti-hacking and cybersecurity laws and regulations, and we will not initiate or support legal action against you for accidental, good faith violations of this program;
- Authorized in view of relevant anti-circumvention and copyright laws, and we will not bring a claim against you for circumvention of access control technological protection measures; and
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
You are expected, as always, to comply with all applicable laws.
If legal action is initiated by a third party against you and you have complied with this program, we will take steps to make it known that your actions were conducted in compliance with this program.
Thank you for helping keep APNIC and our Members safe!
