LiveActive security incident?Get immediate response
CVE Record

CVE-2015-2003: The PJSIP PJSUA2 SDK before SVN Changeset 51322 for Android might allow attackers to execute arbitrary code...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE concerns an Android SDK component in PJSIP PJSUA2. Vulnerable builds may let an attacker turn a bad object cleanup path into arbitrary code execution. The public bundle does not provide CVSS, precise affected products, or confirmed exploitation, so urgency depends on whether your Android apps embed this SDK.

Executive priority

Treat this as an inventory-driven Android dependency risk. Prioritize review for mobile apps handling sensitive calls, authentication, or customer data. Escalate to remediation once a vulnerable PJSUA2 build is confirmed; otherwise record evidence showing the SDK is absent or fixed.

Technical view

PJSIP PJSUA2 SDK before SVN Changeset 51322 for Android may pass an attacker-controlled pointer from a Serializable class finalize method into native code. That unsafe Java-to-native boundary could allow arbitrary code execution. The bundle does not list CWE, CVSS, CPEs, or specific application products.

Likely exposure

Exposure is most likely in Android applications or SDKs that bundle PJSIP PJSUA2 before SVN Changeset 51322. The CVE record lists affected vendor and product as n/a, so teams need dependency, source, and APK/SBOM review rather than relying on CPE matching.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Public research/advisory references exist, but the provided data only supports a potential arbitrary code execution condition, not observed in-the-wild exploitation.

Researcher notes

The strongest available facts are the Android PJSUA2 scope, the pre-SVN-51322 version boundary, and the native pointer misuse through finalization. Missing CVSS, CPEs, CWE, and exploit evidence reduce confidence in impact ranking and require local version validation.

Mitigation direction

  • Inventory Android apps and SDKs for bundled PJSIP PJSUA2 components.
  • Upgrade to a PJSIP PJSUA2 build containing SVN Changeset 51322 or later.
  • If upgrade mapping is unclear, check PJSIP or vendor guidance before release.
  • Rebuild and redeploy affected Android applications after dependency replacement.
  • Document any compensating controls for apps that cannot be updated quickly.

Validation and detection

  • Confirm SBOMs, build files, and APK contents identify the PJSUA2 version used.
  • Verify the shipped build contains SVN Changeset 51322 or a later equivalent.
  • Check mobile release inventories for third-party apps embedding vulnerable SDK builds.
  • Retest affected Android application flows after replacing the SDK.
  • Track unresolved findings where version provenance cannot be proven.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2015-2003 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.