RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 599475 - Potential security problem over migration port
Summary: Potential security problem over migration port
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-03 10:19 UTC by Keqin Hong
Modified: 2013-01-09 22:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-08 12:46:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Keqin Hong 2010-06-03 10:19:58 UTC 
Description of problem:
Migration through tcp connection requires an incoming tcp port for the dest host. If a malicious connection (e.g. a telnet probe) just happens before the migration instruction being entered. Migration will fail/hang.

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.69.el6

How reproducible:
100%

CLI on dest:
/usr/libexec/qemu-kvm -m 2G -smp 2 -drive file=win2008r2-64.qcow2,if=none,id=drive-virtio0,boot=on -device ide-drive,drive=drive-virtio0 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,mac=76:00:40:3F:20:20,bus=pci.0,addr=0x4 -boot order=dc,menu=on -uuid 17644ecc-d3a1-4d3c-a386-12daf50015f2 -rtc base=utc -no-hpet -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -cpu qemu64,+sse2 -balloon none -vnc :1 -incoming tcp:0:5800


Steps to Reproduce:
1. Start VM on host machine (either with vnc or spice)
2. Start VM on dest machine with "-incoming tcp:0:5800"
3. telnet $dest 5800
4. from host machine, start migration 
# migrate -d tcp:$dest:5800
# info migrate

Actual results:
Migration will never succeed.
Even if you stop the telnet process, and start VM listening on dest machine again, migration can no longer proceed unless migrate_cancel being instructed first.
 
Expected results:
Illegal port probe over migration port should be prohibited.

Additional info:
Comment 2 RHEL Program Management 2010-06-07 16:18:25 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 Dor Laor 2010-06-08 12:46:55 UTC 
Why is that a bug? Mgmt will re-issue the migration.
Anyway it seems like low priority. The host environment is presumed safe.
Note You need to log in before you can comment on or make changes to this bug.