UNKNOWN CVSS 2.1
Published: 2005-10-26

CVE-2005-3311

bmc software_control-m_agent Security Advisory (CVE-2005-3311)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2005-3311?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2005-3311 impacting bmc software_control-m_agent. Evaluated with CVSS Base Score of 2.1 (UNKNOWN).

Original NVD Description

Source: NIST NVD
BMC Software Control-M 6.1.03 for Solaris, and possibly other platforms, allows local users to overwrite arbitrary files via a symlink attack on temporary files.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Local (AV:L)
Requires local system execution permissions
Attack Complexity
Low (AC:L)
No specialized conditions required
Confidentiality
None (C:N)
No data confidentiality impact
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product bmc / software_control-m_agent
Affected Versions 6.1.03
Weakness Enumeration NVD-CWE-Other

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2005-3311 impacting bmc software_control-m_agent.

⚡ Nuclei Detection Template (YAML) cve-2005-3311.yaml
id: cve-2005-3311

info:
  name: bmc software_control-m_agent - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: unknown
  description: |
    Automated signature & scanner for CVE-2005-3311 affecting bmc software_control-m_agent.
    Evaluation: BMC Software Control-M 6.1.03 for Solaris, and possibly other platforms, allows local users to overwrite arbitrary files via a symlink attack on tempo...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2005-3311
  classification:
    cvss-metrics: CVSS:3.1/AV:L/AC:L/Au:N/C:N/I:P/A:N
    cvss-score: 2.1
    cve-id: CVE-2005-3311
    cwe-id: NVD-CWE-Other
  tags: cve,cve-2005-3311,bmc,software_control-m_agent,unknown

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "software_control-m_agent"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2005-3311.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2005-3311
# Target: bmc software_control-m_agent | CVSS: 2.1 (UNKNOWN)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2005-3311 (bmc software_control-m_agent)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against bmc software_control-m_agent scope (6.1.03).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2005-3311.sh
# Recommended Remediation & Patching Commands for CVE-2005-3311
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install software_control-m_agent 2>/dev/null || \
sudo dnf upgrade software_control-m_agent 2>/dev/null || \
sudo yum update software_control-m_agent

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i software_control-m_agent 2>/dev/null || rpm -qa | grep -i software_control-m_agent

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2005-3311 in bmc software_control-m_agent?

Review vendor-specific security notices and update bmc software_control-m_agent packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2005-3311?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2005-3311?

CVE-2005-3311 is classified with a CVSS 3.1 Base Score of 2.1 (UNKNOWN). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
2.1
UNKNOWN SEVERITY
CVE ID CVE-2005-3311
Weakness NVD-CWE-Other
Vendor bmc
Product software_control-m_agent
Published 2005-10-26
Vector AV:L/AC:L/Au:N/C:N/I:P/A:N