Keenetic Product Security Advisory

Issuer and the Scope: The issuing entity of this Policy is Keenetic GmbH, Berliner Straße 300b, 63067 Offenbach am Main, Germany. This  Policy is established as the standard governing Policy for all Keenetic entities worldwide.

As a security researcher or vulnerability reporter, your work is vital to strengthening the safety of digital products and infrastructures. We created this Coordinated Vulnerability Disclosure (“CVD”) policy to ensure that your findings are treated with respect, handled responsibly, and acted upon quickly. It sets out how Keenetic (referred to as “Keenetic GmbH”, “we”, “us”) will respond to your reports, the assurances you can expect, and the steps that lead to a successful disclosure process.

Furthermore, we want to make sure your contributions are valued. We encourage you to participate in the Keenetic bug bounty program, that offers financial rewards to express our appreciation and encourage continued collaboration.

By participating in this process, you are not only helping to protect users and organizations but also joining a community where your expertise is recognized and rewarded. Together, we can make Keenetic products safer, build trust, and create a stronger digital ecosystem. 

Ⅰ.    Scope of the CVD policy – What do we consider to be a valid vulnerability

A valid vulnerability, in the context of this policy, is understood as a weakness, flaw, or security issue that directly affects one of the Keenetic’s products or infrastructure that can be exploited. 

To qualify as a valid report, the information disclosed should not already be publicly known, thereby ensuring that the report contributes new and actionable knowledge to the security process.  Furthermore, reports that are solely generated by automated tools or scans without sufficient supporting documentation are not considered adequate, as they lack the necessary evidence to enable meaningful analysis and remediation of a valid vulnerability.  Each report should ideally contain supporting details. This helps us focus on real issues and respond faster. 

Ⅱ.    How to report a vulnerability

When you discover a valid vulnerability, file a report by using the following channels. 

Email: You can email us at security@keenetic.com to ensure proper coordination and tracking.

Web Form: We provide a secure web submission form on our vulnerability disclosure page: https://keenetic.com/security/anonymous-reporting-form. This form supports anonymous reporting. You are not required to provide any personal information to submit a report; however, keep in mind that if you report anonymously we will not be able to ask you follow-up questions, which may limit our ability to investigate the issue. The web form is available in English, and it guides you to include the key details we need.

Security.txt: We maintain a keenetic.com/security.txt on our website which lists our vulnerability disclosure contacts and preferences. Reporters can refer to this file for up-to-date information on how to reach us.

When submitting a report, please include as much technical detail as possible. This helps us triage and fix the issue faster. We suggest providing:

• A description of the vulnerability and its potential impact. What could an attacker achieve? Which confidentiality/integrity/availability aspects are at risk? What could be the affected system in Keenetic’s IT infrastructure (e.g. Keenetic Corporate Systems, Operating System, App, Remote Monitoring and Management, Cloud and Keenetic Account)?

• Specific product names, versions, and configurations affected. (For websites or services, include URLs or IPs; for hardware or software, include model or version numbers.)

• Steps to reproduce the issue – e.g. what commands, inputs, or actions trigger the vulnerability. Screenshots or proof-of-concept (PoC) code are very helpful.

• If known, any suggested remediation or references to fixes (optional but appreciated).

• Your contact information (name or alias, and a secure method to reach you) if you desire a response. You may report anonymously, but then we cannot communicate with you for clarification or to give status updates.

Voluntary Information: The reporter may voluntarily provide contact information for coordination but is not required to submit personally identifiable information. You may use our web site based anonymous reporting form.

Ⅲ.    What we expect from you – Code of Conduct

We only reward reporters and acknowledge their achievements under this CVE policy which adhere to high standards of integrity and responsible behavior when discovering and reporting vulnerabilities. Therefore, we do not tolerate the following behavior:

• Good Faith Testing: Reporters shall only conduct testing that is non-disruptive and necessary to confirm the vulnerability's existence (Proof of Concept). They must not intentionally compromise user data, disrupt services, or damage systems.

• No Exploitation Beyond Testing: Active exploitation of a vulnerability beyond initial proof-of-concept testing is strictly prohibited. In particular, do not abuse the vulnerability to compromise data, alter configurations, pivot to other systems, or persistently access our systems. Triggering the issue to prove its existence is sufficient – do not, for example, download more data than necessary to demonstrate the flaw. If you encounter sensitive information (e.g. personal data of users, proprietary material), cease testing and report it immediately to us, and do not disclose or retain that information. 

• No social engineering or physical attacks: Do not use social engineering techniques (phishing emails, phone pretexting, etc.) against our employees or systems, and do not perform any physical security tests (such as attempting to enter our offices or data centers). This policy is limited to technical vulnerabilities in our products and infrastructure, and excludes social and physical attack vectors. 

