July 25: 1 New Vuln | CVE-2023-35078

In this CISA KEV Breakdown, one vulnerability was added in Ivanti’s Endpoint Manager Mobile (EMM) used against a staggering 12 Norwegian ministries as a 0-day. Norwegian authorities were the first to report exploitation of this vulnerability publicly. Some confusion arose around the initial disclosure of the vulnerability, due to the difficulty in finding technical details about the bug without an NDA in place with the vendor. As a public advisory has been made available as of last night, the addition to the KEV shortly followed. This vulnerability is considered urgent enough that CISA has both added an entry for the KEV as well as issuing an Alert urging organizations to patch.




Exploitation Consequence

GreyNoise Traffic

EPSS Score

EPSS Percentile

Due Date



Endpoint Manager Mobile

Authentication Bypass




Notable Vulnerability Additions

CVE-2023-35078 | Ivanti Endpoint Manager Mobile

A vulnerability exists in Endpoint Manager versions up to 11.10 in which an attacker can exploit to bypass authentication of an API endpoint. An attacker would be able to manipulate data on the webserver, including creating an EPMM admistrative account, as well as view Personally Identifiable Information (PII) upon successfully exploiting the vulnerability. An attacker is able to exploit this vulnerability remotely and unauthenticated, a perfect storm for a whole lot of noise.

Details on how the vulnerability is exploited are still not clear, which is probably a good thing. As Kevin Beaumont points out, the installment of a honeypot to observe behavior tied to this vulnerability appears to be trivial, and the traffic is already visible, leading the community to believe that scanning for the existence of this vulnerability is active and ongoing beyond the targeted attacks against the Norwegian government.

A Shodan search today still shows over 2800 exposed EMM (formerly MobileIron Core) instances on the internet. As far as how many of these are still vulnerable to CVE-2023-35078, let’s hope it is less. Organizations are encouraged to act on mitigating this vulnerability as soon as possible, as we suspect it won’t be long before PoCs are rampant among the research and dark web communities.

Security Advisory(s):


← July 20, 2023 CISA Kev Breakdown

Click here to expand our CISA KEV Breakdown Frequently Asked Questions
  • What makes for a notable addition?
    • A notable addition can arise from many different characteristics. If a particular vulnerability is notable to the security community or a subset of the security community or if the EPSS score reveals notable information about the vulnerability, this can constitute further analysis. It may also be the case that a particular vulnerability shines a light on everyday users and we will highlight important information and key takeaways to ensure users and readers have easy access to actionable information.
  • When is the Breakdown released?
    • We aim to have our analysis of each KEV update posted within 24 hours of the time in which the Catalog is updated. See CISA’s full catalog here
  • I am not bound by BOD 22-01 or federal regulations, why should the KEV concern me?
    • CISA encourages all organizations to utilize the Catalog as an attribute in your vulnerability prioritization framework. Organizations looking to lessen the scope on known dangerous vulnerabilities and make a goal to remediate them can understand where they currently stand against what CISA has confirmed as exploited vulnerabilities in the wild. See CISA’s section on “How should organizations use the KEV catalog?” here.
  • What is EPSS?
    • EPSS is the Exploit Prediction Scoring System. It is an open, data-driven effort for estimating the likelihood (probability) that a software vulnerability will be exploited in the wild. See the EPSS home page on FIRST for more information here.
  • What is the difference between EPSS probability and EPSS percent?
    • EPSS probability is the risk calculated by the model when determining the perceived threat of the vulnerability itself. Percentage is a relative comparison of the rest of the CVEs within the given sample. While the probability only changes upon refreshing the results from the model, the percentage can change purely based on the CVE sample given. In the case of the Breakdown, we use the percentage given by the pool of all CVEs with given EPSS data. Scores may vary post-release of the post given new information about the vulnerabilities and their perceived threat. For more information on applying and understanding EPSS data, see this article on the FIRST website, as well as their FAQ page.
  • What is GreyNoise?
    • GreyNoise is a platform that collects, analyzes, and labels data on IPs that scan the internet and saturate security tools with noise. Through their sensor network, GreyNoise observes vulnerability exploitation attempts for vulnerabilities that are exploited in the wild over the Internet. These are arguably vulnerabilities that should be at the very top of your priority list to remediate.
  • Why are GreyNoise exploitation attempts only observed on ~20% of KEV vulnerabilities?
    • Exploitation of many vulnerabilities in the CISA KEV will not be observed for many reasons that GreyNoise does a good job of explaining in this post. For example:
      • The vulnerability may not be remotely exploitable
      • Vulnerability exploitation may require authentication (and result in privilege escalation)
      • The impacted software may not be exposed to the internet
      • Mass scanning/exploitation is not occurring yet