Analyst readout for executives and security teams
Plain-English summary
CVE-2012-6273 is a reported SQL injection in BigAntSoft BigAnt IM Message Server. A remote attacker could make the server run unintended database commands through a search-user request. The source bundle does not provide affected versions, a score, a patch, or evidence of active exploitation.
Executive priority
Treat this as a targeted legacy-software exposure check. It is potentially serious where the product is deployed, but urgency cannot be scored confidently without version, exposure, and vendor-fix information.
Technical view
The CVE describes SQL injection via an SHU, also called search user, request in BigAntSoft BigAnt IM Message Server. Successful exploitation could allow arbitrary SQL command execution against the application database. Version scope and remediation details are not included in the provided sources.
Likely exposure
Exposure is limited to environments that still run BigAntSoft BigAnt IM Message Server. Risk is higher if the message server or search-user functionality is reachable by untrusted networks. The supplied affected-product metadata is incomplete.
Exploitation context
The sources support remote SQL injection capability, but not active exploitation. The CVE is not marked as CISA KEV in the bundle, and no cited source in the bundle states exploitation in the wild.
Researcher notes
The public bundle is sparse: no CVSS, CWE, affected versions, patch status, or exploitation evidence. Analysis should focus on confirming product presence, reachable attack surface, vendor guidance, and database impact boundaries.
Mitigation direction
- Inventory any BigAntSoft BigAnt IM Message Server deployments.
- Check BigAntSoft and CERT VU#990652 guidance for fixed versions or mitigations.
- Restrict access to the message server to trusted networks where possible.
- Review database and application logs for suspicious search-user activity.
- Retire or isolate unsupported deployments if no vendor fix is available.
Validation and detection
- Confirm whether BigAntSoft BigAnt IM Message Server is installed or exposed.
- Identify installed versions and compare them with vendor or CERT guidance.
- Review firewall, VPN, and access-control paths to the message server.
- Check logs for unusual SHU or search-user requests.
- Verify database permissions follow least privilege for the application account.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2012-6273 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- VU#990652CVE reference · third-party-advisory, x_refsource_CERT-VN
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.