updateNetworkACLItem with partialupgrade=false leaves a rule broken when cidrlist or traffictype is left out, and drops an ICMP type given with tcp
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 42/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- java
- Ambito
- backend-api-design, cloud
Direzione di ricerca
Start by reading updateNetworkACLItem, transferDataToNetworkAclRulePojo(), NetworkACLItemDaoImpl.update() and NetworkACLItemCidrsDaoImpl.updateCidrs(); trace validation alongside createNetworkACL and the default partial upgrade path. Check the existing tests for network ACL rule updates and add coverage for missing required fields, invalid traffic type, ICMP parameters with another protocol, and rollback when CIDR updates fail. Done means invalid calls fail before leaving a partial update and valid calls preserve the documented behavior.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
problem
updateNetworkACLItem with partialupgrade=false replaces every field of the rule with what the call passes. Two cases go wrong.
1. A field left out is written as null, and the rule is left broken.
When cidrlist or traffictype is left out, transferDataToNetworkAclRulePojo() sets them to null. NetworkACLItemDaoImpl.update() then writes the rule row and only afterwards updates the CIDRs, outside a transaction:
- with
cidrlistleft out,NetworkACLItemCidrsDaoImpl.updateCidrs()fails withCannot invoke "java.util.List.size()" because "cidrs" is null. The call fails, but the row has already been committed with the null traffic type. - from then on
listNetworkACLsfor that list fails withCannot invoke "...TrafficType.toString()" because ... getTrafficType() is null, and applying the list fails the same way inSetNetworkACLCommand, until the rule is updated again with every field.
When protocol is left out, the call fails earlier with a NullPointerException in updateIcmpCodeAndTypeFullUpgrade(). Nothing is written in that case, but the error is an NPE rather than a message. (#14046 removes that NPE; the rule would then be saved without a protocol, which createNetworkACL never allows.)
action left out is already handled: it becomes Allow, as on create.
2. An ICMP type or code given with another protocol is silently dropped.
partialupgrade=false protocol=tcp icmptype=8 is accepted, and the rule is saved as tcp without the ICMP type. createNetworkACL with the same parameters, and the same update with the default partialupgrade=true, both refuse it with "Can specify icmpCode and icmpType for ICMP protocol only".
versions
4.20 and later for the dropped ICMP type; the null fields since partialupgrade was added in 4.12. Seen on 4.22 and main.
The steps to reproduce the bug
- In a VPC, create an ACL list and a rule on it:
createNetworkACL aclid=<list> protocol=tcp startport=80 endport=80 cidrlist=10.1.2.0/24 action=allow traffictype=ingress. updateNetworkACLItem id=<rule> partialupgrade=false protocol=udp startport=53 endport=53. It fails with thecidrs is nullNPE.listNetworkACLs aclid=<list>now fails with thegetTrafficType() is nullNPE.updateNetworkACLItem id=<rule> partialupgrade=false protocol=tcp cidrlist=10.1.2.0/24 action=allow traffictype=ingressrepairs it.- On an ICMP rule,
updateNetworkACLItem id=<rule> partialupgrade=false protocol=tcp icmptype=8 cidrlist=10.1.2.0/24 action=allow traffictype=ingressis accepted, and the rule is tcp with no ICMP type.
What to do about it?
- With
partialupgrade=false, refuse the call whenprotocol,cidrlistortraffictypeis missing, before anything is written. Defaulting them as create does would silently widen a rule to every address, or turn an egress rule into an ingress rule. - Refuse an invalid
traffictypeon update, as create does, instead of ignoring it. - Keep an ICMP type or code given with another protocol, so that the existing validation refuses it.
- Write the rule row and its CIDRs in one transaction, so that a failure on the CIDRs can't leave the rule half updated.
- Lingua principale
- Java
- Stelle
- 3.1k
- Fork
- 1.4k
- Merge medio
- 7g 16h
- PR unite (30g)
- 15
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di apache/cloudstack
-
resizeVolume of a running system VM's volume is accepted but the VM never sees the new sizeForse già presa @bhouse-nexthop l’ha presa 3 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
apache/cloudstack#14645 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
VR reports a load balancer change as applied when haproxy.cfg cannot be replacedForse già presa @bhouse-nexthop l’ha presa 4 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
apache/cloudstack#14633 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
restartNetwork reports a ResourceUnavailableException as an unexpected error (530), unlike restartVPC (534)Forse già presa @bhouse-nexthop l’ha presa 4 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
apache/cloudstack#14631 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
apache/cloudstack#14625 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Remote access VPN users are disconnected on every LB, ACL, port forward or firewall change (xl2tpd restarted on every iptables pass)Forse già presa @willbennett-devops l’ha presa 12 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
apache/cloudstack#14545 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di apache/cloudstack
Issue simili
-
[FEATURE] Expose external refresh, node-level translog and warmer statsForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertauntriaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
opensearch-project/opensearch-prometheus-exporter#680 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 2 giorni
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100
-
Good First Issue
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
hiero-ledger/hiero-sdk-java#3059 ·
I maintainer di solito rispondono entro 1 giorno