2021-01-30 02:08:18 +03:00
|
|
|
# stack build plan using GHC 8.8.4
|
|
|
|
|
|
|
|
|
|
nix:
|
|
|
|
|
pure: false
|
|
|
|
|
packages: [perl gmp ncurses zlib]
|
|
|
|
|
|
|
|
|
|
resolver: lts-16.31
|
|
|
|
|
|
|
|
|
|
packages:
|
|
|
|
|
- hledger-lib
|
|
|
|
|
- hledger
|
|
|
|
|
- hledger-ui
|
|
|
|
|
- hledger-web
|
|
|
|
|
|
|
|
|
|
extra-deps:
|
|
|
|
|
# for hledger-lib:
|
|
|
|
|
- pretty-simple-4.0.0.0
|
|
|
|
|
- prettyprinter-1.7.0
|
2021-07-17 06:58:57 +03:00
|
|
|
- doctest-0.18.1
|
2021-01-30 02:08:18 +03:00
|
|
|
# for hledger:
|
|
|
|
|
# for hledger-ui:
|
|
|
|
|
# for hledger-web:
|
fix: web: b64 encode user controlled input (#1525)
This fixes a reported Stored XSS vulnerability in toBloodhoundJson by
encoding the user-controlled values in this payload into base64 and
parsing them with atob.
In my exploration of the vulnerability with various payloads I and
others crafted, it would appear that this is the only available XSS in
hledger-web in relation to stored accounts and transaction details. If
there is other parts of the UI which may contain user-controlled data,
they should be examined for similar things. In this instance,
protections provided by yesod and other libraries worked fine, but in a
bit of code that hledger-web was generating, the user could insert a
</Script> tag (which is valid HTML and equivalent to </script> but not
caught by the T.Replace that existed in toBloodhoundJson) in order to
switch out of a script context, allowing the parser to be reset, and for
arbitrary JavaScript to run.
The real fix is a bit more involved, but produces much better results:
Content-Security-Policy headers should be introduced, and using
sha256-<hash of script> or a different algorithm, they should be marked
as trusted in the header. This way, if the (in-browser) parser and
hledger-web generator disagree on the source code of the script, the
script won't run. Note that this would still be susceptible to attacks
that involve changing the script by escaping from the string inside it
or something similar to that, which can be avoided additionally by using
either the method used in this commit, or a proper JSON encoder.
The second approach has the advantage of preventing further XSS, to the
extent specified above, in practice, a combination of both should be
used, b64 for embedded data and the CSP sha256-hash script-src over
everything else, which will eliminate all injected or malformed script
blocks (via CSP), in combination with eliminating any HTML closing tags
which might occur in stored data (via b64).
This vulnerability appears to have been first introduced when
autocompletion was added in hledger-web, git tag hledger-0.24, commit
hash: ec51d28839b2910eea360b1b8c72904b51cf7821
Test payload: </Script><svg onload=alert(1)//>
Closes #1525
2021-08-22 14:58:46 +03:00
|
|
|
- ghc-byteorder-4.11.0.0.10
|
2021-01-30 02:08:18 +03:00
|
|
|
# for Shake.hs:
|
|
|
|
|
|
|
|
|
|
# for precise profiling, per https://www.tweag.io/posts/2020-01-30-haskell-profiling.html:
|
|
|
|
|
# apply-ghc-options: everything
|
|
|
|
|
# rebuild-ghc-options: true
|
|
|
|
|
# stack build --profile --ghc-options="-fno-prof-auto"
|
|
|
|
|
|
|
|
|
|
# tell GHC to write hie files, eg for weeder. Rumoured to be slow.
|
|
|
|
|
# ghc-options:
|
|
|
|
|
# "$locals": -fwrite-ide-info
|
|
|
|
|
|
|
|
|
|
# ghc-options:
|
|
|
|
|
# "$locals": -ddump-timings
|
|
|
|
|
# "$targets": -Werror
|
|
|
|
|
# "$everything": -O2
|
|
|
|
|
# some-package: -DSOME_CPP_FLAG
|
|
|
|
|
|
