dbcve.org
CoslatApplication · Bg Tek

CVE-2024-10035

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-04
Fix available
A fix is available. Upgrade to after 3.1069 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Control of Generation of Code ('Code Injection'), Improper Neutralization of Special Elements used in a Command ('Command Injection'), Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in BG-TEK Informatics Security Technologies CoslatV3 allows Command Injection, Privilege Escalation. This issue affects CoslatV3: through 3.1069. NOTE: The vendor was contacted and it was learned that the product is not supported.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Command injection vulnerability in BG-TEK CoslatV3 allows unauthenticated attackers to inject and execute arbitrary OS commands, potentially achieving full system compromise and privilege escalation. Affects all versions through 3.1069.

MitigationSince the vendor does not support the product and no patch is available, implement compensating controls such as strict network segmentation to isolate the system, deploy WAF rules to detect and block command injection payloads, or decommission and replace the affected system if possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CoslatApplication
Affected:>= 3.0, <= 3.1069

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify BG-TEK CoslatV3 installation
    Locate the CoslatV3 application on your system. Check for the software in your installed programs, application directories, or web server DOCUMENT_ROOT if it runs as a web application.
    Affected if The software is present on the system.
  2. Determine installed version
    Locate the version information for CoslatV3. Check the application's about page, version file, header files, or configuration files for a version number. If running as a web app, check the HTTP headers or error pages returned by the server.
    Affected if The installed version is 3.0 through 3.1069 inclusive.
  3. Verify network exposure
    Determine if the CoslatV3 web interface is accessible from the network. Check firewall rules, network ACLs, and the application's binding address (e.g., 0.0.0.0 vs 127.0.0.1).
    Affected if The application is accessible to unauthenticated network attackers.
  4. Identify accessible input points
    Examine the web application for input fields, API endpoints, or parameters that accept user-supplied data, particularly those that may interact with system commands or file operations.
    Affected if User-controllable input points are reachable without authentication.

You are affected if BG-TEK CoslatV3 version 3.0 through 3.1069 is installed and its web interface is exposed to unauthenticated network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.1069
Interim mitigation

Since the vendor does not support the product and no patch is available, implement compensating controls such as strict network segmentation to isolate the system, deploy WAF rules to detect and block command injection payloads, or decommission and replace the affected system if possible.

Recommended fix Moderate confidence
  1. Immediately isolate the affected CoslatV3 system from the network to prevent lateral movement and remote exploitation
  2. Implement strict network segmentation and place the system behind a firewall with deny-all inbound rules
  3. If the system must remain in production, deploy a Web Application Firewall (WAF) in front of the application to detect and block command injection attempts
  4. Enable comprehensive audit logging for all system access and commands executed by the CoslatV3 application
  5. Implement least-privilege execution policies for the service account running CoslatV3 to limit the impact of any successful command injection
  6. Monitor USOM (www.usom.gov.tr) and relevant Turkish cybersecurity advisories for any additional threat intelligence
  7. Consider migrating to a supported security information and event management (SIEM) or logging solution as CoslatV3 is end-of-life
  8. Document the risk acceptance decision and implement additional compensating controls such as intrusion detection systems (IDS)
Caveat Product is end-of-life and unsupported by vendor - no upgrade path available; consider migration to alternative supported solutions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Coslat Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10035 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data