UNKNOWN CVSS 4.3
Published: 2012-06-29

CVE-2012-1118

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

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2012-1118 impacting mantisbt mantisbt. Evaluated with CVSS Base Score of 4.3 (UNKNOWN).

Original NVD Description

Source: NIST NVD
The access_has_bug_level function in core/access_api.php in MantisBT before 1.2.9 does not properly restrict access when the private_bug_view_threshold is set to an array, which allows remote attackers to bypass intended restrictions and perform certain operations on private bug reports.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Integrity
None (I:N)
No system modification impact
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product mantisbt / mantisbt
Affected Versions *
Weakness Enumeration CWE-264

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-2012-1118 impacting mantisbt mantisbt.

⚡ Nuclei Detection Template (YAML) cve-2012-1118.yaml
id: cve-2012-1118

info:
  name: mantisbt mantisbt - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: unknown
  description: |
    Automated signature & scanner for CVE-2012-1118 affecting mantisbt mantisbt.
    Evaluation: The access_has_bug_level function in core/access_api.php in MantisBT before 1.2.9 does not properly restrict access when the private_bug_view_threshol...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2012-1118
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:M/Au:N/C:P/I:N/A:N
    cvss-score: 4.3
    cve-id: CVE-2012-1118
    cwe-id: CWE-264
  tags: cve,cve-2012-1118,mantisbt,mantisbt,unknown

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

import requests
import sys

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

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

# 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-2012-1118 in mantisbt mantisbt?

Review vendor-specific security notices and update mantisbt mantisbt 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-2012-1118?

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-2012-1118?

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

Risk Snapshot
4.3
UNKNOWN SEVERITY
CVE ID CVE-2012-1118
Weakness CWE-264
Vendor mantisbt
Product mantisbt
Published 2012-06-29
Vector AV:N/AC:M/Au:N/C:P/I:N/A:N