dbcve.org
AgevoltApplication

CVE-2022-38484

HIGH · 8.8 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to 0.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An arbitrary file upload and directory traversal vulnerability exist in the file upload functionality of the System Setup menu in AgeVolt Portal prior to version 0.1. A remote authenticated attacker could leverage this vulnerability to upload files to any location on the target operating system with web server privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

AgeVolt Portal prior to version 0.1 contains an arbitrary file upload vulnerability combined with directory traversal in the System Setup menu's file upload functionality. An authenticated remote attacker can upload malicious files to arbitrary locations on the host operating system with web server privileges.

MitigationUpgrade AgeVolt Portal to version 0.1 or later, which contains the patch for this vulnerability. Implement strict input validation on file upload endpoints to prevent directory traversal attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AgevoltApplication
Affected:< 0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm AgeVolt Portal installation
    Inspect the web server's deployed applications for AgeVolt Portal. Check for directories or application files named 'agevolt', 'AgeVolt', or similar case variations in the web root.
    Affected if AgeVolt Portal software is deployed on the system
  2. Identify installed AgeVolt Portal version
    Locate version information in the application: check the portal's About page, footer, or configuration files within the AgeVolt installation directory. Compare the version number to the affected range (< 0.1).
    Affected if The installed version is less than 0.1
  3. Verify System Setup menu access
    Log into the AgeVolt Portal and navigate to the System Setup menu. Determine if the file upload functionality is present and accessible.
    Affected if The System Setup menu with file upload functionality is accessible and enabled
  4. Check authentication requirements
    Examine whether the System Setup file upload endpoint requires authentication. Test if the upload functionality can be reached without valid credentials.
    Affected if The file upload endpoint is accessible to authenticated users or allows unauthenticated access

A system is affected if AgeVolt Portal version less than 0.1 is installed and the System Setup file upload feature is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.1 or later
Fixed in 0.1
Interim mitigation

Upgrade AgeVolt Portal to version 0.1 or later, which contains the patch for this vulnerability. Implement strict input validation on file upload endpoints to prevent directory traversal attacks.

Recommended fix High confidence

version 0.1

  1. 1. Back up the current AgeVolt Portal installation and any associated databases before proceeding.
  2. 2. Obtain AgeVolt Portal version 0.1 from the official vendor or trusted distribution channel.
  3. 3. Follow the vendor's documented upgrade procedure to install version 0.1.
  4. 4. After installation, verify the installed version is 0.1.
  5. 5. Test the file upload functionality in the System Setup menu to confirm the vulnerability is remediated.
  6. 6. Ensure proper file permissions are configured according to vendor hardening guidelines.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Agevolt Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38484 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data