dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-4679

HIGH · 7.8 CVSS v3.1 Published 2024-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Incorrect Default Permissions vulnerability in Hitachi JP1/Extensible SNMP Agent for Windows, Hitachi JP1/Extensible SNMP Agent on Windows, Hitachi Job Management Partner1/Extensible SNMP Agent on Windows allows File Manipulation.This issue affects JP1/Extensible SNMP Agent for Windows: from 12-00 before 12-00-01, from 11-00 through 11-00-*; JP1/Extensible SNMP Agent: from 10-10 through 10-10-01, from 10-00 through 10-00-02, from 09-00 through 09-00-04; Job Management Partner1/Extensible SNMP Agent: from 10-10 through 10-10-01, from 10-00 through 10-00-02, from 09-00 through 09-00-04.

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

Hitachi JP1/Extensible SNMP Agent for Windows and related products contain incorrect default file permissions that allow local unprivileged users to manipulate files in the installation directory. This vulnerability enables file modification or replacement, potentially leading to privilege escalation or arbitrary code execution.

MitigationApply the vendor-provided patches: upgrade JP1/Extensible SNMP Agent for Windows to 12-00-01 or later; upgrade JP1/Extensible SNMP Agent to 10-10-02, 10-00-03, or 09-00-05 or later. Alternatively, restrict file system permissions on the installation directories to administrative-only access.

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

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Locate JP1/Extensible SNMP Agent installation
    Check for the presence of Hitachi JP1/Extensible SNMP Agent on the system. Look in typical installation directories such as C:\Program Files\Hitachi\JP1 or C:\Program Files (x86)\Hitachi\JP1, or use the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi to find the installation path.
    Affected if The product is not found on the system (not affected).
  2. Identify installed version
    Locate the version information file or check the program properties. In the installation directory, look for a version file, or right-click the main executable (typically snmpagt.exe or similar) and view Properties > Details to find the File Version.
    Affected if Unable to determine version - manual verification required.
  3. Compare version against affected ranges
    For JP1/Extensible SNMP Agent for Windows: version must be 12-00-01 or later to be fixed. For JP1/Extensible SNMP Agent: version must be 10-10-02, 10-00-03, or 09-00-05 or later. If the version is earlier than these, the system is potentially affected.
    Affected if Installed version is earlier than 12-00-01 (for Windows agent) or earlier than 10-10-02/10-00-03/09-00-05 (for other agents).
  4. Examine file permissions on installation directory
    Right-click the JP1 installation folder, select Properties > Security tab. Check the permissions for Users or non-admin groups. Verify if Users or authenticated users have Write, Modify, or Full Control permissions on the installation directory and its subfolders.
    Affected if Non-privileged users (such as standard Users group) have Write, Modify, or Full Control permissions on the installation directory, enabling file manipulation.

A system is affected if JP1/Extensible SNMP Agent is installed with a version earlier than the fixed releases AND non-administrative users have write permissions on the installation directory.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided patches: upgrade JP1/Extensible SNMP Agent for Windows to 12-00-01 or later; upgrade JP1/Extensible SNMP Agent to 10-10-02, 10-00-03, or 09-00-05 or later. Alternatively, restrict file system permissions on the installation directories to administrative-only access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4679 — 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-2024-4679 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