Skip to content

History / About the CVE 2016 10033 and CVE 2016 10045 vulnerabilities

Edit page New page

Revisions

  • vulns were actually fixed in 5.2.20 however, so it would be wise to reference that here

    @giantsloar giantsloar committed Jan 3, 2017
    b1ad436

  • Updated About the CVE 2016 10033 and CVE 2016 10045 vulnerabilities (markdown)

    @Synchro Synchro committed Jan 2, 2017
    0204f6b

  • Updated About the CVE 2016 10033 and CVE 2016 10045 vulnerabilities (markdown)

    @Synchro Synchro committed Jan 2, 2017
    df281cc

  • I guess it's not an escape character within inline code tags in the GitHub Markdown variant.

    @Zenexer Zenexer committed Dec 29, 2016
    5086e9b

  • Typo in name; note for postfix; wrong link (not sure what that was--failed to copy?); clarification for Act I resolution; backslash is escape character in Markdown, ironically

    @Zenexer Zenexer committed Dec 29, 2016
    42fdb14

  • Updated About the CVE 2016 10033 and CVE 2016 10045 vulnerabilities (markdown)

    @Synchro Synchro committed Dec 28, 2016
    58fe054

  • Updated About the CVE 2016 10033 and CVE 2016 10045 vulnerabilities (markdown)

    @Synchro Synchro committed Dec 28, 2016
    9cca3b3

  • Updated About the CVE 2016 10033 and CVE 2016 10045 vulnerabilities (markdown)

    @Synchro Synchro committed Dec 28, 2016
    a745369

  • Updated About the CVE 2016 10033 and CVE 2016 10045 vulnerabilities (markdown)

    @Synchro Synchro committed Dec 28, 2016
    6dd54fe

  • Updated About the CVE 2016 10033 and CVE 2016 10045 vulnerabilities (markdown)

    @Synchro Synchro committed Dec 28, 2016
    d3bd008

  • Updated About the CVE 2016 10033 and CVE 2016 10045 vulnerabilities (markdown)

    @Synchro Synchro committed Dec 28, 2016
    d8bd91f

  • sendmail transport was equally vulnerable

    @Zenexer Zenexer committed Dec 28, 2016
    e0185ec

  • Created About the CVE-2016-10033 and CVE-2016-10045 vulnerabilities (markdown)

    @Synchro Synchro committed Dec 28, 2016
    871ebd8