Vulnerability record · CVE-2012-6274 · published 24 February 2013
CVE-2012-6274: BigAnt IM Message Server unauthenticated file upload allows arbitrary file creation
Bigantsoft · Bigant Im Message Server
BigAntSoft BigAnt IM Message Server does not require authentication for file uploads, letting a remote attacker write arbitrary files into the AntServer\DocData\Public directory. Because the write path is fixed and unauthenticated, any network-reachable attacker can plant files on the server, which matters for integrity and possible follow-on abuse of uploaded content.
Description
BigAntSoft BigAnt IM Message Server does not require authentication for file uploading, which allows remote attackers to create arbitrary files under AntServer\DocData\Public via unspecified vectors.
AV:N/AC:L/Au:N/C:N/I:P/A:N
Automated analysis
high priorityUnauthenticated remote file write with a very high EPSS percentile, though impact is limited to integrity per the CVSS vector and no KEV listing exists.
What it is
BigAntSoft BigAnt IM Message Server does not require authentication for file uploads, letting a remote attacker write arbitrary files into the AntServer\DocData\Public directory. Because the write path is fixed and unauthenticated, any network-reachable attacker can plant files on the server, which matters for integrity and possible follow-on abuse of uploaded content.
Impact
An attacker gains the ability to create arbitrary files on the server under the public document directory without credentials. Depending on what the server does with those files, this can corrupt data or enable further attacks, though the record does not specify code execution.
Attack surface
Reachable over the network (AV:N) with no authentication required (Au:N) and no user interaction indicated. The flaw is in the file upload handling of the IM message server.
Exploitation
Not listed in CISA KEV and no public exploit references are tagged in the record; EPSS is 0.46868 (98.8th percentile), indicating a high predicted likelihood of exploitation activity.
What to do
- Apply the vendor fix or the CERT/CC-recommended remediation for VU#990652 as soon as possible.
- Require authentication and authorization checks on all file upload endpoints.
- Restrict write access to AntServer\DocData\Public and validate uploaded file types and names.
- Place the IM server behind a firewall or VPN so upload services are not exposed to untrusted networks.
- Monitor and alert on unexpected file creation in the public document directory.
Detection
- Monitor AntServer\DocData\Public for new or unexpected files and alert on writes outside normal business patterns.
- Audit server logs for unauthenticated upload requests to the IM message server.
- Baseline the file types and sizes normally uploaded and flag deviations.
- Watch for files with executable or script extensions appearing in the public document directory.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| http://www.kb.cert.org/vuls/id/990652 | US Government Resource |
| http://www.kb.cert.org/vuls/id/990652 | US Government Resource |
Track CVE-2012-6274 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2012-6274), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.