keepalived run without authentication
Bug #1551314 reported by
Jeffrey Zhang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Fix Released
|
Medium
|
Jeffrey Zhang |
Bug Description
The keepalived conf file is like below. No authentication. The potential issue is that anyone can easily create a same keepalived service and take over the VIP. then all the OpenStack will request to the imitative server.
vrrp_script check_alive {
script "/check_alive.sh"
interval 2
fall 2
rise 10
}
vrrp_instance kolla_internal_vip {
state MASTER
interface eth0
virtual_
priority 1
advert_int 1
virtual_
10.2.0.254
}
track_script {
check_alive
}
}
information type: | Private → Public |
Changed in kolla: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Jeffrey Zhang (jeffrey4l) |
milestone: | none → mitaka-3 |
Changed in kolla: | |
status: | Triaged → In Progress |
To post a comment you must log in.
Jeffrey,
Just to be clear, you would have to run a second copy of keepalived to create another VIP. So the authentication just prevents multiple keepaliveds from trouncing each other on a network? If that is the case, this is no a security problem as there is no attack vector that doesn't already involve root on one of the deployed targets or in the secured private management network.