• No denial-of-service or “brute force attacks”: Refrain from performing DoS/DDoS attacks or any testing that could degrade our services’ availability for users as well as “brute force” attacks. We want to avoid any disruption to our customers.

• No third-party or public attacks: Do not target vulnerabilities in third-party services or products that we use (instead, please notify those vendors directly). Similarly, do not test systems that are not owned or operated by us. If you inadvertently access data or systems of other parties during your research, notify us and cease further action. Do not compromise or manipulate data of any third party during your research. 

• Confidentiality and use of information: Reporters shall keep vulnerability details confidential and shall not publicly disclose, sell, or otherwise distribute exploit code or technical details that would enable exploitation until Keenetic has provided a public advisory or otherwise authorized disclosure. This does not restrict the reporter from notifying competent authorities, national CSIRT, or law enforcement where required by law or where immediate disclosure is necessary to prevent imminent harm.

• Remediation Period: Keenetic shall be afforded a reasonable, remediation period based on severity to investigate, remediate, and distribute security updates. If Keenetic fails to remediate or provide a credible mitigation within a reasonable period, the reporter may notify a national CSIRT or competent authority.

If a reporter inadvertently violates part of this code of conduct, we commit to still handle any discovered vulnerability in good faith to the best of our ability; however, such a reporter might not receive any rewards.

Ⅳ.    Our commitment to you when a vulnerability is reported

All incoming reports are treated to the best extent possible. Therefore, at least one valid contact option should be provided by you when reporting a vulnerability. Of course, you may report a vulnerability anonymously. 

1.   Response

After you submit a vulnerability report to us, we will let you know we received your report. This will be a personal reply from our security team. If we need clarification or additional information, we’ll ask as soon as possible. Be aware, for anonymous submissions, we obviously cannot respond, but we will proceed to investigate. For the transmission of confidential information, we need you to provide at least your email to be able to use our PGP-encryption key available at https://keenetic.com/security.txt

After further analysis of the report, we provide you with feedback as to whether we confirm or reject the reported vulnerability, meaningful queries to understand the reported vulnerability or an explanation why the investigation of the reported vulnerability is taking longer as expected.

2.   Confidential communication

We ensure to the extent permitted by law that each incoming vulnerability report is treated confidential and your personal data will not be disclosed to third parties without your explicit consent.

Information required for the public disclosure of the validated and verified vulnerability is publicly disclosed to the extent we are obliged by law. 

3.   Anonymous reporting (optional)

You may use our web site based anonymous reporting form.

As we respect your wish to remain anonymous, please be aware that anonymous reports can only be processed to a limited extent or possibly not at all, due to the missing option to request technical or content-related queries, especially in the case of complex issues. 

4.   Respectful and open communication

All communication will remain professional and we will treat you with respect. We expect the same courtesy in return – we have zero tolerance for any discrimination, harassment or disrespect in communications from either side.

Our security team may reach out with questions to better understand the issue or request reproducible technical artifacts and instructions so the vulnerability can be reproduced and fixed. We encourage you to ask for updates at any time; we consider follow-up inquiries welcome and a sign of your interest, not an annoyance. 

Ⅴ.    Coordinating and completing the disclosure

Validated and verified vulnerabilities are publicly disclosed by Keenetic. The public notification includes:

• A description of the vulnerability.

• Information allowing users to identify affected products/versions.

• The impact and severity.

• Clear instructions on how to apply corrective measures or a patch.

The coordinated vulnerability disclosure process is considered to be complete, if the vulnerability has been mitigated or fixed by appropriate measures and has been publicly disclosed indications of the vulnerability report are unfounded and, therefore, the report can only be processed to a limited extend or not at all.

We consider a CVD process completed when one of the following occurs: 

• a fix or mitigation has been deployed and a public advisory released; or 

• the reported issue was determined not to be a vulnerability (false positive or out of scope) and this was communicated to the reporter; or 

• we are unable to reproduce or need more info and the reporter is unresponsive for an extended period (generally 30 days), in which case we close the case pending new information. 

We communicate the end of the CVD process to the reporter, unless the vulnerability was reported anonymously.

Ⅵ.    Rewards

We deeply appreciate the efforts of reporters and others who privately report vulnerabilities to us. As a token of thanks, we operate a Bug Bounty Program. External security researchers who responsibly report vulnerabilities in accordance with this policy may be eligible for a financial reward as a token of appreciation. The amount of any reward is determined individually based on the severity of the reported vulnerability as described in our Bug Bounty Terms & Conditions.

Ⅶ.    Legal Safe Harbor

By adhering to this CVD policy, Keenetic acknowledges that the reporter is acting in "good faith" research, and will not pursue criminal charges against the reporter in relation to the research activities.

