Security group allows public access despite restricting to specific subnet

Bug #1026350 reported by Ashu Sharma
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

When I open a port in a security group and only specify that it stays open to only its' project vlan, once applied, that port is opened to the public.

I see this happen on these two versions of nova:
nova version: 2011.3-dev (2011.3-workspace:tarmac-20110617180219-fd1htxqerc14otr3)
nova version: 2011.3 (2011.3-nova-milestone-tarball:tarmac-20110922115702-k9nkvxqzhj130av2)

Please advise.

Revision history for this message
Thierry Carrez (ttx) wrote :

Could you paste the commands you used, to exactly reproduce the issue ?

Changed in nova:
status: New → Incomplete
Revision history for this message
Ashu Sharma (as282d) wrote :

Here is an example. My project vlan is 10.4.57.0/24

|=> euca-authorize -P tcp -s 10.4.57.0/24 -p 22 myservers

|=> euca-describe-groups-2.7
GROUP ashusb ashusb-vpn Group for vpn
PERMISSION ashusb ashusb-vpn ALLOWS udp 1194 1194 FROM CIDR 0.0.0.0/0
PERMISSION ashusb ashusb-vpn ALLOWS icmp -1 -1 FROM CIDR 0.0.0.0/0
GROUP ashusb default default
GROUP ashusb myservers test
PERMISSION ashusb myservers ALLOWS tcp 80 80 FROM CIDR 0.0.0.0/0
PERMISSION ashusb myservers ALLOWS tcp 8080 8080 FROM CIDR 0.0.0.0/0
PERMISSION ashusb myservers ALLOWS tcp 22 22 FROM CIDR 10.4.57.0/24

|=> euca-run-instances ami-000000bd -k as282d -g myservers

|=> euca-allocate-address-2.7
ADDRESS 12.208.178.202

|=> euca-associate-address-2.7 12.208.178.202 -i i-00004f4f
ADDRESS 12.208.178.202 i-00004f4f

After I associate a public IP, then I am able to ssh thru the public IP from a public terminal, even though the security group only specifies IPs in the project VLAN. If I were to specify a different project vlan, say 10.4.45.0/24, then port 22 is blocked as expected from public internet.

Thierry Carrez (ttx)
Changed in nova:
status: Incomplete → New
Revision history for this message
Vish Ishaya (vishvananda) wrote :

I'm curious if there is a messed up setting on the network host. It appears that incoming traffic looks like it is coming from the network host instead of the public address. Is it possible that you have masquerading turned on in the network host?

Changed in nova:
status: New → Incomplete
Revision history for this message
Vish Ishaya (vishvananda) wrote :

also can you verify if you are running with more than one nova-network and if nova-network is running on the same host as nova-compute or a different host.

Revision history for this message
Thierry Carrez (ttx) wrote :

We cannot solve the issue you reported without more information. Could you please provide the requested information ?

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

This bug lacks the necessary information to effectively reproduce and fix it, therefore it has been closed. Feel free to reopen the bug by providing the requested information and set the bug status back to ''New''.

Changed in nova:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.