Core Rule Set: ls -la passes in q on a gitea user's or organisation's page (closes #349)
check / check (push) Waiting to run
check / check (push) Waiting to run
On a path of one segment, q now skips 932250 too, unless the path ends in .php, as /index.php does. The Forgejo recording gains the two searches for ls -la, made from the recorded searches for python3. Model: opus-5-5
This commit is contained in:
1 parent
b6aa2cbc4b
commit
2e2ed08d85
4 files changed
+52
-6
No files matched your search
@@ -829,9 +829,9 @@ The changes hold in front of every app, and no setting undoes them:
|
||||
- packages, on its pages and in its API.
|
||||
|
||||
A user's or an organisation's page is any path of one segment, so on
|
||||
every such path, on any app, `q` skips 930120, 932120 and 932260, for
|
||||
example on `/search`. It keeps 932250 there, so `ls -la` is refused on
|
||||
those pages.
|
||||
every such path, on any app, `q` skips these rules, for example on
|
||||
`/search`. A path that ends in `.php`, such as `/index.php`, keeps
|
||||
932250, so `ls -la` is refused there.
|
||||
|
||||
Some of these searches also skip the rule for Java class names (944130),
|
||||
which refused `org.apache.commons.logging`.
|
||||
|
||||
Reference in new issue
Block a user