HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sola-st
wasm-binary-security
WebAssembly2020–2020
sola-st / wasm-binary-security

wasm-binary-security

Discover this repository through its Hacker News conversations.

3Distinct people
3Mentions
0Explicit recommenders
79GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2020-08-20 04:48:15 UTC to 2020-08-20 17:11:36 UTC.

012020-08-20 04:00:00 UTC to 2020-08-20 05:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 20, 04:002020-08-20 05:00:00 UTC to 2020-08-20 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-20 06:00:00 UTC to 2020-08-20 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-20 07:00:00 UTC to 2020-08-20 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-20 08:00:00 UTC to 2020-08-20 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-20 09:00:00 UTC to 2020-08-20 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-20 10:00:00 UTC to 2020-08-20 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 20, 10:002020-08-20 11:00:00 UTC to 2020-08-20 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-08-20 12:00:00 UTC to 2020-08-20 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-20 13:00:00 UTC to 2020-08-20 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-20 14:00:00 UTC to 2020-08-20 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-20 15:00:00 UTC to 2020-08-20 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-20 16:00:00 UTC to 2020-08-20 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-20 17:00:00 UTC to 2020-08-20 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 20, 17:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 20, 04:002020-08-20 04:00:00 UTC2020-08-20 05:00:00 UTC101
Aug 20, 05:002020-08-20 05:00:00 UTC2020-08-20 06:00:00 UTC000
Aug 20, 06:002020-08-20 06:00:00 UTC2020-08-20 07:00:00 UTC000
Aug 20, 07:002020-08-20 07:00:00 UTC2020-08-20 08:00:00 UTC000
Aug 20, 08:002020-08-20 08:00:00 UTC2020-08-20 09:00:00 UTC000
Aug 20, 09:002020-08-20 09:00:00 UTC2020-08-20 10:00:00 UTC000
Aug 20, 10:002020-08-20 10:00:00 UTC2020-08-20 11:00:00 UTC000
Aug 20, 11:002020-08-20 11:00:00 UTC2020-08-20 12:00:00 UTC101
Aug 20, 12:002020-08-20 12:00:00 UTC2020-08-20 13:00:00 UTC000
Aug 20, 13:002020-08-20 13:00:00 UTC2020-08-20 14:00:00 UTC000
Aug 20, 14:002020-08-20 14:00:00 UTC2020-08-20 15:00:00 UTC000
Aug 20, 15:002020-08-20 15:00:00 UTC2020-08-20 16:00:00 UTC000
Aug 20, 16:002020-08-20 16:00:00 UTC2020-08-20 17:00:00 UTC000
Aug 20, 17:002020-08-20 17:00:00 UTC2020-08-20 18:00:00 UTC101

What Hacker News says

3 sources
> This doesn't really seem to offer anything useful, or even contain new information. You are right in that we do not try to attack a concrete host implementation or aim to break out of the sandbox. I disagree, however, that security inside a WebAssembly binary is irrelevant. If an attacker can arbitrarily read/write in linear memory, it depends on the imported host functions what can be done. The larger WebAssembly applications are (and we believe they will become larger in the future, and incorporate DOM functions, as in our PoC application), the higher the risk that host APIs can be abused. This is troubling especially where there is no sandbox (on some standalone VMs), but even in browsers (where it opens the door for a new type of cross-site scripting). For example, even if you only call JS eval() with a constant string in your C cod
Read the rest
e, because WebAssembly has no truly constant memory, this can give XSS to an attacker with a memory write primitive inside linear memory. > The html page there seems to be missing the "main.js" to see what's happening. :( Oops, good point. They are now pushed, sorry about that. > main.js, which looks (without checking) like it came from Emscripten That's correct, you can also check the build script: https://github.com/sola-st/wasm-binary-security/blob/master/...
In Everything old is new again: binary security of WebAssembly
The exploit is against a vulnerable library (the actual input file is here: https://github.com/sola-st/wasm-binary-security/blob/master/...) If you have a wasm application with vulnerabilities (e.g. in the libraries) there are no mitigations that native binaries provide, so simple buffer overflows give you RCEs again. It's still within the sandbox, but the threat is as severe as running eval on user supplied inputs as there might be useful stuff in that sandbox.
In Everything old is new again: binary security of WebAssembly
This doesn't really seem to offer anything useful, or even contain new information. eg: * no corruption of, nor access to host memory. * no corruption of, nor access to memory or other processes. It looks like what they did is create a wasm file that generates a JS "Alert !!!" string, then blindly runs that string in the browser without any kind of validation? It's hard to tell from looking at their code though: https://github.com/sola-st/wasm-binary-security/blob/master/... The html page there seems to be missing the "main.js" to see what's happening. :( --- Hmmm, it might be this main.js, which looks (without checking) like it came from Emscripten: https://github.com/sola-st/wasm-binary-security/blob/master/...
In Everything old is new again: binary security of WebAssembly

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.