github-actions[bot] opened a new pull request, #72829:
URL: https://github.com/apache/airflow/pull/72829
* Document scope boundaries the security model leaves implicit
The 'What is NOT considered a security vulnerability' section states it is
written for security researchers and AI agents to read before reporting. In
practice several recurring report shapes are not covered by it, and each one
costs a triage cycle to re-derive from first principles.
Add five entries for boundaries the project already applies but has not
written down:
- Client libraries act on values their calling application supplies; the
trust
decision about those values belongs to that application, as it does for Dag
authors passing unsanitized input to operators.
- Features documented as experimental or alpha do not yet carry security
guarantees. Defects in them are worth fixing but are not handled through
the
security process, and should be reassessed when the feature graduates.
- Bounding request size is the terminating proxy's responsibility. This is
distinct from the authenticated-DoS entry and applies to unauthenticated
requests too, including endpoints that must be reachable without
credentials.
- A defect reachable only on an end-of-life release line has no release in
which to ship a fix, including where a provider still installs on that
line.
- Params schema validation is a correctness feature, not a security control.
Declaring no params opts out of validation rather than asserting emptiness.
Sharpen the connection-configuration entry, which currently reads as 'this
role is privileged, so nothing counts'. The grant covers worker-context
execution and the values the role may write; it does not cover recovering
credential material the role cannot read, nor reaching a component it has no
execution rights over.
Clarify the Execution API token entry. It currently states a short nominal
lifetime and non-revocability as separate facts, which reads as though the
ten-minute figure bounds exposure. Read together they do not: refresh
re-issues
from the token's own claims, so the lifetime bounds only a holder who stops
using the token, and a leaked token remains usable indefinitely and cannot be
withdrawn. Also record that reissue does not consult the database, so a token
naming a finished or archived task instance still refreshes.
Record one limitation the model asserts but the code cannot satisfy: the
edge3
worker signs its own requests, so remote edge-worker hosts must hold the JWT
signing key. That contradicts the guidance that workers never hold it, and
voids the assurance that the secret is confined to the API server and
scheduler.
* Match the impersonation heading underline to its title
The underline was one character short of the title, which Sphinx reports as
a warning and the docs build promotes to an error, failing both the docs and
spellcheck jobs.
(cherry picked from commit 7e6eeb0383c709c7982627744d9ee0a80283b600)
Co-authored-by: Jarek Potiuk <[email protected]>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
