CVE-2025-0430
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBelledonne Communications Linphone-Desktop is vulnerable to a NULL Dereference vulnerability, which could allow a remote attacker to create a denial-of-service condition.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceLinphone-Desktop contains a NULL pointer dereference vulnerability that can be triggered remotely, causing the application to crash and result in a denial-of-service condition. The vulnerability exists in the desktop client of the VoIP softphone application developed by Belledonne Communications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Linphone-Desktop is installedCheck common installation directories or use system package managers: Windows (Program Files\Linphone or %APPDATA%\linphone), macOS (/Applications/Linphone.app or ~/Library/Application Support/Linphone), Linux (which linphone or dpkg -l | grep linphone)Affected if Linphone-Desktop is present on the system
-
Determine installed versionRun 'linphone --version' from command line, or right-click the Linphone application icon and select 'About', or check the version in the application's settings menu under 'About' or 'Information'Affected if Version cannot be determined or is earlier than the patched release
-
Check for network/SIP configuration enabledExamine Linphone's account settings or SIP configuration: look for registered SIP accounts, enabled SIP transport (UDP/TCP/TLS), or active registration status in the application's main window or configuration files (linphonerc or ~/.linphonerc)Affected if A SIP account is registered or SIP transport is enabled, allowing remote triggering of the vulnerability
-
Review application logs for crashesCheck Linphone's log directory (typically ~/.cache/linphone/logs or %LOCALAPPDATA%\Linphone\logs) for recent crash logs or error entries containing 'NULL' or 'pointer' keywords around the time of unexpected application exitsAffected if Recent crash logs show null pointer dereference or segmentation fault errors
User is affected if Linphone-Desktop is installed with a version prior to the vendor patch and has SIP/network features enabled, allowing remote attackers to trigger the NULL pointer dereference causing denial of service.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-supplied patch when available; in the interim, implement proper null-pointer validation before dereferencing pointers in the affected code paths and consider network-level filtering to limit attack surface.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0430 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0430 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data