VulnerabilityPublished 10 Apr 2024Updated 6 Dec 2024

CVE-2024-28345

Source CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-28345, organizations should first verify if they are running affected versions of Sipwise C5 NGCP Dashboard below mr11.5.1 and plan an immediate upgrade to the latest patched version once available. In the interim, restrict access to the Journal endpoint by implementing strict network-level controls such as firewall rules or VPN requirements limiting access to trusted administrators only. Employ strong authentication and authorization mechanisms to ensure only authorized users can reach sensitive dashboard endpoints. Monitor access logs for unusual or unauthorized attempts to access the Journal URL and investigate anomalies promptly. Consider deploying web application firewalls (WAF) with custom rules to block direct URL access attempts to sensitive endpoints by low privileged users. Conduct regular security audits and penetration testing focused on management interfaces to detect similar access control weaknesses. Educate administrators and users about the risks of sharing credentials or URLs that could expose sensitive endpoints. Finally, maintain up-to-date backups and incident response plans tailored to communication platform security incidents.

Description

An issue discovered in Sipwise C5 NGCP Dashboard below mr11.5.1 allows a low privileged user to access the Journal endpoint by directly visit the URL.

Impact

The impact of CVE-2024-28345 on organizations primarily involves unauthorized access to sensitive journal data within the Sipwise C5 NGCP Dashboard. This can lead to confidentiality breaches where sensitive call or system logs are exposed to unauthorized users, potentially revealing operational details or user information. Integrity could be affected if the attacker can manipulate journal entries, undermining trust in system logs and complicating forensic investigations. Availability impact is limited but possible if journal access is abused to disrupt monitoring or logging functions. For telecom and VoIP providers, such exposure can weaken security posture, aid further attacks, or violate compliance requirements related to data protection and auditing. Since exploitation requires only low privileges and user interaction, insider threats or compromised user accounts pose a significant risk. The absence of known exploits reduces immediate risk but does not eliminate the threat. Organizations worldwide relying on Sipwise C5 NGCP Dashboard for critical communication infrastructure could face operational and reputational damage if this vulnerability is exploited.

References

securitycafe.ro/2024/03/21/cve-2024-28344-cve-2024-28345-in-sipwise-c5/ (opens in a new tab)

Community reviews

Loading reviews…