It is recommended to upgrade publicly available instances of Wavelog 2.1.1 and earlier versions to the latest version.

BI1XJT

Wavelog 2.1.1 及更旧版本存在 DOS 攻击向量，建议使用这些版本的公开实例尽快升级到 Wavelog 2.1.2 或更高版本。

漏洞 POC 的测试结果为，只要可以访问目标网页就可触发。对应 2C 4G 的服务器，单攻击主机可以使服务器崩溃。对于 20C 的服务器，单攻击主机可以使网页无法工作。

我已与 Wavelog 团队商定在一周后（新版本发布两周后）公开披露有关此漏洞的细节。

CQCQCQ

Isn't PHP a great programming language?😅

BG5EQA

I'm using a Docker version, and I also need to connect to my home NAS via VPN when I use it myself.

BG5EGC

2.1.2: Updated immediately after release😃

BI7ALG

I keep repeating the same entries. What's the reason?

BI1XJT

BI7ALG The save button does not have any debouncing; consecutive clicks will result in multiple saves.

ZYT

BI1XJT Abstraction: None of this should be used for debouncing.

BD3QCY

Upgraded

BG5EQA

Upgraded.

BI1XJT

ZYT When I have some free time, I'll try to submit a pull request.

BI1XJT

BI1XJT @ZYT The fix PR has already been submitted:https://github.com/wavelog/wavelog/pull/2433

Initially, when debugging, I found that the QSO saving process actually had some anti-jittering functionality. However, my memory also recalls instances where consecutive contacts resulted in duplicate QSOs… This suggests that OM @BI7ALG The issue of not using Wavelog to record match logs only exists on the competition log recording page currently.😂

BG5VLI

👍
I'm not sure if Cloudlog has this issue, but I've been using it.

BD3PSX

Mysterious 20C server

BI1XJT

The issue lies with the APIs related to data updates. These APIs lack proper locking mechanisms, which leads to denial-of-service (DoS) attacks when they are accessed repeatedly and frequently.

Due to the slow download speeds of servers in China when connecting to lotw and dxcc, I/O blocking can exacerbate the attack's effectiveness.

BG5EQA

I'm having trouble with the JTDX-UniTrak after connecting to Gridtracker2. It seems that the logs are being synchronized to wavelog, but I'm not sure what the problem is. Specifically, if the frequency is off by even a small amount (e.g., 14.074 becomes 14.07576), it causes a slight error in the LOTW upload. Currently, I have to manually correct the values and then resynchronize LOTW. Previously, when I made a mistake, there was no way to fix it.

BG5ATV

BG5EQA 14.07576 is your actual transmit frequency. Is your transmit frequency on JTDX set to 1760 Hz?

BG5EGC

BG5EQA The upload to LOTW worked fine, and it's possible to perform normal matching and confirmation.

BG5EQA

BG5ATV Oh, JDTX transmitting at xxx Hertz – are you saying that this causes inaccuracies?

闽ICP备2021006864号-7

闽公网安备35020602002794号互联网举报中心

用户协议隐私政策社区规范积分规则中继规则转载须知
更新日志联系我们常见问题友情链接运营报告赞助

浩奇科技（厦门）有限公司

是无线电，把我们联系在一起