Security readout for executives and security teams
Plain-English summary
CVE-2022-35857 describes a remote code execution risk in kvf-admin through 2022-02-12. The issue is tied to unsafe deserialization and a hardcoded key protecting the rememberMe parameter. Sources do not provide a CVSS score, confirmed patch version, or evidence of active exploitation.
Executive priority
Treat as high priority where kvf-admin is deployed. Remote code execution can lead to full application compromise, but urgency depends on confirmed exposure because the sources lack exploitation evidence and patch details.
Technical view
The CVE states kvf-admin mishandles deserialization. The rememberMe parameter is encrypted with a hardcoded key from com.kalvin.kvf.common.shiro.ShiroConfig, which can let remote attackers execute arbitrary code. The provided sources do not list CPEs, CWE mapping, CVSS, or a vendor-fixed version.
Likely exposure
Exposure is likely limited to organizations running kvf-admin through 2022-02-12, especially deployments reachable from untrusted networks. The source bundle does not provide formal CPEs or a complete affected-version matrix.
Exploitation context
The CVE text states remote arbitrary code execution is possible. KEV is false, and the supplied sources do not show confirmed active exploitation. Public disclosure exists through a GitHub issue.
Researcher notes
Evidence is sparse. The reliable facts are the product name, affected date boundary, deserialization issue, hardcoded rememberMe encryption key, and RCE impact. Do not assume a specific CVSS score, exploit availability, or remediation path beyond vendor guidance.
Mitigation direction
- Inventory kvf-admin deployments and confirm whether they are from 2022-02-12 or earlier.
- Check the upstream repository and issue for fixed releases or vendor guidance.
- Restrict network access to kvf-admin from trusted administrative networks only.
- Review whether rememberMe functionality can be disabled safely until guidance is confirmed.
- Prioritize replacement or removal if no maintained fix is available.
Validation and detection
- Confirm running kvf-admin version or build date against the affected date in the CVE.
- Review configuration and code for the referenced ShiroConfig hardcoded rememberMe key.
- Check access logs for unexpected rememberMe activity or anomalous administrative requests.
- Verify administrative interfaces are not exposed directly to the internet.
- Document whether a vendor fix, workaround, or compensating control is in place.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
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 lookupCVE-2022-35857 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/kalvinGit/kvf-admin/issues/16CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
