# CVE-2024-3735: Smart Office Main.aspx weak password

> Smart Office allows weak passwords, potentially enabling account takeover if users choose simple credentials.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-3fr5-8rrj-9rf2

## What is CVE-2024-3735?

CVE-2024-3735 is a medium-severity vulnerability in Smart Office, published on 13 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Smart Office up to 20240405. It has been classified as problematic. Affected is an unknown function of the file Main.aspx. The manipulation of the argument New Password/Confirm Password with the input 1 leads to weak password requirements. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. VDB-260574 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-521 (Weak Password Requirements)

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


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

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

## Is CVE-2024-3735 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3735 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3735 is a medium-severity vulnerability in Smart Office, published on 13 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3735 exists.

Affected product: Smart Office. 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-3735/ (Markdown: https://insights.sbomify.com/CVE-2024-3735/index.md)
```

## Sources

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

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