Menu

Star on GitHub · 3.2k

CVE-2005-1736

7.5 · HIGH

PROMS 0.11 does not properly handle "certain combinations of rights," which gives more rights to users than intended.

Published May 24, 2005electricmonkEPSS 1.10%

Overview

CVE-2005-1736 is a high-severity vulnerability affecting electricmonk proms. It was published on May 24, 2005 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

PROMS 0.11 does not properly handle "certain combinations of rights," which gives more rights to users than intended.

Remediation

Check the references section for vendor advisories and patches from electricmonk. Update proms 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
electricmonkproms0Affected

Frequently asked questions

What is CVE-2005-1736?

CVE-2005-1736 is a high-severity vulnerability affecting electricmonk proms. It was published on May 24, 2005 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2005-1736?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2005-1736?

Check the references section for vendor advisories and patches from electricmonk. Update proms 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-2005-1736?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-1736 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 HIGH CVEs from 2005

View all