dbcve.org
Pjsua2 SdkApplication · Pjsip

CVE-2015-2003

CRITICAL · 9.8 CVSS v3.0 Published 2018-03-29
Fix available
A fix is available. Upgrade to 51322 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The PJSIP PJSUA2 SDK before SVN Changeset 51322 for Android might allow attackers to execute arbitrary code by leveraging a finalize method in a Serializable class that improperly passes an attacker-controlled pointer to a native function.

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 · high confidence

PJSIP PJSUA2 SDK for Android contains a vulnerability where a Serializable class's finalize() method improperly passes an attacker-controlled pointer to a native function. An attacker can manipulate this pointer before finalization, causing the native code to dereference an arbitrary memory address and execute arbitrary code.

MitigationUpdate PJSIP PJSUA2 SDK to SVN Changeset 51322 or later, which contains the fix for proper pointer validation in the finalize method.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pjsua2 SdkApplication
Affected:< 51322

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify PJSIP PJSUA2 SDK usage in the Android project
    Search the project codebase and dependency files (build.gradle, pom.xml, libs folder) for references to 'pjsua2', 'pjsip', or 'pjproject' libraries. Inspect any bundled .jar or .so files related to PJSIP.
    Affected if The project includes PJSIP PJSUA2 library files or dependencies.
  2. Determine the PJSIP PJSUA2 SDK version or changeset number
    Locate the version identifier in the SDK. Check the library JAR file manifest, native .so file metadata, or any version configuration file included with the PJSIP library. The version may be expressed as a SVN changeset number.
    Affected if The detected version/changeset is below 51322.
  3. Inspect the Serializable class finalize() method in PJSUA2
    If decompiling or inspecting the Java/JNI layer of the PJSUA2 library, locate any Serializable class that implements a finalize() method and verify if it passes raw pointers directly to native functions without validation.
    Affected if The finalize() method passes an attacker-controllable pointer to native code without proper validation.
  4. Review native library build configuration
    If you have access to the native .so libraries, verify they were built from a PJSIP source tree with changeset prior to 51322. Check any embedded version strings in the native libraries.
    Affected if The native library build originates from PJSIP version < changeset 51322.

The environment is affected if the Android application bundles or uses the PJSIP PJSUA2 SDK with a version or changeset number lower than 51322, where the finalize() method in a Serializable class passes unvalidated pointers to native functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 51322 or later
Fixed in 51322
Interim mitigation

Update PJSIP PJSUA2 SDK to SVN Changeset 51322 or later, which contains the fix for proper pointer validation in the finalize method.

Recommended fix High confidence

SVN Changeset 51322 or later

  1. 1. Identify the current PJSIP PJSUA2 SDK version in use by checking the source code or library build
  2. 2. Obtain the fixed version from the PJSIP SVN repository at changeset 51322 or later (svn://svn.pjsip.org/pjproject@51322)
  3. 3. Replace the vulnerable PJSUA2 SDK files with the fixed version
  4. 4. Rebuild the Android application with the updated SDK
  5. 5. Redeploy and test the application to verify the fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pjsua2 Sdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-2003 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-2003 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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