CVE-2001-1563

Unknown vulnerability in Tomcat 3.2.1 running on HP Secure OS for Linux 1.0 allows attackers to access servlet resources. NOTE: due to the vagueness of the vendor advisory, it is not clear whether this issue is already covered by other CVE identifiers...

CVE-2001-1563

CVE-2001-1563 refers to a vulnerability in Tomcat 3.2.1 running on HP Secure OS for Linux 1.0 where attackers could access servlet resources. The vendor advisory is vague about full scope, but a public remediation exists: Apache Tomcat 3.2.4 fixes this issue. While the exact root cause isn’t deta...

CVE-2002-2012

Unknown vulnerability in Apache 1.3.19 running on HP Secure OS for Linux 1.0 allows remote attackers to cause "unexpected results" via an HTTP request...

CVE-2001-1506

Unknown vulnerability in the file system protection subsystem in HP Secure OS Software for Linux 1.0 allows additional user privileges on some files beyond what is specified in the file system protection rules, which allows local users to conduct unauthorized operations on restricted files...

CVE-2001-1506

The CVE-2001-1506 entry concerns HP Secure OS Software for Linux 1.0, where the file system protection subsystem permits local users to gain additional privileges beyond the configured protection rules, enabling unauthorized operations on restricted files. The available sources describe the vulne...

CVE-2002-2012

Unknown vulnerability in Apache 1.3.19 running on HP Secure OS for Linux 1.0 allows remote attackers to cause "unexpected results" via an HTTP request...

CVE-2001-1506

Unknown vulnerability in the file system protection subsystem in HP Secure OS Software for Linux 1.0 allows additional user privileges on some files beyond what is specified in the file system protection rules, which allows local users to conduct unauthorized operations on restricted files...

CVE-2001-1563

Unknown vulnerability in Tomcat 3.2.1 running on HP Secure OS for Linux 1.0 allows attackers to access servlet resources. NOTE: due to the vagueness of the vendor advisory, it is not clear whether this issue is already covered by other CVE identifiers...