Editing 1957: 2018 CVE List

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 21: Line 21:
 
:This is not a security problem, since Wikipedia articles are public. However, since Shannon formulated how the amount of unique or actual information some entity contains is proportional to the number of bits required to encode it, retrieving only a few bits casts a dark perspective upon the significance of the Shannon article's content.
 
:This is not a security problem, since Wikipedia articles are public. However, since Shannon formulated how the amount of unique or actual information some entity contains is proportional to the number of bits required to encode it, retrieving only a few bits casts a dark perspective upon the significance of the Shannon article's content.
 
;At the cafe on Third Street, the Post-it note with the WiFi password is visible from the sidewalk.
 
;At the cafe on Third Street, the Post-it note with the WiFi password is visible from the sidewalk.
:Cafés often offer free access to WiFi as a service to patrons, as a business strategy to encourage said patrons to remain in the building and buy more coffee. Some use a password, so that only patrons can use the WiFi, and may display the password on signage inside. Since anybody could go into the cafe to read the post-it, and then use the network from nearby, the ability to read it from outside is, at most, a trivial problem. For systems that are supposed to be secure, writing passwords in a visible place is a major security flaw. For instance, following the [[wikipedia:2018 Hawaii false missile alert|2018 Hawaii false missile alert]] (see [[Hawaii]]), the agency concerned received criticism for a press photo showing [https://www.businessinsider.com/hawaii-emergency-agency-password-discovered-in-photo-sparks-security-criticism-2018-1?r=US&IR=T a password written on a sticky note] attached to a monitor.
+
:Cafés often offer free access to WiFi as a service to patrons, as a business strategy to encourage said patrons to remain in the building and buy more coffee. Some use a password, so that only patrons can use the WiFi, and may display the password on signage inside. Since anybody could go into the cafe to read the post-it, and then use the network from nearby, the ability to read it from outside is, at most, a trivial problem. For systems that are supposed to be secure, writing passwords in a visible place is a major security flaw. For instance, following the [[wikipedia:2018 Hawaii false missile alert|2018 Hawaii false missile alert]], the agency concerned received criticism for a press photo showing [http://uk.businessinsider.com/hawaii-emergency-agency-password-discovered-in-photo-sparks-security-criticism-2018-1?r=US&IR=T a password written on a sticky note] attached to a monitor.
 
;A remote attacker can inject arbitrary text into public-facing pages via the comments box.
 
;A remote attacker can inject arbitrary text into public-facing pages via the comments box.
 
:Describes a common feature on news sites or social media sites like Facebook. The possibility for users to "inject" text into the page is by design. This is a humorous reference to the relatively common security vulnerability "[[Wikipedia:Cross-site_scripting|persistent cross-site scripting]]", where input provided by a user, such as through a comment section, can result in dangerous content containing arbitrary HTML or JavaScript code being displayed to other users.  
 
:Describes a common feature on news sites or social media sites like Facebook. The possibility for users to "inject" text into the page is by design. This is a humorous reference to the relatively common security vulnerability "[[Wikipedia:Cross-site_scripting|persistent cross-site scripting]]", where input provided by a user, such as through a comment section, can result in dangerous content containing arbitrary HTML or JavaScript code being displayed to other users.  
 
;MySQL server 5.5.45 secretly runs two parallel databases for people who say "S-Q-L" and "sequel."
 
;MySQL server 5.5.45 secretly runs two parallel databases for people who say "S-Q-L" and "sequel."
:Some people pronounce "{{w|SQL}}" like "sequel", after SQL's predecessor "SEQUEL (Structured English Query Language)". The standard for SQL suggests that it should be pronounced as separate letters; however, the author of SQL pronounces it "sequel", so the debate persists (with even <s>more</s> <s>less</s> <s>more</s> <s>less</s> <s>MORE</s> justification than arguments about how to pronounce "GIF"{{citation needed}}). MySQL is an free relational database management system. The latest generally available version (at the time of writing) is MySQL 5.7.
+
:Some people pronounce "{{w|SQL}}" like "sequel", after SQL's predecessor "SEQUEL (Structured English Query Language)". The standard for SQL suggests that it should be pronounced as separate letters; however, the author of SQL pronounces it "sequel", so the debate persists (with even more justification than arguments about how to pronounce "GIF"). MySQL is an open-source relational database management system. The latest generally available version (at the time of writing) is MySQL 5.7.
 
;A flaw in some x86 CPUs could allow a root user to de-escalate to normal account privileges.
 
;A flaw in some x86 CPUs could allow a root user to de-escalate to normal account privileges.
:{{w|Privilege escalation}} refers to any illegitimate means by which a system user gains greater access privileges than they are supposed to have. The most highly-sought privilege is that of the root user, which allows complete access to an entire system&mdash; a ''superuser''. Any flaw that would allow an ordinary user to escalate to superuser status is a critical security threat, as they then have full control of the machine. This is what most crackers seek to achieve when attacking a device.
+
:{{w|Privilege escalation}} refers to any illegitimate means by which a system user gains greater access privileges than they are supposed to have. The most highly-sought privilege is that of the root user, which allows complete access to an entire system&mdash; a ''superuser''. Any flaw that would allow an ordinary user to escalate to superuser status is a critical security threat, as they then have full control of the machine. This is what most hackers seek to achieve when attacking a device.
 
:
 
:
 
:This CVE presents the less-threatening reverse situation: allowing a root user to ''de-escalate'' to normal account privileges. In fact, root users can already do this at any time; superuser privileges allow them to take control of any user account, so they can simply switch to an account which has fewer privileges than the root user.
 
:This CVE presents the less-threatening reverse situation: allowing a root user to ''de-escalate'' to normal account privileges. In fact, root users can already do this at any time; superuser privileges allow them to take control of any user account, so they can simply switch to an account which has fewer privileges than the root user.
 
;Apple products catch fire when displaying emoji with diacritics.
 
;Apple products catch fire when displaying emoji with diacritics.
:This is a reference to a common problem of modern gadgets catching fire (usually related to flaws in lithium-ion batteries), as well as to Apple products crashing when attempting to display certain character sequences. Diacritics are the accents found on letters in some languages, for example the German {{w|Umlaut_(diacritic)|umlaut}} (ü) or the French {{w|cedilla}} (ç). They usually indicate a change to how the letter is pronounced. Diacritics are not normally found on emojis{{citation needed}}, but since emojis are part of the widely-used {{w|Unicode}} standard which also allows for combining diacritics, it is in fact possible to combine the two to create a diacritical emoji. 🔥̃ is such an example.
+
:This is a reference to a common problem of modern gadgets catching fire (usually related to flaws in lithium-ion batteries), as well as to Apple products crashing when attempting to display certain character sequences. Diacritics are the accents found on letters in some languages (eg. č, ģ ķ, ļ, ņ, š, ž). These would not normally be found on emojis{{citation needed}}. 🔥̃ is an example of such an emoji.
 
;An oversight in the rules allows a dog to join a basketball team.
 
;An oversight in the rules allows a dog to join a basketball team.
 
:This probably refers to the movie ''{{w|Air Bud}}'', about a dog playing basketball. This has been a common theme in xkcd comics: see [[115: Meerkat]], [[1439: Rack Unit]], [[1819: Sweet 16]], [[1552: Rulebook]].
 
:This probably refers to the movie ''{{w|Air Bud}}'', about a dog playing basketball. This has been a common theme in xkcd comics: see [[115: Meerkat]], [[1439: Rack Unit]], [[1819: Sweet 16]], [[1552: Rulebook]].
Line 44: Line 44:
 
:The x86 architecture (used in many Intel and AMD processors) is very complicated. Processors typically implement such a complex architecture using programs (microcode) run on a set of hidden, proprietary processors. The details of these hidden machines and errors in the microcode can result in security vulnerabilities, such as Meltdown, where the physical machine does not match the conceptual machine.
 
:The x86 architecture (used in many Intel and AMD processors) is very complicated. Processors typically implement such a complex architecture using programs (microcode) run on a set of hidden, proprietary processors. The details of these hidden machines and errors in the microcode can result in security vulnerabilities, such as Meltdown, where the physical machine does not match the conceptual machine.
 
:
 
:
:A more complicated instruction set is more complex to implement.{{Citation needed}} The x86 architecture is considered "CISC" (a "{{w|Complex instruction set computer}}"), having many instructions originally provided to make programming by a human simpler; other examples include the 68000 series used in the first {{w|Apple Macintosh}}. In the 1980s, this design philosophy was countered by the "RISC" ("{{w|Reduced instruction set computer}}") design movement - based on the observation that computer programs were increasingly generated by compilers (which only used a few instructions) rather than directly by people, and that the chip area dedicated to extra instructions could be better dedicated to, for example, cache. Examples of RISC style designs include {{w|SPARC}}, {{w|MIPS}}, {{w|PowerPC}} (used by Apple in later Macintoshes) and the {{w|ARM architecture|ARM}} chips common in mobile phones. Historically, there was considerable discussion about the merits of each approach. At one time the Mac and Windows PC were on different sides; owners of other competing systems such as the Archimedes and Amiga had similar arguments on usenet in the early 1990s. This "issue" may be posted by someone who still recalls these debates. Technically, the extra instructions do slightly complicate the task of validating correct chip behavior and complicate the tool chains that manage software, which could be seen as a minor security risk. However, the 64-bit architecture introduced by {{w|AMD}}, and since adopted by {{w|Intel}}, does rationalize things somewhat, and all recent x86 chips break down instructions into RISC-like micro-operations, so the complication from a hardware perspective is localized. Recent security issues, such as the speculative cache load issue in Meltdown and Spectre, depend more on details of implementation, rather than instruction set, and have been exhibited both by x86 (CISC) and ARM (RISC) processors.
+
:A more complicated instruction set is more complex to implement.{{Citation needed}} The x86 architecture is considered "CISC" (a "{{w|Complex instruction set computer}}"), having many instructions originally provided to make programming by a human simpler; other examples include the 68000 series used in the first {{w|Apple Macintosh}}. In the 1980s, this design philosophy was countered by the "RISC" ("{{w|Reduced instruction set computer}}") design movement - based on the observation that computer programs were increasingly generated by compilers (which only used a few instructions) rather than directly by people, and that the chip area dedicated to extra instructions could be better dedicated to, for example, cache. Examples of RISC style designs include {{w|SPARC}}, {{w|MIPS}}, {{w|PowerPC}} (used by Apple in later Macintoshes) and the {{w|ARM architecture|ARM}} chips common in mobile phones. Historically, there was considerable discussion about the merits of each approach. At one time the Mac and Windows PC were on different sides; owners of other competing systems such as the Archimedes and Amiga had similar arguments on usenet in the early 1990s. This "issue" may be posted by someone who still recalls these debates. Technically, the extra instructions do slightly complicate the task of validating correct chip behaviour and complicate the tool chains that manage software, which could be seen as a minor security risk. However, the 64-bit architecture introduced by {{w|AMD}}, and since adopted by {{w|Intel}}, does rationalize things somewhat, and all recent x86 chips break down instructions into RISC-like micro-operations, so the complication from a hardware perspective is localized. Recent security issues, such as the speculative cache load issue in Meltdown and Spectre, depend more on details of implementation, rather than instruction set, and have been exhibited both by x86 (CISC) and ARM (RISC) processors.
 
;NumPy 1.8.0 can factor primes in ''O''(log ''n'') time and must be quietly deprecated before anyone notices.
 
;NumPy 1.8.0 can factor primes in ''O''(log ''n'') time and must be quietly deprecated before anyone notices.
 
:Fantastically, this would be an unimaginable software threat, not to be confused with the even speedier, but future-bound, threat in hardware via {{w|Quantum computing}}.  
 
:Fantastically, this would be an unimaginable software threat, not to be confused with the even speedier, but future-bound, threat in hardware via {{w|Quantum computing}}.  
Line 63: Line 63:
 
:In late 2020, Microsoft [https://support.microsoft.com/en-us/help/4577586/update-for-removal-of-adobe-flash-player released an optional Windows update] that removes Flash and prevents users from installing it again.
 
:In late 2020, Microsoft [https://support.microsoft.com/en-us/help/4577586/update-for-removal-of-adobe-flash-player released an optional Windows update] that removes Flash and prevents users from installing it again.
 
;Turns out the cloud is just other people's computers.
 
;Turns out the cloud is just other people's computers.
:Cloud computing is a system of networked computers wherein the client user's computer can offload some of its work load and storage to the other computers &mdash; known as "the cloud." Many businesses offer their networks for consumer use, and can be marketed as "{{w|Platform as a Service}}" ("PaaS") or simply "cloud service." As with any product companies are always tempted to overhype what they offer, promising cloud computing to be more powerful and wondrous than it actually is. Thus, protestors try to remind people what cloud services really are by referring to "the cloud" as "other people's computers." This is, at its core, entirely accurate, taking away the business jargon and simplifying the situation in such a way that it might cast doubt on the security, reliability, and general effectiveness of using "cloud" solutions.  In [[908: The Cloud]], it turns out that [[Black Hat]] is the "other people" whose computer ''is'' the Cloud.
+
:This refers to a meme that demands that "cloud" be replaced with "other people's computers" in all marketing presentation to CEOs and non-computer literate persons evaluating the security impact of using cloud services. Part of the humor here is that "the cloud" is, in actuality, simply a term for hosted services, or in other words computers being run by other people (typically businesses that specialize in this type of "{{w|Platform as a Service}}" or "PaaS" service model). Referring to "the cloud" as "other people's computers" is, at its core, entirely accurate, though it takes away the business jargon and simplifies the situation in such a way that it might cast doubt on the security, reliability, and general effectiveness of using "cloud" solutions.  In [[908: The Cloud]], it turns out that [[Black Hat]] is the "other people" whose computer ''is'' the Cloud.
 
;A flaw in Mitre's CVE database allows arbitrary code insertion.[[779|[~~CLICK HERE FOR CHEAP VIAGRA~~]]]
 
;A flaw in Mitre's CVE database allows arbitrary code insertion.[[779|[~~CLICK HERE FOR CHEAP VIAGRA~~]]]
:Mitre's CVE database is where all {{w|Common Vulnerabilities and Exposures|CVEs}} are stored. This log message forms the punchline of the comic, as it implies that all of the exaggerated error messages above might have been inserted by crackers exploiting the vulnerability. To pour salt in the wound, they then included in a typical spam link purporting to offer inexpensive {{w|Viagra|brand-name Sildenafil}}.
+
:Mitre's CVE database is where all {{w|Common Vulnerabilities and Exposures|CVEs}} are stored. This log message forms the punchline of the comic, as it implies that all of the exaggerated error messages above might have been inserted by hackers exploiting the vulnerability. To pour salt in the wound, they then included in a typical spam link purporting to offer inexpensive {{w|Viagra|brand-name Sildenafil}}.
 
;It turns out Bruce Schneier is just two mischevious kids in a trenchcoat.
 
;It turns out Bruce Schneier is just two mischevious kids in a trenchcoat.
 
:Appears in the title text. {{w|Bruce Schneier}} is security researcher and blogger. The "two kids in a trenchcoat" is a reference to the {{tvtropes|TotemPoleTrench|Totem Pole Trench}} trope. Shortly before this comic was posted, a [https://rare.us/rare-humor/two-kids-dressed-as-a-tall-man-to-get-into-black-panther-is-caught-on-video story went viral] in which two kids were photographed attempting this for real to get into a screening of ''Black Panther''.
 
:Appears in the title text. {{w|Bruce Schneier}} is security researcher and blogger. The "two kids in a trenchcoat" is a reference to the {{tvtropes|TotemPoleTrench|Totem Pole Trench}} trope. Shortly before this comic was posted, a [https://rare.us/rare-humor/two-kids-dressed-as-a-tall-man-to-get-into-black-panther-is-caught-on-video story went viral] in which two kids were photographed attempting this for real to get into a screening of ''Black Panther''.
Line 97: Line 97:
 
==Trivia==
 
==Trivia==
  
*The word "exploit" in the second line is apparently misspelled.
+
Randall has previously referenced diacritics in [[1647: Diacritics]].
* Randall has previously referenced diacritics in [[1647: Diacritics]].
 
  
* Bruce Schneier was previously mentioned in the title texts of [[748: Worst-Case Scenario]] and [[1039: RuBisCO]].
+
Bruce Schneier was previously mentioned in the title texts of [[748: Worst-Case Scenario]] and [[1039: RuBisCO]].
  
 
{{comic discussion}}
 
{{comic discussion}}
  
 
[[Category:Comics with color]]
 
[[Category:Comics with color]]
[[Category:Comics with lowercase text]]
 
 
[[Category:Charts]]
 
[[Category:Charts]]
 
[[Category:Programming]]
 
[[Category:Programming]]
 
[[Category:Computers]]
 
[[Category:Computers]]
 
[[Category:iOS]]
 
[[Category:iOS]]

Please note that all contributions to explain xkcd may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see explain xkcd:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel | Editing help (opens in new window)