Approved changes feed: RSS · Atom
cpe:2.3:a:cisco:smart_phy:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Cisco (e1b3baff-aaf9-56a6-a68a-41e28ce616a5) |
|---|---|
| Product | Smart Phy (9c8d0485-f13a-5693-b97f-20268207b1a0) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-32433 |
vulnerable | 2026-06-08 07:18:59.762300 |
Erlang/OTP SSH Vulnerable to Pre-Authentication RCE
CRITICAL (10)
Erlang/OTP is a set of libraries for the Erlang programming language. Prior to versions OTP-27.3.3, OTP-26.2.5.11, and OTP-25.3.2.20, a SSH server may allow an attacker to perform unauthenticated remote code execution (RCE). By exploiting a flaw in SSH protocol message handling, a malicious actor could gain unauthorized access to affected systems and execute arbitrary commands without valid credentials. This issue is patched in versions OTP-27.3.3, OTP-26.2.5.11, and OTP-25.3.2.20. A temporary workaround involves disabling the SSH server or to prevent access via firewall rules.
Published: 2025-04-16T21:34:37.457Z
Updated: 2026-02-26T18:28:12.084Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-44228 |
vulnerable | 2026-06-08 05:36:45.320973 |
Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints
Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
Published: 2021-12-10T00:00:00.000Z
Updated: 2025-10-21T23:25:23.121Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.