You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+19-1Lines changed: 19 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,28 @@
1
1
# Security Policy
2
2
3
+
## Security Considerations
4
+
5
+
### Query Injection
6
+
7
+
JSONPath-Plus evaluates JSONPath expressions provided by the caller. While the default `"eval": "safe"` option prevents arbitrary code execution, it **cannot prevent data exposure if the JSONPath query itself is compromised**.
8
+
9
+
If untrusted input is incorporated into a JSONPath expression, an attacker may be able to alter the query structure by adding additional patterns. This can change how the remaining query is interpreted and may result in **unexpected or broader data being returned** than intended.
10
+
11
+
**Important notes:**
12
+
- This does **not** enable random code execution when using `"eval": "safe"` (the default).
13
+
- The primary risk is **data leakage**, not execution of attacker-controlled code.
14
+
15
+
**Mitigations:**
16
+
1.**Do not interpolate unsanitized user input into JSONPath queries.**
17
+
2. If user-controlled input must be included in a query, ensure the target JSON object contains **only non-confidential data**.
18
+
19
+
As a general rule, treat JSONPath expressions as code and avoid constructing them dynamically from untrusted sources.
20
+
3
21
## Reporting a Vulnerability
4
22
5
23
**Please do not report security vulnerabilities through public GitHub issues.**
6
24
7
-
If you believe you’ve found a security vulnerability, please send it to us by emailing [brettz9@yahoo.com](mailto:brettz9@yahoo.com). Please include the following details with your report:
25
+
If you believe you’ve found a security vulnerability, please send it to us by emailing [iamavinashthakur.at@gmail.com](mailto:iamavinashthakur.at@gmail.com) or [brettz9@yahoo.com](mailto:brettz9@yahoo.com). Please include the following details with your report:
8
26
9
27
1. Description of the location and potential impact of the vulnerability
0 commit comments