# CVE-2005-1677: Security feature bypass in n/a

> Remote attackers can bypass restrictions on COM objects in Groove Virtual Office, potentially compromising security controls.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 25 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5755-cxgh-x355

## What is CVE-2005-1677?

CVE-2005-1677 is a high-severity vulnerability in n/a, published on 25 May 2005. It can be exploited over the network.

### Official description

Unknown vulnerability in Groove Virtual Office before 3.1 build 2338, before 3.1a build 2364, and Groove Workspace before 2.5n build 1871 allows remote attackers to bypass restrictions on COM objects.

## Which versions are affected by CVE-2005-1677?

It affects 2 products.


Products: Groove Groove Workspace, Groove Virtual Office.

## How do I fix CVE-2005-1677?

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

## Is CVE-2005-1677 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1676](https://insights.sbomify.com/CVE-2005-1676/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2005-1675](https://insights.sbomify.com/CVE-2005-1675/): Information disclosure in n/a (medium 4.6)
- [CVE-2005-1678](https://insights.sbomify.com/CVE-2005-1678/): Other in n/a (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1677 and fix it if it is affected.

What it is: CVE-2005-1677 is a high-severity vulnerability in n/a, published on 25 May 2005. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2005-1677 in the wild and no public exploit code.

Affected product: n/a. 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-2005-1677/ (Markdown: https://insights.sbomify.com/CVE-2005-1677/index.md)
```

## Sources

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

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