Corporate Nextcloud Security Gaps: Default Settings, Antivirus Failures and Open Source Integration Challenges
Nextcloud in corporate environments demands far more than default open source settings to achieve acceptable security levels, according to a detailed technical review published by K2Tech.
The company’s specialist Roma Masyagutov explains that while LDAP integration, antivirus plugins, audit logging and access policies exist, real-world testing often exposes dangerous gaps. A large infected file can still reach storage even when an antivirus solution is supposedly active.
Architecture and Perimeter Defenses
Corporate Nextcloud runs across load balancers, application servers, a MariaDB Galera cluster for metadata, Redis for sessions, S3 object storage and Elasticsearch for logs, all spread across three availability zones. WAF solutions from vendors such as Wallarm and Qrator plus Anti-DDoS services sit in front of the infrastructure. Additional layers include vulnerability scanning with VULS, infrastructure-level SRK, security groups, IAM and CloudTrail logging.
LDAP and Antivirus Integration Issues
Native LDAP plugins connect reliably to corporate Active Directory, automatically mapping groups and permissions. Antivirus integration, however, proves far more fragile. When the antivirus service becomes unreachable, the Antivirus for files plugin simply uploads the file to S3 without scanning. A later parameter avBlockUnreachable was added, yet it functions only with ClamAV and still requires manual configuration for other engines.
Another critical flaw appears during chunked uploads. Files are transferred in 5–10 MB pieces and reassembled with a MOVE command. Older plugin versions checked only individual PUT requests, leaving the final assembled file unexamined. Administrators must update the plugin and align chunk sizes with the antivirus stream length using commands such as occ config:app:set files max_chunk_size --value="104857600".
Comparing Three Antivirus Engines
Three ICAP-based engines were evaluated on identical hardware: ClamAV, Kaspersky Scan Engine and PT Sandbox.
- ClamAV offers open source signature-based detection but lacks built-in clustering, web panels and monitoring; administrators must build these capabilities themselves.
- Kaspersky Scan Engine provides a web console, native clustering via shared database and integration with SIEM systems, delivering the fastest inline scanning speeds in tests.
- PT Sandbox combines signature detection with behavioral analysis yet proved the most resource-intensive, with load averages reaching 115 during sequential uploads.
Throughput measurements for 30 MB and 100 MB files containing EICAR signatures showed Kaspersky Scan Engine consistently outperforming the others, while PT Sandbox imposed the highest CPU overhead even without behavioral analysis enabled.
The authors conclude that antivirus scanning in a Nextcloud pipeline must be treated as a dedicated service whose failure modes, monitoring, high-availability design and re-scan policies require careful engineering. Frequent Nextcloud releases and plugin updates further necessitate ongoing regression testing on staging environments before production rollout.
Related articles
CrowdSec Confirms Theft of Source Code from Roughly 300 GitHub Repositories via TanStack Supply Chain Attack
French cybersecurity firm CrowdSec has confirmed that attackers stole source code from approximately 300 GitHub repositories, including around 170 private ones. The breach occurred in May 2026 through a compromised TanStack component that exfiltrated an API key with read access to the private codebase. The stolen material included code for the company's SaaS console, AWS procedures, connectors, and automation tools, while the remaining repositories contained already-public open source code. No customer data, passwords, organization details, tokens, or other secrets were included in the leak, and all potentially affected credentials were immediately rotated. CrowdSec stated that the code is tightly integrated with internal systems and has largely changed over the past four months, reducing its usefulness outside the company's environment. The SaaS service code undergoes regular audits, and the company sees no immediate threat from the exposure while the investigation continues.
Dependency Confusion Attacks Let Attackers Hijack Internal Library Names in Corporate Builds
A widespread supply chain risk allows attackers to publish packages with internal company names on public registries such as npm and PyPI, causing build systems to pull malicious versions instead of internal ones. The attack works because package managers treat multiple registries as a single list and select the highest version number, with no inherent priority for internal sources. Researcher Alex Birsan demonstrated the technique in February 2021 by registering names harvested from open repositories and error messages, successfully injecting packages into builds at Microsoft, Apple, PayPal, Shopify, Netflix, Tesla and Uber. The malicious code executes during installation because setup scripts and lifecycle hooks run with the privileges of the build agent, exposing environment variables, tokens and internal network access. Mitigation requires a single internal proxy repository that never mixes public responses for internal package names, scoped namespaces bound to private registries, lock files with content hashes, and disabling install scripts where possible. The technique remains effective against any organization that lists both internal and public registries in its build configuration.
NEOMSA ESB Release Strengthens Supply Chain Security Through SBOM and Dependency Hardening
Neoflex has released a new version of its NEOMSA ESB integration platform with a primary focus on cleaning up the software bill of materials and eliminating critical and high-severity vulnerabilities. The team automated SBOM generation using CycloneDX, ran SCA scans with Grype and OWASP Dependency-Check, and performed SAST and secret scanning across all build pipelines. Instead of blindly updating to the latest versions, engineers applied minimal fixed versions for each advisory while handling complex cases involving transitive dependencies, locked files, and deprecated build tools. The effort reduced the total package count from 5,872 to 1,683 after migrating the frontend build to Vite in Camel Karavan 4.18. Remaining medium and low findings were tracked in DefectDojo with clear remediation timelines. The changes deliver measurable risk reduction for on-premise deployments in critical infrastructure and financial organizations.
CodeScoring Launches CodeScoring.Save Artifact Repository for Secure Enterprise Development
CodeScoring has introduced its own artifact storage solution called CodeScoring.Save, designed to handle packages, libraries, container images, and other software components used in development. The product targets corporate users of any size seeking a predictable and resilient repository that integrates security checks directly into storage and distribution workflows. Built in Go for modern Kubernetes environments, Save supports multiple package formats including Maven, npm, NuGet, PyPI, Go Modules, Docker/OCI, DEB, and RPM while providing proxy access to external repositories. It features role-based access, auditing, independent scaling of compute and storage layers, and native integration with CodeScoring.OSA to surface vulnerability data inside the repository itself. The company positions Save as a standalone local deployment option that can operate independently or alongside its existing OSA Proxy module to block malicious components at the repository level. Future plans include support for AI models as artifacts, starting with storage and distribution for ecosystems such as Hugging Face, along with certification for Russian secure development requirements.