This repository has been archived by the owner on Nov 11, 2023. It is now read-only.
forked from maplibre/maplibre
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathSECURITY_POLICY.txt
68 lines (50 loc) · 2.53 KB
/
SECURITY_POLICY.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
MapLibre Security and Vulnerability Reporting Policy
1. Services Covered by this Policy
This policy covers all services directly operated by us (MapLibre).
Services can be identified by the following means:
- The website has a .well-known/security.txt that links to this policy.
- The reverse DNS of an IP address resolves to one of the following
domain (or subdomains): maplibre.org
2. Acceptable Use
We generally invite security researchers to search for vulnerabilities
in our services. We kindly ask to not put any actual user data or
production systems at risk.
3. Classification of Vulnerabilities
We will consider a vulnerability report most likely as relevant if it
reports one of the following problems:
- Memory-safety issues in any MapLibre project
- The vulnerability can be used to directly access non-public
information that either reveals further security relevant problems or
contains user data, credentials, or sensitive data in general.
- The vulnerability can be used to disrupt the orderly operation of a
service (Denial of Service).
- The vulnerability can be used to manipulate data within the service.
- XSS, CSRF, RCE, authentication/authorization bypass, SQL inections,
etc are considered relevant.
We will consider a vulnerability report most likely as NOT relevant if
it reports one of the following problems:
- Missing security features, for example HTTP headers, if they are not
actually preventing a vulnerability.
- Publicly accessible version strings of used software.
- Security vulnerablities that can only be used within the scope of the
used account.
4. Reporting Vulnerabilities
Report vulnerabilities via e-mail to [email protected]. MapLibre does not
offer a GPG key for encryption.
Please make sure that you include the following information:
- Which service is affected
- How can the bug be used/exploited
- Explanation of the risk
Reports will be answered within 48 hours. If you have not received an
answer within that time frame, feel free to contact us again.
For used open source software, we recommend to file bug reports and/or
pull requests against the upstream repositories. This includes hardening
instructions in the installation documentation.
5. Bug Bounties / Vulnerability Rewards
The MapLibre project does not currently pay rewards.
6. Acknowledgement
We list recognized reports of vulnerablities online if the reporting
security researcher agrees.
7. About this Policy
This policy is MIT licensed. Feel free to suggest modifications and
additions at https://github.com/digitalfabrik/security-policy.