# CVE-2023-0356: Weak cryptography in MODULYS GP

> Attackers can intercept sensitive credentials due to weak encryption on HTTP connections in SOCOMEC MODULYS GP Netvision.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jan 2023
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-g8v2-9qc2-2v9q

## What is CVE-2023-0356?

CVE-2023-0356 is a medium-severity vulnerability in SOCOMEC MODULYS GP , published on 24 Jan 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

SOCOMEC MODULYS GP Netvision versions 7.20 and prior lack strong encryption for credentials on HTTP connections, which could result in threat actors obtaining sensitive information.

Weakness: CWE-261 (Weak Encoding for Password)

## Which versions are affected by CVE-2023-0356?

It affects 1 product.


Products: Socomec Net Vision.

## How do I fix CVE-2023-0356?

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

## Is CVE-2023-0356 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0356 and fix it if it is affected.

What it is: CVE-2023-0356 is a medium-severity vulnerability in SOCOMEC MODULYS GP , published on 24 Jan 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-0356 in the wild and no public exploit code.

Affected product: SOCOMEC MODULYS GP . 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-2023-0356/ (Markdown: https://insights.sbomify.com/CVE-2023-0356/index.md)
```

## Sources

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

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