You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 21, 2018. It is now read-only.
We've had our soon to be launched site externally security tested. The security auditors use the AS/NZS 31000:2009 standard for assessing risk. A few issues recorded were linked directly to the LogViewer component. I will include a new issue per issue recorded by security audit.
Consequence High
This flaw can be exploited to affect the integrity of all applications served from the same server.
The LogViewer component parses the Apache log files and presents the entries to the user. If a log entry contains any HTML component, including Javascript, it is sent to the browser without validation. This introduces a cross site scripting vulnerability.
The text was updated successfully, but these errors were encountered:
I have not had any time lately to fix this bug and #67. If @cjke would like to open a pull request that fixes it, I will review and (most likely) accept.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We've had our soon to be launched site externally security tested. The security auditors use the AS/NZS 31000:2009 standard for assessing risk. A few issues recorded were linked directly to the LogViewer component. I will include a new issue per issue recorded by security audit.
Consequence High
This flaw can be exploited to affect the integrity of all applications served from the same server.
The LogViewer component parses the Apache log files and presents the entries to the user. If a log entry contains any HTML component, including Javascript, it is sent to the browser without validation. This introduces a cross site scripting vulnerability.
The text was updated successfully, but these errors were encountered: