Skip to content
Fencer Intel
medium 4.6

CVE-2022-1955 json

Session 1.13.0 allows an attacker with physical access to the victim's device to bypass the application's password/pin lock to access user…

published 4y ago modified 4mo ago also EUVD-2022-25223

cvss
4.6
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

Session 1.13.0 allows an attacker with physical access to the victim's device to bypass the application's password/pin lock to access user data. This is possible due to lack of adequate security controls to prevent dynamic code manipulation.

Is CVE-2022-1955 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-1955 updated cvss 0.0

perl-SNMP_Session: lack of adequate security controls may lead to information disclosure

  • Red Hat Enterprise Linux 6 perl-SNMP_Session Red Hat Enterprise Linux 7 perl-SNMP_Session Red Hat Enterprise Linux 8 perl-SNMP_Session Red Hat Enterprise Linux 9 perl-SNMP_Session
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/oxen-io/session-android/pull/897 referenced PoC, tagged "exploit" by a source, unverified
  • fluidattacks.com https://fluidattacks.com/advisories/tempest/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 4.6 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

  • n/a Session

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.