Skip to content
Hallway
0:00 / 0:00

#urlparsing#uxss#cve-2018-6128

HOW FRCKN' HARD IS IT TO UNDERSTAND A URL?! - uXSS CVE-2018-6128

LiveOverflow

949K subscribers • 15 videos on Hallway

YouTube
  • Recommended by 2 people: 1 on Lobsters and 1 in engineering communities.
  • May be out of date. Uploaded 8 years ago, in an area where tools change fast.

Intermediate. Assumes working knowledge.

350K views8 years ago2 recommendations

SecurityWeb developmentExploits and vulnerabilitiesHTTP, REST and GraphQLHow browsers work

LiveOverflow explains how different WebKit components parsing the same URL differently led to a universal XSS vulnerability in Chrome for iOS.

URLs are surprisingly hard to read. A Chrome on iOS universal XSS shows what can happen when WebKit components parse the same URL differently, and why URL parser mismatches also matter for SSRF. LEARN ON HEXTREE (ad) Learn hacking on Hextree: hextree.io/ Watch this video and more on Hextree: app.hextree.io/courses/yt-xss/related-client-side-hacks Join the Hextree Discord: discord.gg/xgQpCQCpvy Chrome Bug: bugs.chromium.org/p/chromium/issues/detail?id=841105 Orange Tsai: twitter.com/orange_8361 A New Era of SSRF - Exploiting URL Parser in Trending Programming Languages! - CODE BLUE: youtube.com/watch?v=2MslLrPinm0 Slides: blackhat.com/docs/us-17/thursday/us-17-Tsai-A-New-Era-Of-SSR… CHAPTERS - URLs and Their RFC Grammar - Why URLs Are Harder Than They Look - What Universal XSS Means - Exploiting history.replaceState on Chrome for iOS - Finding the WebKit Root Cause - Chrome's Browser-Crash Workaround - Two WebKit Components Parse the URL Differently - URL Parser Mismatches and SSRF - Python Libraries Disagree About the Same URL SUPPORT Per video: patreon.com/join/liveoverflow Per month: youtube.com/channel/UClcE-kVhqyiHCcjYwcpfj9w/join Buy my handwriting font (ad): shop.liveoverflow.com/ WATCH, FOLLOW & READ Second channel: youtube.com/LiveUnderflow Twitch: twitch.tv/LiveOverflow/ Twitter: twitter.com/LiveOverflow/ Instagram: instagram.com/LiveOverflow/ TikTok: tiktok.com/@liveoverflow_ LiveOverflow blog: liveoverflow.com/ Hextree blog (ad): hextree.io/blog #CVE #SecurityResearch (ad) LiveOverflow YouTube channel is supported by advertisement and product placement.

Why it's here

2 people recommend this

What people say. Linked to illustrate how URL parser mismatches can lead to security vulnerabilities and compatibility issues.

AugustGarciaon Lobsters • Recommends

How hard is it to understand a URL? - uXSS CVE-2018-6128
1View on Lobsters

u/kawagin r/swift • Recommends

On “WebURL 0.2.0 released! A new URL type for Swift”

Standards compliance _is_ the killer feature. This section of the guide explains it in detail: A Closer Look At: Parsing and Web Compatibility. There are some URLs which Foundation's URL(Components) just won't work with, but which browsers and other libraries handle just fine. In some cases, this means your App just won't work with URLs that work fine with, say, Android or JavaScript. In the worst case, it can lead to exploitable vulnerabilities; for example, if WebKit and Foundation interpret the same URL as pointing to 2 different hosts. LiveOverflow made a video about one reported vulnerability. WebURL parses URLs in exactly the same way as a browser (currently, only Safari 15 is full…
0View on Reddit