CVE-2022-31002

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.9% (80th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2022-52709 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Sofia-SIP is an open-source Session Initiation Protocol (SIP) User-Agent library. Prior to version 1.13.8, an attacker can send a message with evil sdp to FreeSWITCH, which may cause a crash. This type of crash may be caused by a URL ending with %. Version 1.13.8 contains a patch for this issue.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.9%
EPSS %ILE
80th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-04). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 31, 2022

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Oct 29, 2026
Patch available. Sources: github_commit, github.
Web page

[SECURITY] [DSA 5410-1] sofia-sip

https://www.debian.org/security/2023/dsa-5410
Web page

Sofia-SIP: Multiple Vulnerabilities (GLSA 202210-18) — Gentoo security

https://security.gentoo.org/glsa/202210-18
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3091-1] sofia-sip security update

https://lists.debian.org/debian-lts-announce/2022/09/msg00001.html
GitHub advisoryMentions a patch (unverified)

url_canonize2 Out-of-bound read · Advisory · freeswitch/sofia-sip · GitHub

https://github.com/freeswitch/sofia-sip/security/advisories/GHSA-g3x6-p824-x6hm
GitHub commit Patch Available

commit 51841eb53679 (freeswitch/sofia-sip)

Patch available: freeswitch/sofia-sip v1.13.8 (contains commit 51841eb53679)

https://github.com/freeswitch/sofia-sip/commit/51841eb53679434a386fb2dcbca925dcc48d58ba

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibsofia-sip-ua-dev (1.12.11+20110422.1-2.1+deb10u3ubuntu0.22.04.1) @ jammy2026-10-29ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(16 across 16 ecosystems)
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.13.8-r0: fixed in 1.13.8-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip1.12.11+20110422.1-2.1
  • every version up to 1.12.11+20110422.1-2.1+deb10u1: fixed in 1.12.11+20110422.1-2.1+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip1.12.11+20110422.1-2.1
  • every version up to 1.12.11+20110422.1-2.1+deb11u1: fixed in 1.12.11+20110422.1-2.1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.12.11+20110422.1+1e14eea~dfsg-3: fixed in 1.12.11+20110422.1+1e14eea~dfsg-3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.12.11+20110422.1+1e14eea~dfsg-3: fixed in 1.12.11+20110422.1+1e14eea~dfsg-3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
sofia-sip—
  • every version up to 1.12.11+20110422.1+1e14eea~dfsg-3: fixed in 1.12.11+20110422.1+1e14eea~dfsg-3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Frequently asked(5)

What is CVE-2022-31002?
CVE-2022-31002 is a high-severity vulnerability; its CVE record was published on May 31, 2022. Sofia-SIP is an open-source Session Initiation Protocol (SIP) User-Agent library. Prior to version 1.13.8, an attacker can send a message with evil sdp to FreeSWITCH, which may cause a crash. This type of crash may be caused by a URL ending with %. Version 1.13.8 contains a patch for this issue.
When was the CVE record for CVE-2022-31002 published?
The CVE record for CVE-2022-31002 was published on May 31, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-31002 actively exploited?
CVE-2022-31002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (80th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-31002?
CVE-2022-31002 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-31002?
A fix for CVE-2022-31002 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-31002

Explore →

Is Your Infrastructure Affected by CVE-2022-31002?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.