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
This sequence in the report*.tex file:
\begin{tabular}{|p{16cm}|}\rowcolor[HTML]{F8A102} \begin{tabular}{@{}p{15cm}>{\raggedleft\arraybackslash}
p{0.5cm}@{}}\textbf{CVE-2019-9947 Medium (4.3)} & \href{https://nvd.nist.gov/vuln/detail/CVE-2019-9947}{\large \faicon{link}}\end{tabular}\
Summary:An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the path component of a URL that lacks a ? character) followed by an HTTP header or a Redis command. This is similar to the CVE-2019-9740 query string issue.\ \hline \end{tabular} \end{figure}
causes pdflatex to error out with this:
! Undefined control sequence.
\n
l.425 ...ument to urllib.request.urlopen with \r\n
(specifically in the path...
Obviously, it's interpreting the text in the summary as an attempted control sequence. Given that you're effectively pulling those from outside sources, it seems like you're going to need to do some escaping before dropping them into the tex output.
The text was updated successfully, but these errors were encountered:
I was able to have a quick pdf quality result by just pasting the tex file content (you can import the file too) into the online tool from here https://www.overleaf.com/ and then using Recompile and pdf download
This sequence in the report*.tex file:
\begin{tabular}{|p{16cm}|}\rowcolor[HTML]{F8A102} \begin{tabular}{@{}p{15cm}>{\raggedleft\arraybackslash}
p{0.5cm}@{}}\textbf{CVE-2019-9947 Medium (4.3)} & \href{https://nvd.nist.gov/vuln/detail/CVE-2019-9947}{\large \faicon{link}}\end{tabular}\
Summary:An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the path component of a URL that lacks a ? character) followed by an HTTP header or a Redis command. This is similar to the CVE-2019-9740 query string issue.\ \hline \end{tabular} \end{figure}
causes pdflatex to error out with this:
! Undefined control sequence.
\n
l.425 ...ument to urllib.request.urlopen with \r\n
(specifically in the path...
Obviously, it's interpreting the text in the summary as an attempted control sequence. Given that you're effectively pulling those from outside sources, it seems like you're going to need to do some escaping before dropping them into the tex output.
The text was updated successfully, but these errors were encountered: