UNKNOWN CVSS 10.0
Published: 2004-12-31

CVE-2004-1812

broadcom unicenter_tng Security Advisory (CVE-2004-1812)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2004-1812?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2004-1812 impacting broadcom unicenter_tng. Evaluated with CVSS Base Score of 10.0 (UNKNOWN).

Original NVD Description

Source: NIST NVD
Multiple stack-based buffer overflows in Agent Common Services (1) cam.exe and (2) awservices.exe in Unicenter TNG 2.4 allow remote attackers to execute arbitrary code.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required

🎯 Affected Versions Matrix

Affected Product broadcom / unicenter_tng
Affected Versions 2.4
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-2004-1812 impacting broadcom unicenter_tng.

⚡ Nuclei Detection Template (YAML) cve-2004-1812.yaml
id: cve-2004-1812

info:
  name: broadcom unicenter_tng - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: unknown
  description: |
    Automated signature & scanner for CVE-2004-1812 affecting broadcom unicenter_tng.
    Evaluation: Multiple stack-based buffer overflows in Agent Common Services (1) cam.exe and (2) awservices.exe in Unicenter TNG 2.4 allow remote attackers to execu...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2004-1812
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/Au:N/C:C/I:C/A:C
    cvss-score: 10.0
    cve-id: CVE-2004-1812
    cwe-id: NVD-CWE-Other
  tags: cve,cve-2004-1812,broadcom,unicenter_tng,unknown

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

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2004-1812 (broadcom unicenter_tng)...")
    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 broadcom unicenter_tng scope (2.4).")
        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-2004-1812.sh
# Recommended Remediation & Patching Commands for CVE-2004-1812
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install unicenter_tng 2>/dev/null || \
sudo dnf upgrade unicenter_tng 2>/dev/null || \
sudo yum update unicenter_tng

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

# 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.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2004-1812 in broadcom unicenter_tng?

Review vendor-specific security notices and update broadcom unicenter_tng 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-2004-1812?

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-2004-1812?

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

Risk Snapshot
10.0
UNKNOWN SEVERITY
CVE ID CVE-2004-1812
Weakness NVD-CWE-Other
Vendor broadcom
Product unicenter_tng
Published 2004-12-31
Vector AV:N/AC:L/Au:N/C:C/I:C/A:C