Menu

Star on GitHub · 3.2k

CVE-2001-1172

4.6 · MEDIUM

OmniSecure HTTProtect 1.1.1 allows a superuser without omnish privileges to modify a protected file by creating a symbolic link to that file.

Published Jul 19, 2001omnisecureEPSS 0.35%

Overview

CVE-2001-1172 is a medium-severity vulnerability affecting omnisecure httprotect. It was published on July 19, 2001 and has a CVSS 2.0 base score of 4.6 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 4.6, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

OmniSecure HTTProtect 1.1.1 allows a superuser without omnish privileges to modify a protected file by creating a symbolic link to that file.

Remediation

Check the references section for vendor advisories and patches from omnisecure. Update httprotect to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2001-1172?

CVE-2001-1172 is a medium-severity vulnerability affecting omnisecure httprotect. It was published on July 19, 2001 and has a CVSS 2.0 base score of 4.6 (MEDIUM).

How severe is CVE-2001-1172?

This vulnerability has a CVSS 2.0 base score of 4.6, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2001-1172?

Check the references section for vendor advisories and patches from omnisecure. Update httprotect to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2001-1172?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2001-1172 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2001

View all