github-actions[bot] commented on issue #14627: URL: https://github.com/apache/cloudstack/issues/14627#issuecomment-6769041720
> [!WARNING] > threat detection engine error > The threat detection engine encountered an error and could not complete analysis. This is a tooling failure, not a security finding. > > <!-- gh-aw-threat-engine-error --> > > <details> > <summary>What happened</summary> > > The threat detection engine failed to produce results. > > Review the [workflow run logs](https://github.com/apache/cloudstack/actions/runs/42824790094) for details. > > </details> ## 🎯 Triage report On a dual-stack VPC tier that uses the built-in `default_allow` ACL list, IPv6 traffic is blocked in both directions. The list's rules carry only `0.0.0.0/0`, so the router skips them for IPv6 and the tier's IPv6 chains keep only the final drop. The reporter is unsure whether IPv6 should be open on this list. Opening it would expose every VM on existing `default_allow` tiers over IPv6. ### 📊 Assessment | Dimension | Value | Reasoning | | --- | --- | --- | | **Type** | type:bug | IPv6 behaviour differs from `createNetworkACL` and `SetNetworkACLCommand`; intent is unconfirmed | | **Component** | component:vpc | VPC ACL lists and the VR ACL code | | **Severity** | n/a | Depends on the intended behaviour | | **Labels** | type:bug, component:vpc | | | **Coding agent** | Not suitable | Needs a decision on the meaning of "Allow All" for IPv6, and an upgrade change | ### 🔗 Similar issues - #14356 (related) — VPC ACL rules given as protocol number or upper-case ICMP lose their ports on the VR - #13266 (related) — v4.22.0 vRouter ACLs are not RFC compliant on the internal interface <details> <summary>💡 Notes and suggestions</summary> - Reproduction: create a dual-stack VPC offering and tier with `aclid=default_allow`, then run `nft list table ip6 ip6_acl` on the VR. - The default list is seeded in `schema-410to420.sql`. Maintainers should confirm the intended IPv6 semantics before changing it. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/42824790094) · copilot · haiku55 · \~5 AIC · ⊞ 3.8K · [◷](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) <details> <summary><sub>Add this agentic workflow to your repo</sub></summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@139fa09ef17cde4135e696ff8e7af09bc5ddfa6e ``` </details> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, model: claude-haiku-5.5, id: 42824790094, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/42824790094 --> <!-- gh-aw-execution: {"version":1,"repo_id":"9759448","repository":"apache/cloudstack","aw_workflow_id":"daily-issue-triage","run_id":"42824790094","run_attempt":"1","run_url":"https://github.com/apache/cloudstack/actions/runs/42824790094","publishing_job":{"key":"safe_outputs","check_run_id":"129867538613"}} --> -- 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]
