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
## What changed
- pin AWS integration credentials to the exact API Gateway ID and Region
returned for the ephemeral CloudFormation stack
- remove response bodies, API key identifiers, and arbitrary error
messages from cleanup logs
- read bounded template files through one `O_NOFOLLOW` file descriptor
for both metadata checks and content reads
- add endpoint-confusion regression tests and release notes
## Why
CodeQL's first scan of the complete v0.1.0 pull request identified three
new flows: a dynamic integration-test destination, clear-text cleanup
logging, and a `stat(path)` / `readFile(path)` race. Even though the
integration destination originates from a dedicated test stack, it
carries a bootstrap credential and should fail closed if the URL differs
from that exact stack. The logging and file race findings are actionable
directly.
## Impact
The AWS integration workflow now independently reads the `HttpApi`
physical ID and the script accepts only its exact commercial API Gateway
HTTPS hostname. Cleanup diagnostics remain useful without retaining
response bodies or key identifiers. Template manifest behavior is
unchanged, but the size/type check and read now operate on the same
opened file.
## Validation
- `npm run check`
- `npm test` — 22 files, 146 tests
- `npm run build`
- endpoint-confusion and bootstrap-key output probes
- `npm audit --omit=dev --audit-level=high` — 0 vulnerabilities
- `cfn-lint==1.53.2 template.yaml`
- Redocly 2.12.5 OpenAPI lint
- `actionlint`
- `gitleaks git --staged`
- signed commit with DCO sign-off
Closes CodeQL findings #3, #4, and #5 on release PR #30.
Signed-off-by: Yusuke Hayashi <yusuke8h@gmail.com>
0 commit comments