Keenetic (“Keenetic”, “we”, “us”) operates a Bug Bounty Program (“Program”). The Program is governed by these Bug Bounty Terms & Conditions and by the Coordinated Vulnerability Disclosure Policy (“CVD‑Policy”). Collectively, these documents constitute the binding legal terms of the Program (the “Terms”).

1.    Program Overview

(1)   The Program’s goal is to improve our products’ security and protect user data by leveraging outside expertise, in line with our Terms. By submitting a vulnerability report or otherwise participating, you agree to the Terms.

(2)   A valid vulnerability, in the context of the Terms, is understood as a weakness, flaw, or security issue that directly affects one of Keenetic's products infrastructure that can be exploited. The amount of any reward is determined individually based on the severity of the reported vulnerability.

(3)   The decisions made by Keenetic regarding Bug Bounties are final and binding. Keenetic may change or cancel this Program at any time, for any reason.

2.    Safe Harbour

(1)   We consider activities conducted in compliance with our Terms to be authorized, this means we will not initiate legal action (civil or criminal) against you for your good-faith efforts under the Program.

(2)   Notably, this assurance applies only if you abide by the Terms of the Program – we cannot immunize you from legal consequences initiated by third parties or authorities for actions beyond our scope. You are expected to always comply with applicable laws and refrain from any actions that go beyond what is permitted here. If in doubt about whether an action is allowed, please stop and ask us first (see contact information under “Procedure for Reporting a Vulnerability and Code of Conduct” of Keenetic Coordinated Vulnerability Disclosure Policy.

3.    Scope of the Program

(1)   The Program covers the following products, services, and websites of our organization (“in-scope systems”):

• Web Applications: e.g., our official website and subdomains, customer portals, and online services.
• Mobile/Desktop Applications: The latest versions of our apps (Android, iOS, Windows) distributed via official app stores.
• API & Infrastructure: Publicly documented APIs and backend services we own.
• Hardware/IoT Devices: Any hardware products with their firmware.

(2)   Only vulnerabilities that directly affect these in-scope systems are eligible for rewards. If in doubt whether a system is in-scope, please inquire before testing. We may update the scope from time to time (e.g., adding new targets or temporarily suspending some systems) – such changes will be noted on our Program webpage.

(3)   For avoidance of doubt, the following systems are out of scope, testing them is not authorized (“out-of-scope systems”):

• Third-Party Services or Infrastructure: Vulnerabilities in third-party platforms we use (cloud providers, SaaS tools, etc.) should be reported to those vendors, not to us. Attacks or scans against our vendors or partners are not allowed.
• Assets Not Owned by Us: Any website, application, or system not expressly listed as in-scope (including domains that don’t belong to our company).
• Denial of Service: Any attacks that disrupt service (DoS/DDoS) or brute-force large numbers of requests or login attempts.
• Social Engineering & Physical Attacks: Manipulating our employees or users (via phishing, vishing, etc.), or attempting to gain physical access to offices, are strictly prohibited. The Program is limited to technical vulnerabilities.
• Privacy Violations: Accessing, copying, or modifying data that is not your own. For example, extracting other users’ personal information or proprietary data is out-of-scope even if a vulnerability makes it theoretically possible. If during testing you encounter someone else’s data, stop immediately and report the issue; do not continue exploring that data.

4.    Program Eligibility

(1)   This Program is intended for external security researchers. To participate and receive any bounty, you must meet all of the following eligibility criteria

       a.   Minimum Age
You must be at least 18 years old. If you are 14 or older but under 18 (or under the age of majority in your country), you must have permission from your parent or legal guardian to participate. In any case, no participants under 14 years of age are allowed.

       b.   Individual or Organization Permission
You can participate in an individual capacity or on behalf of your employer. If you are reporting in the course of your employment or using your employer’s resources, ensure your employer permits participation in bug bounty programs. It is your responsibility to review your employment agreements or policies.

       c.   No Current or Recent Employees/Contractors
Employees of Keenetic or its subsidiaries are not eligible. This includes anyone who has left our employment within the last 6 months, as well as anyone currently working for us as a contractor, consultant, or intern with access to our internal systems. Immediate family members (spouse, parent, child, sibling) of our employees are also not eligible. This ensures fairness and avoids conflicts of interest.

       d.   Public Sector
If you are a public sector employee (e.g., government, law enforcement, military, or education sector), you may only participate in your personal capacity and not as part of your official duties. It is your responsibility to ensure that accepting a bounty from us does not violate any laws or ethics rules that apply to you.

       e.   Multiple Reports & Duplicates
If the same vulnerability is reported by multiple researchers, only the first report we receive will be eligible for a Bug Bounty, provided our Terms are met. If a later report contains new information that we were not aware of, we may, at our discretion, award a partial bounty to the later reporter. Please note we might already be in the process of fixing an issue when you report it; if so, we will inform you, and such a case may not qualify for a reward, if we deem it a known issue.

(2)   We reserve the right to disqualify any Participant who does not meet these criteria or who is found to violate the intent of these rules. Bug Bounties will not be paid to anyone who is on a sanctions list or whom it would be legally impermissible for us to compensate. If you have questions about eligibility or need clarification, please contact us.

5.    Procedure for Reporting a Vulnerability and Code of Conduct 

(1)   As laid down comprehensively in the CVD-Policy, Keenetic provides multiple secure channels for reporting valid vulnerabilities, including 

• email - security@keenetic.com, 
• a web submission form at https://keenetic.com/security/anonymous-reporting-form, and 
• a security.txt file hosted on our website.

(2)   Reports should contain comprehensive technical details such as a description of the vulnerability, its potential impact, affected systems, product versions, and steps to reproduce, supplemented by proof-of-concept material where possible.

(3)   Anonymous reporting is permitted; however, it may limit follow-up communication. All reporters are expected to adhere to our Code of Conduct stated in the CVD-Policy, which prohibits e.g., disruptive testing, exploitation beyond proof-of-concept, social engineering, physical attacks, denial-of-service, brute force attempts, and targeting third-party systems.

6.    Rewards

(1)   The Program offers Bug Bounties for eligible, validated vulnerability reports. Our goal is to acknowledge and reward security researchers fairly based on the severity and impact of their findings, while being transparent about how rewards are determined.

(2)   We classify reported vulnerabilities based on their impact and exploitability into the following categories: low, medium, high, and critical. For each category, we have typical reward ranges (in US-Dollar). A typical reward structure may include:

(3)   The actual reward amount for any individual case is determined at the sole discretion of Keenetic after our security team has validated the reported vulnerability and assessed its severity. We consider factors such as the classification and sensitivity as well as amount of affected systems/data, ease of exploitation, and overall risk to our users and organization. 

(4)   No reward will be paid in the following cases:
a.   Lack of Secure/HTTPOnly flags on non-sensitive Cookies;
b.   Duplicate reports of security issues, including security issues that have already been identified internally;
c.   Automated scanning attacks;
d.   Distributed Denial of Service attacks and Denial of Service attacks;
e.   UI, UX bugs, and spelling mistakes, Usability issues;
f.   Violations of licenses or other restrictions applicable to any vendor's product;
g.  Vulnerabilities that are a result of malware;
h.   Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end-user interactions to be exploited;
i.   Vulnerabilities considered to be below a P1 impact;
j.   Discovery of any in-use service whose version contains known vulnerabilities (such as a specific version of Linux Kernel, or OpenSSL) without a demonstration of intrusion, information retrieval, or service disruption using that vulnerability;
k.   Leveraging the findings of one vulnerability to create further exploits to then test normally inaccessible functionality, e.g. using leaked personal data, if there is no evidence that a vulnerability can be leveraged to a greater degree;
l.   Vulnerabilities in third-party software and services.

(4)   If a Participant violates any provision of the Terms, Keenetic may reduce, withhold, or require the return of all or part of any reward paid or payable in respect of the relevant vulnerability. The amount of any reduction shall be proportionate to the severity of the violation and may take into account factors including the nature of the violation, the degree of culpability and any actual or potential harm caused.

7.    Payments

(1)   To receive payment, you will need to provide us with necessary details (such as payment method, tax information if required). Bounties will typically be paid in US-Dollar ($) or, if we specify, in another currency like EUR – we will clarify this during the award process. We can often accommodate a preferred payment currency at the exchange rate at time of payment.

(2)   Please note that Bug Bounties are generally considered taxable income. You are solely responsible for paying any taxes due in your jurisdiction for the reward. We may ask you to fill out certain tax forms (especially if you are in a different country) before payment. If you are unable or unwilling to complete required paperwork, it could delay or forfeit the payment.

8.    Copyright

(1)   You retain any intellectual property rights in respect of your submission. However, by submitting a vulnerability report to us, you grant us a non-exclusive, perpetual, irrevocable, worldwide, royalty-free license to use, modify, test, create derivative works from, share, and publish the information in your report for the purpose of addressing the vulnerability and improving security. 

(2)   For example, we can use the submitted proof-of-concept code to reproduce the issue, we can disclose details to a third-party vendor if needed (to coordinate a fix in a component), and we can include relevant details in our public advisories. You also agree that any materials you submit are either your original work or you have the legal right to provide them.

9.    Restrictions on Disclosure

(1)   We will investigate the vulnerability that you have reported and will aim to resolve it as quickly as possible. If you wish to publish details of your findings, please contact us first for approval. For 30 days after the vulnerability is fixed, we require that you withhold detailed proof-of-concept exploit code and any other information that could facilitate attacks on our digital products. Keenetic will notify you when the vulnerability in your submission has been fixed.

(2)   Any breach of this section may obligate you to repay bounties awarded for the vulnerability and may result in your exclusion from future participation in the program.

10.   Liability

(1)   Our liability for breaches of the Terms and for tort shall be limited to intent and gross negligence.

(2)   The limitation of liability referred to in paragraph 1 shall not apply to

       a.   injury to life, body and health of the Participant or

       b.   claims of the Participant for breach of cardinal obligations, i.e. obligations arising from the nature of the Terms and the breach of which endangers the achievement of the purpose of the Program. In this case, however, our liability shall be limited to compensation for the foreseeable, typically occurring damage.

In these cases, we shall be liable for any degree of fault.

(3)   Furthermore, the limitation of liability from paragraph 1 shall not apply if a defect was fraudulently concealed.

(4)   Insofar as liability for damages against us is excluded, this shall also apply with regard to the personal liability for damages of our employees, representatives and vicarious agents.

11.   Miscellaneous

(1)   Should any provision of the Terms be or become invalid, the validity of the remaining provisions shall remain unaffected. In place of the invalid provision, a provision shall be deemed to have been agreed which comes closest to the economic purpose of the invalid provision.

(2)   The Terms shall be governed by and construed in accordance with the laws of the Federal Republic of Germany. The statutory provisions restricting the choice of law and the applicability of mandatory provisions, in particular those of the country in which the Participant as a consumer has the habitual residence, remain unaffected.

(3)   If the Participant is a merchant, a legal entity under public law, or a special fund under public law, the place of jurisdiction for all disputes arising from the Terms is Frankfurt am Main, Germany.

ID de aviso: KEN-PSA-2025-WP01
Gravedad: Alta
CWE: CWE-521 (Requisitos de contraseña débil)
Estado: Resuelto en KeeneticOS 4.3 y versiones posteriores

Resumen

Antes de KeeneticOS 4.3, los usuarios podían establecer contraseñas de administrador débiles y aun así abrir la interfaz web del router a Internet, lo que suponía un alto riesgo de vulneración. Investigaciones internas recientes han revelado que esta vulnerabilidad está siendo explotada por escáneres de contraseñas automatizados en dispositivos con las contraseñas débiles más comunes. La última versión de KeeneticOS 4.3 exige contraseñas más seguras y bloquea el acceso web público si se establece una contraseña comprometida conocida.

Hemos identificado que un número significativo de usuarios sigue utilizando contraseñas débiles o fáciles de adivinar. Esto crea riesgos de seguridad sustanciales, como el acceso no autorizado, las violaciones de datos y las posibles interrupciones del servicio. Proteger los datos del usuario es nuestra máxima prioridad, y abordar estas vulnerabilidades es esencial.

Para reforzar la seguridad general y garantizar la protección continua de los datos de los usuarios, se implementará una actualización de software obligatoria para los dispositivos que ejecuten versiones de KeeneticOS anteriores a la 4.3, de conformidad con el artículo 6 del Contrato de licencia del usuario final y en consonancia con la Ley de Ciberresiliencia de la UE (CRA). Esta actualización incluye medidas de seguridad mejoradas, herramientas para la creación de contraseñas más seguras y correcciones de errores críticos que mejoran la estabilidad del sistema y protegen las cuentas de los usuarios.

Lamentamos sinceramente cualquier inconveniente que esta actualización pueda ocasionar. Para minimizar las interrupciones, procuramos implementarla fuera del horario laboral estándar. Si tiene alguna pregunta o necesita ayuda, póngase en contacto con nuestro equipo de soporte.

Productos/Configuraciones afectados

Productos: Routers de Keenetic que ejecutan versiones de KeeneticOS anteriores a la 4.3.

Requisito de configuración: La interfaz web del router debe estar expuesta a Internet y el acceso web remoto debe estar habilitado.

Detalles de la vulnerabilidad

Problema: Se aceptan contraseñas administrativas débiles mientras se puede acceder a la interfaz web desde Internet.

Impacto: Toma de control administrativo total del dispositivo, lo que permite cambios en la configuración, intercepción/redirección del tráfico, habilitación de servicios adicionales y una posible penetración adicional en la red interna.

Vector: Remoto (Internet); no se requiere autenticación previa ni interacción del usuario.

Factores contribuyentes: Exposición de la interfaz de administrador a Internet y credenciales débiles y fáciles de adivinar.

Gravedad (CVSS v3.1 — estimación del analista)

8.8 (Alta) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Justificación: Ruta remota no autenticada para el control de administrador cuando se permiten contraseñas débiles; el impacto en la disponibilidad es secundario a la confidencialidad/integridad.

Solución y fortalecimiento

Controles de la plataforma: El dispositivo comprueba automáticamente si la contraseña administrativa está en la lista de las contraseñas débiles más utilizadas. En este caso, bloquea el acceso remoto a la interfaz web y la ejecución de software personalizado, y la contraseña solo se puede cambiar desde la red de área local. Al introducir una nueva contraseña, el dispositivo impone la seguridad de la contraseña de acuerdo con las recomendaciones de NIST SP 800-63B.

Actualización: Actualice todos los dispositivos que ejecutan versiones anteriores a la 4.3 a KeeneticOS 4.3 o posterior. Utilice el último sistema operativo disponible para su modelo.

Credenciales de administrador: Utilice contraseñas largas y únicas. Recomendamos al menos 15 caracteres o una frase de contraseña generada.

Limitar la exposición: Si el acceso web remoto no es estrictamente necesario, deshabilítelo. Utilice reglas de cortafuegos para permitir el acceso a la interfaz web del dispositivo solo desde direcciones IP específicas.

Supervisar ataques: Esté atento a los inicios de sesión fallidos o bloqueos repetidos, ya que podrían ser una indicación de un ataque de fuerza bruta.

ID de aviso: KEN-PSA-2025-WA01
Gravedad: Media
CVE: CVE-2025-56007, CVE-2025-56008, CVE-2025-56009
Estado: Resuelto en KeeneticOS 4.3 y versiones posteriores

Keenetic ha recibido y verificado informes de tres vulnerabilidades de seguridad graves que afectan a todas las versiones de KeeneticOS anteriores a la 4.3. Un investigador de seguridad independiente reveló responsablemente estas vulnerabilidades, que desde entonces han sido corregidas en la última versión estable.

Las vulnerabilidades se identifican como CVE-2025-56007, CVE-2025-56008, CVE-2025-56009.

CVE-2025-56007 — Inyección CRLF en el punto final de la API /auth:
Una vulnerabilidad de inyección CRLF en el punto final de la API /auth podría permitir a atacantes remotos manipular las cabeceras HTTP e inyectar comandos no autorizados. Los atacantes podrían añadir nuevos usuarios administrativos y hacerse con el control del dispositivo engañando a una víctima para que abra una página especialmente diseñada.

CVE-2025-56008 — Cross-Site Scripting (XSS) en la página «Wireless ISP»:
Los atacantes podrían explotar una vulnerabilidad XSS en la página de configuración de «Wireless ISP» transmitiendo un SSID especialmente diseñado que contenga un script malicioso. Cuando el usuario busca redes disponibles utilizando la interfaz web, el script se ejecuta en el contexto de la sesión del administrador, lo que permite al atacante hacerse con el control del dispositivo.

CVE-2025-56009 — Cross-Site Request Forgery (CSRF) en el punto final de la API /rci:
Una vulnerabilidad CSRF en el punto final de la API /rci podría permitir a los atacantes realizar acciones no autorizadas en nombre de un usuario autenticado. Atrayendo a la víctima para que visite una página maliciosa, los atacantes podrían añadir silenciosamente usuarios con todos los permisos y comprometer el dispositivo.

Dispositivos potencialmente afectados:
Todos los modelos de Keenetic con el índice «KN», lanzados a partir de 2017.

Gravedad:
La gravedad se considera media, ya que el usuario debe haber iniciado sesión en la interfaz web del router durante el ataque. Un ataque a la página «Wireless ISP» también requiere que el atacante esté cerca del dispositivo.

Versiones de firmware afectadas:
Todas las versiones de KeeneticOS hasta la 4.2.

Solución:
Se recomienda encarecidamente a todos los usuarios que actualicen sus dispositivos de Keenetic a la última versión estable del firmware, KeeneticOS 4.3, que incluye parches para estas vulnerabilidades. Las actualizaciones del firmware se pueden realizar a través de la interfaz web del dispositivo o de la aplicación móvil de Keenetic.

Agradecimientos:
Agradecemos al investigador independiente su revelación responsable y su contribución a la mejora de la seguridad de los productos Keenetic.

ID de aviso: KEN-PSA-2025-WD01
Gravedad: Media
CVE: CVE-2025-20674, CVE-2025-20685, CVE-2025-20686
Estado: Resuelto en KeeneticOS 4.3.2 y versiones posteriores

Keenetic está al tanto de una vulnerabilidad de «inyección arbitraria de paquetes» en el controlador del AP wifi, notificada por el fabricante del chipset, Mediatek, Inc. Existe una forma posible de inyectar un paquete arbitrario debido a la falta de una comprobación de permisos. Esto podría conducir a una escalada remota de privilegios sin necesidad de privilegios de ejecución adicionales. No se necesita la interacción del usuario para su explotación.

El fabricante del chipset también informó de vulnerabilidades adicionales, como una posible escritura fuera de los límites debido a una comprobación incorrecta de los mismos. Esto podría conducir a la ejecución remota de código sin necesidad de privilegios de ejecución adicionales.

Las vulnerabilidades se identifican como CVE-2025-20674, CVE-2025-20685, CVE-2025-20686.

Dispositivos potencialmente afectados:
Todos los modelos Keenetic con el índice «KN», lanzados a partir de 2017, se basan en chipsets wifi producidos por Mediatek: MT7628, MT7603, MT7612, MT7613, MT7915, MT7916.

Versiones de firmware afectadas:
Todas las versiones de KeeneticOS hasta la 4.3.1 inclusive

Gravedad:
La gravedad se considera media, ya que el atacante debe estar muy cerca físicamente del dispositivo objetivo.

Solución:
KeeneticOS 4.3.2 incluye las correcciones necesarias para solucionar estas vulnerabilidades. Esta actualización se aplica a todos los modelos de Keenetic afectados. Recomendamos encarecidamente a los usuarios que actualicen sus dispositivos a la última versión de KeeneticOS disponible en línea. Keenetic ya ha comenzado a desplegar actualizaciones automáticas en los dispositivos que tienen activada la opción de actualización automática.

ID de aviso: KEN-PSA-2025-CS01
Gravedad: Media
Estado: Resuelto

A la luz de la información recién descubierta, Keenetic Limited informa a los usuarios de la Aplicación móvil de Keenetic que se registraron antes del 16 de marzo de 2023, de que parte de los datos de su aplicación móvil pueden haber sido comprometidos debido a un acceso no autorizado a la base de datos.

En la mañana del 15 de marzo de 2023, un investigador de seguridad informática independiente nos informó sobre la posibilidad de un acceso no autorizado a la base de datos de la Aplicación móvil de Keenetic. Tras verificar la naturaleza y la credibilidad del riesgo, resolvimos inmediatamente el problema en la tarde del 15 de marzo de 2023. El investigador de seguridad informática nos aseguró que no había compartido ningún dato con nadie y que lo había destruido. Desde entonces, no hemos tenido indicios de que la base de datos estuviera comprometida o de que algún usuario se viera afectado hasta finales de febrero de 2025.

El 28 de febrero de 2025, supimos que parte de la información de la base de datos había sido revelada a un medio de comunicación independiente. Por lo tanto, hemos determinado que ya no podemos garantizar que los datos fueran destruidos correctamente, y que parte de la información puede estar ahora fuera de nuestro control.

Sin embargo, debido a la naturaleza de los datos que podrían estar potencialmente expuestos, estimamos que el riesgo de actividad fraudulenta es bajo.

Un número limitado de campos de la base de datos eran accesibles: ID de Keycloak, correos electrónicos (inicios de sesión) y nombres de cuentas Keenetic, configuraciones regionales; configuraciones de cuentas de usuario del dispositivo, incluyendo hashes de contraseñas MD5 y NT; nombres KeenDNS personalizados; configuraciones de la interfaz de red, incluyendo SSIDs de wifi y claves precompartidas; configuración del canal wifi, ID y claves de roaming; políticas de IP y configuración de la modelación del tráfico; direcciones de pares remotos, inicios de sesión y contraseñas de clientes VPN, direcciones IP asignadas; nombres y direcciones MAC de los hosts registrados; configuraciones IPsec de sitio a sitio; configuraciones del servidor IP virtual de IPsec; configuración del grupo de DHCP; configuración de NTP; listas de acceso de IP y MAC.

Según nuestro conocimiento, ningún otro dato ha sido accesible. En particular, los datos de RMM, los datos de la cuenta Keenetic, las claves privadas y las configuraciones de los túneles VPN de Wireguard, y los datos de OpenVPN eran inaccesibles.

Keenetic no recopila, almacena ni analiza datos sobre detalles de tarjetas de pago o credenciales relacionadas, datos de transacciones, detalles bancarios o contraseñas bancarias. Por lo tanto, dichos datos no se ven afectados.

Recomendamos a estos usuarios de la aplicación móvil de Keenetic que cambien las siguientes contraseñas y claves previamente compartidas:

- Contraseñas de la cuenta de usuario del dispositivo de Keenetic (enlace a las instrucciones);

- Contraseñas de wifi (enlace a las instrucciones);

- Contraseñas/claves precompartidas del cliente VPN para: PPTP/L2TP (enlace a las instrucciones), L2TP/IPSec (enlace a las instrucciones), IPSec de sitio a sitio (enlace a las instrucciones), SSTP (enlace a las instrucciones).

Creemos firmemente que el acceso no autorizado se produjo sin ninguna intención fraudulenta o maliciosa, y que la información de la base de datos no está a disposición del público, no obstante, se envió la notificación correspondiente a la autoridad de protección de datos pertinente.

Pedimos disculpas por cualquier inconveniente y confirmamos que se han tomado todas las medidas necesarias para evitar una situación similar en el futuro.

Establecemos la seguridad como nuestra máxima prioridad para ofrecer un entorno protegido y controlable que salvaguarde las redes y los datos de nuestros usuarios. Trabajamos constantemente para mejorar nuestro sistema operativo, aplicaciones e infraestructura en la nube. Con actualizaciones periódicas, mejoramos continuamente el rendimiento y la seguridad para garantizar que nuestro software se mantenga actualizado.

Si tiene alguna pregunta, no dude en ponerse en contacto con el equipo de soporte técnico pertinente.

ID de aviso: KEN-PSA-2024-ED01
CVE: CVE-2024-4021, CVE-2024-4022
Gravedad: Baja
Estado: Resuelto en KeeneticOS 4.3 y versiones posteriores

Keenetic fue notificado con antelación y es plenamente consciente de las vulnerabilidades CVE-2024-4021 y CVE-2024-4022.

Dispositivos potencialmente afectados:
- KN-1010
- KN-1410
- KN-1711
- KN-1810
- KN-1910

Versiones de firmware afectadas:
Todas las versiones de KeeneticOS hasta la 4.1.2.15 inclusive.

Aclaración de las vulnerabilidades notificadas:
1. CVE-2024-4022 se refiere a una divulgación notificada de información destinada a ser de dominio público. Mostrar el nombre del modelo y la versión del firmware en la interfaz web se hace por diseño y no se considera una vulnerabilidad. El nombre del modelo se muestra explícitamente en la interfaz de usuario, y la versión del firmware puede aproximarse fácilmente debido a las frecuentes actualizaciones, que cambian visiblemente la interfaz.
2. CVE-2024-4021 no permite el acceso remoto, el control ni la filtración de información privada del usuario. En su lugar, permite a un atacante identificar qué componentes de software (por ejemplo, WPA3-E, WireGuard, OpenVPN) están instalados en el router. Es importante destacar que esta vulnerabilidad no indica si estos componentes están activos o habilitados. Tampoco revela si se está proporcionando un servicio específico externamente (por ejemplo, WireGuard podría estar disponible a través del reenvío de puertos en lugar de estar instalado en el propio router). Tras consultar a un investigador de seguridad independiente, Keenetic clasificó esta vulnerabilidad como de divulgación de información de bajo riesgo. Esto significa que no compromete directamente el dispositivo ni la información del usuario.

Gravedad:
La gravedad de la divulgación de información excesiva sobre el dispositivo y el sistema operativo se considera baja.

Solución:
Debido a la naturaleza de bajo riesgo de estas vulnerabilidades, Keenetic abordará estos problemas en la próxima actualización de KeeneticOS. Se incluirá una corrección en la versión 4.3 de KeeneticOS, cuyo lanzamiento está previsto para mediados de 2025. No se requiere una actualización urgente.

ID de aviso: KEN-PSA-2021-WD01
Gravedad: Media
CVE: CVE-2020-24586, CVE-2020-24587, CVE-2020-24588, CVE-2020-26139, CVE-2020-26140, CVE-2020-26146, CVE-2020-26147
Estado: Resuelto en KeeneticOS 3.6.6 y versiones posteriores

Keenetic está al tanto de las vulnerabilidades de seguridad de wifi conocidas como FragAttacks (ataques de fragmentación y agregación). Puede encontrar información detallada en https://www.fragattacks.com.

Se han identificado las siguientes vulnerabilidades:
- CVE-2020-24586
- CVE-2020-24587
- CVE-2020-24588
- CVE-2020-26139
- CVE-2020-26140
- CVE-2020-26146
- CVE-2020-26147

Dispositivos potencialmente afectados:
Todos los modelos de Keenetic con el índice «KN», lanzados a partir de 2017.

Versiones de firmware afectadas:
Todas las versiones de KeeneticOS hasta la 3.6.5 inclusive.

Gravedad:
La gravedad de FragAttacks se considera media, con un amplio impacto en casi todos los dispositivos wifi desde 1997. Las vulnerabilidades pueden conducir potencialmente a la divulgación de información y a la escalada de privilegios. Sin embargo, su explotación no es sencilla y requiere que el atacante se encuentre muy cerca físicamente del dispositivo objetivo.

Solución:
La versión 3.6.6 de KeeneticOS incluye las correcciones necesarias para solucionar estas vulnerabilidades de wifi. Esta actualización se aplica a todos los modelos de Keenetic afectados. Recomendamos encarecidamente a los usuarios que actualicen sus dispositivos a la última versión de KeeneticOS disponible en línea. Keenetic ya ha comenzado a desplegar actualizaciones automáticas en los dispositivos que tienen activada la opción de actualización automática.