Closed hortongn closed 6 years ago
Made changes on scholar-qa that should resolve most if not all of the real vulnerabilities. However, it's possible that SSL settings for Scholar on BigIP may also need to be tweaked.
Sent email to Info Sec on 6/1 asking them to re-scan scholar-qa to see what's resolved.
Info Sec re-scanned and says that we only have one vulnerability remaining (TLS 1.0 enabled). That appears to be a BigIP thing. I've asked Andy to look into it.
Resolved by updated package version httpd-2.4.6-67
Resolved by updated package version httpd-2.4.6-18
Resolved by updated package version httpd-2.4.6-31
Resolved by updated package version httpd-2.4.6-45
Resolved by updated package version httpd-2.4.6-67
Resolved by updated package version httpd-2.4.6-40
RedHat says it's Enterprise Linux 7 Apache package is "not affected" by these vulnerabilities
RedHat lists this vulnerability as "Will not fix"
Needed changes have been made to the Puppet scripts https://git.uc.edu/UCLIBS/scholar-puppet-vagrant/compare/4bd3ce13ae3db5724d712b6d1bdaf4c17d506f2f...scholar-3-update
All of the needed changes have been made to scholar-dev, scholar-qa, and production. Info Sec re-ran the security scans and found no remaining vulnerabilities. The changes have been committed to the Puppet repo as well.
Descriptive summary
We've received a report from Infosec for a security scan run against scholar-qa.uc.edu and scholar.uc.edu
We need to resolve the vulnerabilities and report back to Infosec. Changes to the server environments should be added to the Puppet scripts when applicable. Scholar code changes are probably not needed.
The specific vulnerabilities are not listed here for obvious reasons.