CVE-2022-41550

What it actually does

Integer overflow in osip_body_parse_header allows malformed input to trigger arithmetic wraparound during header length calculations, resulting in memory corruption or application crash.

Why it matters to the business

Systems processing untrusted SIP or related protocol data may experience denial of service, interrupting services that depend on the affected parsing library; the issue is old with low exploitation probability and no known active campaigns.

How an attack unfolds

An attacker crafts a SIP message containing a body header with specially chosen length values that cause integer overflow during parsing in osip_body_parse_header; successful overflow leads to invalid memory access and process termination without requiring authentication.

How to fix it

Upgrade pts/sam2p to the commit b953f63307c4a83fa4615a4863e3fb250205cd98 or later; rebuild any dependent packages that statically link the vulnerable oSIP component.

How to confirm the fix worked

Confirm the installed source revision contains b953f63307c4a83fa4615a4863e3fb250205cd98; recompile and execute unit tests that exercise osip_body_parse_header with boundary-case header lengths.

Typical attack path

1. Identify a network endpoint accepting SIP or oSIP-processed data
2. Send a single crafted message containing an oversized or malformed body header
3. Trigger the overflow inside osip_body_parse_header
4. Cause the target process to crash or become unresponsive

How to detect it

Review application and system logs for unexpected crashes or segmentation faults in processes linked against oSIP during SIP message handling; correlate with inbound network traffic containing unusual Content-Length or body-header values.

What your security team should do

• Apply the referenced commit to all builds using the affected oSIP code
• Scan build pipelines and dependency manifests for references to vulnerable oSIP versions
• Monitor EPSS and KEV updates for any future increase in exploit maturity