News

CERT Sorts Out Recent Barrage of Lotus Vulnerabilities

CERT on Wednesday moved to help users make sense of a flurry of recent vulnerability notices involving Lotus Notes and Domino on several platforms, including Windows.

"Multiple reporters, the close timing and some ambiguity caused confusion about what releases are vulnerable. We are issuing this advisory to help clarify the details of the vulnerabilities, the versions affected, and the patches that resolve these issues," CERT noted in its advisory.

Confusion stemmed from a barrage of advisories from NGS Software and Rapid7, Inc. In February, NGS reported five vulnerabilities in Notes and Domino. In March, Rapid7 highlighted three more flaws. According to CERT, the impacts ranged from denial of service to data corruption and execution of arbitrary code.

CERT noted that all but one of the vulnerabilities are resolved by upgrading to versions 5.0.12 and 6.0.1 of Lotus Domino. The one remaining vulnerability can be patched.

The CERT advisory is available at www.cert.org/advisories/CA-2003-11.html.

About the Author

Scott Bekker is editor in chief of Redmond Channel Partner magazine.

Featured

  • Microsoft Starting To Roll Out New Excel Connected Data Types

    Microsoft on Thursday announced some Excel and Power BI enhancements that add "connected data types" on top of the standard strings and numbers options.

  • Windows 10 Users Getting New Process for Finding Optional Driver Updates

    Accessing Windows 10 drivers classified as "optional updates" will be more of a manual seek-and-install type of experience, starting on Nov. 5, 2020, Microsoft explained in a Wednesday announcement.

  • Microsoft Changes Privacy Platform Name to SmartNoise

    Microsoft Research has changed the name of its "differential privacy" platform from "WhiteNoise" to "SmartNoise," according to a Wednesday announcement.

  • Why Restarting a Failed SCVMM Job Might Be a Bad Idea

    Occasionally, restarting a failed System Center Virtual Machine Manager job can leave your virtualization infrastructure in an unknown state. Here's how to avoid that.

comments powered by Disqus