# CVE-2024-47256: Hardcoded credentials in 2N Access Commander

> An attacker with admin access can read a hardcoded AES passphrase to decrypt backup data in 2N Access Commander.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2025
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-c3j7-hfc5-cvhx

## What is CVE-2024-47256?

CVE-2024-47256 is a medium-severity vulnerability in 2N Access Commander, published on 6 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Successful exploitation of this vulnerability could allow an attacker (who needs to have Admin access privileges) to read hardcoded AES passphrase, which may be used for decryption of certain data within backup files of 2N Access Commander version 1.14 and older.

2N has released an updated version 3.3 of 2N Access Commander, where this vulnerability is mitigated. It is recommended that all customers update 2N Access Commander to the latest version.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2024-47256?


## How do I fix CVE-2024-47256?

No fix has been published for CVE-2024-47256 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-47256 being exploited?

There is no known exploitation of CVE-2024-47256 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47256 and fix it if it is affected.

What it is: CVE-2024-47256 is a medium-severity vulnerability in 2N Access Commander, published on 6 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47256 in the wild and no public exploit code.

Affected product: 2N Access Commander. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47256/ (Markdown: https://insights.sbomify.com/CVE-2024-47256/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47256
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47256
- OSV: https://osv.dev/vulnerability/CVE-2024-47256

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47256/
Summaries are generated and may contain mistakes; the official description above is the record.