Repository navigation
Conversation
| _logger = logging.getLogger(__name__) | ||
|
|
||
| if settings.ALLOW_INSECURE_HEADER_CONTENT_GUARD_JQ_PROCESSING_AND_FORFEIT_ALL_COMMUNITY_SUPPORT: # noqa | ||
| import jq |
There was a problem hiding this comment.
Can we keep the import as it was before? What is the benefit of this change?
There was a problem hiding this comment.
Being sure that we really don't use it.
|
|
||
| # JQ is a query language after all. And it shoudl be considered on the same level as SQL. | ||
| # Do not allow users to write arbitrary programmes to run on the content app. | ||
| ALLOW_INSECURE_HEADER_CONTENT_GUARD_JQ_PROCESSING_AND_FORFEIT_ALL_COMMUNITY_SUPPORT = False |
There was a problem hiding this comment.
This should be documented in docs/admin/reference/settings.md. And maybe also in docs/user/guides/protect-content.md?
Also, would not be ALLOW_INSECURE_HEADER_CONTENT_GUARD_JQ enough? :)
There was a problem hiding this comment.
I disagree, as any of that would encourage using it.
There was a problem hiding this comment.
Let me say it like this: The name is purposefully making it really icky to use.
14122b5 to
524cde9
Compare
9c99079 to
29f3242
Compare
29f3242 to
16025b6
Compare
There was a problem hiding this comment.
Maybe I overlooked it, but do these tests contain a regression test?
There was a problem hiding this comment.
There is a test to make sure the feature flag is honored. And now a set of tests that the patched up jq path is not exposing the env as before.
6234f06 to
bd1ec61
Compare
| else: | ||
| # Match a dotted identifier path. | ||
| # e.g.: "tenant.auth.token" | ||
| json_path_re = re.compile(r"(?:\.\w+)+", flags=re.ASCII) |
There was a problem hiding this comment.
If we define the regex outside if/else, we would not need to duplicate it again in the serializer...
853246d to
37212c0
Compare
37212c0 to
34c7ea5
Compare
CVE-2026-123084
📜 Checklist
See: Pull Request Walkthrough