Cache poisoning

This is an old revision of this page, as edited by Pokechu22 (talk | contribs) at 23:27, 22 January 2021 (Convert to stub). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Cache poisoning refers to a vulnerability where invalid entries can be placed into a cache, which are then assumed to be valid when later used.[1] Two common varieties are DNS cache poisoning and ARP cache poisoning. Web caches can also be poisoned,[2] along with other more specific caches.[3][4][5]

References

  1. ^ "CAPEC-141: Cache Poisoning". CAPEC.
  2. ^ Nguyen, Hoai Viet; Iacono, Luigi Lo; Federrath, Hannes (6 November 2019). "Your Cache Has Fallen: Cache-Poisoned Denial-of-Service Attack". Proceedings of the 2019 ACM SIGSAC Conference on Computer and Communications Security: 1915–1936. doi:10.1145/3319535.3354215.
  3. ^ Hensler, Christopher; Tague, Patrick (15 May 2019). "Using bluetooth low energy spoofing to dispute device details: demo". Proceedings of the 12th Conference on Security and Privacy in Wireless and Mobile Networks: 340–342. doi:10.1145/3317549.3326321.
  4. ^ Daswani, Neil; Garcia-Molina, Hector (2004). "Pong-cache poisoning in GUESS". Proceedings of the 11th ACM conference on Computer and communications security - CCS '04: 98. doi:10.1145/1030083.1030099.
  5. ^ Wang, Dong; Dong, Wei Yu (April 2019). "Attacking Intel UEFI by Using Cache Poisoning". Journal of Physics: Conference Series. 1187 (4): 042072. doi:10.1088/1742-6596/1187/4/042072.