Menu

Star on GitHub · 3.2k

CVE-2011-2910

6.7 · MEDIUM

The AX.25 daemon (ax25d) in ax25-tools before 0.0.8-13 does not check the return value of a setuid call.

Published Nov 15, 2019CWE-269EPSS 0.38%

Overview

CVE-2011-2910 is a medium-severity vulnerability. It was published on November 15, 2019 and has a CVSS 3.1 base score of 6.7 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 6.7, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

The AX.25 daemon (ax25d) in ax25-tools before 0.0.8-13 does not check the return value of a setuid call. The setuid call is responsible for dropping privileges but if the call fails the daemon would continue to run with root privileges which can allow possible privilege escalation.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. 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.

Frequently asked questions

What is CVE-2011-2910?

CVE-2011-2910 is a medium-severity vulnerability. It was published on November 15, 2019 and has a CVSS 3.1 base score of 6.7 (MEDIUM).

How severe is CVE-2011-2910?

This vulnerability has a CVSS 3.1 base score of 6.7, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2011-2910?

Check the references section for vendor advisories, patches, and mitigation guidance. 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-2011-2910?

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

View all