Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2017-16875
Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Description
An issue was discovered in Teluu pjproject (pjlib and pjlib-util) in PJSIP before 2.7.1. The ioqueue component may issue a double key unregistration after an attacker initiates a socket connection with specific settings and sequences. Such double key unregistration will trigger an integer overflow, which may cause ioqueue backends to reject future key registrations.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
PJSIP Teluu pjproject pjlib和pjlib-util 数字错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
PJSIP是一个使用C语言编写的开源、免费的多媒体通信库。Teluu pjproject pjlib是其中的一个小型框架库;pjlib-util是其中的一个辅助工具库。 PJSIP 2.7.1之前的版本中的Teluu pjproject pjlib和pjlib-util存在整数溢出漏洞。攻击者可利用该漏洞造成ioqueue后端无法进行密钥注册。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
VendorProductAffected VersionsCPESubscribe
-n/a n/a -
II. Public POCs for CVE-2017-16875
#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC
III. Intelligence Information for CVE-2017-16875
Please Login to view more intelligence information
IV. Related Vulnerabilities
V. Comments for CVE-2017-16875

No comments yet


Leave a comment