Oracle Communications / Configuration (libssh) CVEs

VRT 391,192 CVEs tracked · 15,442 in RASP scope · data as of 19 hours ago

Description contains RASP scope Status Exploitation Severity

Reset

Overview 1 match · 0 in RASP scope · 0 protected · 0 KEV · 0 public PoC · 0 CISA SSVC · 0 EPSS ≥ 0.5 · 0 disputed

1match 0in RASP scope0.0% 0protected0.0% 0KEV0.0% 0public PoC0.0% 0CISA SSVC0.0% 0EPSS ≥ 0.50.0% 0disputed0.0%

Critical 0 0.0% High 0 0.0% Medium 1 100.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%

Protected by RASP 0 0.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 0 0.0% No fix identified 0 0.0% Mitigated by environment configuration 0 0.0% Queued for review 0 0.0% Not applicable 1 100.0% Out of RASP scope 0 0.0% Rejected 0 0.0%

blocked by ARMR today 0 0.0% not blocked 1 100.0% not established 0 0.0% unrecorded 0 0.0%

Exploited in the wild 0 0.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 1 100.0%

split by SeverityStatusProtectionExploit maturity peak 1 / month

May 23

1 match CSV JSON

CVE	Severity	Published▾	Status	Exploitation	Description
CVE-2023-2283	Medium	2023-05-26	Not applicable	No public exploit	A vulnerability was found in libssh, where the authentication check of the connecting client can be bypassed in the`pki_verify_data_signature` function in memory allocation problems. This issue may happen if there is insufficient memory or the memory usage is limited. The problem is caused by the return value `rc,` which is initialized to SSH_ERROR and later rewritten to save the return value of the function call `pki_key_check_hash_compatible.` The value of the variable is not changed between this point and the cryptographic verification. Therefore any error between them calls `goto error` returning SSH_OK.

CVE

Severity

Published▾

Status

Exploitation

Description

CVE-2023-2283

Medium

2023-05-26

Not applicable

No public exploit

A vulnerability was found in libssh, where the authentication check of the connecting client can be bypassed in the`pki_verify_data_signature` function in memory allocation problems. This issue may happen if there is insufficient memory or the memory usage is limited. The problem is caused by the return value `rc,` which is initialized to SSH_ERROR and later rewritten to save the return value of the function call `pki_key_check_hash_compatible.` The value of the variable is not changed between this point and the cryptographic verification. Therefore any error between them calls `goto error` returning SSH_OK.