CVE-2024-28113 Vulnerability Analysis & Exploit Details

CVE-2024-28113
Vulnerability Scoring

3.5
/10
Moderate Risk

Exploiting CVE-2024-28113 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2024-28113 Details

Status: Analyzed

Last updated: 🕔 20 Feb 2025, 17:08 UTC
Originally published on: 🕗 12 Mar 2024, 20:15 UTC

Time between publication and last update: 344 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N

CVE-2024-28113 Vulnerability Summary

CVE-2024-28113: Peering Manager is a BGP session management tool. In Peering Manager <=1.8.2, it is possible to redirect users to an arbitrary page using a crafted url. As a result users can be redirected to an unexpected location. This issue has been addressed in version 1.8.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Assessing the Risk of CVE-2024-28113

Access Complexity Graph

The exploitability of CVE-2024-28113 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-28113

The exploitability of CVE-2024-28113 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-28113, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-28113, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2024-28113 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2024-28113 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2024-28113 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.053% (probability of exploit)

EPSS Percentile: 24.47% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 75.53% of others.

CVE-2024-28113 References

External References

CWE Common Weakness Enumeration

CWE-601

CAPEC Common Attack Pattern Enumeration and Classification

  • Cross-Site Flashing CAPEC-178 An attacker is able to trick the victim into executing a Flash document that passes commands or calls to a Flash player browser plugin, allowing the attacker to exploit native Flash functionality in the client browser. This attack pattern occurs where an attacker can provide a crafted link to a Flash document (SWF file) which, when followed, will cause additional malicious instructions to be executed. The attacker does not need to serve or control the Flash document. The attack takes advantage of the fact that Flash files can reference external URLs. If variables that serve as URLs that the Flash application references can be controlled through parameters, then by creating a link that includes values for those parameters, an attacker can cause arbitrary content to be referenced and possibly executed by the targeted Flash application.

Vulnerable Configurations

  • cpe:2.3:a:peering-manager:peering_manager:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.7.3:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.7.4:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.7.4:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:peering-manager:peering_manager:1.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:peering-manager:peering_manager:1.8.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-28113: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-31203 – An integer overflow was addressed with improved input validation. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, iPadOS 17.7.6, macOS Sonoma...
  • CVE-2025-31202 – A null pointer dereference was addressed with improved input validation. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, tvOS ...
  • CVE-2025-31197 – The issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS 17.7.6, macOS Sono...
  • CVE-2025-30445 – A type confusion issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS 17.7....
  • CVE-2025-24271 – An access issue was addressed with improved access restrictions. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS...