diff options
author | Johannes Berg <johannes.berg@intel.com> | 2011-07-07 18:24:54 +0200 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2011-07-07 13:06:09 -0400 |
commit | 34459512ffa7236c849466e3bd604801389734e1 (patch) | |
tree | f363cdbf9618fe2bd424c9288cbee89abdc15584 /net/wireless/core.h | |
parent | 1186980dafcd14d0e257a4dd6990cefdc6f3e362 (diff) | |
download | op-kernel-dev-34459512ffa7236c849466e3bd604801389734e1.zip op-kernel-dev-34459512ffa7236c849466e3bd604801389734e1.tar.gz |
mac80211: fix TKIP replay vulnerability
Unlike CCMP, the presence or absence of the QoS
field doesn't change the encryption, only the
TID is used. When no QoS field is present, zero
is used as the TID value. This means that it is
possible for an attacker to take a QoS packet
with TID 0 and replay it as a non-QoS packet.
Unfortunately, mac80211 uses different IVs for
checking the validity of the packet's TKIP IV
when it checks TID 0 and when it checks non-QoS
packets. This means it is vulnerable to this
replay attack.
To fix this, use the same replay counter for
TID 0 and non-QoS packets by overriding the
rx->queue value to 0 if it is 16 (non-QoS).
This is a minimal fix for now. I caused this
issue in
commit 1411f9b531f0a910cd1c85a337737c1e6ffbae6a
Author: Johannes Berg <johannes@sipsolutions.net>
Date: Thu Jul 10 10:11:02 2008 +0200
mac80211: fix RX sequence number check
while fixing a sequence number issue (there,
a separate counter needs to be used).
Cc: stable@kernel.org
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/wireless/core.h')
0 files changed, 0 insertions, 0 deletions